Elevation Issue with Auto Pause

I read about the elevation issues of the latest firmware update 9.20. I also saw some issues with my last activities.

But yesterday I had some serious issues when I used auto pause when mountain biking with a speed sensor at a bike park (with gondolas and chairlifts). Here the elevation track:

So we startet at about 1300 meters above sea level. We rode down back to that elevation multiple times. In the gondola there was no movement so the fenix5 was in auto pause. The immediate increase seems to be more or less correct. But the following descents are completely wrong. Maybe the descent calculation did not get that there was an elevation change and calculated based on what would be the change if we were still down in the valley.
There is one continuous elevation increase. There we used the chair lift. The bike with the speed sensor was on the chair in front of us and the watch on my arm. So it did not auto pause here. So maybe this problem does only exist with auto pause and speed sensor.

Today I rode with auto pause off:

ciq.forums.garmin.com/.../1370166.png ciq.forums.garmin.com/.../1370167.png

0 thr4 over 7 years ago

Set the Barometer to "Altimeter" mode in Settings > Sensors > Barometer.

https://support.garmin.com/en-US/?faq=FQrOVa18rI7tM4PnIJymR9&searchType=noProduct

More info: https://forums.garmin.com/forum/developers/connect-iq/156623-

In your scenario, since you were sitting still, Fenix probably interpreted the changes in pressure as changes in weather.

0 noox over 7 years ago

Thank you! This could be the case.
It's not totally consistent as it's only an issue when auto pause is on. So when auto pause is off it does detect the movement even if the speed sensor shows no movement.

I assume this setup is probably relatively rare. I think not many have a speed sensor on their bikes for bike park riding. But as this "all mountain" and "enduro" mountain bike riding where people use gondola and chair lifts on their ride it would be cool if there is a mode where the watches detect the lifts automatically. With my old Polar watch I could easily mark the relevant and not relevant parts of the graph and thus remove the gondola lift rides. It then calculated the cycled (by oneself) ascents (e.g. 700 vertical meters) and descents (e.g. 4500 vertical meters) automatically. Also values like average speed were then much more accurate. In Garmin Connect I can manually edit the ascent value but I have to calculate it manually. I already filed a feature request regarding this.