Segment Leaderboards

This is the post for all feedback and feature requests related to Segment Leaderboards.

 

How to format your new idea and/or feedback:

Feedback that is actionable and constructive is most effective. When sharing, please consider the following when framing your thoughts:

  • If you have a new idea, it's helpful for us to understand why that feature is important for you and the value it will bring. For example: I want __. It will allow me to do ___. The reason that is important is because of ___. An example of when I needed that was ___.
  • Specific examples and details that illustrate the problem/confusion you are experiencing. For example: When I do ___, then ___ happens and that is not ok because ___.
  • Screenshots that help visually illustrate the problem. For example: Here is a picture illustrating my point ___ from above. See how ___ is doing ___?
  • An explanation of why this is important. For example: This is important to me because ___.
  • If you propose a solution, an explanation of how that solution would help you and why that is important. For example: I think a ___ would be great because then I could see ___. This is important to me because I have to ___.

 

If someone has already suggested the same idea as you, you can help us quantify the demand for the feature or improvement by upvoting the original comment. To upvote, click the up arrow on the right-hand side of the comment. 

 

Do you need technical assistance or wish to report a bug?

Keep in mind that this space is reserved for feedback. It is not the optimal place to solicit technical assistance or report bugs. To receive assistance with, or to ask a question about our product, please first search our Help Center for the related article. If you do not find what you are looking for, you can submit a ticket with our support team by following the instructions here. To report a bug, first check our Known Issue section. If you do not see the bug you’re experiencing, you can submit this to our team by following the instructions here.

Seguir
22

Comentarios

455 comentarios
  • I'd like to see a separate category created for time trial bikes.  It seems near impossible to compete with them on a road bike and, in these parts, they pretty much hold all the top spots on leaderboards, including KOM's/QOM's.  

    0
    Acciones de comentarios Permalink
  • Has anyone noticed a recent change in the minimum length of bike Segments ?  I have created many segments over the last 4 years and by trial and error I have found the minimum length is 300 metres (I get the actual length from the excellent VeloViewer companion app which gives more precise data than is reported in the Strava web data).  A couple of weeks ago I created a Segment that was 308 metres without a problem.  Today I did the same road in the opposite direction and tried to create the reverse Segment.  However, I kept getting errors saying it was too short while I gradually lengthened it.  I couldn't save it until the length got to 505 metres.  Has Strava recently increased the minimum Segment length from 300 metres to 500 metres ?  If so, why ? (I haven't seen a lot of requests from Strava subscribers asking for such a change).  If Strava have done this can they please revert to the 300 metre limit (yes, I know there may be some small inaccuracies with time and speed measurement over such a distance but I'm happy to live with it)

    0
    Acciones de comentarios Permalink
  • Ian Barton

    Frankly until Strava get a bit stricter on GPS data, shorter segments are totally meaningless. You can gain 9s on each end of a segment currently. In 2022 this kind of tolerance is ridiculous. Reliable GPS data is easily obtainable for all athletes. Strava should update policies first and then revert back to 300m.

    0
    Acciones de comentarios Permalink
  • Segment leaderboard for RUNNING on STRAVA are totally useless.
    Strava has to find a way to detect people that record a bike ride as running. Or even a scooter or other vehicle ride. I live in a very tourist city, Rio de Janeiro, here the running segments are all full of bike rides and electric scooter rides. And dont think it would be hard to Strava to detect it automatically. For example, comparing the pace with previous running pace of the same athlete... or even comparing the heart rate of the activity to see if it is reasonable. Nobody runs at 2min per km with 120bpm.
    I try to report the activities that clearly are wrongly registered, but STRAVA blocks me after some few reports, as if I was doing something wrong. 
    Strava Segment Leaderboard are what keeps us using the platform, Strava MUST open its eyes on it.

    0
    Acciones de comentarios Permalink
  • continuing, I think Strava is loosing its main attraction to me. As I love to see the running leaderboard on the segments I Strava does nothing to identify people riding bikes or vehicles and registering as running. An worse, Strava blocks me for reporting too much activities! 

    0
    Acciones de comentarios Permalink
  • William O.

    Maybe I'm lucky but in my area I've seen very few obvious problems with Segments down to 300 metres.  Occasionally there are some performances where the average speed is higher than the max but these are a very small minority.  I've never seen an anomaly of more than 3 or 4 seconds so I don't know how someone could gain 9 seconds at both ends of a segment.  There is quite a bit of friendly back-and-forth local competition which is both fun and motivating (surely both are good things ?).  Activities that obviously involve a vehicle are not tolerated by the local community and are quickly flagged - generally the leaderboard integrity seems to be good (due to collective effort).  

    Yesterday I noticed a spurious KOM on a Segment I had created - the person involved had joined the Segment about 10% after the start - in the past I would have edited the Segment to either shorten it (to negate the advantage of joining after the start) or lengthening it slightly to disqualify the spurious leader.  As the Segment is only about 450 metres I can no longer edit it to deal with this distortion, which is a little frustrating.

     

    1
    Acciones de comentarios Permalink
  • Leonardo, 
    I think we all agree that there is a problem of athletes mis-categorizing the event.

    We should start by doing both of these:

    1. Default athletes to an activity type called "Activity" (meaning "non-specific") in their Profile.  This generic "Activity" type of activity does not participate in Segments.
    2. Automatically detect anomalies as a function of (average speed, peak speed, acceleration, slope), and perhaps GPS accuracy (intervals, significant speed shifts on same slope, etc).

     

    The first (#1, a user default) is pretty straight forward.  New users get an activity type of "Activity" rather than RUN, WALK, BIKE, E-BIKE, etc.  This will virtually eliminate the person who gets the App, and simply click the "START" button to log an activity, from corrupting the segments used by others.  I like that we currently assume that the activity is the same as the most recent activity.

    One problem I see, is that there is a long alphabetized list of activity types.  Athletes see "BIKE" at the top, and choose it without searching for E_BIKE.  We need to make sure thinks like "E_BIKE and BIKE appear next to each other.  Maybe "BIKE-Electric/Moped" and "BIKE-Traditional" (don't make it so easy for the lazy to choose the wrong category)

     

    With respect to Automated detection of mis-categorized activities (e.g. somebody logging a motorcycle ride).  I think the goal here would be to "auto-flag" and if the athlete doesn't respond or fix it in a week, the activity-type is switched to "Activity" (meaning non-specific), and thus does not participate in any segments.

    NOTE:  Currently, if an event is flagged (sometimes just a data error on that segment), the ENTIRE EVENT is removed from Strava.  This hardship seems a bit extreme, when only one segment has an issue.  I would like to be able to flag just a single segment, in cases where the GPS/data corruption is limited.

    1
    Acciones de comentarios Permalink
  • I forgot... the Bullets and Numbers paragraph options don't work on the forum.
    In the previous post it should read...

     

    ... both of these:

    1.  Default athletes to ...

    2.  Automatically detect ...

    0
    Acciones de comentarios Permalink
  • Yesterday I noticed a spurious KOM on a Segment I had created - the person involved had joined the Segment about 10% after the start - in the past I would have edited the Segment to either shorten it (to negate the advantage of joining after the start) or lengthening it slightly to disqualify the spurious leader.  As the Segment is only about 450 metres I can no longer edit it to deal with this distortion, which is a little frustrating.
    -Ian Burton

    I think it is possible to change the start/finish algorithm for segments.  Today, I think we look for the "first" point within a circle of uncertainty.  I think perhaps looking for the two points could help.  Something like the following...

    At the start of a segment-definition, define a point, exactly where the segment is said to start.  Then, determine from segment-definition data, the direction of the route as passes the start point.  From that direction and point, now define an "abeam" line.  Now, instead of a circle, you have a line (like a start/finish line).

    When an athletes encounters the segment on his route, look for the two date-points (the last point before crossing the start, and the first point after crossing the start).  Use this two point to find the TIME and DISTANCE between the two points.  Using this, you can use this average speed to interpolate the precise time the athlete cross the abeam start point.  [Note, if there is GPS jitter which makes multiple data-points back and forth across the line, then use only the last time (data-point) when the athlete was behind the line, and the subsequent data-point (by definition will be after the line) for the TIME/DIST points].   This algorithm could be done applied to existing data, and would likely change a few of the existing segment rankings.

    1
    Acciones de comentarios Permalink
  • Ian Barton

    So it sounds like you have encountered the exact same issue. Because Strava regard taking a GPS position every 10s as totally legitimate and they round points only within segments, you frequently see people starting segments multiple seconds ahead.

    For example;

    Rider records a point at 0s, then a segment starts at 1s, then they record their next point at 10s.

    Strava deems them to have started the segment at the 10s point and thus they start with a 9s advantage.

    This can also happen at the end point too.

    Now I do agree, this is quite unlikely. I'm looking at a real example here where an athlete has a GPS track with gaps varying from 1s to 8s, e.g. 2:01 2:08 2:09 2:17 2:19 

    So if a segment starts at 2:09 then that's totally accurate, but if a segment starts at 2:10 then they get a free 7 second advantage. There are a lot of random factors at play so it is very unlikely that someone will get a big advantage at both ends, but let's ignore the worst case scenario of 18s, even a few seconds unfair advantage can be crushing on a short segment.

    0
    Acciones de comentarios Permalink
  • Craig W.

    Thanks for the comments.  You mention that flagging (and disqualifying) a whole Activity due to a problem with a single Segment can be harsh - I see the point of the flag is to alert the athlete to the problem and they then have a chance to remedy it.  In the case of a GPS anomaly this can be addressed by splitting the ride and cropping out the offending data, so typically only one Segment is lost and the rest of the Activity is retained 

    0
    Acciones de comentarios Permalink
  • William O.

    For what it's worth, I just looked at a Segment I created a little while ago - it's 447 metres long, I only attempted it once and it took me 55 seconds (about 18 mph).  I edited it just now to count the number of GPS points in it - there are 36, which suggested my GPS is measuring every 1.5 seconds (I just have a simple and old Android phone for GPS).  Hence with 36 data points the error in time/distance might be about 3% - not ideal for distinguishing very similar performances but it's enough to tell me that I'm some way behind the KOM holder (32 seconds) and hence would still give me a good sense of any improvement I might make in working towards a target. 

    I think having such Segments has some purpose and value in Strava and I disagree with the apparent (unannounced) change to increase the minimum length from 300 metres to 500 metres.

    I therefore implore Strava to revert to the 300 metre limit (and if the lack of precision offends some athletes they can always hide the shorter Segments 😀)   

    2
    Acciones de comentarios Permalink
  • Strava leaderboards have been really slow to update recently - on the order of hours to days (even with segment refresh). It’s a bit annoying -  are the any engineering efficiency gains to be made such that when a person uploads an activity with a segment leaderboard accomplishment, that is reflected on the leaderboard in a matter of minutes rather than hours or days?

    0
    Acciones de comentarios Permalink
  • "In the case of a GPS anomaly this can be addressed by splitting the ride and cropping out the offending data"
    -Ian

    Splitting the GPS and cropping out is great for those who are technically savvy.  But that's beyond what the average athlete is willing (or capable) of doing.  

    Flagging is great... but we should flag the problem... not the whole Activity (unless the activity-type is wrong).  I've seen GPS errors on Segments occur because you stop near the beginning or end of a segment.  That shouldn't lead to the removal of the whole activity.  If Athletes start losing their Activities and can't see all of their Hours and Miles, they are going abandon Strava to look for another tracker.

    Let's keep the solutions simple for the athletes.

    We can put the complexity into the software.

     

    1
    Acciones de comentarios Permalink
  • Ian Barton

    I'm totally with you that segments of 300m should be allowed. GPS accuracy is getting better and if anything this should allow even shorter segments.

    However, Strava need to be better at insisting upon good quality GPS data from users, if those users expect to get places on leaderboards.

    I can understand in the early days of Strava they didn't want to discourage users from using the platform if their GPS wasn't very good. But in 2022 even an affordable smartphone can provide really consistent reliable data.

    Strava should scrap the 10s rule and apply much stricter criteria when awarding leaderboard spots. There are far too many people with undeserved XOMs because they got lucky on GPS.

    1
    Acciones de comentarios Permalink
  • When will it ever be possible for the community to report/flag obviously flawed entries in the segment leaderboards? There are so many KOMs blocked by some guy who has somehow teleported himself up a 5 km, 7% hill with literally 71 kph and 3 W power output. Yeah right. There is nothing the community can do about it and that sucks.

    0
    Acciones de comentarios Permalink
  • Hi Johannes J. Thanks for reaching out and sorry for any inconvenience this athlete has caused. In general, Strava is a community-moderated social network. This means that we rely on our community of athletes to monitor the integrity of our leaderboards. Therefore, there is a way for you to address a bad KOM/QOM/CR but you will need to log into your account via the website to do so. Please see our article on how to remove an activity from the segment leaderboards.

    0
    Acciones de comentarios Permalink
  • Johannes J. - It has always been possible for the community to flag flawed activities.  You just have to log into the web version of Strava and then, when looking at the activity (you can click on it from the leaderboard), click the "flag" button on the left and input the reasoning.  I do it just about every day for multiple bad entries to help keep the local leaderboards cleaned up.  Only takes a minute or so including login once you know the routine.  

    1
    Acciones de comentarios Permalink
  • Make Segment Creators Visible (Feature)

    One reason I would like to see this feature be implemented is that it would be cool to see who actually created each segment (and to have that person's name displayed on the segment detail page). Strava is about the social connection among users, and this feature would increase that social aspect.

    Another reason to have this feature is that if there is an issue where a segment on a trail no longer matches the exact trail section due to modification of that trail over the years. It would be a lot better if that existing segment could be deleted and then re-made with the updated trail. This would allow people to know who the segment creator is and contact them to delete the current segment so an updated one can be created to match the updated trail.
    I do not like the idea of creating a new segment as is (with the old segment still in place), as this would be confusing and not look very good on the map.

    My last reason why I think it would be great to show the name of the segment creator is to potentially be able to promote a certain real-life club, group, or individual trail. Maybe it would be cool to even have a page where it shows a map with all the public segments that a user created. This could allow people to discover new trails that they never thought existed.

    I'm sure there are many other reasons why this feature would be great to have as well.

    6
    Acciones de comentarios Permalink
  • Elliott Holt

    Personally I think this needs to go further. What happens if the original segment creator can't be bothered or is no longer active on Strava? There are an awful lot of segments that ought to be deleted for various reasons, perhaps a lot of these should be relegated to "private segments".

    As you say, this should be about the community aspect, there clearly needs to be human input as to which segments are out of date or unsafe, or just daft. I would propose some sort of voting system where certain segments are promoted to become "community segments" and these would then be maintained by all local riders rather than some anonymous creator.

    There are far too many poorly created segments out there, they are either unsafe or of dubious competitive value. They slow down Strava servers and are essentially spam segments. 

    2
    Acciones de comentarios Permalink
  • Unfair advantage of racing in a peloton on segment leaderboard

    I see a lot of segment leaderboards in the area where I live taken during peloton race events. That's frustrating and unfair because drafting effect is huge in a peloton. It means that all these segments aren't reachable anymore by a solo rider.

    Would it be possible to exclude these peloton race efforts from the leaderboards? The best criteria I see would be that the corresponding activity is an activity of 100+ km at an average speed of 40+ km/h, the kind of metrics that aren't possible for a solo rider.

    -1
    Acciones de comentarios Permalink
  • Please add leaderboard filtering option to "local athletes". It's nice to compare and compete over time with other athletes in the same area. But it's no fun when some semi-pro comes in visiting for a week and takes all the local KOMs. Please add an option to filter to local athletes. (I don't know how "local" is most easily defined, maybe people with the largest % of their activities in the area.)

    2
    Acciones de comentarios Permalink
  • Adrian Robert

    As you say you cannot really define local, however I think there is a good solution that does effectively the same thing.

    Strava already records an athletes 3rd best time on a segment (you get a little bronze medal)

    If you only compare these times on a leaderboard then it's much less likely that your "visiting semi-pro" will have 3 results (or at least 3 good results).

    It would also reward the more consistent local riders, as opposed to that guy who got "lucky" one time.

    IMHO there needs to be a leaderboard that combines multiple results (local legends) but also with going fast (so you actually feel proud).

    0
    Acciones de comentarios Permalink
  • Tracks evovle over the years, but the algorithm for placing people on the leader board is to flimsy. A segment should have the ability to time limit new scores.

    I see many people having taken BIG shortcuts on the track, but stil ending as KOM. Kills the segment.

    Add the ability to flag false people on a segment. 

    On a 10km track, Strava should be able to sort out people with only 8km tracked. It destroys the segment completely.

    0
    Acciones de comentarios Permalink
  • Some good recent comments - hard to disagree with them.  I've created a lot of bike Segments in my area - I like to think they have been done with care but I'm a little apprehensive of the Segment creator's name being shared in case it leads to a flurry of requests to make adjustments that might help someone's position on the leaderboard.

    In my area there are some badly created segments (wobbly GPS data, finishing just after a junction, etc.) but they are a small minority.  In these cases I have sometimes just hidden the poor Segment and created an alternative using the same name as the original with the addition of a comment in the name, such as "safer finish" or "better GPS" so people might understand what I've tried to do.

    1
    Acciones de comentarios Permalink
  • Soren, you state "Strava is a community-moderated social network."  If this is true then allow the community the ability to moderate segments!  And by moderate I mean delete duplicates, fix start/stop points, and easily note/remove obvious segment and leaderboard errors. Just allowing the ability to suggest a change to a segment to fix poor start/stop locations would be a step in the right direction.  

    Other platforms (Trailforks for instance) allow for local admins that are able to manage content in their region.   Locally (specifically on MTB trails) we have trails that have changed or been rerouted and trails that are very close to each other.  We use their version of heat maps to fine tune the maps to be more accurate.  One would think that Strava's heat map data could be used to somewhat accurately match a ride to the heat map data associated with the segment.

    Strava does not do a good job differentiating the two trails and often people riding the faster, less technical trail will get credit for the KOM/QOM of the other trail.  The actual segment is good but the way Strava decides if an attempt on the segment is correct is not very good...

    Attached is an example of the clearly defined heat map of the segment compared to the route people are getting credit for the segment (highlighted in red).

    0
    Acciones de comentarios Permalink
  • I'm 50 years old, I use Strava for a long time and I don't beat my PR very often now. To keep motivation I would like to see on each activity for each segment if I've beaten my PR of the year, of 5 years or of all time. Even maybe : pr since...
    Thanks

    1
    Acciones de comentarios Permalink
  • Is it possible to disable the segments feature, meaning: don't include my activities in leader boards, either ever or just by default until I opt in.

    For my type of Strava user - I'm not interested in this feature, and occasionally it becomes a minor hassle actually.

    0
    Acciones de comentarios Permalink
  • Here the BIGGEST problem by far is that one single person intentionally ruins all segment boards by bulk uploading hundreds of faked activities. This is happening for 3 years now on 100s of segments in the region, and that strava is still unable to delete these sh*** directly when attempting to upload is really annoying. It needs one single look at it to easily see that it is all fake - speed graph is just a single line at 40km/h or so, the IDENTICAL data is uploaded several times, mostly created by mimicking one of the top-3 activities with computed speeds.

    I really am disapponted with strava after all that time still not to have any solution for this.

    Here a 5% ascend, the first 2 REAL entries are pro riders from our region.

    https://www.strava.com/segments/5686647?filter=overall

     
    K... . 5. Apr. 2021 42,7km/h - 461W Leistungsmesser 2.078,6 2:57
     
    Strava Athlete 5. Mai 2018 42,7km/h - - 2.078,6 2:57
     
    Strava Athlete 5. Juli 2018 42,7km/h - - 2.078,6 2:57
     
    Strava Athlete 19. Okt. 2018 42,7km/h - - 2.078,6 2:57
     
    Strava Athlete 19. Okt. 2018 42,7km/h - - 2.078,6 2:57
     
    Strava Athlete 5. Mai 2018 42,7km/h - - 2.078,6 2:57
     
    Strava Athlete 7. Juni 2018 42,7km/h - - 2.078,6 2:57
     
    Strava Athlete 7. Juni 2018 42,7km/h - - 2.078,6 2:57
     
    Ohne Perspektive 19. Okt. 2018 42,7km/h - - 2.078,6 2:57
    10 Jason Osborne 7. Juni 2018 33,0km/h 175bpm 523W Leistungsmesser 1.606,6 3:49
    11 Andreas Fließgarten 15. März 2019 30,2km/h - 387W Leistungsmesser 1.471,7

    4:10

     

     

    2
    Acciones de comentarios Permalink
  • Michael Murphy - I believe that if you set your profile so all of your activities are set to "private", then they will not show up on any leaderboards.  The downside is that others that follow you wont see them either, but not sure if that is a concern.  I am not sure of another way to not have segments show up other than marking the activity as something other than a "ride" or "run", such as a "workout" possibly.

    0
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.