So the 62s can hold up to 200 tracks, but this seems at the moment to be almost unmanageable in practice.
The first problem, which has been the subject of other posts, is that it's not possible to do a batch 'show on map' - you have to alter each track individually to get it to show up.
But the second issue is to do with the ordering. Can anyone tell me what governs the order in which the tracks are listed in the Track Manager? It's not alphabetical, nor is it governed by the listing in Basecamp prior to import, nor is it geographical proximity like the waypoints. If you have a large number of tracks and want to find a particular one this is a major pain. Any answers anyone please? I feel like I'm missing something very obvious here.:confused:
Edit: Having experimented more in the field I now see that the tracks are listed in some kind of order of proximity to current position, though I'm still not sure which part of the track this is measured from. This makes the problem of not being able to show all the tracks on the map in a batch process a bit less of a problem, since you can just switch on the first few in the list. This is only likely to be a big issue if you have a large number of tracks local to where you are that you want to see on the map.
However, I also found out that there is a limit to the number of tracks that you can show on the map which is less than the maximum number of tracks (200). I managed to switch on 100+, but then reached a limit. But this also seems to be related to track size: by switching off a large track I could show two smaller ones on the map. I wonder why Garmin can't just explain all this in its documentation. It sometimes seems like 50% is in the manual and the rest is Easter eggs.
