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
21

Comentários

478 comentários
  • Why is it because it is a sport you do not take part in it is considered trolling? If you do not know what canicross is then just do a search and try and educate yourself.

    As a community there are many groups that take part, but not represented properly, and all we are asking for is some way that Strava recognises an activity type so it doesn't annoy other runners. At parkrun, for example, canicrossers were breaking course records all over the place, and now assisted runs can be marked as so.

    Ben Robinson, a UK canicrosser, holds the world 5k record in a time of 12:24 over cross-country, you can read about his achievements in a wide range of press such as Runners World and even breaking out into non-sporting magazines like GQ.

    The UK governing body, BSSF, has been lobbying Strava for a few years to get cani-sport recognised - yes we do actually have a governing body. UK athletes go to to Europe and the USA to compete in championships.

    So if assisted categories like eBikes can be recognised, then why no assisted sports like canicross getting recognised? It might not be on your priority list because you do not do it, but for a great many others it is.

    1
    Ações de comentário Permalink
  • Take no offense I was just saying it’s not something I have heard about. I’m glad you are so passionate for it. I also believe yeah.. strava should create that as an activity type. If they have CrossFit, velomobile, and stand up paddler. They should definitely have canicross. Would be a great leaderboard!

    1
    Ações de comentário Permalink
  • I apologize for flagging same issue that has been raised in previous comments. It saddens to see that issue with unrealistic results in leaderboards isn't detected and sorted out. I keep noticing ebikes or other obviously motorized vehicles recorded as traditional rides. Leaderboard is full of them and no way any traditional cyclists will ever get there as we don't climb with 60km/h speed. It is too much work to flag each activity one by one; and this is example of one segment only. Detecting such abnormal records should be pretty straightforward isn't it? Makes the leaderboard meaningless 

    1
    Ações de comentário Permalink
  • Jason Lamoreaux Strava have to draw the line somewhere, there are dozens if not hundreds of fringe "sports" such as canicrossing, (or Eric Bakke's ice yachting :-)  ) whose participants probably think their sport is big, but when you think that Strava has well over 75 million accounts and adding many more each month, canicrossers would be about 0.003% according to what Google says is the number of active participants and assuming every one of them signed up for a Strava account (unlikely). That number is insignificant and just not commercially important. Strava is, after all, a commercial operation.

    And then there is the animal rights/PR angle ....canicrossers might say that no dogs are overworked but it would only take one rogue participant to step over the line in pursuit of a KOM and Strava could have bad publicity and even a lawsuit. They dropped the live downhill cycling segments because somebody had a crash chasing a downhill KOM and tried to sue Strava for encouraging dangerous practices. Strava would probably want to stay well away from any possible bad animal welfare publicity.

    1
    Ações de comentário Permalink
  • Yulia Mironenko There are segments in Strava that, by some reason, get unrealistic times for most of the riders. They are not cheating and their rides must not be flagged. 

    Look at this, for example. If you open the activities of the top10 riders you see that their speeds in other segments are "normal", but in this particular one they get 100 kmph!!

    1
    Ações de comentário Permalink
  • Auto flagging doesn't always work but I would love to be able to flag a segment-effort as unrealistic or dangerous.

    Like this segment: https://www.strava.com/segments/2070803?filter=overall . This section of road has a bike path next to it and the road itself is prohibited for cyclists. The road is faster than the bike path next to it so most fast efforts are on the road and not on the bikepath.

    Autoflagging doesn't help because there are some efforts which were done during a competition, so they should be allowed. Others should be flagged. The big problem (for strava) is that people go 'KOM-hunting' on dangerous roads which could end up in Strave being blamed for accidents.

    1
    Ações de comentário Permalink
  • FEATURE REQUEST:

    All the athlete to select the age-range he/she is interested in.

    Examples:  

    • If I'm 64.5, I might want to see how my performance stacks up against those 65-70.
    • If I'm 85, I might not want to compare myself to everybody over 75  (80 means more)

    How about creating filters that the Athlete can control when looking at the leaderboards.

    • Filter by age range (athlete can select min and select max, rather than fixed ranges)
    • Filter by sex
    • Filter by weight (athlete selects min/max, rather than fixed ranges)

     

    Also, I do agree with the previous posters, that suggest it would be nice to see the age of the KOM.

    1
    Ações de comentário Permalink
  • Although I would like to have a flexible query tool to filter leaderboards, I think just having a “Last Three Years” (or 4 or 5 years) selection option would resolve some of the complaints I have read. It would not affect the “All Time” leaderboard, but would give a better idea of how active athletes are performing than the “Current Year” selection, which is fairly useless until later in a year. If pro-level riders race on a segment, their times would eventually drop off a “Last Three Years” selection, without requiring complicated filtering.

    1
    Ações de comentário Permalink
  • Please bring back "today" "this week" and "this month" leaderboards. First, they are a great way to see if a trail is open and running as the spring melt hits. Second, especially the "today" leaderboard is great for comparing among a group of friends or to see how you stacked up on that day's conditions. Third, trails change. Thanks.

    1
    Ações de comentário Permalink
  • Jan Nielsen - maybe I'm lucky, but in my area there are lots of Segments (I've completed more than 5,000) and I think less than 1% have fake results.  There are occasionally examples where some data looks suspicious but these can often be resolved fairly easily - for example, a couple of days ago an inexperienced athlete who previously cycled at 8-10 mph set 10 KOMs in one ride at sustained speeds of 35 mph.  I politely asked if it was a genuine ride and he quickly replied to say he was using Strava to measure his commute by bus (and he deleted the Activity).  I also sometimes see rides at 15 mph that end with a couple of miles at 40 mph - clearly because the athlete forgot to stop Strava at the end of the ride - again these can usually be resolved with a polite message to request the athlete crop the activity.

    1
    Ações de comentário Permalink
  • Jan Nielsen - If you see results in the leaderboards that you feel are "fake" for whatever reason, just flag them and they will be removed.  I do it all the time when I see obvious e-bikes or just someone who forgot to turn off their GPS at the end of a ride and took some KOMs on the drive home.  It is pretty simple from the desktop platform.

    1
    Ações de comentário 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)

    1
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário 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
    Ações de comentário Permalink
  • Ian Barton (sorry don't know how to tag people).

    "Something I prefer" is not the purpose. I'm in a group of people managing a small trail center. I would say 80-90% of the segments at this center are corrupt in terms of gps, out of date since we changed the trails or just duplicates or to short to make any sense at all. For me it's no problem, I know which segments are the correct ones. For visitors not riding there frequently, it's just causes confusion with all the bad or out of date segments. Hiding them yes can be done, but how to know which ones to hide if there are 4 of the same and you ride the place for the first time? Most things would easily be solved by deleting the old or bad segments. I think this would be done in 95-100% of the cases if the segment creator could be messaged, made aware of the problem and asked to delete a segment he or she created. Now all bad or corrupt or duplicate segments are floating around like old satellites in space and it annoys me that it could be solved so easily by allowing communication with segment creators. They can still be anonymous if they like.

    1
    Ações de comentário Permalink
  • In addition to recognizing all-time KOMs and QOMs it would be really cool to see cyclists recognized within their age groups with Age group specific QOMs and KOMs. This would create more interest and competition among aging cyclists. It would incentivize older cyclists and even perhaps some younger cyclists to ride more.

    For example, I am 71 years of age. The playing field is stacked against me when measuring my performance against cyclists in their 20s, 30s, 40s, 50s, or even in their 60s. This is disheartening and, is most likely, responsible for many aging cyclists loosing interest and quiting cycling altogether. But if there were age group specific QOMs and KOMs I am convinced cyclists would enjoy having their fastest times in their age group recognized by the cycling community. 🚲

    1
    Ações de comentário Permalink
  • Carlos Vigo Your request is still the most voted and there is not a single Word from Strava.

    https://support.strava.com/hc/es-mx/community/posts/360073465872/comments/360013091092 

    While Strava don't pay attention,  the number of ebikers are growing fast and most of them save their activities as normal bikes because they want THE SAME SEGMENTS WITH DIFFERENT LEADERBOARDS.

    And by other hand standard cyclist are loosing interest in Strava as the segments are contamined with ebikes.

    This situation remember me when Nokia didnt pay attention to Android and they fall from the sky to hell in months 

    1
    Ações de comentário Permalink
  • Mike Nottingham - It is true that age group results can be filtered. However, virtually nobody is going to filter a segment by age group outside their own age group. Hence, for the most part, the only cyclists that will be aware of age group results are cyclists in their own age group. The idea of age group QOMs and KOMs is to let other cyclists outside your age group of your accomplishments.

    1
    Ações de comentário Permalink
  • Is there a mechanism to deal with riders posting ebike rides as regular rides besides flagging.  There are riders I know who have been flagged 100 times but still post rides and take places on leaderboards.

    1
    Ações de comentário Permalink
  • Stuart Fealk - Yes, there is.  For something like that, us the "Submit a request" link at the bottom center of this (and other Strava) page.  In there, just click on the option to look for more answers a couple times, then submit a report via e-mail once prompted with an explanation of what is going on.  Make sure to point out that it isn't just a few instances, but a systematic issue.  I've done this multiple times and the Strava support people were able to take care of the problem.  I believe they either suspended or removed those people ultimately.

    1
    Ações de comentário Permalink
  • Segments or challenges are great ideas, but the reality at Strava is a lot of disappointment!

    E-bike riders or car drivers cheat cyclists, cyclists cheat runners, runners cheat walkers, etc, etc. And it's that easy: just select a wrong (lower) activity type and you're in first place or KOM/QOM of a segment.

    The same applies to challenges where people are at rank 1 having walked 30000 km in 10 days.

    Flagging is not of any help. As long as this is possible at Strava and is not punished, I will never become a paying Strava member. 

    1
    Ações de comentário Permalink
  • Jason Lamoreaux

    Hi Jason - I appreciate your recent comments.  Clearly I can only comment on my own Strava user experience which I accept could be quite different to that of others.  I live at the edge of a town in the North of England, a few miles from the sea.  There are quite a few old rail lines that have been converted to cycle paths.  Hence I can start an Activity from my house and easily ride on country lanes, explore urban areas or ride to the coast.  This is enough to keep me interested.

    I use the VeloViewer companion program to Strava (veloviewer.com) - this gives a lot more options for analysing performance data and, for example, downloading it to a spreadsheet (there's a small annual fee but it's well worth it).  VeloViewer shows I have done about 900 bike rides in the last 4 years (4 per week) and attempted about 5400 Segments (excluding the 300 I have hidden due to duplication or being badly created).  92% of the Segments I have done are within 10 miles of my house.

    Each week VeloViewer scans all my old Activities for any new Segments - I can then decide if I should hide them or add them to my "to do" list.  Recently there have only been 2 or 3 new Segments per month, perhaps suggesting that the area is saturated and every road and path is already part of a Segment.  Hence proliferation of poor Segments is not a problem.

    Each week Veloviewer also checks all the Segments I have attempted and reports any changes in my position on the leaderboard.  This then gives targets, for example, to try to get back a KOM (I find I only get notifications from Strava for about 60% of the KOMs I lose).

    Veloviewer also allows me to sort Segments based on their KOM speed - this is useful to highlight bad GPS data or use of a vehicle.  There are usually only a couple of outliers and they tend to be very recent Activities - I therefore conclude that other people are doing a good job of keeping the leaderboard reasonably clean.

    Overall I'm very satisfied with my Strava user experience (as augmented by VeloViewer), with the exception of the recent increase in the minimum length of a bike Segment from 300m to 500m, but that's another story 🤨

    1
    Ações de comentário Permalink
  • Ian Barton, Jason Lamoreaux

    There is definitely an issue with poorly made segments and I really don't think it is an insurmountable problem to appoint some local moderators based on various criteria. I would see this as a group of people who would vote on matters rather than a single all powerful individual. Maybe the whole top 10 local legends just as an example, that would keep a bit more consistency and also spread the work around.

    I don't think there need be any alarm over removing segments. I would suggest that nothing is removed, but made private instead. Although I also really like Ian's idea about "validated" segments (or I might term them "community" segments).

    You could make these validated segments more special. These would be calculated first by Strava servers. You could say that you only get a XOM on these segments and others you get a 1st Trophy. Strava could apply more thorough checking on these segments for ebikes, vehicles, GPS errors, etc. Also the local moderators could apply a bit of human level checking on these.

    1
    Ações de comentário Permalink

Publicação fechada para comentários.