Elevation value error in creating routes

Hi! In the last few days I noticed that when I create my cycling routes with Garmin Connect the elevation value is completely wrong.
For example I created a route with an elevation showed to be 1700m, but the real value after I cycled it was 1000m (which is more realistic). 

My garmin edge 530 has registered the value of 1000m (and also importing the original route to komoot give me the exact same value 
of around 1000m), so the problem is only in the Garmin Connect website creating a new route. 

Also importing a gpx file gave me the same error: I imported the Tour de France 1st stage, with an elevation of 3600m, but in my Garmin Connect
the elevation became of 6000m !!

All the new routes created in the last week have wrong values, but before I never had this differences in the elevation's value, 
but it has always been more or less correct.



Has anyone else encountered this problem?

thank you
Niccolò

0 JoergD66 4 months ago

Same here. @Garmin, any fix?

0 trux 4 months ago in reply to JoergD66

JoergD66 said:
@Garmin, any fix?

I recommend reaching out to the Product Support through their website at https://support.garmin.com. Use the Phone or Chat options. Email exchanges take a lot of time.

0 Niccover 4 months ago

Garmin support told me they were aware of the problem, but at the moment nothing has changed...

0 Velsanin 4 months ago

Yes - all my routes recently have been massively over estimated

0 Matteo 4 months ago

same error for my and my girlfriend account. We are waiting for a solution

0 Marco 4 months ago

Several topic on this already. Let's try and keep them all a bit high on the forum, so there' more chance the devs or mods actually pay attention.

0 PVieceli 4 months ago

I also experience that the output of altitude meters is massively higher than in reality. The same applies to the descents.

0 #Matthias# 4 months ago

I usually don't use Garmin connect for route planning because it is bad for multiple reasons (the elevation is one of them). I gave it a try after following this thread for some time and I did not notice any difference compared to about 3 years ago. It seems to me the many reports popping up lately is pure coincidence and there is no new bug in GC.

As far as I can tell, the issue is that GC is using a low resolution elevation model and this creates these wrong values. But this has been the case for years.

My test route: 846m ascent, 4m descent measured with a high resolution LIDAR elevation model. The values measured by my Fenix 7X are very close to that.

The same route in GC web: 1033m ascent, 197m descent. A lot of up and downs are introduced by the inaccurate elevation model, although the route is basically one continuous climb.

For me, GC stays unusable for route planning because of this and multiple other reasons (the osm map has not been updated for at least 6 years!!!...). In case anyone is wondering, I am using Locus map for Android along with Sonny's high res LIDAR elevation model for Europe.