jfheath wrote: ↑Tue Jan 16, 2024 3:13 pm
A few things
1. The number of points reported in the Basecamp route is weird. The count of Via Points appears to be the number of route points - via and shaping including start and finish. This software was developed afte Mapsource, and seems to have retained som of its features. Mapsource only dealt with Via Points - as they were then. The heading in the route list is also stated as Via Points.
2. The number of points - I haven't got a clue. I know that if you recalculate the route - the first time it changes value.
3. Your route. I am not sure what is going on, but I can find out. First an answer to a question.
If you send data via the Drive App, the file is stored as a separate GPX file on the Internal Storage / GPX folder. But the XT recognises that it has received a file and it will import it. It should then appear in the trip planner app. If it doesn't it is likely that the importing process - which sifts through the contents of the gpx file and finds the routes to import, the Waypoints to store in Favourites, the tracks to put into the track app. In looking at the routes, it also sifts for any Waypoints that have been used and not declared separately. I am guessing that it finds any named route points (vias and shaping), looks at the coordinates and uses its internal database of stored locations and retrieves a name from there - over-writing the name that you gave to the point. (If it doesn't do that exactly, then it does something similar with the same end result.).
When the XT says 'Calculating', for the first few seconds, that it what it is doing. If it takes more like 25-60 seconds, then it is calculating the route. The question that you then have to ask is "Why ?" It shouldn't need to. Possible answers include the map on Basecamp being different from the map on the Zumo, and the Edit->Options->Device Transfer settings in Basecamp are not set appropriately for your Zumo. Untick all options and apply to all devices.
If it fails for some reason in any of the above processes, the route is not made available to Trip Planner - so you have to find out where the fault is in the route.
If you PM me a copy of the gpx file that contains the offending route, a copy of your temp. gpx and current.gpx, then I can look through and let you know what I think has happened. I'll see if I can reporduce the error - if I have the same maps - just checked - yes I do, you're in the UK. Those two files I would need immediately after you have transferred the route from Basecamp. If you transfer more routes having disconnected the USB cable in the meantime, temp.gpx will have been over-written
In case you thin there is anything sensitive in there:
temp.gpx contains all of the files that have been transferred to the Zumo - ready for import.
Current.gpx contains all of the routes, waypoints, tracks (maybe) that are ready to be loaded.
Neither of these files tell me where you have been, when and how fast you were going. That information is in CurrrentTrackLog.gpx and in the Archive folder. I don't want any of these files !!
Either of these could contain the location of your home. This is a publically available forum - which is why I suggest sending it in a private message.
(Assuming that you would trust me with it).
