gpxstudio.github.io: Not able to route ways when access=private
I might be wrong, but it seems that it is not possible to use the routing feature on ways that are marked in OSM with access=private or possibly other values, but not access=yes or access=permissive
I assume this behavior is a feature rather than a bug, but for my use case I would like to be able to create routes using such ways. Is there a way to do so with the current version ? If not, could this be considered it as a feature request ?
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Comments: 20 (2 by maintainers)
Commits related to this issue
- add setting for routing on private roads, see #285 — committed to gpxstudio/gpxstudio.github.io by vcoppe 3 months ago
I have added a setting to allow routing on private roads. Feedback for each activity type is welcome, since I am not an expert with the routing profiles. I have adapted existing ones in the following commit if you want to check: https://github.com/gpxstudio/brouter/commit/7229bc4c547adccacc2a6001983bcdc9180127a3.
Great, exactly what I asked for.
And it (seemingly) works !
Thx
ok ok, as I am not sure that the developer will take into account the development of such a feature, I wanted to help by a workaround. no need to spam this thread
mapa4, I don’t understand your suggestions, mistertttt wants to add a feature to gpxstudio, not an advice on how to get kind of the same result with less than optimal solutions.
It must be because of my poor English, but if you perfectly understood my request, then I don’t understand your suggestion. I don’t want to “have to follow roads [my]self” (which I have been doing so far). I would rather have gpxstudio automatically follow roads for me. Even private roads. That’s the point.
It could be a checkbox option, like
Allow routing via private propertieswith a default set toNoand the ability for each user to set it toYes. I don’t see the problem with providing this option: routing via private properties is not illegal, entering without authorization is. OSM data isn’t 100% accurate on that topic, and ways that are not tagged as private could be in reality, ultimately it’s the responsibility of the hiker/cyclist on the field to respect (or disrespect) the law.