Moritz Schott

For the user it may seem strange that you clip the geometry for a `contributions` or aggregation endpoint. The idea was that we have a _result_ that is what the...

> could you please share the large input geometry and rest of the query parameters, so we can replicate this issue? I updated the issue with a file link. As...

> one last question: is the snippet above the full result you get, or is there more which you omitted? It is the full ohsome-py log output but I have...

The [raw response (see attached file)](https://github.com/GIScience/ohsome-api/files/6575944/outOfMemory.zip) shows that data is transferred for this error just as for a timeout that occurs during transaction. Its just not valid json.

yes, I just wanted to provide a raw response, as requested, as this was not contained in the errorOnLargeBuffer.zip above (masked by oshome-api).

> could maybe related to issue #1 @rtroilo I don't think so because the bug persists if I remove the only overlapping bpoly (way/168019944) > @SlowMo24 can you provide a...

just for clarification: the file contains three curl requests that only differ by their bpoly parameter. Each is run for the two mentioned timestamps. All bpolys contain the geometry of...

thats what I expected :-)

Just to emphasise the severity this bug can have depending on the setup: I **assume** (havn't checked though) it to be accounable for a considerable part of that bar at...

Just FYI: The reason for ohsome-py to log into seperate files is that - the produced bpolys.geojson can be directly loaded into GIS for analyses - the bpolys.geojson may eventually...