ZUMO XT2 CONCLUSIONS

[FrankB]

I wonder if this little trick would also keep via points from being moved when converted to shaping points on the XT?

That's a good question. But I have little hope. Here's why:

- The trick to not have the route points is performed in Basecamp.
- Via points that are moved after being converted to Shaping, is something that is done by/on the XT.

But you never know until you test it.

[jfheath]

If you set your maps in Basecamp to an older verison and recalculate your route.
Then you set them back to the maps that you intend to use, and recalculate the route.

Then send your route the the 590, 595 or XT - the route point names do not get altered by the Zumo.

It would be extremely useful to know whether or not that same trick works with the XT2.

I wonder if this little trick would also keep via points from being moved when converted to shaping points on the XT?

Odd you should say that Larry - I was wondering the same thing - so I tested it earlier today. Unfortunately not.
Yesterday, I also tested whether it was another way to avoid RUT behaviour. No that didn't work either.

But having a workable fix for RUT behaviour and for the renamed route points - the XT is beginning to look reliable !!

[lkraus]

But having a workable fix for RUT behaviour and for the renamed route points - the XT is beginning to look reliable !!

After only four years and countless volunteer hours of experimentation...

Thanks, Garmin!

[maciekptk]

Hi guys, newbie from Poland here!

I also did some tests and found out that when creating a route in Tread (or XT2) we can use predefined calculation modes between via/shaping points: Faster time, Straight line, Shortest distance, Adventurous level 1-4 (names might be a bit different - I'm using Polish UI).
And I suspect that sync between Tread and XT2 is using simple GPX file with just via/shaping points and chosen calculation modes but the problem is that there is no distinction between Adventurous levels in that GPX file so XT2 doesn't know about different levels between the points. And it recalculates the route using some defaults (from my observation it looks that 'Adventurous' is treated by the device similarly to 'Shortest distance').

Route created in Tread:

route_tread.png (541.73 KiB) Viewed 10 times

Same route in XT2 (synced with Tread):

route_xt2.png (1.35 MiB) Viewed 10 times

GPX exported from Tread:

gpx_tread.png (386.77 KiB) Viewed 10 times

GPX for the same route exported/shared from XT2 (but already modified in the device) - it's huge, contains thousands of points, rather like a track, not a route:

gpx_xt2.png (1.43 MiB) Viewed 10 times

It seems that Garmin needs to define another way of syncing between Tread and XT2 to get similar results in both.