Zumo User Forums

2.11.27 Android and I've just rolled back to 5.40 on my XT2.

I'll guess they've tweaked the algorithms again, pity they can't match the one in the 590 etc

I have just noticed something - an improvement on previous behaviour.

Route Point Names are no longer changing when routes are imported from a GPX files.

XT2 Version 6.10 systems software

Previously - ever since the Zumo 595, Zumo XT1 and until now the XT2 - route points carefully named in Basecamp would randomly have those names altered. In place of my meaningful 05 123 Coffee Stop, I'd have Bryn Teg Place which means nothing to me. In place of the lat/long coordinates, there would be a town, county and/or postcode.

It never happened with points that had been created as Waypoints and used in a route as either Via Points or Shaping Points.
It only happened with via or shaping points which had not been created as waypoints first.
Changes were (apparently) random. I would see it in approximately half of my route points. I never found out why some did and some didn't.

An example of this is shown in the scrollable route on Pic 1 here: app.php/ZXT-P07. I had taken the precaution of creating my Via Points as Waypoints - which were never changed.

I was trying to get some screen shots of this behaviour. I eventually resorted to an old multi-day trip from 2024 where I know that route point names were changed. Checked the route point names, loaded the into the XT2 - internal storage AND SD Card.
I could not make it go wrong.

If this is a genuine observation and not just a lucky strike, then it may mean that someone somewhere is tackling some issues. It's possible that this behaviour changed with v6.10. Am I interested enough to roll back to v5.40 to try it out ? Time will tell.


Nb the above is on an XT2 without Tread installed

-------------------

The attachment is of an altered route captured as a screenshot from my XT2 in Sept 2024 - before v 6.10 came out, showing the changed shaping point names and the charactersitic addition of town and county and/or postcode..

There was also a new version of Tread released a few days ago.
I wonder if they fixed the changing of shaping points.

I'll test properly.

UPDATE:

I'm no longer getting the issue where shaping points are changed during sync.
I can now properly insert gpx1.1's trough Tread.

Could anyone else please test this out.

V6.10 XT2

jfheath wrote: Tue Sep 30, 2025 3:28 pm I was trying to get some screen shots of this behaviour. I eventually resorted to an old multi-day trip from 2024 where I know that route point names were changed.

Hi John. I do hope I'm wrong and I'm definitely not trying to kill your excitement. But if the trip was from 2024 it is very likely calculated with an older CN map than currently on your Zumo. We found some time ago, that would prevent renaming the points.

I did a few tests and a few recalculations. I think I recalculated every time, but I'll check just in case.

Coincidence, but someone on FB reported that the new tread app was no longer changing shaping points. I've asked for some more details, but I'll certainly double check my observation - see if I had my rose tinted glasses on.

Thanks Frank

Ok - Update

I tried the same routes again and added a few from another tour.
And yes - I did recalcuate every route last time. As soon as I started doing it I remembered doing it before.

Result - the original routes produced identical results. All route points were as I had named them.
The new route - well it wasn't 100%. 1 route had four name changes, another had 1 name change. The rest were un-altered.

Not exactly what I thought had happened, but it is still a change - I'd normally expect about half of the points in any route to have been altered - except the waypoints.

jfheath wrote: Tue Sep 30, 2025 10:58 pm And yes - I did recalcuate every route last time. As soon as I started doing it I remembered doing it before.

Recalculating (in BaseCamp) with another Map, or Map version, causes resetting the subclasses for Via and Shaping points to '00fff'. Preventing renaming.
Remember the subclass has the MapSegment number in it, that changes with every CN map update.