GPS Accuracy

And if you want to ensure a good lock, no only wait for a lock before running but all check pace is zero (as this will confirm the lock is solid). I wonder how many of the issues here are caused by impatience?

Thanks guys, but:

1. I waited much longer than usual (over five minutes), and I'm sorry, but I do not have that kind of time to spare at 6 in the morning when I have to be back in time to get kids out of bed and to school - and in particular when the F5 normally locks on in about 5 seconds.
2. This was (as I indicated) an out of the ordinary situation in that I had reset the watch which obviously erases GPS memory
3. I still find it astounding that (never mind the precision) it took the GPS 1km to get a lock - the last time I had this type of performance was with a fitbit surge
4. This is the first time this happens with this watch which always used to lock on much faster even when "empty".
5. I pointed this out because it happened after the 7.6 FW update.

So please, do me a favour and read my posts (plural) before talking about impatience.

Thanks.

Anyone seeing stronger GPS results now?

Can't see any mention of GPS fixes in the F5 update changelog but does seem better than when I first bought it.

Here's a recent test between F5 and a FR935 I've borrowed from a mate.

Ran 4 miles earlier to compare GPS on each watch. To my surprise the 935 and F5 measured 4.01 with exact same average pace and 1 mile laps were 1-3 within each other. Strava on my android recorded 4.1m. There was some tree cover throughout and pretty overcast. Current pace was a little worse on the F5 but not massive plus that can be fixed with the footpod. Each device used normal GPS and had 1 second recording set.

Given that it wasn't mentioned in the firmware release notes (7.60), plus, the GPS firmware is still 4.30 (Since April 2017) - I don't see what exactly could fix the issues depicted.

I've noticed some improvement, but it's inconsistent so you can't tell if it's a firmware fix or just good satellite reception at that particular day.

Until we get some transparency from Garmin (and acknowledgement from them that they know there's an issue), we cannot be asked to state whether something was actually fixed.

Just tracked a walk through urban Melbourne, the track recorded is pretty useless, spikes go all over the place, it logged 14km while 1/3 of that would be more appropriate.
why isn't there some kind of low-pass-filter on the recorded data.

Firmware v7.6, gps v4.3
??????

I understand that the watch is not the cheapest option available on the market, but do you really expect its GPS tracking features to be tailored for dense urban areas with all kinds of possible obstacles?
Also, what GPS tracking mode had you used?

I don't think anybody expects stellar precision for complicated environments but for a 700$ watch I would expect: gps tracking that stays within 5% variation between same runs on same track/trail, tracks that are in some reasonable relationship to the actual roads/paths on which I run, pace measurement that provides me a decent way of estimating performance. This is not the case, and that is the reason why, despite the additional cost, I now use a footpod for distance and pace.
Don't get me wrong - overall I like the watch, I think the feature set is impressive and I use it literally all the time and won't change anytime soon. But for this price tag I would expect more GPS precision, even if accuracy as in a car or so is obviously not possible.

I understand that the watch is not the cheapest option available on the market, but do you really expect its GPS tracking features to be tailored for dense urban areas with all kinds of possible obstacles?
Also, what GPS tracking mode had you used?

Ofcource the route does not have to be 100% but this bad i did not expect. I would at least expect a decent route, it wouldn't be to hard to figure out in some clever firmware an average calculated path, in walking mode.other than that it's physically impossible to jump 10meters (qccelrpmeaccrs and gyros should be able to assist here) I used "gps only" mode.

I've bought a Fenix 5s last June. I'm also experiencing very bad readings in Walking, "Track Me" and Hiking modes. The GPS track is very inaccurate. Some examples:
https://connect.garmin.com/modern/activity/1914112277
https://connect.garmin.com/modern/activity/2472933620
https://connect.garmin.com/modern/activity/2507548147

At the beginning, I thought it has to do with a not very mature SW release, but last activities listed have been tracked a couple of days ago, with latest SW version (7.60). The situation is the same with SW version 8.00.
What I've done to try to fix the errors:
1. Reset the Watch to the default settings (I do this every new SW release);
2. Used both GPS trackings methods "GPS only" and "GPS + GLONASS"
3. Used tracking method "Auto" or "Every second"
Latest examples have been tracked on the same track (the way to/from my work place) in a completely open space, no buildings to interfere, as you can see from the trackings. The track is 1.23 km long and sometimes the watch tracks 2.40 km!!

I've sent 2 mails to Garmin Support center, no answer so far. I'm very disappointed with the bad quality and inaccuracy of GPS of this watch, not expected in this price range.

I only get that kind of miserable track in ultratrack mode. I have no doubt that the Fenix GPS struggles a lot in a city environment. However, in my case, in open fields it's spot on.

I've bought a Fenix 5s last June. I'm also experiencing very bad readings in Walking, "Track Me" and Hiking modes. The GPS track is very inaccurate. Some examples:
https://connect.garmin.com/modern/activity/1914112277
https://connect.garmin.com/modern/activity/2472933620
https://connect.garmin.com/modern/activity/2507548147

At the beginning, I thought it has to do with a not very mature SW release, but last activities listed have been tracked a couple of days ago, with latest SW version (7.60). The situation is the same with SW version 8.00.
What I've done to try to fix the errors:
1. Reset the Watch to the default settings (I do this every new SW release);
2. Used both GPS trackings methods "GPS only" and "GPS + GLONASS"
3. Used tracking method "Auto" or "Every second"
Latest examples have been tracked on the same track (the way to/from my work place) in a completely open space, no buildings to interfere, as you can see from the trackings. The track is 1.23 km long and sometimes the watch tracks 2.40 km!!

I've sent 2 mails to Garmin Support center, no answer so far. I'm very disappointed with the bad quality and inaccuracy of GPS of this watch, not expected in this price range.

Looks to me like you are stopping a bunch of times, and the GPS is drifting in those spots.

If so, try doing one of those routes non stop and see if it works better.

If you have to stop, i think pressing pause when you stop may help.