-
### Bug Description
When requesting a IDL-crossing bbox the result is wrong, the inverted bbox is queried (doing some sorting magic on the bbox parameters internally?).
### General Information
…
-
Based on the advice given in https://wiki.openstreetmap.org/w/images/8/88/GDPR_Position_Paper.pdf ohsome limits its functionality by removing the UID from all data extraction endpoints and not exposin…
-
### Bug Description
The way the CSV output is configured differs between endpoints.
Sometimes fields are quoted with double-quotes (/elements/count) and s.t. not (/elements/count/groupBy/boundary)
…
-
### Bug Description
The area filter (and possibly the length filter) will compute the area of geometries only within the given area of interest. This is the case even if `clipGeometry=false`. This is…
-
### Use Case Description
Too large bpolys can overcharge the ohsome api depending on its settings (e.g. with a 3MB geojson of 900 polygons with an avg of 109 vertices). Sending this request will (aft…
-
Current proposal:
- have a folder where geojsons can be dropped (./data/geojson)
- query to ohsome api for data, then drop important stats for plots as json (e.g.{"progress_data":{"x_value":"y_val…
-
contributions could be counted more than once with the current implementation of the `/stats` endpoint when the wildcard `*` filter is used.
When using the wildcard filter we could first group val…
-
During the execution of the comand `ohsome2label --config config\config.yaml image` with the following file `config.ymal`:
```yml
project:
name: TestSentinel
workspace: ./Sentinel_result
…
-
JSON is a widely used format that can be processed in many applications. Accepting JSON as input would increase the usability of the API.
For example https://github.com/GIScience/ohsome-py is loggi…
-
This continues with the original idea about the /contributions endpoint defined in https://github.com/GIScience/ohsome-api/issues/23.
- [x] needs https://github.com/GIScience/ohsome-api/issues/117 …