XT3: delete default profile zumo Motorcycle

[jfheath]

I came to an interesting conclusion. I used the good old (simple) MapSource to plan the route. I saved the route in GPX format in a folder on the disk. Later, I transferred the gpx file to the SD card in the XT3 with a cable. After importing the file into the internal memory, the calculation was very fast and the route and points were exactly where I placed them. Is this just a coincidence or does it work?

Mapsource doesn't create via points or shaping points. It simply creates route points without any reference to the type of route point.
However, when the GPX file is imported into an XT1, it is evident that the route points have been 'looked up' and given new names - some of which include the county code. These were set as Via Points in the XT1. Others - which I inserted after making the route using the insert tool - were not known locations (not known to Mapsource anyway). They simply kept their original name (decided by Mapsource) and they were set as shaping points in the XT1.

So without being told, the XT1 is changing the name of points and deciding which should be via and shaping based in the simple route points from Mapsource.

This confirms something that I never got chance to look into. When I had my 550 I noticed that some points could be ignored when navigating - ie it didn't mind if they were placed slightly off route (ie not carefully enough). Others did mind and insisted that I went back to them.

I later linked these two behaviours with the way that I created the points - some on known locations on the map, others using the insert tool to drag a point onto a road - deliberately avoiding known locations. There seemed to be a correlation.

I never got chance to check it out. My 550 died and they didn't have any replacements, so they sent me a brand new in-the-box 660. That behaved slightly differently too, and I never got to the bottom of that either - although I recorded my observations.

[proofresistant]

Just looking in, and have a question.

If a user is importing a gpx file and the file does not contain a recognised profile name, do you know which profile the XT3 uses as a default ?

It should be the profile currently selected on the device or in the Tread app.
I'm pretty sure about that with the Tread app.

There's a bug in the Tread 2 device, because there it always uses a generated auto profile for imported Routes.

[proofresistant]

I came to an interesting conclusion. I used the good old (simple) MapSource to plan the route. I saved the route in GPX format in a folder on the disk. Later, I transferred the gpx file to the SD card in the XT3 with a cable. After importing the file into the internal memory, the calculation was very fast and the route and points were exactly where I placed them. Is this just a coincidence or does it work?

That’s exactly how it should always work. This has also been observed with other planning software.
However, it has also been observed ometimes that the navigation system shifts the Shaping points slightly, though usually insignificantly.

As long as you don't use the Tread app, which can (and will) shift the shapings significantly.

[proofresistant]

I cant confirm your statements. Meaning I CAN delete, edit ALL profiles, also the default.

You didn’t have a zumo XT2 profile yet, did you?
The zumo XT2 has its own profile; it’s invisible in the zumo XT2. It appears in the Tread app or in the navigation system if it was inherited from another zumo XT2 into a Tread 2, the Tread app, or presumably also into the zumo XT3 also.
May test if you can still find a “zumo motorcycle” profile from my samples, somewhere in the demo profile databases and insert it via SQL (if you like).

[jfheath]

Just looking in, and have a question.

If a user is importing a gpx file and the file does not contain a recognised profile name, do you know which profile the XT3 uses as a default ?

It should be the profile currently selected on the device or in the Tread app.
I'm pretty sure about that with the Tread app.

There's a bug in the Tread 2 device, because there it always uses a generated auto profile for imported Routes.

I suspect not - the 590, 595, XT1 used to use the default routing preference for the device (always faster time), regardless of what the current setting was. It received the route, saw the route calculation mode that was declared in the route and if it didn't recognise the name it would use Faster Time. Never mind, it's not important. Just curious.

This was quite significant on the 590/595 as it had different user settings for when it was in the bike cradle and when it wasn't. And it could get confused between which was which (eg if you set it to car mode/shorter distance when it was in the bike cradle - that is what it would default to.) However, when it loaded a route it looked for the transportation mode/ calculation mode in the route file and if it didn't find anything that it recognised, it defaulted to using Motocycle and Faster time. When the route was ended, the default would be back to what it was before.

I wondered since the XT2 has no alternatives for storing profiles - whether the XT3 did, and if so, which one it defaults to. Its not going to be an issue if you use Tread - that will provide it with a correct profile name. But routes from gpx files will not.

[proofresistant]

It could also be from Explore cloud, I don’t want to rule it out 100%, but I don’t think so, and it doesn’t match the results of countless tests.
But it’s may possible (or nothing is inpossible). edit: I’ve come to believe also that the device profiles are actually stored in the cloud. I decided to see what would happen if I completely reinstalled the Tread app without a Bluetooth connection to the device. And lo and behold, the profiles were there in the Tread app as if by magic—so they must be coming from the cloud.

I had to revise my previous thoughts because I now do believe in the existence of vehicle profiles in the Explore cloud