@Peter-Zehentreiter Very valid question.
In the app it seems to depends on:
where you are in the app : In-app route editor, opening page of a route or during navigating.
The global setting 'Navigate route as tracks'.
a:The global setting 'Offline navigation'.
b: The route level toggle 'Use offline/online maps'.
I have observed the following issues/behaviours but it is unclear to me wether these are caused by map issues, app issues or wether they are supposed to be like that.
A) 3a and 3b seem to be related: changing one also changes the other. The fact that the app changes the global setting is a bit confusing. I suggest to make the route level toggle a temporary one.
B) The in-app route editor assumes that you navigate a route as route. It doesn't use 2). So when you navigate a route as track you don't get the same route as in the editor.
C) Closures are sometimes ignored in offline mode (even if they are available in the offline map). Is it an error in the map or in the app? Don't know.
D) Closures are always ignored in the opening page of a route. So what you see in the opening page might not correspond to what you see in the route editor or while navigating.
E) Closures CAN be ignored when navigating a route as track. It has surprised me that the way you navigate a route controls how closures are handled. It also depends on Where you press Navigate : from the opening page of a route or from the in-app route editor. That there is a difference here must be a bug.
