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.

Follow
21

Comments

423 comments
  • 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
    Comment actions 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
    Comment actions 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
    Comment actions 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
    Comment actions 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

     

     

    1
    Comment actions Permalink
  • Michael Murphy 

    With the exception of the "My Results" filter, our leaderboard filters only display segment times from activities set to "Everyone". If your activities are set to "Followers" or "Only You", you will not opt into the public leaderboards.

    For more information on all of our privacy controls, please visit our privacy center and take the time to ensure your selections in Strava represent your intended experience.

    1
    Comment actions Permalink
  • https://support.strava.com/hc/de/community/posts/360073465872/comments/6346371347469

    Thanks for your help, Jason and Soren.

    I usually use the mobile app, so it would be nice to have this feature (report bad leaderboard entries) in the app, too.

    1
    Comment actions Permalink
  • szh hke - I understand your concerns about over-proliferation of Segments. 

    Maybe I'm lucky, but where I live I don't see it as a major problem.  As an example, I went on a 2-hour bike ride from my house yesterday.  It included 50 Segments, ranging in length from 0.18 miles (current Strava minimum) to 2.15 miles.  I have 7 of the Segments hidden (5 for corrupted leader-boards due to poor Segment creation and 2 for duplication).  This is all fine for me.

    0
    Comment actions Permalink
  • Suzanne Garner - CR = Course Record (fastest overall time posted for that segment).  It is the equivalent of a KOM or QOM (King of the Mountain or Queen of the Mountain) for cycling.  PR = Personal Record.  

    0
    Comment actions Permalink
  • Susun Corda - I don't think the negative votes were associated with the concept you presented.  They are more likely associated with the understanding that there is no good way to separate solo and group rides.  Strava's algorithm is terrible and should not be used in any way.  It thinks anyone who happens to be in the same vicinity for a while is part of the same group.  Even if you could get everyone from now on to indicate whether it was a group or solo ride themselves (you never would, but just hypothetically let's say you did), you wouldn't be able to correct the 10+ years of rides already in the database, so your leaderboards would already be messed up from that.  I like the idea of separating them, but only if it was done from day one.  Now, it is too late to change unless you reset everything which would take a lot of legitimate KOMs away from people .  This is very similar to the issues raised about separating road and MTN biking.  It would make sense to do IF it was done from the start.  Now, there are millions of rides already logged that do not have the proper designation one way or the other, so the results in the leaderboards would be a mess.  

    0
    Comment actions Permalink
  • Following choice no long shows up the day after you ride.

    Why not? I find this feature useful.

    It now only show all time and all time this year. They say after you ride.

    0
    Comment actions Permalink
  • Hi Carlos,

    I agree, I think the same too. Your proposal should be accepted as soon as possible, it would solve the problems you have reported

    0
    Comment actions Permalink
  • Hey strava community team. As a Zwift leader and a IRL Club route designer, i'm worried about the increasingly eroded user experience around segment leaderboards.

    Issue: #1: i post leaderboards for segment efforts after each SMITE ride in zwift on saturdays, and periodically with our IRL club, however, the 'club' filter mechanism often RETURNS 0 records.

    Issue #2: The filter mechanism itself is of little use because the only options are 'today', 'weekly', 'monthly', 'yearly' and all-time. The ability to target a specific date would give it greater utility, because presumably, if you are there to mine data for a single data, you may not be fortunate enough to be there on the exact date you and your club rode. Examining the difference between the following use-cases would reveal that most of us are looking for specific data, not generalized data.
    - "I want to find out what happened on date xyz, becuase it was a fondo event i participated in" Is probably more likely than "i wonder who was the fastest rider in month x of this current year".

    Issue #3:The removal of our ability to create segments in areas where there are many duplicates demonstrates an architectural issue that only appears with scale. I hope this is temporary, because it is killing a lot of use cases where competitive races that identify certain segments, would like to capture their results. Most of my competitive segments in Zwift have been irreversibly marked 'private' and i can no longer use them on behalf of my clubs. IRL segments are less of an issue because there is less duplication. I would recommend allowing us to create as many segments as we want, but to place a cap on query retrieval that is filtered by 'popularity'. However, the continued ability to harvest data for less popular segments should remain. Throw some NFRs in the backlog to improve scaling with this feature, or at least tell us what your plans are on this front.

    I know this type of refactoring takes time and effort, especially if short-cuts were built into the architecture in order to focus on user adoption years ago. I get it. But tech debt has a habit of coming back to haunt us with exponential delivery and maintenance effort, so it can't go ignored for too long. Give your engineering team 20% of their iterative budget allocation to focus on tech debt and architectural integrity - i trust them.

    0
    Comment actions Permalink
  • Leaderboard exclusion is easy for runner and roadcycle. It will be a problem for MTB.
    Every month, some guys shortcut some technical singles and damage the shappers work to try to win the precious KOM. Shortcuts are under GPS precision limit. And they win only some minutes. Undetectable except by local rider.
    Local rider could be another way to validate some controversial results

    0
    Comment actions Permalink
  • Pieter Godderie, interpolation has been suggested many times already, both in this version of the forum and in the previous version. I am pretty sure Strava is aware of that suggestion. They mention that themselves here:

    https://support.strava.com/hc/en-us/articles/216918227-Optimizing-Segment-Creation-how-to-create-good-segments

    Recording intervals vary between devices - for example, the Strava mobile app records every second while Garmin devices use either 1-second intervals or a smart recording which has a varied recording interval. Segment matching works the same on each GPS dataset, but depending on the device's recording interval, can yield different results. Segment matching uses the GPS points in the data closest to the start and endpoints of the segment, and as this can vary with each activity, timing on a segment can vary slightly because of this. At the present time, we don't interpolate or extrapolate GPS data to normalize for the exact start and end positions of the segment. 

    0
    Comment actions Permalink
  • Steven Zeller - Are you sure about that?  When I look, Nordic skiing and running have their own segments and leaderboards.  There are a few random occurrances where someone recorded their ski as a "run" initially and then changed it later and for some reason they still show on the run leaderboard, but that is very rare.  99.9% of the time, when they change, they are removed from the running leaderboards and added to the Nordic ski segment leaderboards.  

    0
    Comment actions Permalink
  • Yes to Stephen! Totally agree. Very difficult to get on a Nordic leaderboard if you primarily classic ski. Please consider dividing the activity into: Nordic (Skate) and Nordic (Classic). Same segments. Easy!

    0
    Comment actions Permalink
  • I'm not a fan of the removal of so many Zwift segments from leaderboards. Who are Strava to decide which segments should and shouldn't be there? It should be community driven; wisdom of the crowd.

    As a subscriber I pay for the leaderboards feature and it's useful to see where I stack up against my friends.

    Now I see just 1 segment on some rides. Fat lot of use that is.

    By all means, chop out the duplicates and the ones with nonsensical names but please attempt to ensure close to 100% segment coverage of each route. Now there are gaps and even some reasonable climbs missing. 

    0
    Comment actions Permalink
  • TRUE AGE-GROUP KOMS @PatrickMorris agree. Whilst I can still chase KOMs, it would be nice to know if I am 55, or 65, or 75 It will show an achievement. Perhaps not showing a Gringott's Vault of Crowns, but a nice Rosette. 

    0
    Comment actions Permalink
  • ^ If you are a paid subscriber, with full access to the leaderboards, then it only takes one extra click to see the segment leaderboards by age group, if you are #1 in your age group should n't that be enough ?

    And if people are not willing to pay to subscribe, why should they get everything they desire from a free website ?

     

    0
    Comment actions Permalink
  • I want to add Nordic Ski (and all the other) activities into Leaderboard for Club Athletes. It will allow followers to make all activities count on the leaderboard. The reason that is important is because of Leaderboards shows total activity time only for Swim, Runs and Cycle. An example of when I needed that was during winter time where our followers spend more time on Nordic skiing than running/cycling as they normally do during summer time. And they are frustrated that their time spent on Nordic Ski is not counting as an activity on the Leaderboard.

    0
    Comment actions Permalink
  • ^ Let's hope it works ! At least we now know you are trying to do something about this problem.

    0
    Comment actions Permalink
  • Jojo
    Thank you for a good answer to Jaisah's question.
    I have the same problem, and I think there are some possible remedies Strava could implement.

    In my case, there's a segment that used to go straight downhill, and now the clearly marked route is a series of switchbacks. Following advice here, I created a new segment, hoping that future matches would be better.

    However, that isn't working. New riders who cut the switchbacks still match, and old rides were matched to the new segment. Not only is it impossible to compete with the old matches, but this situation also encourages current riders to harm our trails by cutting the turns.

    See this segment: https://www.strava.com/segments/20484448
    and the KOM from 2012 is clearly very different.

    It seems to me that 1) you could NOT match rides predating the segment, perhaps as an option when creating the segment, 2) possibly improve the matching algorithm (I realize that would also cause complaints), or 3) tighten the matching on segments that are marked or flagged as problematic.

    0
    Comment actions Permalink
  • I agree with Jaisah Webb

    0
    Comment actions Permalink
  • ^ How could they merge the segments and databases without merging the leaderboards ? Possibly they could if the databases had been future proofed many years ago with activity ID tags but it seems pretty obvious from many other problems that they did not ....of course, 20/20 hindsight is a wonderful thing for us to have now ! How many e-bikes were around when strava started their segments, and database in 2009?

    keep e bikes separate, where they belong. (IMHO :-) )

    0
    Comment actions Permalink
  • Jojo Jaisah Webb I raised this very issue back in November and still think within your database constraints it would be possible to archive segments and set start dates for mountain bike trails that have evolved over time.

    https://support.strava.com/hc/en-us/community/posts/360073465872/comments/360013367231

    0
    Comment actions Permalink
  • Is it possible to increase the GPS drift tolerance for water sport segments. I'm trying to create some segments along a river that averages 30m in width. Multiple efforts along the same river will not yield a segment match because each route is not close enough to the original. Could strava increase the tolerance for watersports to remedy this?

    0
    Comment actions Permalink
  • I totally agree with KJ Paul de Jong

    I know it may be shocking to some, but there are people who don't look at the Strava leaderboards.  They are out there enjoying the fresh air and use Strava for the maps, for the social aspect and for keeping track of their own data.  

    Is there a way to set "E-bike Ride" as default?  It might help for those new users, who might not realize that an "E-bike Ride" is not the same as a "Ride".

    0
    Comment actions Permalink
  • Once again I want to revisit eliminating live Segments for downhill grades. I've really started to pay attention to what local Segments are live and which aren't, and there are so many grade inaccuracies in your database it's rather ridiculous. 

    0
    Comment actions Permalink

Please sign in to leave a comment.