Max number of waypoints & current.gpx issue

[Peobody]

Help please... Two things.

1. I received a .gpx from a riding buddy. It gets truncated when loaded on the XT. It contains 38 route points (33 alerting, 5 non-alerting). What is the max? Is the fix to change alerting to non-alerting until below the max?

2. Basecamp has started displaying an error about being unable to read current.gpx when I connect my XT. Please let me know what you think might be causing this.

[lkraus]

If the gpx exceeds the limit for via (alerting) points the XT should split it into multiple routes on import. Personally, if it is a single day's ride, I would load it into Basecamp and change most of those vias into shaping points, with vias only at stops. If it is a multiple day route, I'd split it manually into one route per day.

There is some evidence in the file 'GarminDevice.xml' on the XT that the limit is actually 31 via points per route. That file also suggests that the max number of shaping points between any two vias is 198, though I think that most would say the limit is 125. I've never reached either limit and don't have the patience to create a route with nearly 6000 points as a test.

[FrankB]

2. Basecamp has started displaying an error about being unable to read current.gpx when I connect my XT. Please let me know what you think might be causing this.

What you could try.
1) Backup the trips from Internal Storage\.system\trips
2) Delete them from the device.
3) Reboot, Current.gpx should be recreated.
4) if Basecamp has no more problems it was definitely a trip that caused the error.
5) If you want to know which trip, copy them back from the backup. Likely it is a trip that was created around the date Basecamp started to complain.

If it turns out that the trip was created by TripManager, I would be interested. Maybe I should fix something?

[Peobody]

If the gpx exceeds the limit for via (alerting) points the XT should split it into multiple routes on import.

I didn't look for a second route but the one I looked at appeared to end at about the 31st alerting point. I will change a bunch of them to non-alerting and look for a route that contains the last few miles.

If it turns out that the trip was created by TripManager, I would be interested. Maybe I should fix something?

TripManager is a possibility since the problem started after transferring one, maybe two routes. I also now think that I could have disconnected the XT without releasing it in Basecamp first. Tomorrow I will try to identify whether it is a .trip that is causing the problem.

Thanks guys!

[Peobody]

@FrankB, I have identified two .trip files that will cause the Basecamp device read error when either one is on the XT. This afternoon I transferred three route using TripManager and these are two of the three. There size was an indication that something wasn't right but tests removing both, then adding back one, removing it and adding back the other confirmed the either one would cause the problem. I will attach them to a PM for you to take a look at.

My process is:
Export the routes to C:
Use TripManager to transfer route and track to the XT
Compare to identify deviations
Return to Basecamp to fix
Export again
Transfer again
Compare again
Repeat until no deviations

I did not restart TripManager between each cycle. I refreshed the right pane instead. It is possible that I forgot to refresh before a transfer so give thought into what problems that might have caused.