Martin Raifer

to summarize and clarify the bug further: * likely "something" caused a topology exception in JTS; potentially while performing a _intersection_ check * the OSHDB API catches the exception, and...

I believe the following 3 could be removed without (big) history-rewriting troubles, since they were not (yet) merged into master: > c41cd0fa27d3 5,5MiB oshdb-api/src/test/resources/update-test-data.mv.db > c997c5c33936 5,8MiB oshdb-api/src/test/resources/test-update-data.mv.db > 6683c395170b...

Note: _Concurrent_ edits cannot happen in major versions of OSM objects because of the "optimistic locking" mechanism of the OSM API (concurrent uploads will cause a conflict in one of...

> Note: Concurrent edits within the same seconds are possible, but very unlikely, the "optimistic locking" prevent concurrent edits (edits of the same version) but does not prevent multiple edits...

Ah ok, sure. :sweat_smile: As I wrote above, the most likely situation would be in concurrent creations of minor versions of relation geometries. It's definitely a bug that those are...

this is now ready to be reviewed :blush:

> the ohsome API would always need an info about the extract region yeah, but the ohsome API is not the only thing in the world potentially using an OSHDB...

> data.bbox (which is computed from the node locations) […] the ohsome-api could fall back to one of those with a warning. @rtroilo In general, we don't want to fall...

> So in my opinion ETL could also either place a parsable dummy value for `extract.region` if it is not given or omit the information. @SlowMo24 What dummy value should...

related: #225 :pray: