oshdb
oshdb copied to clipboard
GIScience
OpenStreetMap History Data Analysis Framework
we have same very old and largely test-data files in our git history which lets our repository grow to the current size of 120mb. files in the history like the...
Our current global keytables approach has many downsides: they are bulky, slow, unintuitive and cause headaches when implementing code that needs to be executed on a distributed system (because contrary...
ZGrid is preferred over XYGrid. This needs to be fully implemented to replace it. See https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb/issues/67 https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb/tree/transitionToNewIndex
opened by @tyrasd Feedback from today's workshop: spatial proximity queries are a very important topic for geographers. An example query would be: calculate all benches that are inside of a...
Extension of #315 which takes different measurement units into account. e.g. `maxspeed >= 50km/h` should match OSM highways with all of these tags: * `maxspeed = 50` * `maxspeed =...
(possible) syntax: `key < value`, `key > value`, … example: `lanes >= 2` to clarify: * [ ] what selector should do if the tag is not present? intuitively, neither...
Possible syntax: `key ~ valueRegEx` or `key ~ /valueRegEx/modifiers` > This issue was originally posted at GIScience/ohsome-api#65 and https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/libs/ohsome-filter/-/issues/11 related: #285
Should it be allowed to let users provide empty lists for example in `id:()` or in `highway in ()`. Normally these don't make much sense, because they just select nothing...
When defining ranges (e.g. id ranges `id: (1..42)` or geometry selector like `length: (123.4 .. )` or `area: (..1000)`), it could improve readability when the parentheses were optional: `id: 1..42`,...