The case for Idaho Stops

Our Community Forums General Discussion The case for Idaho Stops

Viewing 15 posts - 1 through 15 (of 44 total)
  • Author
    Posts
  • #915281
    sethpo
    Participant

    One of my colleagues (unbeknownst to me ahead of time) wrote a great article today making the case for Idaho stops being legal.

    http://www.vox.com/2014/5/9/5691098/why-cyclists-should-be-able-to-roll-through-stop-signs-and-ride

    Ultimately, a cyclist occupies a space somewhere in between a pedestrian and a car (faster and more dangerous than the former, but smaller and slower than the latter), so the laws that apply to bikes should be somewhere in between — exactly like the Idaho stop.
    #1000709
    mstone
    Participant

    I’d actually argue that idaho stops should be legal for self-driving cars, also. The elephant in the room is that people driving cars simply aren’t as aware of their environment as they think they are, so they simply need more of a stop to compensate. It makes no sense to apply the same standard to anything that lacks that same awareness gap.

    #1000713
    brendan
    Participant

    This is probably the best article written about the concept that I’ve encountered. That said, to fully flesh it out, I think it should also include an additional discussion about any changes to bike/pedestrian interactions that may arise (hopefully positive, but…). I say this mostly because the ad hoc idaho stop behavior I’ve seen in DC, esp. on group rides, has often been pedestrian-unfriendly.

    EDIT: also, I like comparing stopping a bike at a stop sign/red-light to turning off your car and putting it in park at every stop-sign/red-light, then starting it up again and putting it in gear when you are clear to proceed.

    #1000714
    sethpo
    Participant

    My one quibble with it (which I am going to discuss w/ Joseph) is that he doesn’t address the cyclist safety reasons for running lights. There are numerous times when I feel safer going through an intersection early.

    #1000717
    brendan
    Participant

    By “running” lights, do you refer to a) proceeding through a stale yellow or fresh red, b) proceeding through a stale red, c) slowing for a red but rolling through if clear or d) stopping for a red and proceeding if clear (Idaho Stop)?

    “Running lights” is a loaded term, so just asking to clarify…

    #1000718
    cyclingfool
    Participant

    @sethpo 84774 wrote:

    My one quibble with it (which I am going to discuss w/ Joseph) is that he doesn’t address the cyclist safety reasons for running lights. There are numerous times when I feel safer going through an intersection early.

    In addition to cyclist safety, it can be very beneficial to drivers, too. Along the Alexandria portion of Potomac Avenue, which I ride as part of my daily commute, I routinely slow/stop and then roll through red lights at all the T intersections (many to still closed/unopened roads). By getting out ahead of the clumps of cars that accelerate from the lights, I give them time to come to speed and sort/merge themselves into the left lane to easily pass me. If I waited and went with the light, there’d be a whole column of cars stuck in the right lane behind my 12-15 mph pace struggling to merge over.

    #1000722
    sethpo
    Participant

    @brendan 84778 wrote:

    By “running” lights, do you refer to a) proceeding through a stale yellow or fresh red, b) proceeding through a stale red, c) slowing for a red but rolling through if clear or d) stopping for a red and proceeding if clear (Idaho Stop)?

    “Running lights” is a loaded term, so just asking to clarify…

    Personally, I mean “d” the Idaho stop. On occasion on empty roads it might be “c” but the difference between “slowing” and “stopping” on a bike is fairly negligible. But good point about the term “running” lights. Lazy language by me.

    #1000723
    Steve O
    Participant

    @cyclingfool 84779 wrote:

    In addition to cyclist safety, it can be very beneficial to drivers, too. Along the Alexandria portion of Potomac Avenue, which I ride as part of my daily commute, I routinely slow/stop and then roll through red lights at all the T intersections (many to still closed/unopened roads). By getting out ahead of the clumps of cars that accelerate from the lights, I give them time to come to speed and sort/merge themselves into the left lane to easily pass me. If I waited and went with the light, there’d be a whole column of cars stuck in the right lane behind my 12-15 mph pace struggling to merge over.

    I posted this on the Arlington improvements thread, but it relates directly to your behvaior at the T intersections, so I thought I would re-post here.

    @Steve O 76389 wrote:

    This is not so much a fix as an improvement that makes sense and also elevates cyclists in the transportation hierarchy.

    At locations that are T-intersections with lights, provide a separate “through” light for cyclists traveling opposite the T. Some examples include:

    – Wilson w-bound at Pierce (by the Fire Department). Since cyclists are on the far right, they do not really need to stop for cars entering from Pierce. Flashing yellow for cyclists might be appropriate to accommodate peds.

    – Wilson w-bound at Courthouse (by Ireland’s Four Courts). Same thing. Adjustments to how the parking is designed here would help. Also, perhaps flexible bollards to delineate where the cyclists are, to prevent wide turning cars from straying into the bike lane

    – Military s-bound at Marcey. No reason to stop here on red if cyclists can just keep the right lane. May not even need a separate light, but just a sign, “Cyclists may proceed on red with caution; yield to pedestrians”

    In fact, all three of these locations could probably be accommodated with signage, some paint and maybe some flex bollards, which would be cheaper than designing and installing separate bicycle signals.

    FYI – I already “Idaho stop” these locations, even though I fully observe the red lights at all the other Wilson/Fairfax Dr. intersections. It’s because these lights are senseless for the cylist in the same way they are senseless for the peds on the adjoining sidewalk.

    There are probably more of these around. Anyone?

    Part of the point here is not that these changes would make an enormous difference in travel times for cyclists (one staff member asked me, “What problem would this solve?”). The point is more that it provides a visible advantage to cyclists in a completely safe and appropriate way. Observers who note this may be inclined to think:
    “Wow, that’s cool. The County is doing a good job improving cycling infrastructure.”
    “Hey! Maybe I should ride a bike, too, if I can get a special light just for me.”
    “WTF! Now those radical cycle lobbyists are getting even more special treatment. Time to run one over.”

    On balance, I hope the first two sentiments would outweigh the third.

    #1000726
    dasgeh
    Participant

    I wonder if this wouldn’t be politically more acceptable (and easier for drivers to understand/not oppose) if we explained it as:

    1) “stopping” for bikes is defined as anything under 3 mph (I pulled that number out of the air, but basically, really slow); and
    2) cyclists should be allowed to go through a red light, after “stopping”, if there are no cars coming/stopping in conflicting lanes.

    In practice, I think #1 gets you exactly the same behavior as the Idaho stop sign policy, but it’s an easier sell than “cyclists get to treat one kind of sign as another kind of sign”.

    As to #2/the red light issue — around here, I think simply saying that bikes should treat red lights as stop signs is tricky, because there are lots of fairly travel patterns that are not obvious to a cyclist stopped at a light. Take, for example, Penn Ave and Constitution (just east of 6th). When a cyclist is headed east in the cycletrack and has a red light, for part of the cycle (let’s just say it’s the first part), the traffic from Constitution has green, and for the other part, traffic turning left onto Constitution has green. A cyclist can’t see the signals for these other directions, so they can’t know which has the green or is about to get the green. Imagine a seen where: a cyclist pulls up to the intersection while Constitution has green. There’s a car waiting to turn left onto Constitution, but no cars coming from Constitution. But, as the cyclist starts to go through the intersection, the signal changes and the left-turning car now has green. These are large intersections, so you can really see disaster. My #2 above would address this situation, because the cyclist wouldn’t be allowed to go if there are any cars in conflicting positions. If, in my example, the car turning left gets through the intersection, and no other cars come, so there are no cars at the intersection, then the cyclist could go through the red.

    I hope that makes some sense.

    #1000733
    mstone
    Participant

    @brendan 84778 wrote:

    By “running” lights, do you refer to a) proceeding through a stale yellow or fresh red, b) proceeding through a stale red, c) slowing for a red but rolling through if clear or d) stopping for a red and proceeding if clear (Idaho Stop)?

    “Running lights” is a loaded term, so just asking to clarify…

    Yes, please don’t use that term. It’s so vague as to be without meaning.

    #1000734
    mstone
    Participant

    @dasgeh 84788 wrote:

    As to #2/the red light issue — around here, I think simply saying that bikes should treat red lights as stop signs is tricky, because there are lots of fairly travel patterns that are not obvious to a cyclist stopped at a light.

    Yeah. There are some lights that I’m just not going to sit at (suburban car-sensor lights on empty streets) and other lights where it’s never going to be safe to go. I don’t know that there’s a practical way to distinguish the two from a legal standpoint. (And sometimes the same light fits either case, depending on the time of day.) Would it be sufficient to simply permit the behavior and hold the cyclist responsible for misjudging? (I tend to think, probably, yes–I’ve already got all sorts of incentive to not be run over, a ticket doesn’t really change the calculus.)

    #1000736
    jrenaut
    Participant

    After reading Wash Cycle’s point about the comparison with right on red, I finally read this article, and it reaffirms my feeling that Idaho Stops, just like right on red, should be illegal anywhere you’d reasonably expect to see a pedestrian. Right on red is terrible in crowded cities – it just lets cars bully pedestrians in the one section of the street that’s really supposed to belong to walkers, not cars. Bringing in the Idaho Stop would just let bikes bully pedestrians, too.

    Both laws are fine for Idaho and places with low population density, or suburbs where the infrastructure is already so hostile to pedestrians that they don’t bother getting out of their cars.

    #1000737
    americancyclo
    Participant

    @mstone 84796 wrote:

    hold the cyclist responsible for misjudging?

    Isn’t this what ‘contributory negligence’ amounts to?

    #1000739
    lordofthemark
    Participant

    @jrenaut 84798 wrote:

    After reading Wash Cycle’s point about the comparison with right on red, I finally read this article, and it reaffirms my feeling that Idaho Stops, just like right on red, should be illegal anywhere you’d reasonably expect to see a pedestrian. Right on red is terrible in crowded cities – it just lets cars bully pedestrians in the one section of the street that’s really supposed to belong to walkers, not cars. Bringing in the Idaho Stop would just let bikes bully pedestrians, too.

    Both laws are fine for Idaho and places with low population density, or suburbs where the infrastructure is already so hostile to pedestrians that they don’t bother getting out of their cars.

    Well that would be just fine for me, as those are pretty much the places where I do an Idaho (at the stop signs, not the reds). Heck, there are places with stop signs where there is nowhere for a pedestrian to walk to https://maps.google.com/maps?q=Little+River+Turnpike,+Lincolnia,+VA&hl=en&ll=38.832237,-77.205649&spn=0.000001,0.0006&sll=38.893596,-77.014576&sspn=0.37089,0.614548&oq=little+river&t=h&hnear=Little+River+Turnpike,+Lincolnia,+Virginia&z=21&layer=c&cbll=38.832237,-77.205649&panoid=zXCDFMXCrUUlbB5jG7RkwA&cbp=12,278.39,,0,0

    So either leave the law as is but implement Idaho by exception with signs, or change the law to Idaho but add exceptions to it by signs (as we do with right on red)

    as for feeling that right on red should be illegal anywhere there are pedestrians, given that we can’t seem to get it removed at some place like the intersection of doom, a place with a huge number of cyclists and peds and a demonstrated safety issue, I am skeptical that the law will change in any major jurisdiction. I think the fear that an Idaho Stop law will justify the right on red law is, therefore, not a reason to oppose Idaho, because right on red is a fact of life.

    I think mentioning right on red is quite apt – it does not prove that idaho is safe (other data does that) it merely points out that there is precedent for making a change for the purpose of addressing energy use issues.

    #1000740
    mstone
    Participant

    @americancyclo 84799 wrote:

    Isn’t this what ‘contributory negligence’ amounts to?

    No, what I’m talking about would give specific permission to go (so it can’t be ticketed) but still require the cyclist not to go unless the way is clear (retaining the liability). Currently we have the liability, and as a bonus we can also get ticketed whenever somebody decides to do a street smart campaign.

Viewing 15 posts - 1 through 15 (of 44 total)
  • You must be logged in to reply to this topic.