My suggestion would be: Nearest point on route : nearest coordinates on the route path (not waypoint)
Edit: Nearest point on route usually would insert a new WP on the route path.
If the user wants Nearest waypoint then a “skip next waypoint” afterwards would do the job.
Same here, I find this the best option for “Standard” when starting outside of the planned route. But don’t delete Start, this can also be useful depending on the tour… but I would find this more useful as a general setting (if others agree and it is not too much work), because the text size is too smal for motorcycle gloves and old guys like me who need spectacles for reading (not for driving). While driving I find it better to keep things simple. When I start the tour outside of the planned route, the app automatically can find the nearest point on route by default. If I want it differently from Start I can change the setting. At the moment with tiny buttons there are just 2 more possible faulty entries.
IMO ideally there should be no question at all at start of navigation.
If I am somewhere near the route (but not on the route) maybe after a break, I want to be guided back to the route as seamless as possible.
Whether this is “nearest point on route” or “nearest waypoint” isn’t too important. But not both.
Keep the start menu as simple as possible!
Some people seem to expect start as an option as well, so I would offer start and one other option.
nearest point on route
or nearest waypoint
Edit:
Despite the issues dicussed here I still prefer nearest point on route
Edit 2:
Maybe onother option could be “nearest unvisited waypoint”.
So that after a break, you won’t be guided backwards, providet that the route is still in memory.
I think, you have to differentiate between manually placing a waypoint, and doing this by a program i.e. the program that has created the turn instruction.
manually created waypoints are not exactly at the intersection point, and therefore can have strange effects.
when you use "nearest instruction*, this point has been created by the router itself.
So it should be exactly at the correct place, the router would expect it?
Well, at least if you use the same router and routing graph that has created the original route.
This might be not true for offline routing with different routing engine.
Setting new waypoints on each rerouting request is never future-proof, so “Nearest route point” can never be safe either at start (discussed here) or during navigation and removing it seems the most sane choice everywhere, falling back to:
Probably the easiest way.
The beauty of “nearest waypoint” is, that users would understand what is happening, and probably don’t complain - even if they might not like the result.
My concern is the following situation:
At a break along the route, I would stop navigation and maybe even close the app.
My position may be 100m away from route.
Then when I start navigation again, app may route back to a waypoint I have already visited, because the history of visited waypoints has been lost then.
The “nearest waypoint” may be many km back.
Let’s not move away from the discussion’s purpose, what are the most useful start options.
When be away from route, navigation always asks for rerouting, it’s fundamental workflow.
When be near the route, can cancel rerouting at start, resume route & continue navigation.
There is no need to do reroutings for small stops / deviations & risk serious route changes.
Do you mean that disable should be replaced by resume?
Navigation would then pause automatic rerouting, until I am back on the route for the first time.
And then continue with automatic rerouting
I replaced it with “Cancel” so that can skip that rerouting action, resume navigation on your own and automatic rerouting continues from there. So workflow can be more flexible based on user preference.
I did some testing with Kurviger 1.13.6 (Beta) around my home base, to simulate this situation:
The “flexible version” (nearest waypoint) behaves very nicely.
If 100m away from route, hit cancel and navigation continues as soon as you are back on your route.
The “strict navigation” works if you start navigation where you paused the route.
It is a bit tricky if you start navigation 100m away from route.
Would it be possible to add a “resume” button (maybe additionally to cancel) as proposed above
Edit:
Maybe this scenario isn’t too realistic.
I think in most cases, you would start navigation at the exact place where you left your bike.
What do others think?
Edit 2:
I think, I had such situations in the past e.g. at a gas station:
stop navigation at the gas pump
after filling up move the bike a few meters without navigation. e.g. to get some eating.
More buttons usually are not nice, they complicate UI and implementation.
Can always stop navigation and restart it anytime later.
Now can cancel rerouting at start & so “resume” route.
So resume already exists in some way, only strict navigation has its own rules.
It’s difficult to bend them & want making it flexible again, defeating its purpose.