1
TopoFusion Pro / Automerging Garmin .tcx with Laps?
« on: December 10, 2008, 04:20:16 PM »
Hi there,
I use the GOVSS feature to track and plan my running training volume, but there's a large inconvenience in the workflow I use as it stands right now.
I use Garmin trainging center to auto-download and organize my track logs, and export workouts as .tcx to analyze in Topofusion. I also use an autolap feature to get automatic 1 mile laps taken.
Unfortunately, a .tcx with laps taken appears to topofusion as a number of separate tracks within the same file. I can use the merge tool to connect them before analysis, but this is somewhat cumbersome for repeated loops or out-and-backs.
Could there be an option added to the merge tool to automatically merge multiple tracks within one file sorted by time? Or a detection routine that would merge on .tcx import if the files are seperated by only a single sample/few seconds?
Actually, another small annoyance is that the GOVSS analysis doesn't warn you if you're analyzing a file with multiple tracks, and returns info based only on the first track within that file. Took me a while to figure out my GOVSS numbers were only for my first mile of each run! '>
Thanks for any input on this,
Ethan O'Connor
I use the GOVSS feature to track and plan my running training volume, but there's a large inconvenience in the workflow I use as it stands right now.
I use Garmin trainging center to auto-download and organize my track logs, and export workouts as .tcx to analyze in Topofusion. I also use an autolap feature to get automatic 1 mile laps taken.
Unfortunately, a .tcx with laps taken appears to topofusion as a number of separate tracks within the same file. I can use the merge tool to connect them before analysis, but this is somewhat cumbersome for repeated loops or out-and-backs.
Could there be an option added to the merge tool to automatically merge multiple tracks within one file sorted by time? Or a detection routine that would merge on .tcx import if the files are seperated by only a single sample/few seconds?
Actually, another small annoyance is that the GOVSS analysis doesn't warn you if you're analyzing a file with multiple tracks, and returns info based only on the first track within that file. Took me a while to figure out my GOVSS numbers were only for my first mile of each run! '>
Thanks for any input on this,
Ethan O'Connor