oshdb
oshdb copied to clipboard
GIScience
OpenStreetMap History Data Analysis Framework
see #91 Results are stored here: https://reports.ohsome.org/oshdb/ (see e.g. https://reports.ohsome.org/oshdb/0.5.0-SNAPSHOT_master/204_c11a8e02/infer/bugs.txt) - [ ] oshdb-tool - [ ] oshdb-api
see #91 - [ ] etl - [ ] oshdb - [ ] oshdb-api - [ ] oshdb-util - [ ] oshpbf-parser
see #91 - [ ] etl - [ ] oshdb - [ ] oshdb-api - [ ] oshdb-util - [ ] oshpbf-parser
see #91 - [ ] etl - [ ] oshdb - [ ] oshdb-api - [ ] oshpbf-parser - [ ] oshdb-util
As of now there are 36 JavaDoc warnings recognised by jenkins. Note: Fixing these does not mean we have god javadoc. Nor does it make our javadoc doclint compatible. The...
via option `.oldStyleMultipolygons(true|false)`? how to handle these exactly? see: https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb/issues/54
[TIL](https://github.com/openstreetmap/osm2pgsql/issues/678#issue-203310567) that one also could have used `enclave`/`exclave` as roles on boundary multipolygons. We should add support for them as well when dealing with old data. Btw: on a more...
opened by @franz-benjamin with title **mapReducer.getTimestamps** It would be nice to have `mapReducer.getTimestamps()`, `mapReducer.getAreaOfInterest()`, etc. see https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb/issues/150
opened by @tyrasd Currently, the bounding box will be calculated according to the bounding boxes for all of his nodes(over the complete history). This could lead to big bounding boxes...
For many analysis operations (e.g. calculation of histocounts), the result of a `map` function doesn't depend on the snapshot's `timestamp`. When this is the case, consecutive calls to the `map`...