Screenshot
|
Details
|
Description
|
|---|---|---|
After your workout is completed, connect your ForeRunner/Edge to your Mac and start TrailRunner.
|
||
Open a new Document.
Press the Import from GPS Device toolbar button.
|
||
If you have configured TrailRunner to use Garmin Training Center as the source for the import Button, the following steps will not apply and the Import Routes pane will directly open.
|
||
The Helper Application LoadMyTracks will open.
Select Garmin USB and press the Acquire… Button.
|
||
LoadMyTracks will now ask you where to store the gpx file it will download from the ForeRunner.
In the save pane, select open file with TrailRunner.
Sidenote: GPX is a common file format to store GPS related Information. It‘s like PDF for GPS receivers.
|
||
Back in TrailRunner the left routes pane will change into the Import Routes pane. All workouts loaded from the ForeRunner will appear in the list on the left.
Select the workout you want to import.
|
||
Below are options on how to import the selected tracks.
Merge will eliminate duplicate track paths. Split at lap-points will place way-points at lap-points you set during the workout.
|
||
Below the workout information is displayed. You can directly add a workout entry to the diary. Or you can import the track only, alter it and later add the workout diary entry.
Press the Import button to import the workout and the track.
|
||
After the import is done, the route is inserted into the list of routes on the left. The workout data and the course are shown on the right.
|
||
TrailRunner has automatically loaded background maps for the area of the imported route.
To change background maps to another display type, open Settings in the lower left corner and select other maps.
Please note that not all maps are available for all regions.
|
||
If you have merged your route with existing tracks and way-points of if you have merged with the split at lap-points option your route will show several check-points in the left list.
You can now follow the course of the route by selecting the checkpoints in their order.
|
||
Above the map you see a chart of your workout.
To further analyze the workout, drag a selection over the workout chart to view detailed recordings for the selected range. Use Command +/- to zoom in and out.
|
||
Please note that a route and a workout is not the same thing. This is because you might use one route for several workouts.
After importing a route accompanied by a workout, the tracks of the route will be merged with any existing tracks (if the merge option was chosen). The route itself will be added to the list of routes on the left. The workout information will be displayed in the workout chart above.
|
||
The Diary
|
To store a workout for future reference, add the workout to the diary, either by checking the import option or by adding a new diary entry with Route > Add Entry for Selection.
|
|
The TrailRunner diary holds your personal history of workout data.
You can customize what columns the diary should show.
Also you can view a chart with your Training progress and publish your favorite routes to a .Mac Weblog.
|
||
Managing your Net of Tracks
|
||
Although TrailRunner has methods to automatically merge tracks into your network of tracks, the magic has its limitations.
To manually correct your merge results, use the following techniques.
|
||
As TrailRunner only merges the path of the last imported route into the net of tracks, it‘s a good idea to follow the routes course to check the merge result.
Use the route slider at the bottom of the map to follow the routes path.
|
||
Please note that routes are build of tracks. Several routes can share the same tracks. Depending on the routes course, crossing-points can direct routes into different directions.
In other words: All tracks in a document build a net of tracks. Routes are sequences of tracks inside this net.
|
||
When you merge Tracks, TrailRunner sometimes does not recognize all parts of the track to be identical to existing ones.
The clipping on the left shows a problem where two tracks overlap, resulting in a missing crossing-point.
|
||
To create a new crossing, place a way-point at the crossing. Do this with the way-point tool. Hold the ⌘-key down while you click onto the crossing. This will force a so called „deep-split“.
TrailRunner will split all underlying tracks at this point.
|
||
Please note that whenever you manually merge tracks with any of the operations shown here, TrailRunner will adjust all routes to utilize the resulting track segments.
|
||
Another problem resulting from merges are tracks that are parallel to each other.
You now might want to remove any redundant tracks by selecting the track you want to keep and then using the Remove similar tracks from the context menu.
|
||
After you have merged a track, the edging way-points are no longer needed. Select the way-point and press the backspace key to remove it,
|
||
In case you still have a route selected, use the remove redundant waypoint context menu command to remove way-points that have no name and are no real crossing.
|
||
This will help you clean up the way-point gutter that stays left from merges.
|
||
To relocate a way-point, select the way-point and ⌘-drag it to new location.
|
||
To relocate a point on a track, hold the command key and watch out for the gray track-points on the track.
Then ⌘-click on a track-point to select it and ⌘-drag it to a new location.
|
||
If moving the track-point is not worth it just select and backspace delete it.
|
||
Sometimes, automatic merges leave undead loops behind.
To remove loops select a track-point on the loop and backspace delete the track -point.
Repeat until the loop has no more track-points and collapses.
|
||
In extreme cases you end up with a situation like shown on the left.
The route and possibly many others should go over X to A to B and in reality, the X-B track isn‘t existing and should be removed.
You could manually correct all routes by rerouting them but as X is a false way-point anyway just command drag it onto A.
TrailRunner will ask you if you would like to merge the two way-points. Do so.
|
||
What did happen with the result is that X was merged with A, the track X-A collapsed and the double tracks AB and XB where merged into one.
The good thing about this technique is that all routes are automatically aligned to follow the new path.
|
||
Summary: What you learned here where the most complex parts of TrailRunner. But they help you to keep your network of tracks clean even though GPS devices could be very inaccurate at times.
|
||
Importing tracks from a GPS Device is one approach to build a net of tracks that routes can use.
But the main purpose of TrailRunner is to find new tracks and new variations and to plan routes in advance.
These basic techniques where not described in this tutorial.
|
||
Tip: Read the QuickGuide Tutorial to learn more about basic techniques in TrailRunner.
|
||
For more information, tools and techniques, consult the TrailRunner Help.
|
||
Type keywords into the search field to find help pages to certain topics.
|
||
Use the Index to find help pages available by topic.
|
||