That track is pretty awful, unless you have a habit of running through buildings.
But that's GPS in urban environments, I am afraid.
See the posts by jminar, it appears Garmin Connect could well be one of the issues here (in some cases plotting in Google Earth shows a much better track)
I see what you mean- GPS in an urban environment is quite bad by definition.
My friend's Vivoactive HR did a much better job though and I would certainly expect the F5 to be able to match that!
I see what you mean- GPS in an urban environment is quite bad by definition. My friend's Vivoactive HR did a much better job though and I would certainly expect the F5 to be able to match that!
Your friends Vivoactive had him swimming smack dab in the middle of the canal at the second mile. Both tracks are less then stellar, but overlay them both in Google Earth and wouldn't declare either a winner.
Sorry, but I don't believe your M400 was able to measure 6.22km exactly each run based solely on GPS. The difference made by Fenix was less than 1% which I find quite acceptable.
Let's put the measurement aside, when I looked at the map after a run using the M400, I could see my trail on the right side of the road - sure, there were a few times the GPS would put me on the other side for a moment, but then I'd appear again on the right side.
Using the F5, I'm usually on the other side and I'm "taking" wider turns than I actually did - this alone should bother anyone reviewing the map after a run.
Plus, the fact that all these "extra" movement are adding quite a bit to the measurement, is even worse...
I don't want to break PRs by getting extra meters from faulty GPS readings...
But are all the extra 'wobbly bits' adding to the overall distance measured by the GPS? There is difference between track accuracy, how well the displayed track follows the path taken, and distance accuracy, how well the GPS recorded the distance. Some folk can't appear to see that difference and, more often than not, the discussions centre on the track display not the distance recorded.
As has been suggested, the issue may well be more to do with Garmin's ability to display the track, since it appears that when displayed in Google Earth the tracks are invariably good.
Distance issues appear to be very small. So the GPS distance accuracy may well be fine, but Garmin's ability to reproduce the track might not be so good.
