Navigation Option Show "Original Route" Does Not Display Consistently

[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)

[Bouke Ent]

a track is not a orginal route. a track is a list off points in a sequeance. so track is not fixed with a map or road. with online calculation the server connects the points and looks if there is a road or path on the map and tries to follow that. offline is less able to do that and then you get straight lines between the points. because a track has many points it seem it is following the road. for old basecamp users it was the same. if calculation was not done or offroad you also got straight lines between points.

the white line can be 2 things. if you ride a route it can be the original route and it will show if you do recalculation and route takes a new way but it will follow the road. other option it is a route based on track information and then it depends on the calculation off the server or offline in app.

[Marinus van Deudekom]

@Con-Hennekens just got back from an 8days tour in The Eifel. Since réception is por over there I user offline navigation all the t8me. I’ve noticed the the original route under my actual route was mostly bespied the route. Sometimes, mostly while driving hairpins it was way Off. Could using the offline mode be cousinage this

[Corjan Meijerink]

The calculated route is infinitely detailed
Routes stored by us have a certain resolution to not take up way too much space when syncing them. This results in the minor differences so to say.

The original route is a nice indicator of how you planned it so I personally would not be too bothered by it showing these minor divergences (in resolution due to missing coordinates, not actual route).

[Brian McG]

@Corjan-Meijerink sorry the divergences of the "original route" are sometimes not minor, they are major, hundreds of metres, plus the issue is the system is not consistent

if the original route can fit to the road correctly after the route is edited in the app route planner,
why does it not fit correctly when the last edit is done on the web planner?

[Con Hennekens]

@Brian-McG, are you saying that a web-planned route that shows these imperfections does NOT show those imperfections if it got last edited in the in-app planner? That would be interesting...

[Brian McG]

@Con-Hennekens yes that is what I am saying, it would be nice if someone could replicate
I am seeing the error in offline navigation
the route is edited in web planner - then synced to the device
the device is taken offline (airplane mode or wifi/network off)
the route is opened & navigation started with original route displayed

sometimes the web planned route appears ok with small errors as @Corjan-Meijerink expects
other times it can have larger errors & occasionally very huge errors
if I edit the web planned route in the app planner it seems to fit perfectly

I can understand the idea of trying to save storage, reduce data & speed up transfer
if the errors were always small then I would say - not a problem
when the error is large the original track line can obscure whole junctions & makes it difficult to read the map
for me the problem is the original route is not displayed consistently

I don't think a long term solution is to re-edit every route every time it is transferred/synced to the app

oh & don't forget the lack of contrast with a white original track
on the default garmin style map with this bug you can see nothing of the roads

[Con Hennekens]

@Brian-McG, This is a good find. Thanks for your elaborate explanation. I will try to replicate this behavior.

[Brian McG]

Sometimes the errors with the "original track" can be huge,
with the above route the "original route" is wrong by hundreds & hundreds of metres

what causes the wrong calculation of the "original route" in offline mode?

I have also noticed that with a route created in the web planner,
if the navigation is started with a network connection, the "original route" will fit perfectly to the road
the same as when the route is edited in the app planner, you get a perfect fit

I only seem to get the bad fit of the "original route" when I start the navigation in offline mode