Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LARGE discrepancy in distance while hiking

8492331
over 6 years ago

I was wondering if anyone else noticed any large discrepancies in distance being reported? For an activity I did recently, it reports me doing 5.1 miles. However, if I export and reimport the GPX file, I get 6.32 miles. That's a greater than 20% difference, and I'm wondering what could be contributing to such a large offset in the actual distance traveled?

Is anyone else seeing this behavior?

  • 0 over 6 years ago

    Can you post a link to the activity and/or post the GPX file? Do you have auto-pause enabled?

  • 0 over 6 years ago in reply to CloggyAbroad

    Sure thing! Here are both the GPX file and the activity.

    https://drive.google.com/open?id=1mr-CEF6n8JImr6bKJ5BvYQdKej_0tjVO

    Auto-pause is disabled, and I had Power Save Timeout set to Extended since I had some problems with it being on Normal while hiking.
  • 0 over 6 years ago in reply to 8492331

    Odd. I would say the longer distance is the correct one. Why did you need Power Save Timeout, did you stop the timer during breaks? There is some discrepancy in the timing information in that it says you only have 1H35 moving time at an average of  3.2 mph (which works out as 5.1 miles) and a maximum speed of well over 30 mph. It appears some of it was so slow that the watch did not register it as moving (neither in time nor in distance), but if you ddn't use auto-pause this shouldn't be an issue.

    Maybe somebody why has the Fit File Repair Tool can have a look at the Fit File for you.

    Epic hike BTW.

  • 0 over 6 years ago in reply to CloggyAbroad

    I had the watch timeout on me during the approach, but maybe I accidentally stopped the activity and that is why it timed out? Looking online, it's hard to tell exactly what that feature does!

    But yeah, I'm definitely thinking the longer distance is the correct one.

    And thanks! It was a long day, but an absolute blast.

  • 0 over 6 years ago in reply to 8492331

    The watch will timeout if you’ve selected an activity without starting it.

  • 0 over 6 years ago in reply to 8492331

    Auto-pause will stop an activity when GPS detects no movement for some period of time. If you have auto-pause on and the signal is lost it can take some time for it to be regained when moving leading to the watch timing out. I do a lot of my activities under conditions where the GPS signal might reach a threshold below which the watch would pause if auto-pause was enabled. As a consequence, I've always left it disabled.

    In your case, you either had auto-pause enabled and did not realise it or, as you note, accidentally pressed stop