Rerouting problem
I understand what you mean, and you are right,... there is quite some misunderstanding around this. I've thought about adding such a feature in the past, but I've not yet decided on it for several reasons.
Implementing this is more difficult than it initially sounds because there is an edge case that needs to be considered. I'll write about this here (1) to structure it for myself, and (2) perhaps you guys have some ideas on how to address these.
In a typical scenario this would work as follows:
Typical scenario
- Imagine you have a normal A to B route with lots of via points (like when you generate a curvy route)
- You deviate from the route -> the route is recalculated to get you to the first unreached via point
- You decide to ignore the recalculated route because you know the way and will join route further ahead -> route is recalculated again.
- You decide to keep ignoring -> route is recalculated a couple of times more.
- Eventually, you join the original route again, "skipping" a few via points. Scenic recognizes you are back on the original route, skips the via points automatically, and navigation continuous normally.
👍
Side Note 1: This is performance-intensive as, from the moment you are not on the original route, Scenic needs to constantly monitor whether you are close to one of the coordinates that make up the original route.
Side Note 2: Sometimes, you don't want to skip a via point. Maybe you are not familiar with the area, and you placed that via point on a road you heard is really nice. Skipping it could skip that entire road segment altogether, making you miss that road unintentionally.
Side Note 3: Scenic already has an auto-skip via point feature that is able to deal with this scenario, without requiring user interaction.
Edge case:
- Imagine you have a round trip. Initially, this is a clean round trip that does not cross itself and does not use the same road twice.
- Now, imagine you deviate from the route somewhere early on in the round trip.
- The route is recalculated, and the recalculated route crosses "the way back" of the round trip. (This is not uncommon, knowing that when you are close to the route start/end, the roads to get to/from the start/end are few and can be close to each other.)
- You follow this recalculated route, and you reach the point where the recalculated stretch crosses the original route
- Now, what should Scenic do? (Realize that from a technical perspective, this looks exactly the same as the typical case described above)
- If handled as the typical case above, Scenic would assume you reached the original route, skip all via points before this point, and continue navigation.
- Basically, Scenic now cut of a huge part of the round trip. It's sending you back again even though you are just a few km/mi into the round trip.
Side note 4: This is a very simple version of the edge case. We might be able to recognize this edge case by knowing it's a round trip and the traveled distance so far. But now consider a normal route with a big loop inside it.
At the arrow, you accidentally take a wrong turn, and Scenic recalculates the red route to get you back to the first unreached via. However you cross the original route while on the red route, and you miss that waterfall because of it.
UPDATE: I suppose you could make the waterfall a Stop, which would solve this scenario. But now imagine this scenario:
Probably you don't want to miss that little loop.
How likely is this to happen? Well... in a mountaines area with few roads probably not very likely. But, in an urban environment with many roads it becomes more likely.
This is why I'm hesitant to implement such a feature, and so far have preferred to leave this decission to the user on a per case basis, by manually skipping waypoints.
