I’m trying to build a route using Directions API, but it seems there is a bug in the routing algorithm. Here is the route.
As you can see, there is a main highway, but for some reason it’s ignored and instead the secondary road is used for the route. I’ve checked OpenStreetMap data for any kind of restrictions, but there are none.
I’m wondering, maybe the turn restriction’s attributes are wrong. It looks correct for me. Both the main highway and the secondary road are available for turn at this point. Why does GraphHopper ignore the main highway in this case?
But are not these lift gates allowed for all to pass? I know for sure that it is possible to pass them at this place. I’m trying to edit the lift gates in OSM editor, but it still doesn’t compute the route correctly.
I’ve marked these lift gates permissions for motor vehicles as yes and destination. But it still doesn’t compute a correct route. Should I just wait for cache updates or something?
Hi! Just FYI it has been updated. One question: does it allow destination access for motor vehicles? For some reason it ignores the minor road and uses the main one, though the minor is the correct one on that route. Any ideas why?
One question: does it allow destination access for motor vehicles?
Yes, we should support this
For some reason it ignores the minor road and uses the main one, though the minor is the correct one on that route. Any ideas why?
You can append debug=true&details=average_speed&instructions=false to the URL on GraphHopper Maps to see which speeds are used and look for suspicious values.