App does recalculate despite recalculation setting being off
-
I have a case where the App recalculates unexpectedly. See pictures attached. In my functional settings the auto recalculate is off and navigate as track is on.
Picture 1 shows the planned route with a viapoint 4 and a shaping point 5 to take me back on the planned route.
Picture 2 shows what the app has come up with after I decided to stay on the main road and ignore the viapoint 4. The app has somehow created the lower blue route which is unexpected because I am on the upper blue route as planned.
Picture 3 shows what happens when I stop and restart the navigation after having passed point 5 (and ignored 4).
-
@Herman-Veldhuizen Okey, this is a hard one.
If I understand correctly, you were ignoring waypoint 4. This being a viapoint. However, you were still "on the route" so yes, then you will indeed be sent back to waypoint 4 as this may not be missed (it's a via).
The lower blue route in picture 2 is the route to ensure you pass waypoint 4
Cause that's the fastest way to waypoint 4. You cannot do a u-turn on your current road.Picture 3, that then makes sense using the above reasoning.
This entire issue can be resolved by me allowing viapoints to be missed (when recalculations disabled). Yet, that would give other results in different scenario's and to be fair that makes less sense as viapoints by design are not allowed to be missed
-
@Corjan-Meijerink Yes I was ignoring the viapoint (4). I was thinking that with the auto recalc off (and skip waypoints automatic) the app would not try to force me to go to that via point. But I understand what you are saying now. For me however it does look strange that a restart of the navigation gives a different result. After the restart it knows it is on the track to the next point (direction taking into account) and ignores the via point 4 and this is what I expected to be the case after having passed the junction to that via point.
Changing the via point into a shaping point I think has negative side effects for me (app not showing proper ETA's to next possible stops). -
@Corjan-Meijerink I think that in the end the question we need to answer is how smart or dynamic should the 'navigate as track' really be? I have no good answer but 'feel' that it should not be smart and only recalculate on user request or confirmation. But people have different opinions.
Another fundamental question is how via points and shaping points should behave. Personally I think that shaping points should be very simple and only play a role in shaping the route which means that when navigating as a track they have no relevance anymore. This puts more responsibility/requirements to the via points which means adding extra attributes to them. I understand that this is a big change.
One unrelated thing that came to my mind is that it maybe could be useful to have audio points. They play no role in navigating but the app would speak the text in the audiopoint when the driver gets close 'enough'.
