I took a look at that comparison and something seems a bit weird with the Foretex and Montana tracks. While they're closely mimicking each other quite well in most areas, there's strange angular turns. That's not to say the f5 tracks are stellar, though I don't know your territory and Google maps isn't putting down a track marker on your entire route. It seems the Foretrex and Montana are set to Smart Recording, or something else that's making those angles, with the Foretrex being the worse of the two.
I had noticed that my track accuracy always was much better for cykling than running and trying to figure out why, one of the differences is that when grabbin the handle bars, the watch face pretty much is pointing right up in the sky, while when running with my normal arm positions, it is directed sideways. So today when I took a run, I tried to hold a wrist angle where the watch face was pointing upwards. This yielded, by far, the most accurate and clean track for a running session up till now.
There is of course no statistical significance with a single session and another reservation is that I had updated from v2.90 to v3.30 since the last run, but it can be worth a try for others with gps problems.
May be too soon to draw conclusions, but GPS seems much improved for me after the 3.30 update... a run this morning and a hike this afternoon, and the tracks were almost dead on, more in line with what I was used to on my VSHR that cost me half as much ;) Keeping my fingers crossed that it wasn't just a fluke!
Did a couple of long hikes the past weekend I had with me my garmin eTrex GPS as well On Friday, I updated to v 3.30 on my F5 Up until now I have been more or less satisfied with the F5's precision (not excellent, but good enough for me) However, check the below hikes The track is all over the place especially in the second hike where the distance is off by a lot There was dense forest of course, but I cannot justify such vast difference in distance
as long the sky is open the track is looking good, but quite bouncy when in proximity to houses and trees.
did you use the stryd as source for pace and distance?
as long the sky is open the track is looking good, but quite bouncy when in proximity to houses and trees.
did you use the stryd as source for pace and distance?
For everyone experiencing GPS issues- please write to Garmin support and provide them with evidence. No one will bother to look into fixing things otherwise!
