I’m quite an experienced Strava user having done about 1200 bike rides over the last 7 years. I’m aware of the feature that auto-excludes Efforts that are considered infeasible, however, up to now I have not knowingly been affected by it. I just noticed that in an Activity in April 2024 the first 4 Segments in a ride had been auto-excluded. I looked at an analysis of the data and it did indeed show an infeasible speed over a short section - from 14 mph to 42 mph and back to 14 mph in about 4 seconds. This occurred between about 0.08 and 0.13 miles into the Activity (close to home !). The first 2 Segments included this range and so were reasonably excluded. However the 3rd Segment started at about 0.26 miles and the 4th Segment to be excluded didn’t start until about 0.57 miles, well beyond the very short GPS anomaly. Hence I’m wondering why the auto-exclude algorithm would exclude all 4 of these Segments ? Does it need some tuning to minimise unnecessary auto-flagging of “good” Efforts as happened in this case ? There was nothing remarkable about the Efforts in this example (I don’t need them to be reinstated) - this is more about making the auto-exclude tool as good as it should be.
+29Hello
Thanks for this post. I've tagged it as Feedback, so it can be reviewed and discussed by our Team.
Thank you again.
A further bit of feedback about auto-exclusion of Segment Efforts…
Yesterday I created a new Segment and today I see that I have recorded 125 Efforts on that Segment over the last few years. So far so good. However, I notice that there is 1 Effort (from 2021) that has been auto-excluded. During that effort there was some minor GPS glitch and my speed over consecutive GPS points went from 15 to 36 to 27 to 9 mph. The position and timing of the ends of the Effort look quite correct, as does the (modest) average speed of 14 mph for the 0.8 mile Segment. As the overall Segment Effort seems quite normal I’m wondering why the Effort was auto-excluded and perhaps such rather trivial GPS glitches shouldn’t lead to an auto-exclusion. By the way, the GPS data during the glitch suggests high acceleration so I would have expected the calculated power to show a high value, but during this period the power showed as zero, suggesting some issue with the power calculation.
The specific Effort in question is of no great significance - I just mention it in case it could help improve your methodologies.
+26I have a feedback for that too: I have an activity where when I use the “Correct Elevation” feature it leads to excluding all the segments on the activity and asks me if I have used an ebike. When I use “Revert Elevation” everything is okay again and no segment efforts are excluded. It seems that imprecise Strava elevation maps can mislead the AI, maybe it deems some parts of the track much steeper than they really are. The activity contains power and heart rate data and the GPS is very precise due to multiband so those measurements can’t be the problem.
Login to the community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.