Why is a re-calculation needed when navigating routes as tracks?
-
The latest release is a big step up, congratulations!
I love navigating routes as tracks, and that's why I sometimes missed my zumo XT, where this worked perfectly with a GPX 1.2 export.
I understand this idea and concept as pre-calculating a route during the planning phase and using it "as is" when it comes to navigation - without a re-calculation!But that seems to be wrong. Here's an example:
The Koman Lake Ferry in Albania is not recognised by HERE, so planning to use this ferry results in a significant deviation. Fortunately, TomTom knows it, and using this routing engine leads to the expected result.
When opening this route in the app, the preview also looks as expected. When starting the navigation, however, a re-calculation starts, throws an error ("route can't be calculated") and ends up with a straight line to link the ferry points while the original route is displayed as a white line.
This is not just a "ferry thing"; other examples work similarly.
Two questions here:
-
Is there a setting to avoid re-calculation at the navigation start?
-
If a re-calculation is always needed, what is the core difference between navigating "routes as routes" and "routes as tracks"? Is it all about handling deviations and re-routing during navigation?
Thanks for clarification.
-
