oshdb
oshdb copied to clipboard
GIScience
OpenStreetMap History Data Analysis Framework
### Problem Description The geometry filter "other" is not well defined (at least not in the docu of the ohsome-api). It remains unclear what it contains, apart from geometry-collections. ###...
### Bug Description The oshdb-filter will only check if the *whole* element adheres to the geometry-filter. If it is a geometry collection that contains the requested geometry the object will...
### Problem Description Linestring vs Line has been addressed multiple times. Accepting both values for our geometry filter would help me. ### Expected Solution Accept both "line" or "linestring".
New way to generate contributions of an OSHEntity by scanning down from latest timestamp to newest timestamp. ### Checklist - [ ] My code follows the [code-style](https://github.com/GIScience/oshdb/blob/master/CONTRIBUTING.md) rules, and I...
**Note:** This may need further investigation if the observed performance issue is actually due to large objects. Currently this is an assumption. ### Problem Description When analysing the contributions certain...
More advanced geometry-aware filters would be possible and perhaps useful to implement. Some examples: * quantitative geometry filters * [x] `length` & `area` (already implemented) * [ ] `perimeter` →...
### Description Adds the following new filters: * `perimeter` – select polygons based on the length of their boundary * `geometry.vertices` – selects geometries by their number of points (note:...
### Problem Description Sometimes one desires that polygonal or line features are reduced to a single point before further operations such as counting-by-geometry are performed in order to avoid potentially...
This PR is for working on issue #424. Wrong geometry generation for multipolygon where shells share a common node. ``` lat ^ 4 a--d 3 | | 2 b--c--e 1...