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

Correcting inaccurate ClimbPro elevation profiles?

Is there anyway to submit feedback on inaccurate ClimbPro elevation profiles in stored map data?  There are a few climbs in my area that are very consistent 6-8% grades but show completely different and inaccurate elevation profiles when ClimbPro kicks in. I'd love to see Garmin use real ride data from EDGE units to update and fix inaccurate ClimbPro segment elevation profiles in the stored maps by correlating data across many riders and fix stored information, but I'd totally be willing to manually submit data too. 

  • I don't know where they get the data from, but in my area (Zurich, Switzerland) the profiles for detected climbs are horribly inaccurate. Start and end points of climbs don't make sense (I am usually surprised that a climb is announced out of the blue and I am as surprised when it is marked complete even though the ascent with the same grade continues further). Gradient segments don't make sense (it's a uniform climb whereas I see dramatic gradient changes by few percent) and gradients are clearly off (like a descent is marked while I am clearly climbing).

    It looks to me like the climb profile is extracted from some coarse elevation data confused by surrounding terrain and/or vegetation - it clearly does not match the road profile. I would have also expected that profiles would be determined from tons of recorded rides uploaded to Garmin Connect, but it's either not the case, or Garmin screwed up data filtering and averaging.