document.write("

$\"Gravatar\"$ I am starting to get the difference between track, route and workout, but still I wonder how I should manage the data I imported from my Forerunner 405. When importing I get both workouts and routes. The workout data are straightforward, the route data is what puzzles me most. I have a lot of routes there, but as they just come from the GPS device, they don't seem useful for the purpose of generating new routes. For example, as most of my runs start from my home, I have a lot of lines (with an error of about 20m) in my street, splitting every route into tracks seems a bit overkill as, at least the start is generally the same. On the other hand, I am not sure how to hide the routes in order to draw the tracks. Anyway, I'd be glad if you could give some hints on how to convert route data (from workouts) into useful routes and tracks.
Aaike De Wever | 04.05.09 - 6:31 am | #

$\"Gravatar\"$ Hi, there's a tutorial available on how to master track merge, that's what I expect you are looking for:
http://www.trailrunnerx.com/en_t...rack_Merge.html
Berbie | Homepage | 04.05.09 - 6:41 pm | #

$\"Gravatar\"$ So, when I have planned a tour and I want to follow this do I have to export it as a gpx-track or a gpx-route?
Exporting as a route won't bring a path to follow.
Juergen | 08.04.09 - 2:35 am | #

$\"Gravatar\"$ This highly depends on the device you are using. In theory the GPX track would be the preferred one but many GPS devices can't handle them. Just try both and take what's working best for you…
- berbie.
Berbie | Homepage | 08.04.09 - 5:07 pm | #

$\"Gravatar\"$ I too had trouble understanding the differences between Tracks, Routes, Workouts, and what I was actually editing when dragging the track data points around. I read that the app was for creating a network of trails, but it really didn't click for me how it works until I had imported about 4-5 workouts.

I'm using Trails on the iPhone to record the trails I bicycle on. When I first used Trailrunner, I didn't have data for a network of trails, I simply had a single workout that I was eager to explore and play with. The app immediately created a workout, a very large single track, and a route for me. I had some bad GPS readings which I wanted to clean up, so I started clicking in the map and trying to delete them, but I was informed they were in use by a Route. That prompted me to read about what a Route was, but I didn't really understand it even then. Had I found the glossary right away, things may have been different. Up until about 2 imports ago, I still didn't really get how Workouts were considered (that is, they don't show up on the Track editor at all). The second workout I wanted to import, I chose \"import as one track\" instead of merging, because I did not realize my old workout data were safely stored outside the trails network.

As a software developer, may I humbly suggest you sit down with 3-4 of your friends or family who have never used the app. Without giving them any hints whatsoever, have them import one workout to TrailRunner and then watch them try to use the app. Take notes. Then, have them import the \"next day's\" workout, merging the new trails and monitor them again.

You obviously have a unique view into the application because you have seen it grow and change from conception to what it is now.

Thanks for providing this app, I'm very impressed, and am enjoying using it!
Chris | 09.13.09 - 10:39 pm | #

$\"Gravatar\"$ @chris: thanks for your feedback, I rewrote the article above and I hope it is an improvement to what stood there before. But anyway I am still cooking to find the best approach in TrailRunner to make the UI as intuitive as I can.
have fun,
- berbie.
berbie | 09.15.09 - 3:47 pm | #

Commenting by HaloScan

$\"\"$ ");