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

Edge triples altitude in routes

Sim-MH

My Edge 530 significantly overestimates the elevation of routes. Here comes an example:

Route in Garmin Connect - elevation 1685 m (realistic):

Elevation calculated by Edge 530 - 6479 m (much too high)

Height seems to be correct on the Edge 530 (max. 380 m), but overestimated elevation causes "too red" climbs:

Cycling maps north-east and south-west, digital elevation map, and basemap are active:

Any idea about the reason of this miscalculation?

Feedback is highly appreciated. Thanks!

  • 0

    Hello, I bought a Garmin Edge 530 recently and I have the same issue, for example I created I course on Connect with a 3500m elevation correctly displayed on the website, when sending it through Connect on my Edge, I now have a 17000m elevation on the same course, and ClimbPro can't figure out the correct climbs and grades.

    When exporting the course as a gpx from Connect, converting it to .fit on a third party software, and transferring it to my Edge with an USB cable in the NewFiles folder, the issue seems to be resolved, but it's a bit disappointing for a 250€ device.

    I hope the issue will be adressed soon.

  • 0 in reply to 3142378

    The issue is not with the Edge, but with the data Garmin Connected is sending.

    I've been told that a fix will be released soon.

  • 0 in reply to aweatherall

    Ok, that makes sense considering that the issue is "fixed" by uploading .fit files from third party to the Edge.

  • 0 in reply to 3142378

    Garmin rolled out a fix to Garmin Express to address this today. (2021-07-01)

    Delete the course off your Edge unit and re-send it from Garmin Connect and it should now have the corrected elevation data in the exported file.

  • 0 in reply to aweatherall

    I can confirm this is resolved for me.

    Just some oddness, but we'll discuss that on a rainy winter day: A 32km route created in Garmin BaseCamp shows 893hm climb, analyzing it GPXSee also shows it as 893hm, importing it into Garmin Connect shows as 852hm and from there sending it to the Edge 530 comes out with 878hm... Something is still touching (smoothing?) the data along the way, but not nearly as dramatic. Wish they would all just leave data alone and take it as is...

  • 0 in reply to allanhvass

    It is to do with the distance between data points that Garmin recommends you have in a course file to give you the best experience with elevation plots and ClimbPro.

    From a navigational perspective if you were to have a section of road that was 2 miles long and dead straight you may only really need 2 data points. One at each end. That would meet the needs from a navigational perspective, but would give you a wholly inaccurate view of the elevation profile over those 2 miles. 

    Garmin recommends that the course has a data point every 35 meters. The small change in elevation gain that you are seeing is to do with the insertion of the extra data points.

    Garmin do leave the elevation data alone if it is a course that is synced to Garmin Connect via the 3rd party integration interface used by Strava and Trailforks.

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries