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 over 3 years ago

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!

Top Replies

All Replies

0 aweatherall over 3 years ago

When was that course sent to the Edge?

Garmin made a change to the way Garmin Connected generates the elevation data when sending a course at the end of April, but for to you get that change the course needs to be modified after that date.

Try making a small change to the course, save it and re-send it to your Edge and see if the values look any better.

0 Sim-MH over 3 years ago in reply to aweatherall

Thanks for your support! The course was sent to the Edge this evening just after creating it. But the issue affects older courses as well (over-estimated elevations for courses that are saved on the Edge already for a long time).

A few days ago I tried to update the maps on the Edge via Garmin Express. But the update got stuck and I had to manually re-install the maps in Garmin Express (Edge 530 -> map details -> map options -> re-install map). Might this be the root of the trouble?

I use software 7.19 beta.

0 L.Rouge over 3 years ago in reply to Sim-MH

Perhaps 7.19 Beta does not know its feet from its meters, has happened at NASA in the past?

0 Sim-MH over 3 years ago in reply to L.Rouge

I checked it once again:

The elevation of courses that are stored on the Edge since a longer time is shown correctly by the Edge.

The elevation of courses that have been uploaded to the Edge just recently is significantly overestimated. It affects the course overview, the displayed remaining elevation during a ride and the climb classification. It did not help to modify the course a bit, save it and upload it to the Edge again.

So it seems that it goes wrong since Garmin implemented the change at the end of April.

0 aweatherall over 3 years ago in reply to Sim-MH

Where are you uploading the course from?

0 Sim-MH over 3 years ago in reply to aweatherall

From a Windows PC / Garmin Connect Website, and from Garmin Connect Android app. The issue is the same for both methods.

0 aweatherall over 3 years ago in reply to Sim-MH

Sorry I should have been clearer. Where are you authoring the course and how are you getting it into Garmin Connect if it is not being authored there?

0 Sim-MH over 3 years ago in reply to aweatherall

Okay, the course was created with the Garmin Connect website. The elevation shown at the Garmin Connect website is correct, it's faulty only after transfer to the Edge.

If it helps, I can make the course available to public and share the link, or post the .fit course files from the Edge.

0 aweatherall over 3 years ago in reply to Sim-MH

That would be helpful if I could see the course in GC and try and download it

0 Sim-MH over 3 years ago in reply to aweatherall

The course is now set to "available to all" in Garmin Connect:

https://connect.garmin.com/modern/course/60855509

Furthermore, I you can find the FIT file of the course as it is stored on the Edge 530 (after uploading via Garmin Connect Website) here:

https://drive.google.com/drive/folders/1NY1ICdufpHQJxu_U5VjojKfwdc6OBJmZ?usp=sharing

I rode the course today (with some minor deviations due to closed roads). The measured elevation was 2056 m - a bit (25%) more than calculated by the Garmin Connect Website, but significantly less than the > 6000 m displayed on the Edge 530.

https://connect.garmin.com/modern/activity/6867144817

Thanks for your efforts!