I’ll do a running workout on a flat surface and the GAP will be much faster than my average pace. This is less frequent. (see picture 1)
I’ll do a running workout with hills and the GAP will be almost the same as the average (or slower) (see picture 2)
Based on what I’ve read in other posts, issue #2 could be due to running easier on downhills, but I’m not sure what could be causing the difference on issue #1. It honestly does not bug me that much, as I have in the information in Strava, but it does skew the training load quite a bit.
Would it be possible to make GAP an editable field? So that when this issues occurs, it can man modified manually to adjust the training load accordingly?
The first run has weird velocity data. It has you running at better than 30km/h for 6 minutes or so. The gradient adjusted velocity is derived from that data. Here I have plotted both of them and as you would expect from a flat run there is very little difference:
Hi David!
Today I faced similar bug too. I got strange high GAP in uphill “running” interval even if the pace was ±steady. GAP climbs to 2:36 which can´t be true for me. There is no such a high value in Garmin connect.
Hi David!
I have another “BUG” with GAP. It seems to me, that GAP is counted from external elevation data and not from activity elevation. Because I run on flat 200m oval and I got very strange GAP and much stranger 30s GAP, like there were elevation changes which they weren´t.
I’m also seeing some strange GAP values for short running intervals. On my 200m repeats on 14th April, the GAP is slower than the Pace despite the re being a modest uphill gradient (~1.5%)