temp.gpx question

[Peobody]

When a route is imported from temp.gpx, what is the mechanism the prevents it from being detected as a new route available for import once it has already been imported? Does its data get removed from temp.gpx, or is just some sort of marker that indicates it has already been imported?

[Peobody]

Testing reveals that data is not deleted from temp.gpx upon import nor does it appear that a route in temp.gpx should repeatedly prompt about being available for import once it has been imported. Mine did though, both before and after a recent map update but that prompt hasn't appeared since so I'll attribute it to a fluke and move on.

[jfheath]

Temp.gpx is created when Basecamp sends data to the Zumo internal storage.

When the Zumo restarts after disconnecting the USB cable, I have always assumed that the Zumo has scanned the contents, and that this scan is a one-off. If you do not import any of the data, then I do not think that it alerts you again.

Weird things will happen with temp .gpx.

if you reconnect the usb cable and transfer additional data, the old temp.gpx is deleted and a new one is created. So any data not imported into the Zumo is lost. I believe that this is behaviour from having to use MTP protocol, rather than mass storage. But only because the 590 and 595 never did it, and I always had them set to use Mass Storage mode. Also it seems feasible, because MTP cannot amend or modify existing files.

Waypoints may be imported automatically.
Waypoint may be removed from the temp.gox file after automatic import.
Tracks may be imported automatically.
Tracks may be removed from the temp.gpx file after automatic import.

Some of the above is be true for any gpx file placed in internal storage/gpx. So for me the question about temp.gpx is academic. The Zumo does so much weird stuff with gpx files in general and temp.gpx files in particular that I stopped using Basecamp to transfer data. Instead I use Basecamp to create a gpx file and I place it on the SD card, where the Zumo cannot odify it.

I use the term ‘may’. That is because I cannot remember whether all of the above applies to the XT1. Most certainly applies to the XT2. The query remains about - whether waypoints are removed from the gpx file on either device.

Sorry, I’m passing time in a hotel room. I don’t have my notes or Zumos.

[Peobody]

When the Zumo restarts after disconnecting the USB cable, I have always assumed that the Zumo has scanned the contents, and that this scan is a one-off. If you do not import any of the data, then I do not think that it alerts you again.

This is what I determined after doing some testing.

The Zumo does so much weird stuff with gpx files in general and temp.gpx files in particular that I stopped using Basecamp to transfer data. Instead I use Basecamp to create a gpx file and I place it on the SD card, where the Zumo cannot odify it.

Me too, most of the time. This route was named "Test CEP" so was a route I created solely for testing something with CEP. I thought I had imported, tested, then deleted the route from Trip Planner so was surprised to see the notification about it as a new route available for import, twice. It's moot now. I don't understand the inner working of temp.gpx but have refreshed my brain about how it 'should' work so I'm good until something else happens that makes me second guess what I think I know.