Hi Folks.
I'm well aware of all the GPS accuracy issues, and I have contributed in the other threads. After many years and many Garmin devices, I'm so frustrated by the GPS accuracy of the Fenix 5. I wish I could return this thing. But anyway, I'm not going to waste another thread complaining. I just need some additional advice on marathon pacing.
I'm running the Buffalo Marathon this weekend and I'm very concerned I won't be able to rely on this watch for accurate GPS data. For the past couple of days, I've tried to dial in my goal marathon pace (7:50 min/mile), and I've failed miserably. I've never had this issue before. When it seems like I'm dialed in (by effort), I look at the watch and it ping pongs all over the place and then my split ends up being either way too fast or way too slow.
See attached image from last nights run, which is a suburb with no tall buildings and mostly wide open roads and sky.
Yes I know I shouldn't rely on "instant pace", but I've used these devices enough over the years to understand how to ballpark it. I've always been within 5-10 seconds of my goal splits by using a combination of effort and instant pace.
Some things I've done:
- I have the latest beta software.
- I've done a few GPS "soaks", even though it's probably not necessary.
- I always wait 5+ minutes to make sure I have both GPS and HRM lock.
- I've tested combinations of GPS, GPS+Glonass, smart recording, 1 second recording. So far GPS+Glonass with 1 second recording yields the best results for me.
- I do have a Garmin footpod, but I haven't tested it enough to trust the calibration. I wish there were a way to see both GPS pace and footpod pace.
- I installed the "Race Screen" data field so I can at least correct the splits on the fly when the GPS is inevitably off.
Am I missing anything? Anybody have any helpful hints? I'm really nervous about this marathon due to this stupid watch.
Thanks all.