-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bicycle and oneway, routing wrong #5557
Comments
OSRM seems to be ignoring bicycle=use_sidepath, routing cyclists over dangerous thoroughfares. The highway=secondary road is tagged with:
Routing over the highway=footway crossing at the bottom is okay if the rider is expected to dismount of course, but this is not reflected in the routing instructions (yet?). |
jdhoek
added a commit
to jdhoek/osrm-backend
that referenced
this issue
Dec 1, 2019
jdhoek
added a commit
to jdhoek/osrm-backend
that referenced
this issue
Dec 1, 2019
6 tasks
jdhoek
added a commit
to jdhoek/osrm-backend
that referenced
this issue
Dec 1, 2019
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Location routing.
At the red circle, de bicycle route against a oneway=yes, this is wrong.
On this road, there is a bicycle=use_sidepath tagged, because of a nearby cycleway and no traffic_sign for bicycle on the road. By law rule, bicycle must use the cycleway, there are exceptions.
My question.
Is oneway routing wrong?
Or the use of bicycle=use_sidepath, then oneway=yes is ignored? ( This is wrong too. )
In the Netherlands, bicycle wider then 75 centimeter can use the roads with use_sidepath, other should use the sidepath (cycleway).
Although the route start at a road with use_sidepath, the oneway=yes should not be ignored.
Edit: I did search and read other related issue.
There was changed a lot over the years in the code.
Because this is a basic issue, I made a new issue.
The text was updated successfully, but these errors were encountered: