rufasim wrote: ↑Sun Apr 03, 2022 8:48 am
I think I got it. If you don't import the route onto xt, after transferring it from basecamp, you can loose or damage your route. I can delete and transfer and import as many times as I wish and no issues will incur to the route, just as long as I import it after transferring it. Is that correct?
That is correct. But if you like your routes to be available for import when you are out and about (I do), then the routes that were transferred during an earlier USB connection will no longer be available.
Read the bit below, becasue although what Russ described is what appears to be happening, it is not what actually happens.
rbentnail wrote: ↑Sun Apr 03, 2022 10:03 am
That is correct but there is another way. I do not like to leave my routes imported, it's too cluttered for me. I delete them when I don't need them. But many different models of Garmins delete the route COMPLETELY from the device- the nuvi780, the 595 and the XT all do this. If you want to use that same route again, you have to re-transfer it.
No Russ, that is still not correct.
If a route has been imported, the XT will
not delete that route when you transfer new ones.
Suppose you do this:
Transfer Routes 1, 2, 3, 4, 5.
You then transfer routes 6, 7, 8, 9, 10.
You then disconnect the cable and use the XT screen.
You then go to import the routes. All of the routes are available to import. ie 1-10.
But you choose to import routes 2, 4, 6, 8, 10
Now when you got to choose a route in trip planner there are 5 of them available. The evn numbered ones.
If you take a look at import all 10 of them are available to import. (You can import the same route twice - you get two copies of it in the XT).
Now you reconnect the USB cable to Basecamp because you forgot to transfer route 11-15.
So you begin transfer of routes 11, 12, 13, 14, 15.
You disconnect the cable and go to import the routes that you have transferred. Only routes 11, 12, 13, 14, 15 are available for import. The other transferred files are no longer available. So you import all 5 of those routes.
Now go to Trip Planner, see what routes are available. It will be all of the routes that you have imported.
ie 2, 4, 6, 8, 10, 11, 12, 13, 14, 15.
Routes 1, 3, 5, 7, 9 are not there. But they weren't there in the first place. You didn't import them. You only transferred them.
I agree you have lost them, but they haven't been deleted from the Zumos store of available routes. They have been deleted fromt he set of files that were transferred.
All of the transferred routes from the first two batches ie routes 1-10 are no longer available for import. You had the chance to import them, but chose only to import the even numbered routes.
As soon as you reconnected the USB cable and started to transfer more routes, the previous transfers were deleted. But not the imports.
Technical bit. When you transfer routes from Basecamp, they are stored in a file called temp.gpx on the XT While-ever the USB cable is attached, that file is open and ready to receive more routes. This is a holding location - somewhere to put the routes after transfer. The import process takes copies of the transferred routes and stores them somewhere else. I know not where, but suspect it is in the .System folder. I ahven't been able to find it.
It used to be - with the 660, 590 and 595 that I know of, then when a new transfer process was started, temp.gpx was opened so that new routes could be appended to the bottom of the file.
Not any more. As soon as the file temp.gpx is opened up, it is opened to write. Not to append. So anything that is in it is lost.
That's OK. It makes sense. Why would you want to transfer routes if you had no intention of importing them.
I reckon that Garmin had spotted that temp.gpx never gets deleted on the 590 and 595. It will get massive. And there is no way of clearing it out either on the Zumo or from within Basecamp. I reckon that this would cause all sorts of unforseen errors as the amount of memeory available in the Zumo was gradually eaten away.
Getting rid of temp.gpx was quite difficult. It involved having to dleete it twice and performing a cold restart.
I don't think it is a bug. I think it is deliberate to prevent the other problems. But it actually creates some.
As I said before - either transfer routes to SD card (being aware of the issues that this can create)
Or if you need to add to routes that you have already transferred, when you coonect the USB cable, transfer all of them. So in the example above, the mistake was to just transfer routes 11, 12, 13, 14, 15 after reconnecting the cable.
What would have solved everything is to transfer all 15 routes 1-15.
Then import just the ones you want to be immediately available.
You can then delete routes from the Zumo XT and then import whatever you want from the 15 routes that have been transferred.
Nothing will delete thos imported routes except you using the Zumo Trip planner DELETE option.
Nothing will delete the transferred routes until you reconnect the USB cable and transfer something else. But that will not delete the routes that have been imported.