oshdb
oshdb copied to clipboard
GIScience
OpenStreetMap History Data Analysis Framework
In addition to OSM-Data, notes (with a T) are comments on the map by registered or non registered users similar to the fixme-tag. Similar to changesets (#52) they have a...
**Problem** Tagtranslators are not updated automatically if the Keytables are updated. Using the Updater #38 may cause problems on long running TagTranslators. **PossibleSolution** Subscribe TagTranslators to PostGres Notification mechanism. See...
**Problem** In some use-cases the information on deleted objects is valuable. The `OSMEntitySnapshotView` does not provide objects that were deleted but had their last location in the requested area. **Solution**...
Currently the [CellIterator](https://github.com/GIScience/oshdb/blob/master/oshdb-util/src/main/java/org/heigit/bigspatialdata/oshdb/util/celliterator/CellIterator.java#L182) accepts GridOSHEntities as input to perform checks and return a Stream of OSHEntites. This could be split inito seperate methods to allow other functions to use this...
**Desciption** Streaming `OSMContribution`-Objects from an Ignite-Cluster creates runtime exception. **To Reproduce** Steps to reproduce the behavior: 1. Run ``` Stream entityStream = OSMContributionView .on(oshdb) //small example: .timestamps("2009-01-01", "2018-12-31") .areaOfInterest(new OSHDBBoundingBox(-90.7620867,...
**Problem** When instantiating a new `Contribution-` or `SnapshotView` the user by default gets a nearly complete `MapReducer` with default values. But to get the values for these defaults one has...
**Problem** The Stacktrace of a failure in the .map() step is cryptic: ``` Apr 13, 2019 7:53:20 PM org.apache.ignite.logger.java.JavaLogger error SCHWERWIEGEND: Failed to obtain remote job result policy for result...
This article (Neis and Zipf (2012) Analyzing the Contributor Activity of a Volunteered Geographic Information Project — The Case of OpenStreetMap, https://www.mdpi.com/2220-9964/1/2/146) suggests that users might have increased the version...
Benchmark b2 has different checksums for Ignite and H2 (see db-1 postgres server benchmark results). This may point to an error in the code we should investigate.
Storing serialized objects prevents us to do changes afterwards without rebuilding the entire database. see also this comment: https://github.com/GIScience/oshdb/pull/131#issuecomment-472456015 I would like therefor store a generic byte array instead.
