Round trips and navigation

Benjamin Brücker shared this problem 9 days ago
In Progress

When navigating I have a problem with round trips.

At OsmAnd this is not a problem. From the beginning the course is calculated from the start to the end point. Unfortunately not with Locus. So shortly after the start I'm told that I'm only 2 meters away from the finish. Only after I have driven or run several kilometres do I get a realistic indication of the distance to the finish.


I use tracks I have planned with Locus for the navigation.


Is there any way to improve this?

Comments (2)

photo
1

Yes, I had observed this kind of response when navigating pre-planned round trips. Especially when first and the last part of track are the same or very close one another.Then when i start navigating, track and distance is corectly displayed, but after a short time, recalculating start to take place and the track is modified(directly to the finish point) so no good

This is the present logic of routing of Locus ?

photo
1

Good day guys,

not sure if Benjamin has same problem as Marius.

Benjamin, how you start navigation? Directly by a tap on the map on the route and from popup menu choose "Navigation"? App most probably starts navigation along the route from the point you selected. It may be the final destination, which may cause this problem. In case, such similar issue happens, it may be useful "Nearest point" option in the main navigation menu.

In the second case, isn't this expected behavior if you have enabled recalculation (to the point)? You just say the app that if you leave route, you want to recalculate to next valid target point which is the target. So simple solution > disable recalculation.

How behave OsmAnd? Is there option to turn on/off recalculation? And if so, it does not recalculate to the final point if you left route?