The closer the recorded GPS points are (the shorter the time between each) the more accurately they will describe your actual path (and the closer the computed distance will be to the correct distance). Note that the distance between each point is assumed to be straight line (regardless of how you are actually travelling). GPS distances are determined by recording the current GPS location and adding the distance between the current point to the prior point to a running total. Your TomTom watch can only use GPS distance. The Garmin 800 writes/saves the wheel-rotation distance, the GPS distance, and the GPS coordinates to the fit file (there's other data being written also). The Garmin 800 keeps track of two different distances: 1) distance by wheel rotation and 2) distance by GPS. Let's explain how the distances are determined and see if that will give you an idea of what is going on.
(Note this is from looking at how the Garmin 800 works.) So it doesn't appear to be a one time thing. fit file to Strava it reported it as a 9.3 mile run. UPDATE: I should also note that I used the watch yesterday for a run and the watch reported I ran 9.47 miles but when I uploaded the. fit would be showing the shorter distance. I don't really know enough about the differences between the file types to know why the. fit file be showing only 9.7? If I upload a gpx version of the file it shows closer to the 10.2 but it doesn't include my heart rate data. I've made the ride numerous times before with other devices (Garmin 210, iPhone) and it's always been right around 10.2 miles so I'm assuming that is the more accurate distance. The problem is Strava is reporting the ride was only 9.7 miles. fit file that the watch downloads to my computer to Strava.
I use Strava to organize and manage my rides so I uploaded the. The watch itself reported that I went a total distance of 10.14 miles. I have a TomTom multi-sport watch that I used on my morning commute today.
0 kommentar(er)
