Define which statistics/numbers are needed and define example queries accordingly. We will check to what extend this covers the existing functionality of the OSM stats api. Outline which queries will not be supported.
[x] check if hashtags need to be case sensitive --> #missingmaps and #MissingMaps
[x] do we need to distinguish total map edits further? e.g. into creation, modification and deletion? --> we will distinguish this, but not all these will be displayed in the leader board in the first place.
[x] is there a use case to combine hashtags with AND, e.g. should one use #bloombergand ' #amerinstead of just#amer? --> yes there is a use case for this. accenture uses a global hashtag, e.g.#accenture` and another hashtag for the fiscal year
[x] is there a use case to combine hashtags with OR, e.g. should one filter for #missingmapsorhotosm-project-*?
[x] is a spatial resolution of 1m enough for our statistics, e.g. meter for length, square meters for area? --> we can go with a resolution of 1m and can use integer values
[ ] are there any other wildcard hashtag filters than hotosm-project-%
[ ] check in which situations filtering by country is useful
Define which statistics/numbers are needed and define example queries accordingly. We will check to what extend this covers the existing functionality of the OSM stats api. Outline which queries will not be supported.
#missingmaps
and#MissingMaps
#bloomberg
and ' #amerinstead of just
#amer? --> yes there is a use case for this. accenture uses a global hashtag, e.g.
#accenture` and another hashtag for the fiscal year#missingmaps
orhotosm-project-*
?hotosm-project-%
https://github.com/GIScience/ohsome-contributions-stats/blob/main/notebooks/example_queries.md