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

ClimbPro useless?

Pan Milan
over 1 year ago

There is a short climb not far from my home which i ride quite often... and ClimbPro never recorded it correctly. It starts the "climb" 200 metres before it really gets uphill... and then it stops the climb in the hardest part like 200 meters before the climb ends... See attached picture below. I guess there is no need for any corrections in climbs that are XX km long... but in a short climb like this, it is basically useless because there is 200m flat/downhill recorded as a climb and 200meters of the hardest part missing... I noticed this on several different climbs but this short one is the most obvious... Is there any way to participate in updating climbs according to reality? Or we just have a feature which looks nice but is useless? I have latest updates on my Edge 1040 (18.23) and also latest maps. And the recordings of this particular climb were always the same - even on older SW/map version...

  • +1 over 1 year ago

    Hi I have the same problem and more... in the route planning there are climbs that end in a dead end in the last few meters (even on flat sections). However, if you drive this climb, the map on the 1040 does not show the useless part of the route.
    But contact with support revealed that they were currently working intensively on the errors in ClimbPro. 

  • 0 over 1 year ago

    I find climbpro always wrong, when following a track and in automatic mode. The profile it shows it's correct, but it's not in synch with my ride, so it shows me climbing when I'm on a flat piece, for example.

  • 0 over 1 year ago

    Garmin does most things exceptionally well, and for the most part the 1040 is near perfect. However, ClimbPro is terrible, and Garmin should be embarrassed to not have address it by now. Sometimes it is within 20-30 yards/meters of being in sync with reality. But most times it is 50-500 yards out of sync. If I’m on rolling terrain, I honestly have no idea if I’m looking at the current climb, the previous climb or the next climb. 

    I came to the 1040 from a Hammerhead Karoo 2 for the battery life.  Karoo 2’s “Climber” is excellent (I just wish the battery life was 2x). 

  • 0 over 1 year ago in reply to RUNNINGBANTER

    Totally agree. I love Garmin products but ClimbPro is a total failure

  • 0 over 1 year ago

    Climb pro was the main reason to buy a new Garmin. Nowadays for me is completely useless. In several roads where i ride mainly in Spain N634 and N611 because of a error in the categorized of the roads does not appear on climb pro and where appears works badly. I dont know if they are working on it. And for last, why i cant choose or customize the climb pro screen and choose what to see?. Garmin have in his climb pro screen an useless little font that i cant see. its annoying. 

  • 0 over 1 year ago in reply to DavidKroter

    Climb pro was the main reason to buy a new Garmin. Nowadays for me is completely useless. In several roads where i ride mainly in Spain N634 and N611 because of a error in the categorized of the roads does not appear on climb pro and where appears works badly. I dont know if they are working on it. And for last, why i cant choose or customize the climb pro screen and choose what to see?. Garmin have in his climb pro screen an useless little font that i cant see. its annoying. 

    Wahoo climb pro seems magnifique

  • 0 over 1 year ago in reply to camillo.vezzoli

    i disagree completely, climbpro is GREAT. there is definitely a bug in the latest fw though. i posted about it in the other climbpro thread. the climbs disappear mid climb and you lose credit for them with the latest 18.23

  • 0 over 1 year ago in reply to Skyewalkr

    Im a Garmin fanboy too... but... how can you call Great something that is so badly off (like 50% of a short punchy climb is recorded incorrectly)?? :)

  • +1 over 1 year ago in reply to Pan Milan

    I agree that ClimbPro (at least the "Freeride" version) is mostly useless.

    - For not-so-characteristic shorter climbs (like 2km) with small ascent (like 20m) it's pretty random where it starts and where it ends. Sure, for such "climbs" it's often disputable anyway, but it announces the start and the end where it clearly does not make sense - for example the climb continues just as steep for the next 100m or so when you get the fanfare. Oh, no fanfare anymore ;-)

    - If there are forks, it often seems to have a different idea where I should go. Or maybe I am just confusing it by stopping to check the route or going the wrong way for few meters and turning around? On long climbs I often get them in multiple sections - like 8 for my last 1400m climb. Admittedly, I did the climb with short breaks, but the splits didn't align with my breaks :-D

    - When there is a long characteristic climb on a route without forks, it kind of works. Except that displayed gradient sections usually have no relation to reality. It says it's steep when it's nothing, it says it's nothing when it's steep. The only kind of useful information is remaining distance and ascent, which looks believable (a small error does not matter there).

    I am trying to understand where are the errors coming from. Maybe it uses poor DEM data? But then why not use zillions of uploaded activities? Maybe lagging barometric data screws it up? Maybe some outlier measurements are messing up the data? I can't see anything that a sensible engineer couldn't deal with (I'm one, and I can't believe that they released something so much off), but maybe they need to iterate on the approach?

  • 0 over 1 year ago in reply to Marcin

    Marcin, it's not just the Freeride version. I see the item #3 constantly when following a route. Strava has been blamed for this, but after it's been declared resolved I kept seeing the problem... even for routes not created with Strava. First versions of ClimbPro, when the 1040 has been released, didn't have the issue, it appeared (for me) with a subsequent firmware upgrade.