Route cannot be computed Hiking/Walking
Have "route cannot be computed" message popping up quite often while setting up Hiking/Walking Navigation over established hiking routes.
I usually set it up from my current location to some point on map located on the route or in the next settlement.
The same happens while creating a route in the Route planner. See screenshots.
The difference is that in Route planner I can undo last step and try to place a point once more and sometimes it works. But the Navigation just refuses to compute the route even if I add intermediate points.
This happens on both LoMaps and OAM.
One interesting thing I have noticed is that in some problematic places there are few slightly different routes at the same time marking the same path in OSM. Maybe that is the reason.
With best regards.
The same problem 
If you are using BRouter in offline mode, it uses routing data downloaded by the BRouter app. If that data is outdated, the trail you see in LoMap and OAM may not correspond to what BRouter's data says is on the map. Make sure you use the BRouter app to downloaded the latest routing data for the map area you wish to use.
If you are using BRouter in offline mode, it uses routing data downloaded by the BRouter app. If that data is outdated, the trail you see in LoMap and OAM may not correspond to what BRouter's data says is on the map. Make sure you use the BRouter app to downloaded the latest routing data for the map area you wish to use.
I have also tried this in latest beta and in different location on map. Still the same.
İn Route planner sometimes zooming in very close and positioning the next point very precisely on the trail helped in problematic areas. And sometimes it still did not.
But in some other areas pointing even on forest still beautifully created a route on nearby trail. I really hope this is intended behavior because it is very convenient. Especially while planning the route in a moving car.
I have also tried this in latest beta and in different location on map. Still the same.
İn Route planner sometimes zooming in very close and positioning the next point very precisely on the trail helped in problematic areas. And sometimes it still did not.
But in some other areas pointing even on forest still beautifully created a route on nearby trail. I really hope this is intended behavior because it is very convenient. Especially while planning the route in a moving car.
Hello Lux,
if you are using GraphHopper, are you able to simulate same problem on GraphHopper online map here https://graphhopper.com/maps/ ?
If so, you may post this issue directly on GraphHopper support forum https://discuss.graphhopper.com/ , or copy here url from mentioned map page and I'll post this issue there by myself.
Hello Lux,
if you are using GraphHopper, are you able to simulate same problem on GraphHopper online map here https://graphhopper.com/maps/ ?
If so, you may post this issue directly on GraphHopper support forum https://discuss.graphhopper.com/ , or copy here url from mentioned map page and I'll post this issue there by myself.
You are right Taras,
That newer route is incorrect and also was not edited before posting to OSM, so it has those weird portions of GPS jumping when the guy took a break or something. But the KariaYolu marking is right. I am not yet familiar with OSM editing, so if you can remove this newer route somehow and mark the older one as KariaYolu that would be great. The older one is very accurate.
I would also really appreciate İf you can suggest some good resources on OSM editing.
Thank you.
You are right Taras,
That newer route is incorrect and also was not edited before posting to OSM, so it has those weird portions of GPS jumping when the guy took a break or something. But the KariaYolu marking is right. I am not yet familiar with OSM editing, so if you can remove this newer route somehow and mark the older one as KariaYolu that would be great. The older one is very accurate.
I would also really appreciate İf you can suggest some good resources on OSM editing.
Thank you.
Replies have been locked on this page!