How to Navigate Route as a Track?

[Corjan Meijerink]

@Lenny-O no, definitely not

[Con Hennekens]

@Thomas-Neumeyer, that maybe, but you started the navigation module In cannot be changed while navigation is running.

[Con Hennekens]

@Lenny-O, no, it does not. Its a just an extra feature of the existing subscription

[Martin Kjell]

Maybe I'm doing it wrong. But if I deviate from the route (as a track) with some shaping points, it still wants to reroute me back. I was stubborn and after around 10 km it told me it skipped that waypoint. Is it expected behavior. Tomtom for instance just tells me closest way back to the track in case I deviate.

[Con Hennekens]

@Martin-Kjell, Yes that's expected behaviour, if you keep being stubborn and don't follow the suggestion... What you need to do in such a case, is long-press your own chosen point of re-entry. Then it will guide you to there, insead of back to a point you obviously don't want.

[Martin Kjell]

@Con-Hennekens Ok Thanks! But reading the manual states that shaping points will be ingored during "route as a track". And Waypoint (via points) is never ignored. A bit contradictaional to me, or (trying to be humble) I'm probably misinterpreting the instructions. In other words, route as a track does not seem to ignore shaping points.
E.g. I would like to point out a route with say for instance 10 shaping points. But circumstances like weather, change of mind, road work etc. makes me pick another route and needed to ignore shaping point #4. Since Ive passed it I would no longer be interested in that one since it's just a shaping point. But MRA "Route as a track" tries to guide me back and after a few tries gives up. For me, theres no difference from normal route. What am I missing? Eager to learn and understand.

[Con Hennekens]

@Martin-Kjell said:

route as a track does not seem to ignore shaping points.

But it does. Instead of leading you back to a shaping point, it leads you back to the track. Depending on the density of your shaping points and the layout of the roads, the difference can sometimes be not so obvious.

The way you describe sound perfectly logical. Navigation will lead you back to the track, sometimes that can be through a previous route point, but that does not mean it took it into consideration. Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.

[Herman Veldhuizen]

MRA prioritizes points over the track (or route), also if the point is (just) a shaping point and you have specified that you want to use all points. So it sends you back if you missed one, even if you are already back on the track.

Corjan wrote this about the release following 5.1 (and I hope that a solution for the issue above will be found, as it is my biggest issue):

• Rework some internal algorithms such as searching for fuel stations and skipping waypoints

• Generic track navigation improvements

[M. Schrijver]

@Con-Hennekens said:
Since MRA is a scenic navigation app, it tries to have you drive as much of the preplanned route as possible and only skipps parts of it after multiple redirections.

This is inherently wrong. Back on track, is back on track and no sending back to missed shapingpoints. This is very confusing for users.
You are deviating and you're guided back to the track/route. When you're near the route you see the blue routeline on the crossing ahead but it goes in both directions (left and right). The navigation tells you to go right. But why is the blue routeline also going left?
But okay, I turn right and after a mile I reached a shappingpoint. Then the navigation tells me to turn around and go back. So taking the left direction was the right one after all. What was the point to send me back to that point?
Did i miss something, besides a shapping point?
A must see?

A basic principle of a shapping point it shapes the route nothing more and because of that it is allowed to be missed. The navigation should use this principle and not sending me back to a missed shapping point.

[Con Hennekens]

@M.-Schrijver, we are not starting that discussion again.

[Lenny O]

I think at this point there is still no clarity in understanding the process and setting the expectations. Maybe a good detailed write up from the mothership is in order to cover all the questions asked and clarifying misunderstandings.
I navigate route as a track and have had situations where my next way point is North of me, so I should turn left at the intersection, but the Nav sends me to the Right (South) just to do a U-turn a mile down the road (at the SHAPING POINT I MISSED) and then head North to the next way point. That is wrong no matter how you look at it. A Shaping Point should not be forced so hard, right?
Of course I can long press the next way point and get around the issue, or skip the one I missed, but should I have to do that?
Using Navigation should make my life easier, not to be second guessing every instruction it gives me to see if it still makes sense.
Agree / DIsagree?
Thank you!