GPX Versions 1.1 vs 1.2 for Garmin Visually Explained
-
@John-S-Parry I figured that the recalculation was going to happen and screw up the route. I agree completely with your conclusions including that restarting the route and selecting the closest point as the starting point would have probably put you back on your intended route.
The Garmin has a LOT of gps coordinates in the track that's embedded in the route section of the 1.2 gpx file so it should be able to take you to the closest coordinate to where you are without recalculating the route.
If you test it let us know, and I'll do the same. Thanks a lot for the update!
@Steve-Jarrell I got out again today to run another test of "Up Ahead", but this time without adding/inserting a via stop into the 1.2 route.
For testing, I created a new 1.2 route to simulate a real situation. When I was few miles from my test deviation, I did the "Up Ahead" thing, selecting the via point to route to. This time, I selected "create a new route" instead of modifying my 1.2 route. I pressed "Go", and my new route started guiding me. I got to the new destination without issue. While stopped, I brought my 1.2 route back up, and it immediately presented the starting point radio box. I selected 'Closest Enry Point", and off I went. Long story short, the remaining route continued exactly as originally planned. Success!
I love it! No skipping waypoints or other stuff you have to deal with on the Next app. I'm now confident I can use 1.2 for just about any situation.
-
@Steve-Jarrell I got out again today to run another test of "Up Ahead", but this time without adding/inserting a via stop into the 1.2 route.
For testing, I created a new 1.2 route to simulate a real situation. When I was few miles from my test deviation, I did the "Up Ahead" thing, selecting the via point to route to. This time, I selected "create a new route" instead of modifying my 1.2 route. I pressed "Go", and my new route started guiding me. I got to the new destination without issue. While stopped, I brought my 1.2 route back up, and it immediately presented the starting point radio box. I selected 'Closest Enry Point", and off I went. Long story short, the remaining route continued exactly as originally planned. Success!
I love it! No skipping waypoints or other stuff you have to deal with on the Next app. I'm now confident I can use 1.2 for just about any situation.
@John-S-Parry Awesome!
That makes logical sense (that's not always the case with Garmin)
as the 1.2 gpx route has a LOT of gps coordinate pairs in it so when you selected "Nearest Point" it obviously guided you back to one of those points then you were on your way. That's the way that I was hoping that it worked.Thanks very much for the update!
-
@steve-jarrell that was a huge typo on my part. It was meant to read āand even if you are not using Treadā. I must have been tired. Iām all Zumoād out.
-
@steve-jarrell that was a huge typo on my part. It was meant to read āand even if you are not using Treadā. I must have been tired. Iām all Zumoād out.
@Carl-Lee Been there. Done that. Have the t-shirt!
-
I'd like to add something about recalculation. I haven't played with 'Up Ahead' places by inserting them into my route but on a normal deviation from a 1.2 route with recalculation left on, I've found there is a recalculation but it logically puts you back on your intended route - maybe with a u-turn or merging with it a little further along.
@simon-james-hancock, which Zumo do you have? On the XT2, you can change the colour in Tread or the Zumo but the width is done on the Zumo. And if you are using Tread, the track must be put in a collection that is visible. I've found red on the widest to be very visible on the XT2. If you don't see the track underneath when zoomed in, just zoom out a little and you'll see it. I wouldn't want it any wider as otherwise it would obscure junctions etc.
" I'd like to add something about recalculation. I haven't played with 'Up Ahead' places by inserting them into my route but on a normal deviation from a 1.2 route with recalculation left on, I've found there is a recalculation but it logically puts you back on your intended route - maybe with a u-turn or merging with it a little further along."
This got me thinking about recalculation to get the Zumo to return you to the route. So I had to go out and check.
You're correct that going off route, with recalculation left on, will simply attempt to return you to the route. It does not recalculate the whole route and trash your custom shaping up ahead. I performed conscious off-route deviations at least three separate times, and they all did nothing other than try to return me to the route. A few of the Zumo decisions on returning me were head scratchers, but they worked, and the route continued as normal.
The recalculations that are a NO-NO are actions that modify the route itself. As discussed, that can be through using "Up Ahead" and inserting a new via point as the next stop. Using Search to find a POI and inserting that via point as the next stop is equally disastrous. In short, don't do anything that modifies your route and triggers a recalculation.
From my perspective, using 1.2 GPX files in the Zumo works very well if you understand the behavior.
-
" I'd like to add something about recalculation. I haven't played with 'Up Ahead' places by inserting them into my route but on a normal deviation from a 1.2 route with recalculation left on, I've found there is a recalculation but it logically puts you back on your intended route - maybe with a u-turn or merging with it a little further along."
This got me thinking about recalculation to get the Zumo to return you to the route. So I had to go out and check.
You're correct that going off route, with recalculation left on, will simply attempt to return you to the route. It does not recalculate the whole route and trash your custom shaping up ahead. I performed conscious off-route deviations at least three separate times, and they all did nothing other than try to return me to the route. A few of the Zumo decisions on returning me were head scratchers, but they worked, and the route continued as normal.
The recalculations that are a NO-NO are actions that modify the route itself. As discussed, that can be through using "Up Ahead" and inserting a new via point as the next stop. Using Search to find a POI and inserting that via point as the next stop is equally disastrous. In short, don't do anything that modifies your route and triggers a recalculation.
From my perspective, using 1.2 GPX files in the Zumo works very well if you understand the behavior.
@John-S-Parry "In short, don't do anything that modifies your route and triggers a recalculation."
I think that sums it up perfectly!
I leave auto-recalculation turned off just from habit using so many different versions of the Garmin, and I'd rather just get back on the route by myself, but off-route re-calculation does not seem to trigger the dreaded "ok, you changed the route manually so that gives me (the Garmin) permission to do whatever I want to to your route".
-
Still some more testing to be done I think. Iām wondering if āshapingā the route on the Zumo just by adding some more shaping points (not vias) will damage it. In reality, this is something I would rarely, if ever, do but it would be nice to know.
When I get chanceā¦ā¦And anyway, even leaving auto recalculation off, if youāre struggling to get back on the route (it happens!), stopping it and restarting with CEP is a fine and still wonāt destroy the route.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better š
Register Login
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
-
1113178
-
021312
-
014382
-
08145
-
71075.5k
-
0344
-
1975
-
06290
