Rafael Troilo

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 within...

My note where base on the issue description of @SlowMo24 > Concurrent edits (within the same second) to the same OSH-Entity are possible but neglected by the logic choosing only...

@FabiKo117 the problem here is that the extract.region is not an mandatory parameter (`--ploy` or `--bbox`) of the Extract step.

There are 2 more infos in the extract, - header.bbox (which comes from the pbf header itself, not always set!) and - data.bbox (which is computed from the node locations)...

Moving the ownership for the TagTranslator from MapReducer to OSHDBDatabase could solve the problem. Up to now I don't see a case where we need to have the same OSHDBDatabase...

related to #70

Basically using a ConnectionPool (e.g. Hikari) would already solve the problem, as it trys to reconnect if the connection is closed! Also have one connection per thread is also advisable...

what you see here is a feature: 1. `validFrom`: timestamp of the minor edit contribution, it was a geometry change, which "moved" this feature into my area of interest ->...

> Also, is not the combination of "(at)creation" and "@geometryChange" sufficient to know that this feature has just been moved into my bbox. That's true, I guess this this combination...

I also prefer option 1, I think tools like qgis couldn't handle nested properties. > if I'm not mistaken than currently there are none to be found in the OSM...