Martin Raifer

what would you do with the multi-groupBy requests, like [`/groupBy/boundary/groupBy/tag/`](https://docs.ohsome.org/ohsome-api/v1/endpoints.html#post--elements-(aggregation)-groupBy-boundary-groupBy-tag) for example. currently, those look like this: ```json "groupByObject" : [ "Heidelberg", "highway=tertiary" ] ``` Would you name those `groupByObjectIds`...

ok, there are two issues potentially at play here: one is the definition in the OpenAPI "swagger" JSON, and the second is the user interface. Of course when one upgrades...

@SlowMo24 can you provide a (simple :pray: ) API request link which triggers this bug?

Sorry, I somehow overlooked the link to the zip file at first glance. With "simple" I meant a minimal example, reduced to the absolute minimum input data needed to trigger...

I was able to reduce the input data to the following more easily to handle geojson: https://gist.github.com/tyrasd/c9e769288539821d93d3f62eae66d446#file-in_buggybpoly_modified-geojson as one can see [very clearly](https://gist.github.com/tyrasd/c9e769288539821d93d3f62eae66d446#file-in_buggybpoly_modified__with_expected_output_overlayed-geojson), the second polygon in _bpolys_ shares the...

can you please open an issue at the OSHDB repository for this?

> I'm not saying that it is OK that a topology exception triggered by one of the input polygons cause a feature to disappear completely from the output. The code...

> But I'm not quite sure if you are able to use multiple -d (or --data-urlencode) in a cURL request. it does work with the (default) form url-encoded content, but...

> the produced bpolys.geojson can be directly loaded into GIS for analyses Yes, this makes sense :+1: > body.json Maybe a small addition to my previous proposal: ohsome-py could just...

> JSON is a widely used format that can be processed in many applications. This is true. > Accepting JSON as input would increase the usability of the API. Would...