Q: calculation of ascent

0 views
Skip to first unread message

Wolfgang Berberich

unread,
Dec 5, 2009, 11:27:30 AM12/5/09
to erik goetze, TrailHead
Hi Erik,

the ascent value may be affected by three things:

a) It comes from your GPS device, for example from a lap recording. 
b) I calculate it on my own, using a high-pass filter as minor variations of inaccuracies of your GPS may otherwise sum up to huge errors.
c) I calculate them with a different threshold in the low pass filter. You can switch between the lower and the higher values in Application Preferences > Advanced.

The Problem with the ascent value is that it is a nice theoretical number but practically it is almost senseless when your GPS altimeter is inaccurate
e.g.:
100
101
102
100
103

Will sum up as 5 meters in ascent where in reality it may be a straight climb from 100 to 103. Imagine what can happen over the course of 5 km.
The lower value in TrailRunner is 2 meters, the higher is 12 meaning that I assume anything that is less that 2 meters away from the last settled altitude point as the same height.

I know that I answered like nothing, but this is what makes this topic so philosophical.

BTW: I did no receive the screenshots, you may send then again and I'll take a look at these.

cheers,
- berbie.
--
Hint: To keep updated with TrailRunner, become member of the trailhead group (http://groups.google.de/group/trailhead) and follow the TrailRunner developer blog (http://trailrunnerx.com/en_blog).

Berbie

unread,
Dec 5, 2009, 11:31:43 AM12/5/09
to TrailHead
Minor correction to the above:
Its a high pass filter in any case. And the cut-off threshold is
either 2 meters or 12 meters.

On Dec 5, 5:27 pm, Wolfgang Berberich <berbie.trailrun...@mac.com>
wrote:
Reply all
Reply to author
Forward
0 new messages