-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Wrong Steps for Route #5114
Labels
Comments
oxidase
added a commit
that referenced
this issue
Jun 21, 2018
oxidase
added a commit
that referenced
this issue
Jun 21, 2018
6 tasks
TheMarex
pushed a commit
that referenced
this issue
Jun 21, 2018
TheMarex
pushed a commit
that referenced
this issue
Jun 21, 2018
datendelphin
added a commit
to fossgis-routing-server/osrm-backend
that referenced
this issue
Nov 19, 2020
- Changes from 5.18.0: - Optimizations: - CHANGED: Use Grisu2 for serializing floating point numbers. [Project-OSRM#5188](Project-OSRM#5188) - ADDED: Node bindings can return pre-rendered JSON buffer. [Project-OSRM#5189](Project-OSRM#5189) - Profiles: - CHANGED: Bicycle profile now blacklists barriers instead of whitelisting them [Project-OSRM#5076 ](Project-OSRM#5076) - CHANGED: Foot profile now blacklists barriers instead of whitelisting them [Project-OSRM#5077 ](Project-OSRM#5077) - CHANGED: Support maxlength and maxweight in car profile [Project-OSRM#5101](Project-OSRM#5101] - Bugfixes: - FIXED: collapsing of ExitRoundabout instructions [Project-OSRM#5114](Project-OSRM#5114) - Misc: - CHANGED: Support up to 512 named shared memory regions [Project-OSRM#5185](Project-OSRM#5185)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just came over an odd behavior.
Geometry for the route and alternative looks good, but the steps are wrong. Happens on my own instance and on the demo-page:
http://map.project-osrm.org/?z=8¢er=50.159581%2C10.023680&loc=52.120056%2C8.667266&loc=48.115082%2C11.508351&hl=de&alt=0
Reversing the route, the directions are fine.
The text was updated successfully, but these errors were encountered: