Route transfer to XT - how many?

[Peobody]

Are you sure Russ's method won't allow you to do this? When I can find a tuit I'll try it myself.

I'm sure. When in Basecamp, Memory Card > User Data does not show a directory structure. A drag-n-drop of a route to the Memory Card writes to files on the card named Route.gpx and Waypoints.gpx. A subsequent drag-n-drop writes to Route0.gpx and appends to Waypoints.gpx. Then Route1.gpx, Route2.gpx,...

Edit: To expand on this a bit further, when you delete a route from the SD card while in Basecamp, its data is removed from the RouteX.gpx file it was in, but the file remains, even if it no longer contains any route data. I have accumulated 5 of them in my testing. All now show 3KB in size which is the resulting size once all route data has been removed (routes deleted via Basecamp). I don't know if there is a self-cleaning mechanism that eventually removes or reuses these RouteX.gpx files but I did test whether an empty Route.gpx file would be utilized on the next drag-n-drop and it wasn't.

[twowheelstom]

Are you sure Russ's method won't allow you to do this? When I can find a tuit I'll try it myself.

either method will work.
either using Basecamp to install routes/waypoints into Zumo memory or using file copy/paste to an SD Card , both methods work

[rbentnail]

I'll tell you my reasoning, because I want to be able to specifically identify the files on the SD card that are associated with specific routes or trips (for me, "route"=ride done in a single day, "trip"=multi-day route). This allows me to surgically remove files from the SD card that I no longer need. I will export from BaseCamp to my local drive, one route at a time, assigning meaningful filenames as they are saved. I them copy those files to the SD card, using a logical file structure (eg: all local routes will be in a folder named "Local", all files associated with a Colorado trip will be in one named "Colorado"). Once I'm done with that trip I cleanup by deleting any associated routes remaining in Trip Planner and Tracks, and the Colorado folder from card. If I modify a local route, I can easily identify which file I need to replace on the card.

I recognize that this requires extra effort, especially doing the exports one route and track at a time, but that provides the most flexibility and file control. That effort is worth it to me. YMMV.

Ok, I see your reasoning. I'm just not that particular about it. I mean, to me, I have a group of routes named D1 xxx, D2 yyy, etc. There's no reason for me wasting my time "assigning meaningful names", organizing in order in a folder, blahblah. At any given time, on any given trip, they are the only ones named that way on the card. Simple enough for me to find and import when wanted. When I do have a multiday planned route, to see the entire thing, I'll do like you (somewhat ) and name it Ohio or Mobile or Delmarva Lighthouses or whatever. When I get back home, I make sure any changes I made on the road are applied and saved in Base Camp then delete them from the card.

I do do the "export to my local drive one at a time". I do this mostly just to share individual routes with others via DropBox, but two or three times per year I do it to save my routes, etc on an external drive.