Course ascent data very different between Connect and Komoot/Outdoor Active

Hi Matthias, thanks for your reply :-) do you know if this is being sorted by Garmin? Makes it extremely difficult to plan routes. 

I was thinking of there is a difference between planning on the map providers Garmin uses : here maps, Google maps, open source maps?

What would be your suggestion as a work around while Garmin fix the problem?

Many thanks in advance:-)

I don't know if Garmin is working on it. You should write to Garmin support directly. You can find contact info under support.garmin.com. 

The routing and elevation model is in the background, so changing the map should not make a difference.

You can use another route planner as workaround, e g. plotaroute.com, brouter online , outdooractive, komoot 

Hi Matthias, thanks for your response, ive just posted to another thread, but will copy below here too.

You're right -the test ive done between here/google/open makes no difference in garmin ascent data.

I'll try and contact Garmin today.

While the planning workaround is ok the problem becomes that the courses plotted on other platforms and then loaded up to your device via Connect (eg EDGE840) get corrupted with the incorrect garmin data. So you start your ride thinking you're on a 3000m ascent day and then when you ride your device says 5000m ascent to go...Arrggghhh!!!

...Copied from other thread... I've done some work on this...

A simple Route planned on garmin connect at my home town using garmin connect Here Maps, Google Maps or open street map all result ascent of 336m . The same route planned on Komoot, Strava, Outdoor Active gives ascent of 274m.

A 1 day route im planning in the alps garmin gives 5500m ascent vs 3600 on Komoot & Outdoor Active. So Garmin, its important you get this basic stuff correct, right?!?

The problem gets worse, if you plan the route on Outdoor Active and import it into Connect, the ascent initially looks ok (the same as was planned on Outdoor Active), but when you send it to your device (Edge840) then the ascent suddenly jumps up to what Garmin thinks it is.

8946798 said:

if you plan the route on Outdoor Active and import it into Connect, the ascent initially looks ok (the same as was planned on Outdoor Active), but when you send it to your device (Edge840) then the ascent suddenly jumps up to what Garmin thinks it is.

Maybe if you send the route directly, not via Garmin Connect, this can be avoided? For Android phones there are some apps available to send routes to Garmin devices (e.g. gexporter). 

unfortunately gimporter isnt available for Edge 840. thanks though.

I've raised this with garmin, they didnt have an answer on the phone and i'm the first to have raised it. i pointed them towards this forum, but i think the more people who phone them the faster we could get a solution

8946798 said:

gimporter isnt available for Edge 840

GRouteLoader is  https://apps.garmin.com/de-AT/apps/f03dbbbc-c4b8-4da8-af9c-f262af8c2d0e

You can also use plotaroute.com for creating the course, export it in Garmin's native FIT file format, and place it directly on the device (into //Garmin/Courses). Not as comfortable as with Garmin Connect, but if you need it urgently, and cannot wait till Garmin fixes it, it is another alternative.

In fact, there are not 2 apps to agree on total ascent…

You upload a given file to RWGPS, Plota, Wikiloc, GC, Basecamp, GE, etc and they will give you different figures…

Regards,

PS: One “good” ball park number is Google Earth -10% when verified after the ride.