GPS accuracy very bad !!

Glonass is the thing you were looking for ;)

You can use what ever you like, both give a good track. One track was made on a Fenix 5x the other on a Descent Mk1ciq.forums.garmin.com/.../1424512.jpg

I said in an earlier post that Pace IS affected by GPS accuracy. I never claimed otherwise.



This is an instance where GPS accuracy failed you. And I agree that this is not as good as it should be. (Happy? ;)) I don’t know the reason, but since it was in the beginning of the run I can only speculate that it could have something to do with acquiring enough GPS signals. How much time from when you selected the activity until you pressed start? Could you share four FIT file or link to the activity in Garmin Connect?

Strava does also do some processing of the data, with some pros and cons… all explained here;
https://support.strava.com/hc/en-us/...-is-Calculated
But in this instance I don’t think that is the reason for the difference in distance (assuming you ran on somewhat flat surface.) But it is something to be aware of…

I only ever press Start after the Fenix gives me a green tick on GPS.

The Garmin Connect link is at https://connect.garmin.com/modern/activity/3146847850 - I have added you to my connections.

I did another run last night with similarly shocking tracking - https://connect.garmin.com/modern/activity/3161703391 - although the total distance seems quite similar to Strava - 5.02 vs 5.0 miles.

Thanks Moo5e.

I had a look at the run on Nov 8th and the watch was definitely struggling with something for the first 22 seconds. (no elevation data and position marker stuck at start.) GPS lock must have dropped. I see you were using a 3rd party data field. Do you experience more of this kind of behaviour when using such data fields?

The second run last night I don't immediately see any GPS drops outs, but yes some inaccuracies from L. drive to S. drive (My thoughts: not uncommon inaccuracy at the start of an activity while the device is acquiring more and more GPS signals. At the end of the activity GPS looks more accurate at the same segment.)

Looking at your surroundings I only see some thick trees along E. lane and S. lane that could potentially throw off the gps receptions. Other than that the area is very flat and no tall buildings. Nothing that would affect GPS reception significantly. What GPS settings were you using again? I use GPS+Galileo and smart recording. No 3rd party IQ datafields.

Thanks Moo5e.

I had a look at the run on Nov 8th and the watch was definitely struggling with something for the first 22 seconds. (no elevation data and position marker stuck at start.) GPS lock must have dropped. I see you were using a 3rd party data field. Do you experience more of this kind of behaviour when using such data fields?

The second run last night I don't immediately see any GPS drops outs, but yes some inaccuracies from L. drive to S. drive (My thoughts: not uncommon inaccuracy at the start of an activity while the device is acquiring more and more GPS signals. At the end of the activity GPS looks more accurate at the same segment.)

Looking at your surroundings I only see some thick trees along E. lane and S. lane that could potentially throw off the gps receptions. Other than that the area is very flat and no tall buildings. Nothing that would affect GPS reception significantly. What GPS settings were you using again? I use GPS+Galileo and smart recording. No 3rd party IQ datafields.

Thank you for taking the time to look. The latest run you looked at was with a new unit but as you can see, no major improvement. I didn't use a 3rd party IQ datafield, but it was GPS Only. I will try a run tonight with GPS=Gailieo and see how that looks. I have also acquired a Vivoactive 3 Music so I will track with that as welland see if there's a difference.

Thanks Moo5e.

I had a look at the run on Nov 8th and the watch was definitely struggling with something for the first 22 seconds. (no elevation data and position marker stuck at start.) GPS lock must have dropped. I see you were using a 3rd party data field. Do you experience more of this kind of behaviour when using such data fields?

The second run last night I don't immediately see any GPS drops outs, but yes some inaccuracies from L. drive to S. drive (My thoughts: not uncommon inaccuracy at the start of an activity while the device is acquiring more and more GPS signals. At the end of the activity GPS looks more accurate at the same segment.)

Looking at your surroundings I only see some thick trees along E. lane and S. lane that could potentially throw off the gps receptions. Other than that the area is very flat and no tall buildings. Nothing that would affect GPS reception significantly. What GPS settings were you using again? I use GPS+Galileo and smart recording. No 3rd party IQ datafields.

Is gps plus Galileo better than gps plus glonass? What should I use for best accuracy ?

I use GPS+Galileo at the moment since it gives me good results, other people use GPS+Glonass. Just try both on the same track you walk/run, see what’s the best for you.

A few last trainings (runs) - only gps - acceptable results. It's a bit worse in the forest, but it's not bad. Tomorrow I will try GPS + Galilleo.




Beta Release 5.57 - good direction of change.

A few last trainings (runs) - only gps - acceptable results. It's a bit worse in the forest, but it's not bad. Tomorrow I will try GPS + Galilleo.




Beta Release 5.57 - good direction of change.

Please report back to us. I appreciate you
Also how long until we get official update?

Better side (open area):
1) green - 09.23.2018 - GPS + Glonass - 4.74.0.0
2) red - 11.19.2018 - GPS + Galileo - 5.57.0.0
3) blue - 11.18.2018 - GPS - 5.57.0.0

ciq.forums.garmin.com/.../1426025.jpg

I've recently moved to a new neighborhood and this has resulted in me finding a new loop. The GPS accuracy on the loop has been fantastic AND the distance accrual has been to the .01 both times I've run it. GPS performance is obviously highly variable due to environmental conditions and other factors, but I really don't have any reasons to complain.

On my old loop the worst of the GPS performance always happened when I ran under/near some power lines. My headphones, if they were going to cut out, would also skip in this section. I'm guessing the power lines interfered with the GPS and Bluetooth signals in such a way that the watch couldn't compensate. Expecting it to overcome every environmental condition is probably expecting a bit much.