April 15, 2020 | Version 6.0-upd8
This appears to be a complete waste of time on my Forerunner 645.
Nothing says whether the GAP pace shown is your current pace of the total pace of the run, but it appears to be neither.
Running up a steady incline at a constant pace the GAP pace varied from 7m/mile to 9 mins/mile in the space of 20m. It also managed to show a faster pace than actual when going downhill.
I did s 2.4m circular run, uphill and down again, at 10min/mile with a pretty constant effort. At no time did the GAP pace ever show a worse pace than 9mjn/mile.
I’ll not bother again. A great idea if it works, but clearly not at all accurate.
April 20, 2020, montereyjack
Yeah, I have a 645 and the altimeter isn't very reliable. Sometimes on flat ground it thinks I'm going up/down 20+ foot rolling hills. Sometimes it gets "stuck" at an altitude when I'm going up or down a hill, then suddenly jumps to the correct altitude. I had different issues with the altimeter on my 920xt before this, but now I have a Stryd foot pod and its data is way better.
November 21, 2018 | Version 6.0-upd8
Seems to work really well, but I need to test it in a race to know for sure. Pacing myself uphill is not my best discipline so if I either collapse from exhaustion or miss my pr with minutes I know who to blame. :)
June 1, 2018 | Version 6.0-upd5
Would you please explain the difference between this app and your other app "Normalized GAP" ? What does exactly means "normalized since the start of the current activity." ? Can you please make an example? Thank you.
September 24, 2015 | Version 4.0-upd
I love this. Thank you for writing it!
If you're taking suggestions, I often use "Lap Pace" during my runs. I'd love to see a "GA Lap Pace", which simply displays a running average of GAP until the lap button (or auto-lap) is pressed, after which it restarts the averaging. This would be nice in trying to hit split paces on hilly routes. Thanks!