Alle: I should read the manual again thoroughly, but perhaps it could be stated a little more clearly what exactly takes place with a .kurviger file import.
It is common to call a .kurviger file a route due to the general use of words. Technically, however, this is not correct and even therefore confusing.
This is not a route but it is a track with many individual track points with already attached correct turn instructions in separate (technical) waypoints and also the used reference Via and Shaping waypoints that are transported in that same .kurviger file.
It is therefore these Via and Shaping Waypoints that you can then also call later on to recalculate a new updated current track with the turn instructions for you in full or in part.
In the meantime, if the routing game rules on your previously planned track have changed, the router will of course generate you another track with different turn instructions in waypoints.
If you import an existing .kurviger file, this polite app will not just recalculate unsolicited on the basis of the Via and Shaping waypoints that are still present.
So you can navigate perfectly out of the box, so to speak, over mountain and valley with that still unaltered original .kurviger track navigation file.
If you manage to schedule it through manual sections and overriding router rules design, you can even navigate perfectly by such a design in places that aren’t even mapped properly.
In a manner of speaking, you can navigate in any desert even without a clear road network or even a map, if someone designs you a nice usable navigation track like that.
The only really (technically) correct name for this file is therefore not a route but a Track navigation file with all (previously) attached turn instructions already nicely attached.
By the way, with import you have the choice of how you show all that information onto the map. The most meaningful, instructive and most powerful selection in my opinion is therefore the third choice: [EN] Overlay + Routing and Unchanged.
You will then still see the original planned track loop, even if you unexpectedly or intentionally trigger a new actual router recalculation.
If you stay alert you so can easily notice that there is a difference from the original track trajectory.
The Web planner, that busybody, however, does not even wait, but immediately recalculates unsolicited, this can be very confusing.