Elevation good in Strava but v odd here

[Adamo]

Hi there I’m recording using iFit and using Rungap to send the file to Strava and Intervals separately (thought I would try to help out with the Strava connection thing) . Anyway the Rungap version has some strange elevation data around minus 4000m , Strava interprets that into a proper elevation but when it comes to Intervals I get a positive value of about 8000m!

Todays run for instance was mostly downhill and here are Rungap, Interval and Strava charts of same, only Strava seems to be correct, have I missed some kind of offset setting?:

[david]

Tx. The data in the fit file from RunGap says 8771m so that is what Intervals.icu is using. Likely that is what it is getting from iFit but you could contact the developer in app to investigate.

Strava has elevation correction which sorts it out.

Intervals.icu also has elevation correction. I captured a threshold pace value for you in /settings for run (6min/km adjust as needed) to enable all the pace settings:

You can see elevation correction is on auto. This means that it will be used for devices that do not have a barometric sensor for altitude.

If you choose Actions → Settings on the activity timeline chart you can control this per activity and see what device your activity was recorded with:

I have set accurate elevation = false for device “42” so future runs will have elevation correction applied automatically.

I added the “Fixed altitude” chart and this is what that run looks like now:

[Adamo]

Oh brilliant thanks David I hoped it was something like this but newish to running and I tend to ignore pace stuff at moment while I get going, so didn’t see it there. Much appreciated

(For completeness: this run was a treadmill with incline adjustment)