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

Wrong Climb identification on courses created Strava

Marcio80
over 1 year ago

Hi Colleagues,

I´ve just bought my EDGE 1040 and I´m facing a quite strange behavior related to the ClimbPro Feature.

I have one climb (4km and 6% gradient) near to my house. In case I riding in free mode (not using a course) this climb is correctly identified by ClimbPro and everything is fine.

Riding a course where this climb is included in the route, the ClimbPro is not able to identify it in case the course was created on Strava and integrated on Garmin Connect. Only in case I create the course straight on Garmin Connect the ClimbPro is able to identify this climb properly.

Does it make any sense for you? Is it a kind of know problem? Other people already facing similar problem? Should I avoid to create courses on Strava?

Best Regards,

Marcio Santos

  • 0 over 1 year ago

    My question is related to yours. To maximize the use of the detailed Climbpro data/option offered by Garmin I wondered if the digital elevation data in for instance GPX courses made in Komoot or Bikemap is overruled by the Garmin data. Guess not reading your question. If the Garmin elevation/climb-data is superior this should be an option otherwise you are obliged to use Garmin Connect for all you courses in relation to Climbpro.

  • 0 over 1 year ago in reply to Michel

    On second thought, Garmin’s Climbpro data might be connected to road elements, instead of a very detailed elevation model, and these roads might not exactly overlap with the roads in a GPX course. So overruling might be difficult. Any ideas how it exactly works?

  • 0 over 1 year ago in reply to Michel

    I´ve absolutely no idea how it works. In the end of the day, a given workout will be available on both platforms (Strava and Garmin Connect).

    What is quite weird is that originally the course was record using a Garmin Device -> Synchronized to Garmin Connect -> then from Garmin Connected to Strava, isn´t it? So I suppose the elevation data on Garmin Connect and Strava should be the same. By the way, looking the elevation chart in Garmin Connect and Strava it´s pretty similar on both systems.

    But making the exactly the same course (captured from the Garmin Device) results in different data climbs on ClimbPro in case I do it on Strava or Garmin Connect. I can only suppose that the elevation data was filtered/adapted in someplace from Garmin Device to Strava and back to Garmin Device as a course.

    Ok, it´s a kind of annoying behavior which I can handle. I just have to use only Garmin Connect, but Shouldn´t it work regardless I create the course on Garmin Connect or Strava?

  • 0 over 1 year ago in reply to Marcio80

    There was a Strava bug where course created from an activity had bad elevation data. Strava fixed that something in July I think, so if the course was created before the fix then would need to recreate the course.

    forums.garmin.com/.../strava-not-garmin-after-all-broke-climbpro

  • 0 over 1 year ago in reply to aweatherall

    Hi,

    So I suppose the bad elevation data on Strava side is still active. I´ve created this course this week.

    For while I´ll use only courses created on Garmin Connect.

    Hope this bad behavior can be fixed in a near future in somehow.