We are using the Route Optimization API and found a place that it wasn’t able to navigate to. I tried it on GraphHopper Maps and surprisingly it worked. However I noticed that quite confusingly it only works when turn_costs = true.
Turn costs off: https://graphhopper.com/maps/?point=54.622183%2C-3.352203&point=54.563055%2C-3.297787&locale=en-GB&vehicle=car&weighting=fastest&elevation=true&turn_costs=false&use_miles=false&layer=Omniscale
Turn costs on: https://graphhopper.com/maps/?point=54.622183%2C-3.352203&point=54.563055%2C-3.297787&locale=en-GB&vehicle=car&weighting=fastest&elevation=true&turn_costs=true&use_miles=false&layer=Omniscale
I’m not sure if this is a bug or I’m missing something with regards to turn_costs.
Thanks for finding this - something strange is happening here and we will investigate.
The reason does not seem to be a turn restriction but this cattle grid node
https://graphhopper.com/maps/?point=54.622183%2C-3.352203&point=54.573256%2C-3.298988&turn_costs=false
It is a bug introduced recently. You can see the progress of the fix here: https://github.com/graphhopper/graphhopper/issues/2300
We will also roll back to the old version for production in the next minutes. update: done
Thanks for looking into it, and rolling back
We already found and fixed the problem - thanks again for reporting! (We will now roll out the new version in the next days as usual.)
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.