New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
highway=cycleway + access=no + bicycle=NULL is used for routing #2980
Comments
See discussion in #870. Maybe @ratrun can comment on this.
|
Access parsing aside, the road isn't tagged properly IMHO. This should be |
Currently we are treating |
And should we remove the special case |
I extended the check there in my first version of the PR, see #2981
Yes that is a good idea. I'll try to extend the PR. |
Broadly speaking, we should do this for all cases where foot access is allowed but biking isn't. |
Have also thought about this like using |
Describe the bug
Cycleways that are tagged as closed with access=no (and no conflicting bicycle=*) are still used for routing, e.g. https://www.openstreetmap.org/way/424854123
Expected behavior
Cycleways with access=no are not used for routing unless there is a bicycle=* or vehicle=* with a positive value
System Information
Tested via openstreetmap.org and graphhopper.com
Screenshots & Logs
https://graphhopper.com/maps/?point=61.459975%2C5.814842&point=61.459033%2C5.827119&profile=bike&layer=Omniscale
https://graphhopper.com/maps/?point=59.911557%2C10.627221&point=59.909744%2C10.625891&profile=bike&layer=Omniscale
The text was updated successfully, but these errors were encountered: