segment elevation accuracy / averaging

[kfulke]

since Strava no longer notifies losing 1st place on a segment with grade lower than 0.0%, can we have some sort of mechanism that;

1. filters activity data where GPS resolution is < 1sec (eg, garmin 'smart' mode)
2. filters > 95% peaks / troughs. (outliers)
3. averages the observed gradient change in remaining activities for that segment, and updates the segment gradient profile accordingly. (not absolute elevation, just profile)

many antique segments were created when GPS recording for sports activities was wildly inconsistent, and many are incorrectly considered uphill or downhill.

[Bryant]

​​Thanks for submitting your idea. It has been reviewed by our moderation team and is now open to voting.

[Jan_Mantau]

Sorry, but I don't understand what this is about and what these points mean.

Is this about notifying or about changing segment characteristics or about discarding activities from a segment?

I have never seen a GPS resolution < 1 s yet (would be wonderful accurate) so what is this filter and where and when and how should it be applied?

Filters > 95% peaks? What is the base for the percent and what are peaks?

The third point I have an inkling what it suggest, that's autocorrecting segment data with activity data from reliable sources?