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.

S’abonner
21

Commentaires

478 commentaires
  • I recently rode on a tarmac road next to a off road segment. I was recorded as doing the segment and awarded 2 x KOM. I am unable to delete the KOMs without changing the ride to private. I don't wish to do that, but I do want to take out the false KOMs. There should be a way to do this, after all it's my ride and i should be able to delete my recorded effort if it's incorrect.

    2
    Actions pour les commentaires Permalien
  • Samuel C. - I understand what you are saying, but it really wouldn't be possible to separate "winter" and "summer".  First, only some areas on the globe have different winter and summer conditions.  Second, half the work is opposite of the other half, so "winter" in one country would be "summer" in another.  Even in any one location, the months when snow is on the ground varies greatly.  I live in Alaska.  Some years, we are still riding on dirt into late December.  Other years, we have snow in the middle of October.  In the spring, sometimes we are still riding on snow in mid-late April, other years we are back on dirt in March. It also varies a lot depending on what part of the state we are in.  Some places are on snow a lot longer than other places.  It would be impossible to pick a set of dates when to switch from "winter" to "summer" to be able to break down the leaderboard accurately.

    2
    Actions pour les commentaires Permalien
  • I'd like that Strava think about "an alpha stage" for new public Segment. As most athlete interested to some extent in KOM hunting, I'm just frustrated by "far from optimal segment". For instance, most of my demand for Segment Mismatching are related to the pictured segment.

    In green the actual road, in red the segment (that I believe is used as THE pattern to be matched), in fact if the trace was true, one should run in the forest, enter in several private property, jump across 2 fences....

    So the problem is that the mismatch is --to me-- due to the reference used. It annoys me since every time I run in the area I know I should flag the mismatch in order to have it taken into account. However, we can notice that I (and other) went close to the segment, and if we superimpose 3 traces, we obtain this picture

    In fact the trace are relatively consistent ! And a simple trace averaging (a technique pretty used in statistics) could lead to a better consensus trace.

    So :

    1) Some segment use a poorly defined trace, which lead to frustration, lot of work handling segment mismatching, foster other poorly defined GPS trace or, even worst, creation of new, somehow redundant, segment.

    2) Strava have the data to obtain a better consensus trace

    My suggestion would be to create an "Alpha stage" for Public segment. During this stage, the segment would be tagged as alpha, so that athlete would know that the segment could still change, but as community members their run would contribute to the community. Most importantly, during the alpha stage, all the trace matching the segment would be gathered to create a "consensus segment", all the mismatch request, number of athlete running the segment or even the hazard flag, will be counted. At the end of the stage, a final decision from Strava would be delivered with some additional statistics explaining their choices, what is right and what is wrong with the segment.
    I believe, this could enhance the user experience, reduce the number of problematic segment and create another kind of challenge for the community who during a short period could benchmark new Segment.

    2
    Actions pour les commentaires Permalien
  • In the recent example from François G. the fundamental problem is that the Segment was not created very carefully and was subject to GPS drift, meaning not all subsequent Activities will match with it.  It has been suggested that communicating with the Segment creator might be helpful in addressing such issues although it may not always be successful.

    In my local area I became frustrated with a poor Segment that showed it going through a couple of houses and my Activities (on the adjacent road !) only matched about half the time.  I created a new Segment (based on an Activity with no drift from the line of the road) and simply used the same Segment name but with "less GPS drift" added in parentheses.  I then flagged the old Segment as hidden.  I notice that the new version of the Segment is now showing significantly more attempts than the old version, hence indicating the better matching.

    2
    Actions pour les commentaires Permalien
  • I don't have a problem with lots of segments on a route. What is annoying is multiple segments with the same name, and also segments that are not descriptive. Ideally it should describe a start and end, or a nockname for a certain part of a route. But eliminating identical names should be pretty easy to do.  

    2
    Actions pour les commentaires Permalien
  • ''Strava verified segments''

    I am writing because of the story I read on the strava blog. It's the featured story: 10 historic climbs in the Tour de France 2021. In this article they wrote about the climbs and with every climb they linked the segment to it. Well this made me think. It could be nice to see something like 'Strava verified segment'. Now when you take on a climb it's not always easy to find the right segment as a climb is mostly loaded with segments of (part of) the climb. With Strava verified segments it would make it so much easier and so much clearer which segment is the right one. There could be for example a SVS (Strava verified segment) of the Mont Ventoux from Bedoin to the top. The segment could be highlighted with some sort of token in the segments so it's even easier to find in your activity segments. In addition to this it could become a filter on the map when searching for nearby segments to only select SVS.

    Another addition to this suggestion would be that when you complete a Strava verified segment is would be highlighted in your profile. This way you can compare yourself to your friends much easier as to see who has done a big climb and how (s)he did.

    2
    Actions pour les commentaires Permalien
  • is it planned for near future updates that also all achieved top 10 segment results can be seen later on in a list, like all personal koms and local legends? So that we can also see if we drop out of the top 10 at a segment for example and get notifications for that? that would be really nice!

    2
    Actions pour les commentaires Permalien
  • When I go to a segment detail screen from a Friend's activity, I can not see where he stands on the leaderboards. If I have not attempted the segment before, the ranking is empty. (Tapping into the specific leaderboard rankings doesn't show his ranking either)

     

    If I have attempted the segment before, the leaderboards show *my* ranking, but not my friends. (example below). If I tap into the leaderboard, it only shows my placement within the rankings, but not my friend's rank.

    Could this be changed so that we can see the friend's ranking, at least within the ranking page when you tap into the leaderboard (eg, "All Time"). As an example, this way I can see that my friend is 600/2000, and I'm 722/2000 on the All Time ranking, whereas right now I can only see my own ranking of 722/2000.

    Thanks!

     

    2
    Actions pour les commentaires Permalien
  • Erik Bakke Soren This definitely happens with real rides as well. In one recent case Strava did eventually take action, but it shouldn't happen in the first place. If Strava regard the leaderboards as being "user patrolled" then they need to make it less of a headache. It is not realistic for users to make tickets to keep the leaderboards clean, especially if it takes a week to action each one. Hopefully they will finally make auto-flagging actually work, because clearly there are not enough man hours available to do the job by hand.

    2
    Actions pour les commentaires Permalien
  • Can you create a page or a folder for not KOM’s but podiums, ie 2nds and 3rds. Makes a user have a list of ones their close to to strive for = the essence and name of Strava.

    2
    Actions pour les commentaires Permalien
  • Ok! Just seen the post where Strava now suggests politely that an activity might have been on an eBike - NOT GOOD ENOUGH - also needs automatically flagging and exclusion from segments? Currently either their QOM/KOM is still allowed if they never log on and respond OR this algorithm isn’t working else I wouldn’t still be spending so much time flagging…

    2
    Actions pour les commentaires Permalien
  • Michał K. I had a similar problem with a KOM I got yesterday and a friend had one they got this morning. About 3 hours after my friend's KOM this morning, both of ours converted from the PR icon to the crown and showed up on our list. Apparently Strava is having issues with the behind the scenes processing. If I had to guess, I'd say your's will likely appear within 24-48 hours.

    2
    Actions pour les commentaires Permalien
  • Steve Tucker

    I'm not necessarily taking sides, but I think there is an important distinction to make here.

    It may not be the fact that groups have an aerodynamic advantage that Richard is objecting to.

    It may instead be the fact that the leaderboards are filled with large numbers of (near) identical times.

    He may be perfectly happy with the scenario where only one member of the group is recording. It's one thing if a pro comes by and takes the KOM, but if a large group wipes out the entire top 10 and beyond, then it effectively makes the segment pointless for local competition.

    What I would quite like to see is a feature between pure leaderboards and "local legends". Something that rewards people who ride the segment regularly but is still based on performance. For example you could have a leaderboard based on each riders 3rd best time. This would exclude freak events like a Pro Peloton going past or an unusually windy day and instead reward riders who can consistently record good times.

    Also it might be nice if Strava gave more credit for Top 10 results this year. Perhaps a rolling 365 day period might be better to avoid everyone getting KOMs on New Years Day!

    The thing is eventually all segments will be full of amazing times, this will make trophies and KOMs practically unobtainable, this is one of Strava's key selling features. Strava needs to plan ahead and make sure athletes always have reasonable targets and a sense of reward for performing well against their peers.

    2
    Actions pour les commentaires Permalien
  • I support william o's reasoning and suggestions.

    For a possible improvement on that, maybe the leaderboard could require minimum 3 efforts, and post average of the last x # of efforts or the average of the sliding 365, or average best 3 efforts over a sliding 365 - rather than the 3rd best time in absolute.

    2
    Actions pour les commentaires Permalien
  • William O.

    I guess where we differ is in that I don't view a segment as "dead" just because a pro has it.  You can track your progress over time, and being 10th or whatever number against a pro is totally fine.  A digital crown on it's own at that point may just mean you're riding obscure segments.

    Masters compete in bike racing, or ironmans or whatever.  They don't beat pros.  They still are achievers.

    2
    Actions pour les commentaires Permalien
  • It's not a bad idea (and auto-flagging is something that users have been requesting for some time), but it sounds like it might be over-zealous, especially if it cannot be contested. irreversible auto-flagging should not be flagging "unlikely" efforts, but be more conservative and flag "impossible" efforts (ie, faster than world record pace, 1 minute mile runs, etc)

    2
    Actions pour les commentaires Permalien
  • The auto-exclusion of "infeasible" efforts could be a good improvement, although it clearly needs to take account of gradient (both positive and negative) in determining maximum feasible speeds.  Maybe the algorithm could also be tweaked based on feedback from "trusted" users ?

    Hopefully once the bugs are worked out it can be applied retrospectively to old Activities and not simply used for new ones.

    I recently created a new Segment - after allowing Strava time to populate the leaderboard with old Activities, I had a look to see if I was close to the KOM.  It was a little de-motivating to see the KOM had an average speed of 113 mph !  Hopefully the new algorithm will remedy such data issues. 

    Keep up the good work !

    2
    Actions pour les commentaires Permalien
  • Worst forum i have ever been.

    I can not believe the way it works.  If you want to comment a post in the first page, you have to write 11 pages later...

    Do you think with this forum some can follow a topic?

    2
    Actions pour les commentaires Permalien
  • Cesar Corral 🇪🇸 I fully agree, we have a great contender at the title of worst forum ever.

    Note :

    1. Less than one year old and already a real mess
    2. No more then 21 subscribers to sub-topics
    3. Ironically, a lot of the point raised in forum receive no clear answer...while in fact new feature fixing these points have been added over the year in Strava !

    So the problem is not only the forum, but also the way relation to its users is managed

    And by the way...https://support.strava.com/hc/fr/community/posts/360073566191-Feedback-about-our-Forum may be the correct place to report this !

     

    2
    Actions pour les commentaires Permalien
  • Jason Lamoreaux  I don't think it matters where we post.  I looked to see when the Strava folks who set-up the forums last posted and its been quite a while.  I think we users are all just talking to each other...  I think you may be the most active of all.👍

    2
    Actions pour les commentaires Permalien
  • I would like to see more age categories. Now there is no more categories past age 75.

    Those of us over 80 or 90 ate competing with 75 year old's and it does make a huge difference

    2
    Actions pour les commentaires Permalien
  • In the mobile app (I'm on iOS), when looking at someone else's activity, if I tap into a segment, I would like to see how my ranking compares to theirs. Eg, they are 1000/10000, and I am 800/10000.

    Currently, in the segment detail page, it shows my friends time (for the current ride, and their PR), and my own PR below that. However, when you scroll down to the leaderboard, the ranking is my own.

    If i then tap into a leaderboard like All-Time, only my own ranking is show (below the top10). It would be great if, at the very least, this leaderboard would show my friend's ranking as well. So it would have the Top 10, my ranking, and my friend's ranking. This is useful to see how my friends and I stack up compared to everyone else.

    Thanks

    2
    Actions pour les commentaires Permalien
  • I didn't read this entire thread, but I know it was mentioned at least once: Virtual rides and their KOMs and leaderboards are littered with bogus inputs. I've seen multiple rides where the wattages too low to achieve the indicated speeds for the uphill grades of the segments. Either the rider is changing their weight to be 1 lb or they are changing the grade to be 0%. Example: https://www.strava.com/activities/1318667888#32639183162 

    This rider managed to virtually ride Col e la Madeleine, one of the toughest climbs in the Tour de France,  with an average speed of 20.3 MPH while only expending an average of 169 watts. The only way that is possible is if the rider was weightless or the grade was flat. As a comparison I completed the ride expending an average of 211 watts and only went 8.5 MPH.

    So I tried to Flag this ride, but that was denied since it had already been flagged and resolved. I'm really curious what the resolution was.

    Strava could use a simple algorithm to detect and eliminate this sort of data so users don't have to deal with it.

    2
    Actions pour les commentaires Permalien
  • When looking at a segment leaderboard the following period related options are: All-Time, Today, This Week, This Month, This Year

    Please add: Yesterday, Last Week, Last Month, Last Year

    2
    Actions pour les commentaires Permalien
  • Sometimes riders get unreal data from their ride, some of which result in KOMs. The rider acknowleges the unreal KOM. However, there is no way for the rider to easily flag the unreal KOM so that Strava can fix the issue. I think most people would want to remove their unreal KOMs but there is no easy way to do it. As a result, people just leave it the way it is.

    Maybe Strava can include a button for the KOM holder to flag the unreal data which will automatically remove the entry from the leaderboard.

    2
    Actions pour les commentaires Permalien
  • Is there not some way Strava can detect e-bike rides automatically and make the app ask the user "is this an e-bike ride?" before it uploads to the leader boards?

    Surly some formula can be applied where it compares climbing times to flat and descent times to estimate the likelihood of it being an e-bike ride and automatically remove it from leader boards unless the user declares it is legit (a one off hill effort for example), maybe also factor in HR data if available too?

    I see so many people top 10 a fire road climb at 130bpm then ride everything else at mediocre pace. I don't think most people are being willfully dishonest, it's likely they just don't know you can change the ride type etc. At least this would automatically weed out most e-bike rides from the league tables. A simple algorithm must be possible surly?

    2
    Actions pour les commentaires Permalien
  • Greg Scott 

    "Why would the segments not carry over to e-bike"

    perhaps because e-bike rides are a different activity, just like running or walking is different to cycling. Run segments are not carried over to other activities either, why should they ?

    A lot of segments in some areas are just garbage anyway, would n't it be better to start with a clean slate and make your own segments best suited to e-bikes ?

    2
    Actions pour les commentaires Permalien
  • @Andrew Paterson

    This thread has many many obvious modifications to Strava that benefit large swaths of the user community, and they don't even do those.

    So the answer to your question might be apathy, or it might be the same as why a restaurant choses to serve the food they want, not the food you want.  It's a private business under no obligation to do other than what they like, as long as it's within the law.

    2
    Actions pour les commentaires Permalien
  • Greg Scott - From what I have seen from their requests, it is not necessarily that those asking for cani-cross or other similar activity types are asking for a leaderboard for their activity.  They are just looking for their own activity type designation so that their activities don't get incorrectly mixed into the leaderboards of regular unassisted activities like running or riding.  I can see three clear activity types, cani-cross (running with a dog), dog-joring (biking with a dog), and ski-joring (nordic skiing with a dog).  If these were to have their own activity types, people would not be recording them under the unassisted acitivity type and incorrectly taking course records or KOMs.  

    2
    Actions pour les commentaires Permalien
  • Allow comments and photos on segment pages

     

    It would be great to make the segment pages real pages and allow people to both comment (with some upvote/downvote system?) and to add photos.  Could also just automatically use photos that people have publicly uploaded while on that segment. 

     

    My main reason for this is safety.  When exploring a new area or trying to help a friend in a different area plan routes, it's hard to tell if a road is dangerous, or if it's boring and filled with traffic, or if the pavement is a bit dicey.  Right now for this I generally look at strava segments and then jump over to google maps streetview.  This is kind of ridiculous - you have TONS of very useful photos, and I'm sure people would quickly add lots of helpful comments (potholes to watch out for, car/traffic warnings, good places to stop for food/water/etc).  

    2
    Actions pour les commentaires Permalien

Cette publication n’accepte pas de commentaire.