Recalculation of the route does not point to final destination.

[ATLast]

Hi.

I use the app to ride through small routes and thus I choose a destination and let the program guide me.

However, sometimes, I choose not the follow the computed route (road closed, better landscape, etc...) : I noticed that, when I choose not to follow the proposed route, MyRoute recalculates a new one but not to the destination: instead, it wants to send me where I left the planned route for the remaining part of the route.

This is incorrect: in this screenshot taken about 750m from my destination and after riding about ten kilometers against the program's will, it wanted me to drive an additional 17 km.

In this case, knowing the area, I could override the displayed route. But it is not the case when I don't know the region...

The expected behaviour would be : recalculation to the final destination.

PS: By the way, you will notice what seems to me a quality problem of the Here maps as buildings are wrongly displayed over the road. I tried selecting OSM map and the display was correct.

[Axel Härtl]

Hi ATLast,

Under the assumption that you use waypoints: did you set this configuration: "skip waypoints automatically" (see second point on the German screenshot)?

I always monitor the distance to the next waypoint at the right top. If this value increases, then I am obviously moving away from the waypoint. In that case I manually skip that point by klicking on the waypoint. That works.

I admit that I didn't check the behavior of MRA without using waypoints. If you don't use waypoints, you only have two viapoints - the start and the final destination. These points are mandatory to ride to. Probably here is the cause of the observed misconduct.

Best Axel

[Con Hennekens]

@Axel-Härtl, If you choose curvy options, you are in essence generating a track for navigation. When deviating from a track, indeed you are lead back to the track. This non-optimal. I am hoping for a future feature where the track will be picked up from wherever you hit it. But momentarily that is not the case.

[Axel Härtl]

@Con-Hennekens Thanks for the explanation. Now I understand the behaviour of MRA.

Best, Axel