Elevation Gain off by significant amount (about -10%) during cycling - Fenix 5

Former Member
Former Member

I have had my Fenix 5 for a few weeks ago and have been observing incorrect Elevation Gain data from day 1.

My rides take place on very familiar hilly territory that I have been capturing usually every 2 or 3 days, with my ultra reliable 10 year old Garmin Edge 500, and I have been using the Edge 500 as a backup device to the Fenix for my rides.

I have noticed that the Fenix underestimates the Elevation Gain by roughly 10%.  My testing involves creating a data screen on the Fenix showing Altitude, Elevation Gain and GPS Altitude and on the Edge 500 I have Elevation, and Total Elevation. 

From this setup I am confident that the Altitude on the Fenix is correct as it shows the correct elevation while on the top of several mountains with clear sky and no building or trees within 100's of meters.  It also matches the Altitude on the Edge 500.

What I have now noticed and confirmed over and over is that the Fenix often ignores the first few meters on a climb and sometimes the last few meters of a climb.  For example if I click a hill starting at 100 meters the Fenix would show:

Altitude = 100, Elevation Gain = 0

Altitude = 101, Elevation Gain = 0

Altitude = 102, Elevation Gain = 0

Altitude = 103, Elevation Gain = 1

Altitude = 104, Elevation Gain = 2

Altitude = 105, Elevation Gain = 3

.......

Altitude = 196, Elevation Gain = 93

Altitude = 197, Elevation Gain = 94

Altitude = 198, Elevation Gain = 94

Altitude = 199, Elevation Gain = 94

Altitude = 200, Elevation Gain = 94

Altitude = 200, Elevation Gain = 94

So total for the Fenix would be 94m, and the Edge would correctly show 100m.

At the bottom my road is a short ramp that is about 4 meters high and need a good climb out of the saddle to keep your speed up over it.  It remains at the same level after the ramp for a long way.  The Fenix sees this as a 2m Elevation Gain and the Edge 500 correctly sees this as a 4m gain.

I chose the Fenix 5 specifically because it had a barometer and there was a considerable price increase for this feature.  Anyone else seeing this and can this be fixed?  The looks to me like either a bug or I wonder if the Elevation Gain algorithm uses an aggressive hysteresis to ignore small changes in Altitude that would be more suited to a Hiking data collection profile.

FW 13.30.0.0 set to log every second, GPS+Glonlass, calibrate Altitude from GPS.  I should also say that I have followed all of the Garmin Support advice on this.

Attached below are images of my last ride from today where the Fenix reports 959m and the Edge 500 reports 1031m - a difference of 72m!

  • Hi,

    That is an excellent write-up. I've had the same issue with Fenix 3, and now with Fenix 6.

    I suspect Garmin has set their SW algorithm to avoid counting elevation from the swinging arm of someone running. Too much hysterisis, as you put it, or filtering. Since an Edge unit is handlebar mounted, they probably didn't do that there.

    This would mean the issue is totally fixable. If activity = road bike, Garmin should use the Edge algorithm.

    Did you ever get a response from Garmin? I'll reach out, but don't have my hopes up. Disappointing this issue still persists years later.

    For now, at least POST-ride, elevation correction using Strava post-ride seems to correct for the Fenix error.

  • Yes, your fenix (and my forerunner 935) has a barometer but it's not a very good one. Just use gps for altimeter. GPS is not very precise for altimeter, but it's way better than with the barometer.

  • Former Member
    0 Former Member over 5 years ago in reply to Elbo

    The air pressure sensor used in the Fenix and Edge500 is a very good one and certainly good enough for the purposes of calculating total climb, stairs climbed, etc..  It is the Garmin software in the Fenix which is "not very good".  if you are going to use GPS for Alitimeter, then why pay significantly more for a Barometer/Altiimeter sensor in a Fenix.  Might as well just use your phone.

    I did have a live chat with Garmin and the guy I spoke with simply did not understand the issue after he compared the GPS ride data from my Edge and Fenix.  I pointed out that the GPS data is nothing to do with the height calculations and Total Climb algorithm in the Fenix.  

    if you are capturing data for a ride then any wrist swinging algorithm should not be used.  I don't believe Garmin factor in wrist swinging anyway because when I run, the pace calculations are also a joke.  The Total Climb calculations are all wrong too for a run.

    Using Strava to "correct" the total climb is the whole issue that chosing a Fenix with a barometer is all about so that you don't have to use the incorrect Strava total climb calculations.

  • Former MemberI didn't pay more for the barometer. I actually payed more for battery life. And the barometer came with it.

    I used to do hangliding, where a barometer is used for altitude and variometer. IMHO the barometer in my forerunner is no good. Also comparing to actual airpressures from a near by weatherstation shows its no good.

    But it might be my specific forerunner 935.

  • I agree, we shouldn't need to use Strava for correction. Just what I'm doing now. Also, doesn't help during the ride.