-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Route found is not optimal. #6853
Comments
You're only reporting route What you're seeing is that for the route you get, So it is definitely not an OSRM bug, it's more related to the weighting decisions inside the routing profile. This is what would need investigating if you think the profile can be improved in some way. Maybe worth looking closely at the debug map around that area. |
I think the main issue here is around what to do when a point is dropped close to an intersection. A few things are confounding each other here:
There are a few ways to address the problem:
|
@jcoupey Thanks for the hint to investigate the weight I found out that there is a I suppose that either of
is causing the penalty. I will look into using Thank you! |
Issue
Abstract:
A route is obviously not optimal with regards to its arrival orientation. A obviously better routing option is not chosen.
Adding an arrival bearing or adding an additional step decreases the duration.
Example
A-B
:262.6s
http://router.project-osrm.org/route/v1/driving/10.92775739,49.90174097;10.90822200,49.89178000A-B-C
:233.7s
http://router.project-osrm.org/route/v1/driving/10.92775739,49.90174097;10.90822200,49.89178000;10.90816281,49.89148290A-B*
:226.2s
http://router.project-osrm.org/route/v1/driving/10.92775739,49.90174097;10.90822200,49.89178000?bearings=;180,30Steps to reproduce
See Links above
Specifications
/
The text was updated successfully, but these errors were encountered: