Use Case Description
Hiking, bike routes etc. are mapped as route relations. This relation-link is though lost in the ohsome api: neither the relation contains information on its members (which is present in the OSHDB core) nor the members contain information in the relations they are a member of.
In the current case I want to distinguish between road that are potentially and explicitly walkable. E.g. a highway=track is potentially walkable but I suggest that it is 'explicitly walkable' if it is the member of a hiking trail.
My current solution is to request highways and routes separately and then geographically intersect them but that method seems error prone (e.g. rounding errors)
Request Description
- Escalate the relation tags down to its members (that should not be much data and could be hidden behind a feature flag)
- Add a
member of filter parameter to get elements that are part of a relation
Use Case Description
Hiking, bike routes etc. are mapped as route relations. This relation-link is though lost in the ohsome api: neither the relation contains information on its members (which is present in the OSHDB core) nor the members contain information in the relations they are a member of.
In the current case I want to distinguish between road that are potentially and explicitly walkable. E.g. a
highway=trackis potentially walkable but I suggest that it is 'explicitly walkable' if it is the member of a hiking trail.My current solution is to request highways and routes separately and then geographically intersect them but that method seems error prone (e.g. rounding errors)
Request Description
member offilter parameter to get elements that are part of a relation