Application Preferences

To customize the overall behavior of the application, you can set application wide preferences in TrailRunner > Preferences.

The Preferences bar contains the following topics:

General

Scale to fit selected route will always scale the map display to fit the size of the selected route.

Show Graph for selected route controls if you would like to view the elevation chart along with a selected route of if the elevation chart should be keep hidden.

Visually emphasize multiuse tracks draws tracks bolder that have the multis attribute set (see help on mulituse in the info pane for a sleeted track)

Personal

Depending on the other values you enter, TrailRunner can estimate your HRMax which then gives you heart-rate zones in the activity workout chart.

iPod

Set the size of the display of your iPod to export NanoMaps that fit the iPod screen.

Synchronize

Set the preferred companion application that will be used when you click on the iPhone or Import / Send buttons in the main document window toolbar.

Advanced

Filter altitude noise uses a low pass filter to filter out elevation noise from your GPS signal. Checked, the noise filter is 12 meters, unchecked it is 2 meters. This means that with an elevation profile of 2, 4, 8, 4, 16, 10 meters the ascent value without noise filtering is 2+4+12= 18 meters and with noise filtering 14 meters. Setting this value highly depends on the quality of your GPS device. If it has a barometer (e.g. Garmin Edge) -- disable filtering, if not (e.g. Garmin ForeRunner) -- enable it.

Calculate Statistical Aggregates ignores the values for average and maximum speed that come from your device and uses TrailRunners internal heuristics to calculate these values.

The Horizontal and vertical resolution sliders control the interval and scaling display of the workout chart.

More Information on this topic: http://trailrunnerx.com/en_faq/files/tag-calculations.php.

When you drag scanned maps into your TrailRunner document, you can either store maps centrally or locally within the document. Centrally is the better choice as storage is less resource intensive.