But what about my suggestion to display both the route and the track in the in-app editor when I have have route as track enabled? We see both when navigating so I assume it is technically possible.

pure track navigation is no option for me. the ETA info to waypoints is the most important feature for me.

When you edit a track in the in-app planner, the traffic info is already there, and what I see when I start navigating is exactly as it was in the editor. The only change is there when you did NOT load it in the editor, and in that case you will not notice a change because you did not open it in the editor.

You say that you don't change anything, but actually by opening a route it get's recalculated. That has always been that way and will always be. That's in this case where the change happens, and a new track is calculated. In the end it is still a route, not a track.

I very much agree that tracks are chosen for stability. For that reason I am all for a feature that converts a route to a track (without export/re-import), so people actually navigate a track instead of a "route as track".

I guess it makes sense for those who know the internals of the app. I struggle to see that it makes sense for an average user.

Yes I can imagine that, but that's why we are trying to help out

You must agree with me that when I spent an hour or so in the inapp editor to make or check the route that I expect the route to look the same when I press navigate directly after (from the opening page of the route). Currently this isn't the case when navigating a route (with closures) as track.

I believe that people choose route-as-track because they like the stability of the track. In one way this is now the opposite. The stability is there during navigation but not in the time period between planning the route and riding.

In the end it boils down to this: when should the track be created? I sort of feel that it should be created when the route is created/edited and saved. Of coarse when roads change or close/reopen this track becomes out of date. This I understand and I would accept that I would have to revisit the route with a newer map to get an up to date track.

If I had a way to see the track in the in-app editor I would be happy too (i think) because then at least I can see where the app will take me when riding. As far as I know this isnt possible now.

View 'maasland' in MyRoute-app! https://www.myrouteapp.com/route/open/13720793

The images below illustrate the issue.

The first one shows my mini test route in the editor.
The 2nd and 3rd show what I can see during navigation (route as track). Sometimes the 2nd, sometimes the 3rd.

@Atse-Kroes said:

Als ik de knop start indruk van de route dan verschijnt er een popup schermpje met de tekst; 'TomTom route Track navigatie gebruiken'
Wat betekend dit???

Please try to adhere to the language in the opening topic.
The message indicates that the route was planned on the TomTom map, and therefore will be navigated as a track instead of a route.

@Herman-Veldhuizen said:

Could it be that planner and navigation are not using the same user settings?

No, theoretically not, since the avoidance settings in the planner replicate to the app along with the route. There can be differences in map-versions though, and also of course in trafic information.

Yes. The navigation system always uses the Here map. So if you plan a route using a different map, make sure to finalize the route on the Here map and check it.

Ik heb hetzelfde probleem. Ik lees elders dat je beter Here map kunt gebruiken. Ik heb TOTOM map gebruikt. Is het waar dat ik dus beter Here map moet gebruiken voor in de auto met MRA app te reizen?

Groet Atse Kroes