Incorrect segment altitude gain

[vendruscolo]

Hi there, I configured my charts to display the “Altitude Gain” field:

My last run has some segments, so for each one I see the altitude gain of each segment:

(I see the same data in the table visible in the data tab)

However, this run was done in a mostly flat area, where I get 10m elevation at most:

I’m a bit confused now: the total climbing (11m) looks correct to me, and the segments look wrong (as they would add up to 171m). Unless the two values are for totally unrelated things?

The device used for recording has accurate elevation, so there’s no elevation correction getting in the way.

Am I missing something here?

[MedTechCD]

@vendruscolo

nless the two values are for totally unrelated things?

That’s not exactly what it says, but they are not necessarely results from the same thing.
Read this post to understand how it works.

Incorrect altitude data fix

I’ll try to explain best as I can… First off: add a chart which has both Altitude and Fixed Altitude. [image] If your settings are to not correct elevation, the above is what you will see at import. Altitude and Fixed Altitude are exactly the same. They just show both the elevation data from the elevation stream in the FIT file. And, this is important to understand the rest, the climbing field in the summary, has the value that was calculated by your device with its own implemented algorithm…

Then check your settings from the Actions - Settings menu and tell us your findings.

[vendruscolo]

Thank you so much, that post explains what I’m seeing. I simply had the wrong expections

I think the key (for me) is the explanation at the end:

The algorithms for calculating climbing (elevation gained) are different for all manufacturers/software etc. There is a threshold to decide what is a ‘proper’ elevation gain or not and that’s different for each algo. Is 1m up immediately followed by 1m down an elevation gain or not? For some, it is, others ignore that.

I record using an Apple Watch, and when I look at segment data on iOS apps I see the same numbers, but that’s likely because they all use the same (system provided) algorithm.

I thought that once exported (via HealthFit) the FIT file would contain elevation information for each segment, but that’s not the case (I checked on fitfileviewer). I only provides elevation for each gps point, so then Intervals has to re-count everything from scratch. TIL something new!

Thanks again, that was very insightful