Problem: I expect that when I import new workouts into the main document, the main document should behave like a journal. But on the other hand there’s the diary where I can enter additional information on workouts. Why are these two separated?
Explanation: Unlike pure journaling applications, TrailRunner has two modes. The route planning mode and the diary mode. These two modes are separated into the main window (with the primary focus on building a network of tracks to plan routes within) and the diary (with the main focus of archiving the raw data of recorded workouts). Even though seperated, TrailRunner still displays workout information for a selected route in the main window (if a related workout can be found in the diary).
Advice: When you import new workouts, make up your mind, if the workout course contains track segments you would like to add to your network of tracks. If so, use one of the merge options. If you (just) want to archive your workout in the diary, check the add diary option.
Tip: Unlike the main document, your diary is stored in a central location on your Mac. As you can have more than just one document, each of your documents could cover a different networks of tracks. For example you would like to have one document for your neighborhood and more for each location you where on holidays.
Additionaly, if you delete a route from the main document, it would not delete any workouts in the diary and vice versa. Both are a separate thing even though they might be related to each other.

Tags: workout, diary, routes, import, merge

Problem: Maps somtimes load very slow. Other applications like Google Earth load the maps much faster.
Reason: TrailRunner loads maps from internet services that provide free maps. If the loading process is slow, the map service is slow and TrailRunner can't get anything faster. Another reason are "fair use" agreements for commercial web services. This means that as long as you get maps in a fair amount and frequency, the commercial service won't put you on a black-list. For that reason TrailRunner throttles the keyhole imagery service.
Solution: TrailRunner caches maps. If you have once loaded map fragments from a service, it's unlikely you will need to load the same fragments again. The longer you use TrailRunner, the faster it will become.
Tip: In case the map material on the web service was updated, as it is frequently the case with openstreetmap.org, you can use the File > Consolidate > Reload background maps command to reload what’s currently visible or you can remove the GeoTiles folder in your Application Support/TrailRunner folder.

Tags: maps, performance, cache

Problem: When I view my workout data in other applications like garmin training center, the data points for heart-rate and speed are much more noisy detailed than in TrailRunner. Additionally the TrailRunner graph seems not to start at the left edge of the chart but appears to be indented. Furthernore a TrailRunner graph line sometimes is being drawn as a straight line without any intermediate data points, although there should be some.
Background: Other applications display the raw data of a device. This makes the graph unreadable. The philosophy of TrailRunner instead is to display the overall trend and development of your workout session.
Approach: TrailRunner has an auto split feature where the workout is being sliced into fixed distance intervals. For each interval the statistical median value is being calculated and one data point reflecting this value is then being used as a representative. As the location of the representative can be somewhere in-between the first interval, the graph might appear to be indented. Furthermore if representatives in adjacent intervals fall onto a straight line, only the edges representatives are being drawn and the connection line depicts the trend development.
Details: The auto split feature uses the following distance intervals. By the time of this writing it’s 250 m for workouts shorter than 10 km, then 500m up to 20 km, 1000 m up to 50 km and 10000 m from there on. A route with 42 km would then have 5 intervals.

Tags: workout

Non, mais essayez la traduction automatique:

QuickGuide Introduction courte.
Utilisez TrailRunner avec Nike+iPod.
Utilisez TrailRunner avec ForeRunner.

> Tutoriel en anglais

Tags: tutorial, help, français

Problem: TrailRunner can publish your weblog to either a .Mac or FTP account. Both options might not work for you.
Solution: To manually copy your weblog to another server, follow these steps:
- Press the Preview Button in the Publish pane.
Safari will open and will show you the preview.
- Remove the /weblog.html part of the url displayed in the address bar.
- Press the return key while the cursor is still in the address bar.
Finder will open a new window with the exported files.
- Manually copy these to your server.

Tracks describe connections between two locations. Each track has a start and an end way-point where other tracks could be connected to.
Routes are a sequence of several tracks. You plan routes by adding tracks to its course. The distance of the route is the sum of the distances of all tracks consumed by the route.
Example: The route to my grandmas house is beautiful, I follow several tracks that go through woods and fields. At one way-point, two tracks are crossing where the other goes down to the valley. I have recorded the course with my GPS device for that you might try the same route one day. The recording is either a single track or a sequence of way-points. The problem with the latter is that the recording then misses any intermediate locations between two way-points. Therefore I send you the single track recording. You can import this into your TrailRunner document and merge the course with your existing tracks. TrailRunner will then split the track at locations where existing tracks overlap and at the same time update the routes course to use the resulting tracks.

