-
Notifications
You must be signed in to change notification settings - Fork 7
Issues: GIScience/ohsome-quality-api
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
feat(attribute-completeness): support custom attribute definition via ohsome filter
#840
opened Oct 26, 2024 by
matthiasschaub
Should we improve computation of figures and the result description?
#828
opened Oct 1, 2024 by
mmerdes
Request with currentness and attribute completeness indicators for topic 'Roads' leads to error message
bug
Something isn't working
#825
opened Sep 26, 2024 by
mmerdes
Add integration tests with database connection
tests
Issues with tests
#814
opened Aug 26, 2024 by
matthiasschaub
custom ohsome filters for currentness and mapping saturation
user requirement
#783
opened May 7, 2024 by
Hagellach37
Find out how many queries can be cached
brainstorming
Idea for a potential new feature or adaption that still needs further discussion
#780
opened Apr 17, 2024 by
Gigaszi
building-comparison: provide more information about what the indicator is about and how it works
indicator
#752
opened Nov 30, 2023 by
matthiasschaub
mapping-saturation: weird estimation (or even wrong) for Cyprus
indicator
#747
opened Nov 28, 2023 by
matthiasschaub
Do not use two database library
code quality
Related to our standards for 'good' code
#746
opened Nov 28, 2023 by
matthiasschaub
CA LULC <-> OQAPI Interaction
brainstorming
Idea for a potential new feature or adaption that still needs further discussion
#740
opened Nov 14, 2023 by
SlowMo24
building-comparison: add timestamp of osm and reference dataset to result figure or description
#725
opened Oct 6, 2023 by
matthiasschaub
api: use schemathesis to test API using openAPI spec
api
priority:low
Should be quite a far way down on the agenda
tests
Issues with tests
#711
opened Aug 30, 2023 by
matthiasschaub
api: add useful data of the indicator to the result (New feature or request
priority:low
Should be quite a far way down on the agenda
includeData
)
api
enhancement
#709
opened Aug 28, 2023 by
matthiasschaub
docs: provide information about how an indicator is calculated and what the result value is
brainstorming
Idea for a potential new feature or adaption that still needs further discussion
documentation
Improvements or additions to documentation
indicator
make default/undefined figure look like a figure (add axis)
indicator
priority:low
Should be quite a far way down on the agenda
#701
opened Aug 22, 2023 by
matthiasschaub
api: oqt should define an order in which indicators are selectable
api
priority:low
Should be quite a far way down on the agenda
#610
opened Jun 27, 2023 by
matthiasschaub
api: set default indicator in swagger docs
api
priority:low
Should be quite a far way down on the agenda
#609
opened Jun 27, 2023 by
matthiasschaub
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.