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

Displayed elevation differs from saved elevation (GC) => discrepancy

First of all I dont use elevation correction in GC.

I had a ride today with my Edge 530 and Fenix 5+. I started from an elevation of 157 m, both devices know it due to saved locations. During the ride I did not compare the elevation of the devices, but approaching home I saw that the end elevation of Edge 530 would be pretty close to the start elevation. At the same time the elevation displayed by Fenix 5+ was appr. 25 m more.

Since I use my Fenix without continuous auto calibration for elevation I thought that my Fenix did a good job, becuase in the meantime there was a apressure drop of 3mbar. That has an effect on elevation by 24-25 m on the positive side.

I started to think that Edge 530 had a hidden continuous auto cal feature using both GPS and/or DEM data, but at home I checked that this feature only for outdoor handhelds and the watches with map.

What made me surprise that in GC I can see exactly the same elevation for Edge 530 as my Fenix t5+ logged.

So what the heck! Does Edge 530 show a different elevation in datafield called "Elevation" than the data stored in the .fit file as elevation data????

It could be only if it displayed the elevation data retrieved from DEM, while at the same time it ha no effect on the elevation data recored by the device.

I do swear that I did not mix the datafields, there are no datafields in the datascreen of Edge 530 being close to elevation datafield, which could cheat me with the same sort of displayed number.

Any ideas or explanation from anybody?

Thanks.

Top Replies

Tisztul_A_Visztula over 4 years ago +1

In the meantime I found a thread showing that Edge 520 has the same sort of behaviour, see forums.garmin.com/.../edge-520-displayed-elevation-data-is-not-saved-elevation-data

All Replies

0 AlfreDoss over 4 years ago

My Edge had the same behaviour, it's a bug, and it's got the other bug that when I start an activity and makes altitude calibration it adds altitude difference to total ascent, even if I'm still.

0 Tisztul_A_Visztula over 4 years ago

In the meantime I found a thread showing that Edge 520 has the same sort of behaviour, see forums.garmin.com/.../edge-520-displayed-elevation-data-is-not-saved-elevation-data

0 RDIFRA over 4 years ago

Same issue for me.

The elevation at start and end is correct in the file and showed in the screen

Climbed uphill to 3003 meters (showed by the device) (and right altitude by checking on maps and topographic maps)

the recorded track reported max elevation 2944 meters.

The value showed by the device is the barometric or the gps caluculated altitude?

The value saved in the fit file is the barometric or the gps calculated one?

connect.garmin.com/.../7344112562

0 Yann over 4 years ago

Same thing here, but with a 520 Plus, it displayed an elevation at 1784 m during hiking next to a 1786 m reference spot, so it’s pretty accurate, I was even higher few seconds before, but the report in Garmin Connect display 1764 m for the max elevation, no correction enabled...

Maybe it displays GPS elevations but use barometric elevation...