ClimbPro showing up on flat route - and with incorrect values

Climb Pro is now a FU mess since recent updates within the last month or so. I had to turn it off with the latest iteration because it showed up on every stupid, lame-ass short low-grade climb just getting out of my neighborhood. It was silly and annoying. But if I turn off Uncategorized it ignores pretty much most of the legit climbs in my area. There seems to be a very wide gap between Uncategorized and Cat 5 (or whatever the next range is) that makes the feature mostly worthless now. I suppose if all you do is ride in mountains it may be a nice feature, but for my hilly, but non-mountain area it's now a useless feature.

Check my post from March: https://forums.garmin.com/sports-fitness/cycling/f/edge-1040-series/364732/climbpro---serious-bug-problem---erroneous-determination-of-the-beginning-of-the-climb

Do you have any more questions? :) This device can't tell when it's moving down and when it's moving up, since it displays ClimbPro to me on the descent :-D

Strange… it seems to depend on the area you‘re riding in.
For me - surrounding area Vienna/Austria - free climb pro works (nearly) flawlessly.

For example:
https://connect.garmin.com/modern/activity/15888757609

mcinner1 said:

Strange… it seems to depend on the area you‘re riding in.

here Bavaria - Swabia no problems either

 look for a similar place at your place as it occurs at my place, that is:
- you move above the ground a few-odd meters above the level of the river on a bike path/road that is flat all the way around
- the profile of the ground changes from the river bank - that is, it rises in the direction in which you are riding ( still being above it )

It seems that the Climbpro function does not take into account the height you are at at all, but only whether you have crossed the beginning of the hill in two-dimensional space ( which the map is ). What's more - it is able to continue its operation, despite the fact that the altitude sensor reads a drop in elevation - where, in my second case, the terrain profile rises from the river bank, and the bike path on the bridge a dozen meters away after crossing the bank line begins to drop.

red line - The level of the cycle path on the bridge

blue line - The level of the river - the difference between the water table and the bike path on the bridge is several meters ( actually I should put the line even lower in this picture )

yellow line - descent from bride.

And what I didn't mark on the photo - the profile of the area from the river bank rises to the place from where I took the screenshot google street view - that's why the Garmin runs the ClimbPro function even though I'm riding on flat terrain, even though it thinks I've just started a climb. At the very least, it should abort its operation when my altitude starts to decrease on a downhill....

Yes, at least two of the "climbs" happened where there was a slope up to a roadway or a bridge. Still, I've ridden that path probably a dozen times and it's never done this until now. I can always turn ClimbPro off, but what bothers me more is that it's also recording erronous altitude gains and throwing off my stats. I just hope Garmin reads these forums and is working on a fix! Zero communication from the developers makes it seem like they don't care when there are bugs in the field.

The 21.16/17 update replaced the previous 3 category climb selection (small, medium, large) with a new 6 category (HC, 1 to 4 and uncategorised) and the default seems to have been the uncategorised, thus easiest one. There was no mention of this UI change in the changelog.

"I just hope Garmin reads these forums and is working on a fix!" <-- start dreaming of a trip to the moon - it will come true faster :-D

The climb filter did change so that you now have more control in hilly areas and slightly less in flatter areas.

ClimbPro uses either the elevation data in the course file you are using of the DEM data for the region you are in. It is therefore only as good as the elevation data it has access to.

If I get some time this weekend I will map the old and new filter settings so that you can see how they align.