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
bicycle=dismount is not evaluated #695
Comments
Thanks that is indeed missing! Regarding your example if access=no and foot=yes is already set GraphHopper should already tell you about getting off the bike. Or do you have a example link? |
Ah, okay this way. Maybe the current implementation would use 'get off the bike' if there is no access=no and just a foot:yes. We need to check this and make it working. |
Yes, I should have given you the way number. The evaluation order in OSM is typically that first access=no forbids everything, then individual permissions are opened case by case. Thus you do not need a long list of *=no tags. |
Just for the records, I just removed a bunch of unnecessary turn restrictions from a newbie a the northern end of the road segment. But it seems the issue is still within the road, if I get the start/stop point narrower only on the affected segment, I get the same results. |
Add support for the vehicle tag for bicycles and foot. Theses changes were triggered by issue graphhopper#695.
Add support for the vehicle tag for bicycles and foot. Theses changes were triggered by issue graphhopper#695.
Add support for the vehicle tag for bicycles and foot. Theses changes were triggered by issue graphhopper#695.
I think that this issue can be closed, it should be solved for a while. |
While graphhopper knows the idea of pushing a bike on
path, footway, pedestrian and steps
, the explicit access tagbicycle=dismount
(used about 40000 times) is not evaluated. If found on any highway, it should create such pushing section.E.g. I have a
highway=secondary
here which is for a long timeaccess=no, foot=yes, bicycle=dismount
.The text was updated successfully, but these errors were encountered: