gravity-slave It would be interresting if you recorded your next run with your 520 as well for comparison.
I am very disappointed with the F5+ accuracy. It's ridiculous. I can't believe I sold my 735XT and spent $800 on this.
Yesterday I did a group run and 5 other people uploaded theirs. Everything from phones, Suunto's, other Garmins. There is one track that is obviously the worst. Where everyone was more or less converging on the road, one track was off, zig-zagging 30ft into commercial buildings. Also one track that completely missed a turn. Yes, that one track is the latest-greatest watch from the largest company asking for the most money.
I feel stupid and cheated.
What was your GPS firmware version ? Did you install the last firmware V 5.0 ?
I returned my Fenix 5X plus in july because accuracy was very bad but since I read that recently version of GPS firmware seems good I decided to order the 5X plus titanium but I amaffraid after reading you. I will receive my watch in 20 days... I think I can cancel my order.
Do you have you Garmin connect trace or a KML file to see he accuracy of the GPS ?
Thanks JlGranth for your feddback. Your activity seems very good, even if I don't understand why trace are more accurate riding bike than running. My previous trace with firmware 3.10 were horrible. If I will have trace like yours with the new watch I will be happy. I hope also that all these accuracy problems will be corrected by updates and that it's not an hardware issue.
What was your GPS firmware version ? Did you install the last firmware V 5.0 ?
I returned my Fenix 5X plus in july because accuracy was very bad but since I read that recently version of GPS firmware seems good I decided to order the 5X plus titanium but I amaffraid after reading you. I will receive my watch in 20 days... I think I can cancel my order.
Do you have you Garmin connect trace or a KML file to see he accuracy of the GPS ?
I’ve similarly seen these odd ‘blips’ on a couple of activities, but also noted they make no impact on speed/pace nor impact the distance accumulation. So they are just odd blips that make viewing the track after messy, but don’t actually damage any of the data you observe or rely on whilst in an activity.