Problem: The ForeRunner device displays a distance for a workout. Garmin Training Center displays the same distance but TrailRunner displays a different distance.
Background: Your ForeRunner records geographical data points during the workout. At the same time your ForeRunner internally sums up the distance for the workout. It could sometimes happen that if you sum up the distances between each data points the result will be different to what the ForeRunner has summed up during the workout.
Reason: If you have intelligent recording enabled on your ForeRunner and the GPS signal quality isn't too good, the device will alter the recorded geographical course after it knows better. Problem is that at the same time the overall distance should also be adjusted, which is not the case.
Status: TrailRunner takes only the geographical information from the workout and takes this as the base. If your ForeRunner has internally stored a different distance, TrailRunner assumes this as an error in the ForeRunner device as it delivers contradictory information.

Problem: You have a route and you only want to adjust the pace. The checkpoints should then reflect the new pace.
Solution: Select the route and open the info pane. Enter the new average speed.
Tip: The info pane also displays an arrival time. It's based on the duration (by speed and distance) and the current time. This is helpful if you want to finish a route before sunset and you need to know when you should start.

Problem: When you import a route. you can merge the course into the map and add a diary entry. When you choose to merge the course into the map the course of the route will be aligned to existing tracks. This means that the route will be modified and some values like elevation data or the exact course might become different to the raw data from the GPS. The diary entry instead stores the raw data. If you later compare them, they might differ slightly.
Solution: Please keep in mind that workouts are meant to be stored in the diary and not in the map. The map is the base for planning future routes and by merging route courses into the map you complete your network of tracks more and more. In the long run, workout information like heart-rate and speed isn't of any interest in the map. But in the diary, it naturally is. 
Tip: If for some reason you really want to archive workouts and routes in the map, then you should import the courses in one piece and select TrailRunner > Preferences > Advanced > Store workout data in the map. This will not alter the course of a recorded route (but also will not add crossings or remove redundant tracks) and will keep the workout data persistent in the map.

Problem: You have imported a workout and see heart-rate and pace information in the workout chart above the map. The next time you start TrailRunner the workout data is gone and only elevation data is left.
Reason: When you import a route, TrailRunner displays all imported information in the map and in the workout chart above the map. But workout data should be stored in the diary and will be forgotten elsewhere the next time you start TrailRunner. The reason for this behavior is, that routes could be used by several workouts and the map is the place where you plan new workout-routes.
Solution: The best way to keep your workout information is to add a diary entry. But if for some reason you want to keep the workout information in the document, enable workout archiving in TrailRunner > Preferences > Advanced.

Problem: TrailRunner asks your keychain for a .Mac authentication. The keychain itself uses your .Mac system preferences information. If your keychain is not set up properly, TrailRunner is not able to access your .Mac account. This might be due to a problem with your keychain.
Solution: Read the following support article on how to fix any keychain problems:
> Using keychains with .Mac, troubleshooting keychain issues

The TrailRunner diary has a chart view and customizable columns for the log entries. Read the blogpost for a feature overview.

Although TrailRunner looks like focused on runners, bikers will benefit from TrailRunner too. The only difference is the approach on handling routes:
Runners like to plan their routes detailed in advance and seldom own a GPS device like the Garmin ForeRunner. They would like let calculate a route for a given distance and then export the course onto an iPod for orientation.
Bikers plan routes roughly in advance but primarily like to collect and catalog their rides afterwards and watch an elevation profile. They often own a GPS device like the Garmin Edge and a Mac. Even some runners own a Garmin ForeRunner and a Mac.

So if you are a biker, open a new document, connect your GPS device, download your ride and possibly let TrailRunner download satellite imagery or topo-maps of the course-area. Both, runners and bikers would then make a diary entry and watch their training progress.
It's all that simple.
> Documentation

Sorry, TrailRunner is a pristine Mac OS X Tiger delicacy. But if you are (yet) unsure if you should upgrade — you're not the first user switching because of TrailRunner… So feel welcome to the colorful world of Apple Computer
> Get a Mac

TrailRunner can load maps only from from a limited list of internet map services. But you can import any image by drag & drop, screenshot & paste or file-import. To find other digital map resources in your neighborhood, visit the Library or watch out the developers-blog.
To make a screen-shot and paste it into TrailRunner, do the following:
• Open the digital map service in Safari
• Press Command-Control-Shift-4, a crossmark-cursor will appear
• Select the image area you want to copy, It's now in the pasteboard
• Switch to TrailRunner and click into the main view
• Press Command-v to paste the image into the map
Now you can drag around the map to place it.
For further information on placement, display options and map-calibration, consult the online-help.

TrailRunner can load Garmin ForeRunner data directly from Garmin Training Center or by using the Helper Application LoadMyTracks. Other than that TrailRunner can export and import GPX files.

Motivate, collect, explore. These are the three topics TrailRunner tries to focus on. For an insight into the main idea behind TrailRunner, read the About.

This message appears when TrailRunner is not able to append a selection to the route.
This is the case when the track network does not have a connection to the selected waypoint.
Should there be a connection, some tracks might have to be set to bidirectional (see Shortcuts for Layout Routes in the Library).