-
The current design choice to prevent accidental exposure of the user-filter provides two default filter mechanisms
```java
.filter(filterString)
```
and
```java
String filterText = …;
…
-
### 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 "linestr…
-
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 a way.
…
-
from https://github.com/GIScience/oshdb/issues/165#issuecomment-487129692:
> I believe it wouldn't be too hard to add a second `aggregateByGeometry` method that not only accepts the map of geometri…
-
### Problem Description
The empty filter `""` indicates that the user wants all (or none?) OSM data. But the filter will not return that due to some reasonable filtering in the ETL like meta-relati…
-
If an area-of-interest polygon is given that touches a (polygonal) OSM feature that is to be returned, it sometimes causes the OSM feature to be missing in the result (see https://github.com/GIScience…
-
**Describe the bug**
The following code can be used to retrieve all modifications of a OSHEntity (FULL history):
```
OSHEntities.getModificationTimestamps(oshentity).stream().parallel()
…
-
Paper: https://www.sciencedirect.com/science/article/pii/S0965997813000379
apparently, this one is significantly faster than other algorithms (maybe incl. JTS's one?) and can better handle special …
-
**Problem**
OSHDB chose slf4j as abstraction-layer with simple-logger as default framework for logging.
Currently the following error-message is displayed when initializing an `OSHDBIgnite`:
```
…
-
The user-name-resolver (https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/libs/username-resolver, formerly tracked in #59) is a first step but users have more information then t…