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

Device ascent/climbpro dramatically different then course elevation

I created a course in Strava with 1881 feet of elevation. I see the same elevation on Garmin courses on the website. However, in the course summary the ascent per the device is 8261 feet. The elevation preview graph looks "correct" (ie no large spikes, general elevation range looks right). This then leads to the remaining ascent data field being incorrect and I am getting false 1500 ft climbs on ClimbPro on seemingly flat roads.

Garmin recorded the ride as 1250 feet of elevation and the same uploaded to Strava.

On version 5.5 since April 17th but this issue just started in the last week. It happens every ride.

Any ideas?

0 aweatherall over 5 years ago

The issue is a GC issue that Garmin is aware of. GC is currently using its own elevation data when exporting a course. Garmin are working with Strava to get the Strava elevation data passed over when they send the course.

0 Kurev over 5 years ago in reply to aweatherall

Same issue is with Komoot courses synching, using the new autosync.

If course is pulled to device via Komoot app, elevation is ok. Apparently course is not modified at Garmins servers this way.

0 night_train_78 over 5 years ago in reply to aweatherall

Has something changed in the last week? I wasn't experiencing this behavior before. Is the workaround to just use the connect IQ to bring in the route?

0 aweatherall over 5 years ago in reply to night_train_78

Yes, the current workaround is to use the App to pull the course.