Weird Routing Behaviour (2)

[Peobody]

@sussamb, I am surprised that this is confusing. There should not be any question about whether skipping a point should cause a change in the remainder of a planned route. It shouldn't. It should delete that point and calculate a route to the closest entry point beyond it, or, less preferable, to the next point. It should not recalculate the entire remainder of the route.

We are talking specifically about pre-planned routes loaded with Trip Planner. The current behavior is understandable if the route is created on the XT though.

[Fxwheels]

Gotcha but of course others may not, by skipping a via point they may wish to go direct to the next viapoint or the end of the route. If I skip a via point that's certainly what I want, I doubt if I'm alone. To do what you want somehow your device would first need to know you want to ride part of the route you planned and which part you want to miss, and so be able to plot a route for you to that point. I'm not sure that's a realistic expectation.

If you skip a via it means you want to go to the next via or the end of the route? Nah, @Peobody explained it correctly above.
In your example, you can cancel the route and restart from a certain via or clicking on the end point (checker flag) will do the same.

[sussamb]

@sussamb, I am surprised that this is confusing. There should not be any question about whether skipping a point should cause a change in the remainder of a planned route. It shouldn't. It should delete that point and calculate a route to the closest entry point beyond it, or, less preferable, to the next point. It should not recalculate the entire remainder of the route.

We are talking specifically about pre-planned routes loaded with Trip Planner. The current behavior is understandable if the route is created on the XT though.

Ah, now I understand. If you skip a viapoint then yes, if there is another viapoint it should take you there and then follow the route. If there isn't another viapoint then imo it should take you to your endpoint.

[Stu]

@sussamb, I am surprised that this is confusing. There should not be any question about whether skipping a point should cause a change in the remainder of a planned route. It shouldn't. It should delete that point and calculate a route to the closest entry point beyond it, or, less preferable, to the next point. It should not recalculate the entire remainder of the route.

We are talking specifically about pre-planned routes loaded with Trip Planner. The current behavior is understandable if the route is created on the XT though.

Sorry but I disagree!

It should recalculate the route to the next point as you are skipping a point you are tell the sat nav you no longer need to go there

Imagine if it was a closed road where your way point or shaping point is how is the sat nav still routing you down the same road going to help?

It's always going to calculate a route based on the settings within it and the algorithm in the background it doesn't know that you may want to still ride that route or whether the road is closed etc all it knows is you want to skip it so it has to recalculate again

This is the reason why I have a fair few points to still force me the way I want to go and not let the sat nav choose for me

[Peobody]

I think that is what I said @Stu. A skip should recalculate only to the next point and then continue following the per-planned route. What we are experiencing though is that when a route created in BaseCamp gets recalculated by the XT following a skip, the emphasis on faster roads can really mess up the remainder of the route. BaseCamp doesn't have that extreme faster road emphasis, and the XT accepts those routes as planne, so for it to change the remainder a specified route whenever a point is skipped doesn't make sense, especially considering that it does so automatically, regardless of what the recalc setting is. Recalc = change, most of the time.

[Stu]

I think that is what I said @Stu. A skip should recalculate only to the next point and then continue following the per-planned route. What we are experiencing though is that when a route created in BaseCamp gets recalculated by the XT following a skip, the emphasis on faster roads can really mess up the remainder of the route. BaseCamp doesn't have that extreme faster road emphasis, and the XT accepts those routes as planne, so for it to change the remainder a specified route whenever a point is skipped doesn't make sense, especially considering that it does so automatically, regardless of what the recalc setting is. Recalc = change, most of the time.

I have never experienced that issue! the XT has always either followed the route I have planned or recalculated it as its been loaded and was different to what I had planned

I always check routes match before I go and if not I add extra waypoints/shaping points when I have skipped one it has always just recalculated to the next point with no issue

[rbentnail]

Gotcha but of course others may not, by skipping a via point they may wish to go direct to the next viapoint or the end of the route. If I skip a via point that's certainly what I want, I doubt if I'm alone. To do what you want somehow your device would first need to know you want to ride part of the route you planned and which part you want to miss, and so be able to plot a route for you to that point. I'm not sure that's a realistic expectation.

Oh yes it is a realistic expectation- to me "skip a point" means "skip that one single point". My 595, with the exact same route, skipping the exact same point, does not alter the remainder of the route. It keeps the route intact based on the rest of the points defining the route. It does often alter the route based on its calculation to the next shaping or via point but from there on, the original route remains unchanged.

The XT does not do that. Skipping ONE SINGLE via point results in all the other shaping and via points being stripped from the route and a recalculation direct to the destination. Most times a quick examination of the route points allows for a reasonable guess for stopping the route, restarting the route and picking a point to reenter the route, all of which would be unnecessary if it skipped a point and did nothing else.

[Peobody]

Skipping ONE SINGLE via point results in all the other shaping and via points being stripped from the route and a recalculation direct to the destination.

I don't experience points being removed. I see the route get changed between the remaining points.

[Fxwheels]

I don't experience points being removed. I see the route get changed between the remaining points.

I place enough shaping points to not leaving Garmin a choice to recalculate between them. But if it does happens, follow the track until rejoin the route. Garmin will keep recalculating until agrees with the track.

[rbentnail]

I've yet to figure out this "follow the track" thing. I simply can't see it on the screen unless I zoom in to about 200 ft and then it's useless.