Author Topic: Elevation gain in profile (Read 3962 times)

Dwight Sunwall · « **on:** February 26, 2005, 08:04:33 PM »

OK, I am new to this board and now I am posting like I've had a pint or two, forgive me.
I have noticed that the elevation gained in the attributes of the file window are quite a bit different than what the profile shows. For example on my snowshoe hike last week of California Peak in southern Colorado the attribute shows 3558' of elevation gain and the profile shows 5549'. I know the profile is the most accurate because the hike started at 9000' and the highpoint was 13849'. Why is there so much difference?

Krein · « **Reply #1 on:** March 01, 2005, 09:31:13 PM »

Keep the posts coming, Dwight.

This is an issue I forgot to resolve for the new release.

The two different numbers result from the exclusion of time not spend "moving" on the track. Basically if the speed is too low it considers the elevation change to not count.

I can imagine that in your case the speed threshold is too low. Are the "moving time" numbers also off for your tracks?

I think we will revert to using total elevation gain regardless of "moving" or not in future versions -- so the number in the profile is correct.

Dwight Sunwall · « **Reply #2 on:** March 03, 2005, 07:11:38 PM »

I thought I had replied to this earlier but do not see it.
Moving is what? anything over 2mph something like that. When hiking in tough conditions, deep snow, deadfall, rock walls etc. it is hard to maintain that kind of speed.

Â My not moving time can be hours on some outings. I did not know elevation gained did not count when I was levitating.:O

Krein · « **Reply #3 on:** March 03, 2005, 07:21:34 PM »

'>

You're absolutely correct. I'm going to take it out, or allow it as a setting so that things make more sense.

In some applications it does help to make the number more accurate, but a one-size-fits-all threshold is clearly not what we want.