Rafael Troilo

> ~Note that this did not happen in 3.4.14.~ ... note that I just was unlucky reproducing it with 3.4.14 at first... Thank you, to have a look into it!...

data.bbox is the calculated bbox over all coordinate, vs extract.region don't need to be a bbox and is this region which was used to extract from the planet file. But...

In our ignite cluster we haave a special cache called "ohsome". If you want to retrieve the current/newest prefix you can do it like: ``` try (var ignite = Ignition.start("ohsome-heigit.xml"))...

What would be your expected result of ```java .timestamps("2017-01-01", "2019-01-01", Interval.YEARLY) .aggregateByTimestamp() .flatMap(snap -> { if(!snap.getTimestamp().equals(year2018)){ return Collections.singleton(rnd.nextBoolean()? new Agg("A","Y"): new Agg("B","X")); } return Collections.emptyList();} ) .aggregateBy(Agg::level1) .aggregateBy(Agg::level2) .count() ```

in the current version the result would be: ``` 2017-01-01&A&X->0 2017-01-01&A&Y->6 2017-01-01&B&X->7 2017-01-01&B&Y->0 2018-01-01&A&X->0 2018-01-01&A&Y->0 2018-01-01&B&X->0 2018-01-01&B&Y->0 2019-01-01&A&X->0 2019-01-01&A&Y->32 2019-01-01&B&X->24 2019-01-01&B&Y->0 ```

A.) Yes, for the current version this is the right way to create an OSHEntity. ```java long id = osm_id; List versions = ...; List relationNodes = ...; List

A), this is basically the same as the code snippet I show you. buildRecord is a new version in an side branch, but it is the same as build. B)...

Not necessarily, `OSMMember.getEntity() ` could be null and it fact it is null, in the moment of an import. That's the reason for the separate list. But yes, if you...

Hi Peter, thank you for reporting this bug. One question, could you reproduce this bug with the same dataset and oshdb version. Because there should not be a major change...

Hi Peter, thank you for your report. The closed channel exception at the end should no corrupt your generated oshdb. Could you confirm that your generated oshdb does not work?...