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

How to fix GPS accuracy?

4923958
over 2 years ago

Lately my Garmin GPS is off all the time. It seems that for some reason it is unable to overlap the same route if I run it more than once.

Today my friend ran the same route at the same time with the same model (245M) with the same GPS settings (GPS+Glonass) and at the same speed. For her the GPS is perfect. For me it is trash. How is that possible? How to fix it? The excuses about buildings, tree, weather, solar etc won't work this time.

Here is the image for comparison - my friend on the left and my two laps on the right: GPS route

In google maps the distance is about 1,71km. For her each lap is around 1,71-1,72km as it should be. For me each lap was 1,79km. It might seem like "meh, who cares?" but if I am running intervals, then this difference is more than 10sec/km which is significant (think 3:40min/km or 3:52min/km).

It is annoying because for a GPS watch it is the main goal to track my route... If I wanted a trash tracking, I would be using old phone instead.

  • 0 over 2 years ago

    This doesn’t look like a gps issue.  My bet is that you have smart recording of gps on.  This only affects the map as it records your position every second and uses more storage space.  

    Now, if you get different distance (they will likely not 100% agree) you may have a problem.  I don’t think 7 meters is that incorrect to be honest.   

  • 0 over 2 years ago

    Compare her GPS settings to your GPS settings? GPS + GLONAS?

  • 0 over 2 years ago in reply to bigdwazda

    You are correct, I had smart recording instead of "Every second". I did few tests with new settings, but it still is the same result as I described originally - wrong map and distance is too much. It is 70 meters per lap. I did 6 laps, in total I got about +400 meters. In pace it is 4:24min/km (gps pace) vs 4:35min/km (real pace). So about +10 sec/km. I also did full restart, cleared memory, left my watch in GPS mode for more than 20min etc. No idea how to fix this. 

  • 0 over 2 years ago in reply to Aslam

    Yes, we both have GPS + GLONASS. The only difference was in data recording. I switched it, but it still didn't resolve the issue. 

  • 0 over 2 years ago

    I kind of found the workaround - if I run the same loop in the opposite direction, the route still is a mess, but the distance is exactly as it should be 1,71-1,72km instead of 1,78-1,80km.