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

Elevation Correction WAY off sometimes

Former Member
Former Member
I have a Forerunner 305 that I use strapped to the handlebars on my bike.
Lately I've noticed that every now and then I'll upload a ride to GC and the elevation gains and losses are way off when elevation correction is enabled.

For example I did this ride yesterday:
http://connect.garmin.com/activity/46781019
With elevation corrections disabled I get:

Elevation gain: 1143 m
Elevation loss: 1383 m

With corrections enabled I get:

Elevation gain: 4334 m
Elevation loss: 4558 m

Elevation corrections more than tripled my gains and losses!
Looking at someone else's activity that did the same trail with an Edge 705 the numbers produced without elevation corrections are pretty reasonable. Obviously the corrected numbers are not...
I had a similar problem occur with a different ride a few weeks ago as well.

Is this some sort of bug occuring? Errors with the elevation correction database?

Is there anything I can do to fix this?
  • The F305 does not have a barometric altimeter. GPS for elevation changes is not at all accurate, especially when compared to the 705. Just make sure you have a good satellite lock before you start your ride. Verify that you have the latest software and firmware on your device. Try clearing the satellite cache so that your device will reacquire satellites. To do this, with the unit off hold down the down button while powering on the unit.
  • As SEILOGRAMP noted, the Forerunners do not have a barometric altimeter and use GPS to calculate altitude. However, in my experience, no amount of updating software or getting a good satellite lock has ever fixed the inaccurate altitude that GPS provides.

    Garmin did implement altitude correction on Garmin Connect a couple of months ago. Some people reported good results with it, but on both my Forerunners, even with altitude correction the altitude data are worthless. I still get a lot of variation when running on the same course, and I've gotten completely unbelievable numbers, such as significant altitude gains while running on the beach.
  • As SEILOGRAMP noted, the Forerunners do not have a barometric altimeter and use GPS to calculate altitude. However, in my experience, no amount of updating software or getting a good satellite lock has ever fixed the inaccurate altitude that GPS provides.


    It won't fix it, but there is a chance it might make it better, or at least as good as it can get, given GPS limitations. Not having a good satellite lock will only make matters worse.
  • Former Member
    0 Former Member over 14 years ago
    Thanks for the replies, but I don't think I explained my issue clearly enough...

    The problem I'm having is with elevation corrections implemented on Garmin Connect. I know my forerunner is not going to be very accurate for elevation. The problem is that on certain rides when I enable elevation corrections in Garmin Connect the elevation gains and losses go crazy.
    I actually found another example of it tonight.

    I did this ride a couple weeks ago. GC reports 405m of gain and 952 m of losses with elevation corrections enabled. These numbers sound about right judging from topo maps.
    http://connect.garmin.com/activity/43330403

    About a week later I did the exact same ride again:
    http://connect.garmin.com/activity/44574901

    This time GC reports 2144m of climbing and 2688 m of loss. That is ludicrous. If I disable elevation corrections on that ride I get 627m up and 1165m down. Not particularly accurate, but at least not completely out to lunch. Surely something strange is going on with the website here. I don't understand how the elevation corrections feature could make the data less accurate by a factor of 4 or 5.
  • Former Member
    0 Former Member over 14 years ago
    I should point out that the typical accuracy I see while riding is usually about 4-7 metres. I don't have much experience with other units, but that seems reasonable to me for riding in trees in the mountains.
  • Former Member
    0 Former Member over 14 years ago
    So no one else has this issue?
  • Former Member
    0 Former Member over 14 years ago
    Elevation gain is way off

    I have the same problem I was kayak racing on the ocean and the 310xt said I made an elevation gain of 350meters !!!
  • Former Member
    0 Former Member over 14 years ago
    Is that with Elevation Corrections on or off in Garmin Connect?


    I actually just noticed the other day that this problem started for me when I bought a cadence sensor.
  • Same in Singapore

    Cycling with Edge 500 coupled with HR & Cadence sensors

    Initial numbers on GC:

    Elevation Gain: 61m
    Elevation Loss: 87m
    Min Elevation: 21m
    Max Elevation: 66m

    After corrections enabled:

    Elevation Gain: 108m (+47m)
    Elevation Loss: 111m (+24m)
    Min Elevation: 2m (-19m)
    Max Elevation: 44m (-22m)

    Pretty significant!
  • Former Member
    0 Former Member over 14 years ago
    For me I seemed to fix the problem by removing the wheel speed magnet from the bike. I don't really see a need to have it anyway since I never ride that bike indoors. Once I took that magnet off it seemed to work normally again.