Climbing calculation error

There is an issue with the calculation of the Climbing field for at least running activities.

When I click Reprocess File, the correct value is calculated (similar to how Garmin and Strava calculate).

Example activity with incorrect data (i103976407): Intervals.icu

I find that the Climbing Total includes my height above sea level rather than just metres climbed. If I clipped the first second of the activity then it would be correct. But it is a pain as I have yet to find an easy way to do that. I use the Runcline app to get the climb by the way.

Zoom to the first couple of seconds, then use Actions - Fix data, and apply a function for Elevation where you set the visible part to a fixed altitude. I used 100 in this example

This will correct the first second(s) of incomplete data from your device. My Coros watch has this same behaviour and logs 0 elevation until the GPS signal is locked and I’m moving.

Another option is to crop the activity so that the first second(s) are no longer part of it. Zoom to what you want to keep and the use Actions - Crop.

The climbing field normally contains the value that is calculated and displayed by your device. That is if you have your device set as having correct elevation in Actions - Settings.

If you have ‘Use elevation correction’, Intervals will recalculate from the ‘fixed alt’ stream, which in turn has the elevation from online maps iso the elevation from the barometric sensor in your device, if it has one.

Many thanks for the tip. The Fix Data works as you say but does not seem to change the Climbing total at the top even after re-analzing.

The Elevation Corrction seemed to do nothing & so it is presumably as Runcline app is not using GPS.

The cropping would probably work best but is perhaps a bit difficult to do/justify for just a 1 sec anomaly really. On the finishing line in a race then perhaps yes but not at the beginning. They are also perhaps all a bit fiddly for something that is not crucial as the climbing total can just be manually adjested & GAP will only be incorrect for the first 1 sec. Not a criticism of Runcline just a minor frustration of life seeking a lazy one button press remedy.

Anyway thanks once again for your help with this & helping to educate about Intervals more widely.