Moritz Schott

the code has now been moved from gitlab: https://github.com/GIScience/oshdb/tree/spatialJoin

solved in https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb-benchmarks/commit/c2c0e9743db591d0cc7341dd73933b50d9840f10 Could someone with better ignit-knowledge please verify the .xml: https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb-benchmarks/blob/master/src/main/resources/benchmark-ignite-config.xml @rtroilo @joker234 Import is now rather slow maybe this can be tweaked?

Also H2 is now faster on some benchmarks than ignite: https://reports.ohsome.org/oshdb-benchmarks/0.1-SNAPSHOT_master/123_254b6bf/BenchmarkReports/ignite-benchmark.html https://reports.ohsome.org/oshdb-benchmarks/0.1-SNAPSHOT_master/123_254b6bf/BenchmarkReports/h2-benchmark.html

I think our tools should work seamlessly together with default config. The Ohsome-api handles missing metadata just fine i guess. So in my opinion ETL could also either place a...

When documenting it also has to be mentioned that the ohsome-API only accepts a GeoJSON-geometry, not a Feature or FeatureCollection. I just faced that problem with an extract downloaded from...

It is not possible to move issues between GitLab and GitHub ergo: "Please see multiple comments..." If this is already implemented please merge the feature or close the issue.

so data serialization instead of class serialization? like proposed in #131 and #135 ?

related: https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb/issues/91

closing as nice-to-have. this information is set by the user so it would only be useful in a situation where she does not know, what she is doing

The linked issue requests a string representation of the current settings (state) of a mapreducer-object. if they are not related I think we need more information on what exactly is...