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

Mapped Snowshoe from Edge 800 shows incorrectly low distance

Former Member over 11 years ago

Hi, everyone. I went snowshoeing yesterday and turned on and started my Edge 800 and put it in an outer pocket of my backpack. I uploaded the track here: http://connect.garmin.com/activity/446972648. It shows a total distance of only .68 miles, but you can see from the scale on the map that that is too low. The part that was done twice is about a quarter mile (each way), so the whole thing can't be .68. I uploaded it to Garmin Connect straight from the GPS. What did I do wrong?

It looks like the GPS might have lost reception a few times (quick jumps without intervening points) but with my old eTrex Legend, if it lost reception, it just assumed a distance/route as the crow flies.

0 DW152 over 11 years ago

I'm not sure exactly what happened, but I loaded the activity into a program and recalculated the distance based on your track points, and came up with 2.76 miles. Does that sound more reasonable? If so, a corrected tcx file is attached, which you can upload to Garmin Connect.

0 Dugiflopper over 11 years ago

If you convert it to a course, it shows 2.7 miles for the course. Does that sound more reasonable? You can do a full edit and change the miles if you want.

Does the track look as you expected? Don't have anything to offer as to why. Before I looked at your activity I was suspecting the autopause, but it doesn't look like it in the data.

edit..... deja vu

0 schinder over 11 years ago

The answer is probably auto pause and smart recording. The Edge 800 is a cycling GPS, and doesn't work all that well with low speed activities. It thinks you're stopped when you drop below a certain speed, and stops adding on the distance to the summary that it keeps and that Garmin Connect uses. Turn off auto pause, turn the recording interval to 1 second, set your lowest speed in your lowest speed range to 0 (if it'll do that, otherwise 1), and see what happens next time.