Navigation Option Show "Original Route" Does Not Display Consistently

[Brian McG]

When I load some routes for navigation the display of the "original route" beneath the planned navigation route does not conform closely to the road, it appears to straight line between some unidentifiable points

On other routes it fits very close to the road & can only be seen to deviate a small bit when the navigation app is zoomed in to its maximum setting

All the routes are planned with MRA on the PC & then navigated offline with MRA Navigation.
Some routes may then be edited in the app

Could someone please explain why with some of my routes the display of the "original route" differs?

& while on the subject of the "original route" could the colour be changed from white to a much more contrasting colour?
on a bright sunny day with a washed out garmin map style selected the white "original route" is virtually impossible to see
(yes I know there are other map styles but occasionally for whatever reason my style reverts to the washed out bland garmin default colouring"

[Brian McG]

sometimes the offset from the road for the "original route" (track) can be large

when this happens & zoomed in at a junction the "original route" (track) can sometimes overlay the entire junction so the exit roads from the junction are hidden/obscured by the overlay
This imo is borderline dangerous as instead of concentrating on the dangers of navigating the junction I am busy trying to guess which exit road from the junction the navigation system is telling me I need to take

[JP d]

I had the same problem so I turned off (show original route) from settings.

Which is a shame because it is very useful to have if you decide to go on a detour and then want to get back to the original route at the nearest point. And just as a confirmation that that is the original route you planned.

I'm sure it worked fine last year and belive it was a change or update somewhere that started to cause this issue.

[Adrian Avram]

Had the same problem, turned off the app, deleted cache and restarted app and everything was fine.

[Con Hennekens]

@Brian-McG, I see you are using offline-mode. I suspect you have "Navigate Routes as Tracks" enabled. Tracks work best in online mode, because tracks van only be calculated online. If offline, you get a less optimal track. If offline use is a must for you, you would better disable "Route as Track".

[Brian McG]

@Con-Hennekens nope, not navigating tracks & option is always disabled

I normally navigates routes as you can see from previous post picture - blue line with multiple waypoints

The option to display the "original route" (track) is a great idea/feature, it just needs to work better (& be more visible/greater contrast on the garmin washed out style!)
others seem to be seeing a similar issue so there has to be a cause/reason

[Brian McG]

@Con-Hennekens These statement confused me

because tracks van only be calculated online. If offline, you get a less optimal track.

but they did get me thinking -
I always operate in offline mode, basically airplane mode because my phone, a rugged Blackview BV6200 does not contain a sim card. It is only ever connected to internet via wifi at home or hotels when touring.

So firstly if "tracks can only be calculated online" how is the "original route" (track) being calculated when I am using mra for navigation offline & how is it producing the "original route" (track)s show in my previous posts?
Secondly what does this mean "you get a less optimal track" & why?

So after a bit of playing about I think I may have found something -
If I edit a route in the web planner or via the app website route lab link - when I try to navigate this route offline the "original route" (track) displayed in the navigation will as you say not be ""optimal"

In fact they can be far from it. In the second picture the right turn at the roundabout with the track disappearing off a couple of hundred metres before is the same roundabout shown in my first post which shows very small calculation errors, in this example the track error is huge.

What I have found is that if I take a route that has been created on the web planner & then edit it within the app route planner I get a different & what appears to be optimal "original route" (track)

Yes this is the same round about as in the above posts but with the "original route" (track) completley hidden because it is perfectly matched to the route/road

So my questions are why did you think the "original route" (track) in offline mode would be "less optimal"?
& why is it that when the route is edited in the app planner it appears to calculate the optimal "original route" (track)?

my guess is that there is some tiny difference between the Here online map & the downloaded offline map -
this small difference upsets/causes a glitch in the calculation of the "original route" (track) such that it uses less points (sometimes a lot less points) to calculate the "original route" (track)