Allow the community to unflag "hazardous" segments

Quite often a segment gets flagged as hazardous, and it is really anything but.  The workaround has been that cyclists create duplicate segments.  That is frustrating because as a cyclist, I lose the history that was on the flagged segment, and the duplicates get really annoying on an activity as well.  It takes a long time through the support tickets to try to request that a segment flag be removed.  It would be nice if we as users could put in a vote for or against a hazardous segment once it has been flagged.  If it clears a certain threshold (to be determined) then the hazardous flag can be removed.

61

Comentarios

76 comentarios
  • Can someone review why this segment was reported as hazardous?!
    https://www.strava.com/activities/1491508094/segments/37191422856

    0
    Acciones de comentarios Permalink
  • Adam is a troll. He is the person doing the flagging. His account has no followers and follows no one. He doesn't use Strava to ride, he uses it to flag segments. Probably never been on a bike in his adult life. I think this tells you everything you need to know.

    0
    Acciones de comentarios Permalink
  • There are lots of situations where this is ridiculous. In central Iowa there isn't anything that should be marked hazardous really unless you consider the vehicular traffic into the equation, which seems like a moot point honestly. There's no situation where cyclists can control crazy drivers so to label a particular run as 'hazardous' is kind of stupid.

    I just ran across a 2% decline (read hill) in central Iowa that's labeled as hazardous. The only thing that could possibly be hazardous is the intersection it runs through at the bottom, and traffic on both sides is controlled. Then again if they don't pay attention to the stop signs I suppose you could have an incident, then again with people driving 2+ ton motorized weapons you could always have that as a consequence of riding.

    There seems to be a disconnect between this new type of 'nanny state' protectionism and the whole idea of sharing the road. I'm not sure why Strava has gotten involved in it but I will say this, the Segment feature is the primary feature of your application, otherwise I can get activity logging from anywhere, so the logical extension of the fact that Segments is your only real benefit is to make sure that you don't kill those. Allowing hazardous markings without monitoring the reality of those is dangerous, since someone who just rode it and took the KOM could in effect ask to have the segment marked hazardous to preserve their placement as KOM.

    Think twice before you start to police these sorts of things. You clearly don't want to do any policing on the vast number of segments that are redundant, why now have you come forward to police complaints from singular individuals and render judgement based on those singular complaints?

    This seems very contrary to what the normal Strava response would be.

    1
    Acciones de comentarios Permalink
  • East way to beat this (and I think it's absolutely stupid for one person to be judge and jury too).  I complained when one person pretty much zapped all the segments on the Washington and Old Dominion Trail outside Washington, DC.  Strava did squat.  Ride the roads.  Very few flagged segments.  I've pretty much given up on multi-use trails.

    0
    Acciones de comentarios Permalink
  • If and when my favourite rides end up on hazardous segment lists I'll just create another one. Eventually Strava or whoever is doing the flagging will get the message.

     

    1
    Acciones de comentarios Permalink
  • I'll prefix my following example of how I pass a walker from behind when another cyclist is approaching. I slow down, allow the oncoming cyclist to pass the walker and then I announce on your left and carefully pass afterwards. I don't like two bikes and a walker passing at the same time.

    Now for my example. I am approaching an elderly lady walker while an old fart is coming from behind the walker. I move over as far as I can but the old fart instead of waiting just about clips the lady at full speed as she screams at him. As I write this, I now wish I would have turned around and clocked the guy upside the head.

    After the ride I check Strava and of course there are no flybys near the incident. So the old fart was not a reckless Strava user going for a KOM and I did not flag the segment as hazardous.

     

    In my opinion, the whole hazardous flag serves not a single purpose and should be removed.

     

    PS. I am over 50 and the old fart may or may not have been older than me.

    0
    Acciones de comentarios Permalink
  • LET THE COMMUNITY DECIDE!! Also you need to reverse your policy regarding Hazardous segments not being allowed as a GOAL. 

    3
    Acciones de comentarios Permalink
  • 0
    Acciones de comentarios Permalink
  • I feel like it's people who can't stand to see others do better than themselves. Very annoying. You can unhide and then sign the waiver, but with multiple segments it becomes a real pain. 

    1
    Acciones de comentarios Permalink
  • Please tell me why this is hazardous. Is crossing a road classed as a hazard as it is just a uphill run that I have done loads of times. The road is clear and cars are 30 mile speed limit so not going so fast.

    https://www.strava.com/segments/15134293?show_waiver=1

    I am going to edit it and resave it if noone can give me a good answer

    0
    Acciones de comentarios Permalink
  • Can't we all agree that there exist legitimate reasons why a segment should be flagged, and also that the current system is far from perfect and can be abused?

    Not far from where I live is a 1.5 km segment with an average -7% decline. It goes through a residential area with several intersections with no right of way. To compete for the KOM you would have to average over 60 km/h, 10 km/h over the speed limit. I would argue that this is impossible to do in a safe manner. You just have to make a bet that no other bicyclist or motorist is as reckless as yourself.

    But even though I think this segment shouldn't be competed on, I don't think I should get to decide that by myself either. It's not an easy thing for Strava to fix, but maybe a start would be to at least require a minimum number of user reports before flagging a segment, or subject the decision to a user poll.

    2
    Acciones de comentarios Permalink
  • I agree. Here's another one: https://www.strava.com/segments/3262528

    All uphill. No intersections. It's just a nasty little big ring climb which somebody doesn't like.

    0
    Acciones de comentarios Permalink
  • Thomas - Right On! Sounds So Simple! And an easy fix! HOW CAN WE CONTACT STRAVA ABOUT IT?????

    0
    Acciones de comentarios Permalink
  • This may have been mentioned. I checked a couple of flagged segments suggested by a couple of posters. Strava now allows me to see the leaderboard provided I sign a waiver. One click. Those that flag don't click.... and can mosey along safe and secure. Fair enough.

     

    0
    Acciones de comentarios Permalink
  • 0
    Acciones de comentarios Permalink
  • Yeah, I'm fully aware of the waiver.

    What I'm saying is that there is ABSOLUTELY ZERO reason that that should be flagged as hazardous.

    I can post a video of it for proof. It's 200 metres of climbing on a metalled road with no intersections on it. It's of a difficulty where you'd probably be doing 20 to 25kph. My PR is around 25kph. Hardly unstoppable.

    These things should have some kind of checks and balances.

    2
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.

¿No encontró lo que buscaba?

Nueva publicación