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

Incorrect outlier data

I'm looking to give a little feedback to Garmin, and this is the only place I've found...

Sometimes just as my Forerunner 610 manages to find satellites, it seems to record incorrect data e.g. it recently had me cycling at 173km/h for a short while.

While I'm thrilled with such magnificent speed, it does cause problems with the dashboard graph. The scale is adjusted for that super-high speed, and most of the graph can hardly be read as a result.

Could I humbly suggest that such obviously incorrect data be ignored in the graph? Or at least, allow the user to adjust the scale of the graph so that the real data can be seen clearly?

0 ASmugDill over 8 years ago

Try http://www8.garmin.com/contactUs/ideas/

0 Dr Phil over 8 years ago

And perhaps give it a bit more time to find satellites and settle before you press start.

0 fergusocal over 8 years ago

Thanks for the replies.

What generally happens is I turn up for Parkrun a bit late and the run starts before my Garmin has even found the satellites. So I'm already running when it does find them.

0 michaeljswann over 8 years ago

Then the answer is obvious: leave a little earlier and don't be late :p.

If you drive to the start of your Park Run, put the watch into Pre-Training mode at some point while you're still driving. Give it extra time as a GPS fix is harder to obtain while you're moving or do it when stopped at the lights.

Once you get a lock once, the next time will be a lot quicker, especially if it's not long after the first.