Introducing TripManager

[Peobody]

@Peobody I assume you are referring to the "Track (Including Way points)" checkbox in the dialog box that comes up after clicking the "Additional files" button. The generated waypoints are not actually in the track, they are included in the generated .gpx file. A .gpx file can contain any combination of waypoints, routes (made up of route points - via and shaping). and tracks (made up of track points).

This is a valid comment considering I did not provide any context for my route and trip file. I created routes in Basecamp. I then have Basecamp create a track from each route. I then export each route and each track one at a time to a location on C:.
My process has been to copy each one of those files to the SD card on my XT, and then import each using Apps > Trip Planner and Apps > Tracks.
I am now trying to find a benefit to using TripManager to transfer the routes and tracks to internal storage. I haven't yet delved into getting copies of the .gpx files onto the SD card.

I thought that TripManager would create a track from a route, and yes @smfollen, by using the "Track (Including Way points)" checkbox, except I never tried it due to not knowing what "Including Way points" does. Now it sounds like the track must be included in the source .gpx file being transferrred.

@Peobody
Question: If I would make the 'including waypoints' when creating tracks optional, would that help you? I dont think it would be a great deal of work for me.

If the track must be included in the source .gpx file then I don't think I will use the feature. I want route and track .gpx files stored on the SD card as individual files. Importing the tracks from the card is easy enough.

[smfollen]

Now it sounds like the track must be included in the source .gpx file being transferrred

It does not need to be. If the source gpx file contains a calculated route, e.g. from Basecamp, Trip Manager can generate a track from the route. It can also generate Waypoints from the via points in the route.

Trip Manager can write to either the zumo's internal file system or to the sd card. After connecting the zumo, you can navigate its files in the upper left quarter of the Trip Manager's display. Details are in the Users Guide.

In general, separate gpx files can be used to hold routes, tracks and waypoints, or they can be combined into a single file. Its just a matter of personal preference. The "Track (Including Way points)" checkbox currently puts a track generated from a calculated route, and waypoints generated from the route's via points, into the same gpx file. I think Frank is saying he could change it to make including waypoints optional.

I am now thinking that I need to enhance the user guide to clarify all this.

[FrankB]

If the track must be included in the source .gpx file then I don't think I will use the feature.

No. The track must not be included in the source GPX. It is even preferred to not have a track in the GPX if the GPX contains a BC calculated route. TripManager will create a track (on the fly) from the ghost points of the route. The advantage is that you can not forget to (re)create a track from the route in BC in case you have modified the route in BC

I want route and track .gpx files stored on the SD card as individual files.

TripManager does that. It will create a 'Routes_xxxx.gpx' and a 'Tracks_xxxx.gpx' from a GPX called 'xxxx.GPX'.

The only problem as I see now is that TripManager ALWAYS creates Way Points from all Via Points it finds in the routes. There is, until now, no option to disable that.
The next release of TripManager will have the option to disable that.

Frank

P.S.: This is not meant to change your current workflow if you're happy with that.All I want is TripManager to be flexible.

[Peobody]

P.S.: This is not meant to change your current workflow if you're happy with that.All I want is TripManager to be flexible.

I welcome advice on dealing with my biggest stumbling block which is when the calculated route deviates from the Basecamp route. The Shape Route function on the XT is a relatively easy way to fix the deviations but it only fixes the route in internal storage. That's fine when I don't care about having a copy on the SD card or plan to share it for a group ride, but that is rare. Most of the time I must make edits in Basecamp and to verify those edits I do the transfer/calculate/ compare process again to confirm. Sometimes this requires multiple visits back to Baseamp. It feels like TripManager makes the process more difficult although I admit to being a TripManager novice, still working to figure out how to use it efficiently.

[FrankB]

but it only fixes the route in internal storage.

Maybe the TripManager version that I'm working on can help (a bit) with that. That will have the option to Open/Edit the trip file directly on the device, and export it as a GPX to your PC. That GPX can then be imported in BC. The GPX will not have ghost points, so it must be recalculated in BC, but that's the least problem.