#Lux.kurviger (40.7 KB)
unfortunately the rerouting option didn’t completely fix the deletion of waypoints
the setting for rerouting is “next unvisited waypoint” and the plan was to never delete waypoint which have not been visited unless waypoints are skipped manually for example. I had the automatic re-calculation active.
The problem seems to appear when round trip roads are crossing somewhere. I upload this route. We made this trip on sunday. You see that there is a problem between waypoint 32 and 33. Why kurviger doesn’t use the “route to Haller” to get from 32 to 33?
But this was not the big issue: the deletion of unvisited waypoints appeared between waypoint 7 and 8 in Beaufort. Instead of heading from 7 to 8 it routed from 7 to 33. Obviously the software “thought” we were on the return path, deleted all unvisited waypoints from 8 till 32 and calculated the way back. Even when I imported the route from new via the menu, it directly deleted again all the waypoints from 8 to 32 and “wanted” to take the way back.
The function option “next unvisited waypoint” doesn’t work like explained. The purpose was to make sure that new route’s waypoints remain unchanged during rerouting.
The function maybe works in the way “next unvisited waypoint” from actual GPS position, but this was not meant here.
The problem seems to be when the forward run crosses the way back on round trips. Hope I have explained it right. Can you fix it please?
I have asked the question here:
Can you please explain the exact difference between rerouting options?
- Nearest point on route : it’s the nearest coordinates on the route path (not waypoint).
- Nearest waypoint : it’s the nearest waypoint (i.e. via points, destination) of the route.
- Next unvisited waypoint : it’s the next waypoint (i.e. via points, destination) that has not been passed yet. Thus making sure that new route’s waypoints remain unchanged during rerouting.