I have a lot of activities where the gradient doesn’t look right. Is the gradient calculated on Intervals (based on altitude) or is it from the device? In this case the decivde was Vivoactive 3, now replaced. Tyring to work out if it was a device fault or a bug in Intervals.
See at 40mins onwards, the gradient stays high despite the altitude leveling out. This makes a mess of the GAP. I’ve been adjusting the Settings to ignore PACE etc… as they are showing very high GAP on my overall PACE chart/best values, but there seems to be a lot of them.
I’ve changed all of my vivoactive recorded runs to use elevation correction, following your suggestion. I had tried it on few activites but it either didn’t let me choose the option or it looked wrong still like attached below img.
Applying this to all run activites looks like in the most part to resolve the silly numbers I was seeing. After I changed the setting for activites which would not let me use Elevation correction, to “do not use pace” option on these. And the activity I shared above has a weird bit from 40mins still, but maybe it’s the GPS that is bad on this one? Again I’ve selected to not use Pace from the activity settings.
The devices normally supply an altitude trace but not gradient. Intervals.icu calculates gradient from altitude data. If you tick the “Use elevation correction” box the GPS data and topographical maps are used to compute an altitude stream. If the GPS data is noisy and you are running along the side of a hill or something then this might not be very good.
If your device has a barometric altitude sensor and it is working properly then you should probably not use elevation correction.
If you post a link to that activity I can have a look.
Thanks, that makes sense for the elevation correction. I guess the topo map isn’t great for that part of the activity. It’s in a wooded area alongside a river. For completeness here is the activity Intervals.icu
The Vivoactive 3 bacame miles out last few months on altitude so I will no longer use it. It looked like it was okay on my older activites though, while the elevation doesn’t look too wrong on my first screenshot, the Gradient and GAP don’t seem to agree with that from 40mins onwards. Again, I’m guessing it could be poor GPS data, although the pace looks consistent and as I’d expect.
As a fix, I’ve used elevation correction on all Vivoactice 3 activites, then used the PACE Screen with best times to filter the activities that are showing silly fast times, and selecting the “do not use pace” etc… settings. This for the most part has helped provide more realstic historic values.
Thanks Gerald. Certainly worth noting and I should have mentioned that I’ve done my best to keep it clean and clear and followed those ‘calibration steps’ many times to try and revive the vivoactive 3’s barametric sensor. No luck, so I recently retired it and got a fenix 5s plus. That’s when I realised my old data was so bad that I had to sort it to make sense of my current fitness and prospective improvements. Thanks.
