Navigate as Track > Use all waypoints?

[Rajp]

What exactly does this setting do? and is it directly related to Navigate routes as tracks or an independent function?.

Can't find any information here: https://support.myrouteapp.com/en/support/solutions/articles/12000098531-app-navigation#Navigation-settings -  

The help is not very useful as it says "Enable it to show all waypoints (rather than only viapoints)" implying it's only a display item that the skip button will show viapoints or shaping points and viapoints.

However, I done some testing, and it seems to do more...

Navigate routes as tracks --> enabled
Use all waypoints --> disabled

1. started route
2. starting viapoint is 0.5 miles away, MRA navigating to start point
3. so far all good, route displayed as planned (screenshot #1)
4. skipped the first viapoint (starting point)
5. route recalculated and is no longer displayed as planned (screenshot #2) --> seems to take fastest route to next viapoint
   Expected Result: route to skip viapoint 1, recalculate using combination of further viapoints and shaping points
   Actual Result: route skipped viapoint 1, recalculated quickest route to the next viapoint, ignoring shaping points from the original route.

Navigate routes as tracks --> enabled
Use all waypoints --> enabled

1. started route
2. starting viapoint is 0.5 miles away, MRA navigating to start point
3. so far all good, route displayed as planned (screenshot #1)
4. skipped the first viapoint (starting point)
5. route recalculated but is still displayed as planned (screenshot #3)
   Expected Result: route to skip viapoint 1, recalculate using combination of further viapoints and shaping points
   Actual Result: as expected, no issues

So is Use all waypoints more than just a display (skip) option, does MRA use this function when recalculating and ignores shaping points when Use all waypoints is disabled??

iOS: 18.4
MRA: 4.3.8 - 386

screenshot #1

screenshot #2

screenshot #3

[Con Hennekens]

@Rajp said in Navigate as Track > Use all waypoints?:

Navigate routes as tracks --> enabled
Use all waypoints --> disabled

Expected Result: route to skip viapoint 1, recalculate using combination of further via points and shaping points
Actual Result: route skipped viapoint 1, recalculated quickest route to the next viapoint, ignoring shaping points from the original route.

This sounds very much like it was designed. You disabled the shaping-points (Use all waypoints --> disabled) so they are not taken into account anymore, and you cannot skip to one of them, obviously if they are disabled. If you want to skip to shaping points, just enable them. If you don't want them, visible, you can long-press the route line at any point where you want to re-enter it. This way you can skip to any point on the route line.

[Rajp]

@Con-Hennekens My query was not about visibility, that's obvious, it's more that the app also uses that setting to recalculate, which is not mentioned in the UI help nor is it explained in the support pages.

Had I not skipped the 1st viapoint, but drifted off course, the recalculation will still route me to the quick path to the next viapoint rather than follow the shaping point routes.

If that's by design, so be it, but at least explain it better than "Enable it to show all waypoints (rather than only viapoints)" which is misleading.

[Herman Veldhuizen]

I have never skipped a point by hand, but if I would do it I would also be surprised if shaping points were not used in a calculation. I think that nobody adds shaping points for so not to be used. The setting effects which points (via points only or both via points and shaping points) get displayed in the info box.

[Con Hennekens]

@Rajp, to me it is not a surprise that shaping points are ignored if you disable them. To be honest I cannot see why that would be different. Shaping points are not really relevant for navigating tracks, because the track is already shaped by the breadcrumbs of the track. Skipping to shaping points you cannot see on the map would be very counter-productive. Some people (myself amongst them) asked for shaping points to be visible, because sometimes they have a meaning. A color to indicate view points for example, or even notes to be spoken. If you want to re-enter the track at some random point, just long-press on that point. Re-entering a track is not limited to the shapingpoints, you know. You can re-enter on any point you like.

[Rajp]

@Con-Hennekens You're missing the point, if use all waypoints is disabled, the track is recalculated if you go of course to get you back on, that's fine, but in doing so, it recalculates to the fastest path to the next via point, instead of sticking to the original track --> see screenshot 2.

[Herman Veldhuizen]

@Rajp I think that I misunderstood you. When you wrote "4. skipped the first viapoint (starting point)" I assumed that you skipped the viapoint by pressing on it at the top right corner. Now I think that you meant that you deviated from the track and didn't visit the first viapoint (shouldn't the app by design navigate you to that very first point ?).
I can understand Con's reasoning. But I see a slight difference in a) skipping a point by clicking on it at the top right and b) by clicking on just any point on the track. In the first case (a) I would expect the app to still honour the (hidden) points in the sequence. In the latter case (b) a new direct route is more what I would expect.

[Rajp]

@Herman-Veldhuizen I tested both.

First time, I skipped viapoint 1 (start), instead of the track remaining as the original it recalculated directly to viapoint 2 ignoring the original track line.

Second time, I passed viapoint 1, and then went off course, again it recalculated directly to viapoint 2 ignoring the original track line.

[Herman Veldhuizen]

@Rajp By skipping I assume that you mean that you drive off before arriving at the first viapoint. By current design the app should navigate you to that point as long as you haven't visited it.
If you visited point 1 and then drove off the app should in my opinion do what you expected : take you back to the track. I might be wrong but by design it takes you to the next via point if you are not using all points. That's why I use all points and have the automatic recalculation disabled.

[Rajp]

@Herman-Veldhuizen no, by skipping I meant I hit the skip button

[Rajp]

“ I might be wrong but by design it takes you to the next via point if you are not using all points. That's why I use all points ”

And that’s my point, if this is by design, the in-app popup explanation should make it clearer and online support should have this behaviour described. As right now it simply implies shaping points are visible on the skip button. Where in fact this option is relied upon for track navigation recalculations as well.

[Con Hennekens]

@Rajp said in Navigate as Track > Use all waypoints?:

by skipping I meant I hit the skip button

Again, if you skip to the first available waypoint, being VIA 14 (because you disabled the shaping points in between) all is logical and by design. You just have to remember to long-press anywhere on the track if you want to re-join there. It would not be logical to have to press the skip button 14 times to skip to the first visible waypoint, would it?

Second time, I passed viapoint 1, and then went off course, again it recalculated directly to viapoint 2 ignoring the original track line.

This I could not read from your earlier posts. If this is for real, you have a valid point. Deviating from the track should lead you back to the track in a sensible way. It should not skip to any VIA point unless it is the first sensible point of re-entry to the track. Maybe @Corjan-Meijerink can say something about this?

@Herman-Veldhuizen said in Navigate as Track > Use all waypoints?:

I would expect the app to still honour the (hidden) points in the sequence.

If you disable "use all waypoints", it is not like your disabled shaping points turn into some hidden waypoints.

[Rajp]

@Con-Hennekens said in Navigate as Track > Use all waypoints?:

Again, if you skip to the first available waypoint, being VIA 14 (because you disabled the shaping points in between) all is logical and by design. You just have to remember to long-press anywhere on the track if you want to re-join there. It would not be logical to have to press the skip button 14 times to skip to the first visible waypoint, would it?

I'm not saying you the need to skip 13 other waypoints. what I'm saying is, the skip button shows skip viapoint 1. I hit skip, the skip button should now show skip viapoint 14 - which it does. My concern is, when I skipped viapoint 1, why does it recalculate to the shortest path to viapoint 14, why not stick to the original track??

And if this is by design, can we get some better explanation in the UI/support pages. To me "Enable it to show all waypoints (rather than only viapoints)" reads that when use all waypoints is disabled, the skip button will only show viapoints (which it does), but the track will still be honoured if you skip a viapoint/deviate off track (which is does not)

[Herman Veldhuizen]

@Rajp I tend to agree here. Most people I think want to drive the track as planned. Hidden shaping points are (should be) used implicitly in the form of the track.
Calculating a whole new route after pressing the skip can be a big change which you might want to check on a map first before committing to it. But I can live with both designs.
In my work I never skip a point by hand. I skip points by deliberately deviating. The apps behaviour on my phone has recently changed related to this. Different issue but might be related.

[Con Hennekens]

@Rajp said in Navigate as Track > Use all waypoints?:

My concern is, when I skipped viapoint 1, why does it recalculate to the shortest path to viapoint 14, why not stick to the original track??

Because you explicitly skip to Via point 14. That's what that option does. If you want to honor the track, long-press at your own point of re-entry. It will guide you fastest way there. This is simply how it works.

Maybe it helps if you look at it this way: skipping by pressing the skip WP button does not skip the previous WP, but it skips TO THE NEXT waypoint.

but the track will still be honoured if you skip a viapoint/deviate off track (which is does not)

Like I said earlier, if this is true you have a valid point. I have been asking questions about this in our test group, but are not able to test this myself currently. It does not align with my earlier experience of the "route as track" feature though.