Hello.
I found this problem.
In a cycleway the editor put a point us guidepost.
when the naviky navigator use the data it understand that the the path is not possible to Follow so it look for a way around.
I want to know if there is a bug or there is a mistake in how we guidepost
thanks in anvance
Is the guide post on the way or adjacent to the way?
Can you give a link to the location?
1 Like
it was on the way. I move to and adjaccent just in case that some how matters
coordinates :
41.52068/2.14089
last but not less:
seems to me that some in Germany face the same problem.
but really sorry to say google translate is no very good understanding the conversation so I’m not so sure
Have you tried any other router? E.g. the openstreetmap.org home page offers directions, with a choice of 3 routing engines. If they work OK it would suggest an issue with naviky, whereas if they don’t work it is more likely to be in the data.
At first glance it seems unlikely that a simple guidepost node should affect routing.
OSMR for bike give the same problem.
maybe it is not the point but the way the cycleway is created. cause i move the point just a meter away but the problem persist
It will take several days before the built-in routers update to show any changes.
Indeed, I can see that OSRM behaves very strangely here. But only for Bicycle - the Foot profile routes past this point with no problem. And Graphhopper and Valhalla Bicycle routing shows no problems.
Maybe OSRM really does have an issue with guideposts on a way for cycling, although I don’t know why. If that’s the case then as @Fizzie41 said, you may need to wait a while to see the effect of moving it off the way.
In any case mapping guideposts beside rather than on the way is normal as far as I have seen. It tells you which side of the way to look for the guidepost.
2 Likes