So it begins.
I will have mine Fenix 5 on Saturday and will start doing comparisons to an Ambit 3 Peak. I don't have an F3 to directly compare to as of now.
Anyone have an F3 and F5 to compare?
It would be easy enough to settle this. Someone go ask him to halt his test of the Fenix 5, and restart it with Every Second enabled. He's retested watches before.
NYanakiev7??
If things turned out differently, he'd certainly have some egg on his face. Might be a disincentive for him to retest.
I really wish I could think of a way to describe how bad using smart recording is for any sort of data analysis. I can't think of a comparable thing. ....[/I]
Wrong, he says it gives the best distance/pace accuracy.
I just posed the question about 1sec vs smart on the facebook thread. Let's see what he says.
Personally, GPS performance has been far from satisfactory for me.
https://connect.garmin.com/modern/activity/1643505277 (quite OK but the track is shifted towards the middle by the turn)
https://connect.garmin.com/modern/activity/1643503973 (this one is quite bad- the trees at the end cause a big shift+the turn just before lap 2 has me making the turn in a completely wrong spot.
Ridiculous to say that when performing any analysis that having anything less than the full data set is adequate.
Except one really obvious problem: If smart recording 'skips' over a short switch back (as it's known to do), it simply doesn't exist within the file then - you can't make that re-appear afterwards. Given he focuses heavily (almost exclusively) on trail running, then these add up. Thus, for the purposes of what we're talking about here - it is less than adequate.
Which isn't to say there are other things you can evaluate, there certainly are. You can look at whether the unit plots a track point 100m off the trail, or stuff like that. But that's not what we're talking about. We're specifically and 100% purely talking GPS accuracy in tight (trail) situations.