GPS Accuracy

Also inspired by this gc link by TIMGROSE in the 935 thread:
https://connect.garmin.com/modern/activity/1661355962

Just make pace fullscreen and see how smooth it is, comparing that with the F5 is a difference of night and day...

I do love the F5 overall, just getting more and more annoyed by it's glitches wrt gps and all.

Well, look at the "Power" graph, it looks like he has the Stryde sensor. So I would guess the smooth pace is from the Stryde, not from the watch.

In that thread Tim confirmed the pace went from the watch, If I'm not mistaken.

Edit:

https://forums.garmin.com/showthread.php?372931-Forerunner-935-GPS-Accuracy-Performance&p=970277#post970277
https://forums.garmin.com/showthread.php?372931-Forerunner-935-GPS-Accuracy-Performance&p=970494#post970494

Didn't he say he was getting pace from GPS ?

Some advice please guys if I may.

My lap pace is all over the place (lap = 1km) anywhere near tall buildings or going under anything. This morning I thought I was running 9km with the last km at 4:20/km, instead I was running 9.1km with the last km at 3:51/km. I've got the watch on 1s recording and GPS+GLONASS. Strangely enough though the track on GC is not too far off the mark.

Any recommendations on how I could sort this to get a more accurate lap pace? I'm doing London marathon is 12 days and wouldn't mind a slightly more accurate lap pace! Smart recording make any difference?

TIA!

Not much you can do I'm afraid for "Lap Pace" because even with a footpod "Lap Pace" will still come from the GPS, only "Instant Pace" can come from the footpod and that's not very helpful. On the F5 (not FR235/735) you can also force "distance from footpod" and therefore "Lap Pace" too but that means you'd a very well calibrated footpod...To be honest the problem you describe is what made me send back the F5, didn't want to have to deal with that distraction while running a marathon when I don't have to worry about it (for the most part) with my FR235.

Some advice please guys if I may.

My lap pace is all over the place (lap = 1km) anywhere near tall buildings or going under anything. This morning I thought I was running 9km with the last km at 4:20/km, instead I was running 9.1km with the last km at 3:51/km. I've got the watch on 1s recording and GPS+GLONASS. Strangely enough though the track on GC is not too far off the mark.

Any recommendations on how I could sort this to get a more accurate lap pace? I'm doing London marathon is 12 days and wouldn't mind a slightly more accurate lap pace! Smart recording make any difference?

TIA!

Would be helpfull to share your garmin connect track...

One thing is try to let the watch get as stable a connection as possible before running... Meaning standing as still as possible for a while letting it acquire a gps lock.

I checked my lap-paces for my hm (I only used avg pace there btw) and the 735 is more stable there. But as the F5 instant pace is pretty meh I assume it also takes longer to converge so the end of the 1k might be ok, at 500m it might still be off so to say.

But from the looks it seems the gps from the F5 just isn't as stable/precise as one would hope.

Here's the GC link... the actual track is no different really to the Fenix 3 as there's lots of tunnel like bits on the waterfront and high buildings. You'll see it is 9.01km..

https://connect.garmin.com/modern/activity/1672445157

Now take a look at my strava for the same activity... which I'm inclined to believe a bit more given the effort I was putting in at the end.. 9.1km (hopefully you can view this)..

https://www.strava.com/activities/938690490/overview

The watch showed me about 4:20/km for the whole last 'lap' (km) which was too slow compared to what I was doing. If this happens in London I'm going to be screwed :( Any help much appreciated.

p.s. I did leave the watch for a good 5mins before I started to ensure proper GPS and HR lock, always do (don't even get me started on the OHR!).

There's often been discrepancies between Strava and Garmin on uploads. Clearly that appears to have made a large difference with your pace. But surely, you'd know the difference between 3:50/km and 4:20/km? I only dream of running that pace, but I do know the difference between 4:45 and 5:00. One I can run, the other has me getting very tired very quickly.

Personally, I believe what my Garmin tells me and only use the Strava uploads for, well I don't know what I use them for. Different sites do different things with the uploads. You need to believe one or the other and verify what you see with known distance and known paces. You're on a rocky road to hell chasing the results from different sites.

What i suggest you do is measure out 1km. Run it. See what the GPS measures and feel the pace. Repeat until you know what pace you are running at. For the London marathon? Ditch the device for telling you what to do. Pace by the km markers.

Northern NUNCA

There's often been discrepancies between Strava and Garmin on uploads. Clearly that appears to have made a large difference with your pace. But surely, you'd know the difference between 3:50/km and 4:20/km? I only dream of running that pace, but I do know the difference between 4:45 and 5:00. One I can run, the other has me getting very tired very quickly.

Personally, I believe what my Garmin tells me and only use the Strava uploads for, well I don't know what I use them for. Different sites do different things with the uploads. You need to believe one or the other and verify what you see with known distance and known paces. You're on a rocky road to hell chasing the results from different sites.

What i suggest you do is measure out 1km. Run it. See what the GPS measures and feel the pace.

Agreed with all of that. That's what made me look initially as although the watch said 4:20/km I knew it was quicker than that by the feel of it, hence the question (specifically focussing on the last 1/1.1km). 3:50/km would be my 5k race pace now so I knew something was up. I've run that route a lot too so I'm fairly sure it also under measured, I know 100m isn't a lot but it does play havoc with your lap pace.

I'm going to try my weekend run with smart recording and see what happens. I'm not expecting miracles from the F5 but the lap pace is worse than on the F3 to be honest at present for me. At least by 400m into a 1km 'lap' the F3 would have some idea of what was going on, the F5 will swing wildly throughout.

I ran the Zürich Marathon last Weekend - Pace was far off between the Buildings. So I only used the OHR, that worked realy good.
Tryed to use the Race Screen Datafield. The Pace showing was a bit better, but also mostly off and the HR Field is to small for my Eyes...

Well, looking at the strava link I'd say your pace for the last k there is influenced quite a bit by that jump in pace where you ran 1:30 min/k. Which is pretty much usain bolt topspeed style :P

So yeah, hard to tell but strava seems more sketchy in that last k then gc...

I ran the Zürich Marathon last Weekend - Pace was far off between the Buildings. So I only used the OHR, that worked realy good.
Tryed to use the Race Screen Datafield. The Pace showing was a bit better, but also mostly off and the HR Field is to small for my Eyes...

Doh, sounds like I'm printing off a pace band to accompany my F5 for London then, lol!