Hi David! Again, thanks for all the work you put into intervals.icu!
I’ve seen a discrepancy in altitude gain/climbing for some sessions (I am not sure if it’s specific watches, but I think I’ve seen it in both, Garmin and Coros watches used by athletes.)
If I look at total climbing for a session it says, for example, 164 m. (Top right).
When I look at the data table for the same run, it gives me 40m of climbing.
The top one is for sure wrong, and I think the table one is more likely to be correct.
Any ideas about what may be going on?
The top one in the summary is a field that is populated from the device summary fields which is written to the Fit file as a ‘Total elevation gain’.
The one from the table is a calculation within Intervals from the Elevation data stream directly (barometric pressure sensor), or if absent/choosen differently from the Elevation data retrieved in online maps.
Which elevation data is used in Intervals can be setup from the Actions - Settings dialog.
In your case, if the field in the summary is wrong, you can correct it manually. The wrong elevation data could be caused by poor GPS quality. I see that ‘Ignore velocity data’ was used, that might indicate that the GPS data was missing/faulty for a part of the activity.
Thanks @MedTechCD , I didn’t know about the source for each one of the numbers.
I’realized that elevation correction was actually checked, and that is what made it wrong. When I unchecked it it made it right, matching the number from the table (as well as the number Trainingpeaks was giving me for the same activity).
“Ignore velocity data” was used because the athlete is a trail runner, to avoid counting steep hikes as non-moving time, it should have nothing to do with this specific case, but thanks for pointing that out as well!
TL;DR: thanks, problem fixed!
