Skip to content
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

Closed
polarbearing opened this issue Apr 4, 2016 · 6 comments
Closed

bicycle=dismount is not evaluated #695

polarbearing opened this issue Apr 4, 2016 · 6 comments

Comments

@polarbearing
Copy link

While graphhopper knows the idea of pushing a bike on path, footway, pedestrian and steps, the explicit access tag bicycle=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 time access=no, foot=yes, bicycle=dismount.

@karussell
Copy link
Member

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?

@polarbearing
Copy link
Author

See here and switch between bike, car and foot. Maybe the issue is the highway=secondary ? The access evaluation appears to be rather complex.

@karussell
Copy link
Member

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.

@polarbearing
Copy link
Author

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.
Thanks.

@polarbearing
Copy link
Author

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.

ratrun added a commit to ratrun/biketourplanner that referenced this issue Apr 4, 2016
Add support for the vehicle tag for bicycles and foot.
Theses changes were triggered by issue graphhopper#695.
ratrun added a commit to ratrun/biketourplanner that referenced this issue Apr 5, 2016
Add support for the vehicle tag for bicycles and foot.
Theses changes were triggered by issue graphhopper#695.
ratrun added a commit to ratrun/biketourplanner that referenced this issue Apr 8, 2016
Add support for the vehicle tag for bicycles and foot.
Theses changes were triggered by issue graphhopper#695.
@ratrun
Copy link
Contributor

ratrun commented Sep 27, 2016

I think that this issue can be closed, it should be solved for a while.

@karussell karussell added this to the 0.7 milestone Sep 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants