Related
Options

Implementation of ClimbPro in 4.62 and later for trail running

drkglb
over 5 years ago

Hi,

with the latest beta updates ClimbPro climb calculation has changed in order to give (I suppose) more accurate data and a more sensitive detection of climbs.
Now I find my next long race (76km with 2000m total climb, which is not that much) with lots of climbing segments as below.

I think it used to be more relevant before, with the 6 or 7 biggest climbs (more than 100 meters).
Now it's kind of useless. Don't want my watch to notice me for every 1% / 2% climbs Disappointed

What do you think ? Couldn't we have a sensitiveness setting like for bike activities ?

  • 0 over 5 years ago

    I wish they would let us choose what’s considered a climb. They let you do that for bicycle activities 

  • 0 over 5 years ago

    I haven't tried ClimbPro since the latest update yet, but I liked whatever the sensitivity used to be before the update. It seemed like it did a perfectly fine job of identifying individual climbing segments. Now (based on what I'm seeing other people report) it seems like anytime there's even a very slight level or downhill spot during a climb, it breaks it up. Which is kind of annyoing to me. Let's say I'm climbing a mountain - I want it to show the whol mountain as one climb, even if there's a 10ft drop somewhere along the route.

    There should be some sort of a "tolerance" setting, where you can have it ignore downhill sections that are A) less than X feet/meters elevation loss, or B) less than X feet/meters in length. So that way, I could make sure it doesn't start a new climb every time I cross a creek bed or get to a short level segment of trail.

    Like I said, the tolerance seemed to work fine before. Whatever they changed made it way too sensitive. So I'd rather it either go back to the way it was, or even better, let us adjust it ourselves.