Continuing the discussion from Kurviger 1.13.5 (Beta):
How do this rerouting options behave?
-
Nearest point on route : it’s the nearest coordinates on the route path (not waypoint).
It does guide you back to the route as soon as possible (but does not prevent from skipping waypoints).
This can mean that you are guided to a point you have already been. -
Nearest waypoint : it’s the nearest waypoint (i.e. via points, destination) of the route.
This allows to automatically skip waypoints.
e.g. you can pass a waypoint on a street nearby.
If a waypoint is behind you it won’t route you back. -
Next waypoint : it’s the next waypoint (i.e. via points, destination) that has not been passed yet.
This is somehow a compromise between Nearest waypoint and Strict navigation.
Usually it does not allow to skip waypoints, with one exeption.
If you are on your route, it does not guide you back, even if there are waypoints behind you, that you have not visited yet. -
Strict navigation: It does never allow to skip a waypoint automatically.
It does guide you to every waypoint you have not visited yet, even if that waypoint is already behind you.
If you want to skip a waypoint, you have to do it manually.
Do we need all this options?
There does not seem to be a common consent:
- Some forum members say, the more options the better.
Keep them all! - Some forum members are concerned about the complexity of the app.
Do (novice) users understand the behavior of this options, or would they be confused?
My personal opinion would be to keep only two:
- nearest waypoint: - because this is the most flexible one, and allows seemless skipping of waypoints.
- strict navigation - because this is ensures, that you don’t miss any waypoints.
What do others think.
What rerouting options do you want to keep, and why?