Total Ascent Values Exaggerated by 50% [Bug 29]

[GPSrChive]

@MAXW1N

Total ascent values are too high in trip computer data field or in FIT/GPX recording?

Compared to what data?

[MAXW1N]

Trip data and fit file 'total ascent" seem to be identical. (too high) - compared to my Apple watch, my hiking buddies' devices and Wikiloc tracks from the past years by other people

[GPSrChive]

The Total Ascent values taken from your GPSMAP 67 FIT files seem to be 15% greater than what is reported by your apple watch, your buddies GPS devices and wikiloc tracks recorded by others in years past using unknown equipment?

You are complaining about a 15% variance in reported elevation gain between your GPSMAP 67 and data taken from multiple unidentified devices and users over several years time? There are simply too many unknown variables here to take this seriously. I can take two identical GPSMAP 67 devices and get a similar result deviation by changing just one recording setting, and/or by carrying them differently on the same trek, or taking them on the same route on separate days and times with different ambient weather conditions, etc...

[dhg]

The bug for this ticket is already completely described at the beginning. If there's an issue of 15% with the recorded and display data being the same then that is not the same bug. Please raises a different thread for that and not conflate it with this one. This issue is a 50% difference between the expected ascent/descent of a gpx route being followed and what is displayed on screen. For example if a circular route gpx is being followed which has an ascent/descent of 1000 feet then the device ends up showing 1500 feet whilst the recorded gpx correctly shows 1000. It's all about the display figure only being wrong.

[GPSrChive]

Please, everyone, let's try to keep posts 'on topic', productive, and skip the negative rants that serve no purpose.

Thank you!