Different altitude levels in same gpx-track
Not a Problem
LM shows different levels of altitude up and down, after correction of altitude values. Both panels should shows the same values.
Files:
1000107557.jpg
The same problem 
Hi Jörg,
The two circled values are the track's total ascent (591 m) and total descent (−597 m). These aren't two versions of the same figure — they're calculated separately: ascent is the sum of every uphill step along the whole track, and descent is the sum of every downhill step.
The two totals only come out equal when a track finishes at the exact same altitude it started at. Yours ends about 6 m lower than the start (the profile runs from roughly 1120 m up to 1720 m and back down to about 1150 m), so the descent is slightly larger than the ascent. A 6 m difference over ~590 m of climbing is completely normal — it's the expected result, not an error.
The altitude correction you applied did its job: it replaced noisy GPS altitude with cleaner elevation data, which is why the ascent and descent now look realistic for this hike. What it doesn't do — and isn't designed to do — is force the two values to be identical, because that depends on where the track begins and ends, not on the correction.
So there's nothing wrong here: 591 m up and 597 m down is correct for this track. If you expected them to match because the route looped back to the same spot, even genuine loops rarely match to the meter, since each direction is summed independently.
Hi Jörg,
The two circled values are the track's total ascent (591 m) and total descent (−597 m). These aren't two versions of the same figure — they're calculated separately: ascent is the sum of every uphill step along the whole track, and descent is the sum of every downhill step.
The two totals only come out equal when a track finishes at the exact same altitude it started at. Yours ends about 6 m lower than the start (the profile runs from roughly 1120 m up to 1720 m and back down to about 1150 m), so the descent is slightly larger than the ascent. A 6 m difference over ~590 m of climbing is completely normal — it's the expected result, not an error.
The altitude correction you applied did its job: it replaced noisy GPS altitude with cleaner elevation data, which is why the ascent and descent now look realistic for this hike. What it doesn't do — and isn't designed to do — is force the two values to be identical, because that depends on where the track begins and ends, not on the correction.
So there's nothing wrong here: 591 m up and 597 m down is correct for this track. If you expected them to match because the route looped back to the same spot, even genuine loops rarely match to the meter, since each direction is summed independently.
Sorry for that inconvevience. I think, my post was a little bit misunderstadable, because the second screenshot wasn't loaded up.
Now, you can see, that there were 2 panels wirh different pairs(!) of ascent and descent AT THE SAME TIME.
Know, 48h later, both are the same, so it sermed to be a latenz inside locus, not a real problem.
Thank you.
Sorry for that inconvevience. I think, my post was a little bit misunderstadable, because the second screenshot wasn't loaded up.
Now, you can see, that there were 2 panels wirh different pairs(!) of ascent and descent AT THE SAME TIME.
Know, 48h later, both are the same, so it sermed to be a latenz inside locus, not a real problem.
Thank you.
Second sreenshot
Second sreenshot
Replies have been locked on this page!