Thanks for the response. For the last couple of runs I've tried to give lots of time for the GPS to get a good fix before starting. Lately I'd been in the habit of just starting it right away, not even checking signal, and putting it in my belt :-)
Even if the signal says 'good' how do I know if its a strong or weak good?
You could do the following:
- leave your device lying in open space for some minutes before you start running (the GPS needs some time to get a good fix, even if it already shows status 'good')
- carry the device in a belt or arm band, do not hold it in your hands as this also influences GPS reception
- use QuickGPS if you have that installed on your ASUS (loads GPS positions from the internet)
I've noticed several times where my distance is very inaccurate after a run. I'll compare my RunGPS distance with Garmin Forerunner values of fellow runners. I'm wondering how to track down where the inaccuracies lie, for a few of the runs it was during hill interval training. So maybe that has to do with the smoothing buffer not being set to a proper value?
Here's last nights run where RunGPS computed I ran 15.7K -- and the route it shows isn't even accurate:
http://www.gps-sport.net/trainings/running_17607
Here's what we really did. First we ran to the street where we're doing our 9 hill repeats (this shows the run there and back) which is approx 2.53K:
http://www.mapmyrun.com/run/canada/on/ottawa/174532223
Then we did the hill nine times. One hill repeat is approx .5K:
http://www.mapmyrun.com/run/united-states/on/ottawa/832112349
So in total RunGPS should have computed a distance of about 7K.