PROS AND CONS OF BIKE LANES – 15 years ago

Just found this encapsulated in one of Michael Bluejay’s constellation of web pages and thought I should copy it back here since I wrote it… and it holds true today just as much as in the early aughts. I sure did like numbered lists back then, huh?

Source: https://bicycleuniverse.info/bicycle-lanes-no-brainer/

PROS AND CONS OF BIKE LANES

There are no good studies proving that bike lanes or wide curb lanes are better than the other. ALL theories you hear on which one is better are resting on somebody’s opinion. [Updated, Feb. 2007: A few months ago, a study did come out which claimed to show a non-trivial safety enhancement for marked bike lanes vs. wide curb lanes.]

then some more text by me:

I’m one of the people who thinks we overprescribe bike lanes, but it bugs me that so many Forsterites are so hostile to them in general. Both bike lanes and wide curb lanes have their place.

I’m operating under the assumption that we’re comparing bike lanes to wide curb lanes; not narrow curb lanes. The theory that we can reengineer the 98% of Austin that needs it to a grid pattern like Hyde Park where we don’t need EITHER facility is just ludicrous.

My general feeling on when bike lanes are appropriate:

  1. Where there are lots of inexperienced bicyclists
  2. Where speed differential is fairly high
  3. Where volume of bicyclists is very high

My general feeling on when wide curb lanes are appropriate:

  1. Where speed differential is lower
  2. Where bicycle volume (all types) is moderate to low

Where not to put bike lanes:

  1. Low-speed or congested roadways where turning volume is very high
  2. Residential streets (NOTE: DESPITE NEIGHBORHOOD MISREPRESENTATIONS, “RESIDENTIAL STREET” IS A CATEGORY OF ROADWAY SEVERAL LEVELS BELOW SHOAL CREEK BOULEVARD).
  3. Where they can’t be swept or otherwise maintained
  4. Where you can’t commit to “no parking”.

Things I believe that are PROs for bike lanes:

  1. Bike lanes attract new cyclists; wide curb lanes do not. I think this is self-evident. Patrick agreed, and so do most people who actually work in the field (not the people who commute and criticize; but the people who are paid to try to increase cycling in their particular city).
  2. No amount of education so far has been able to match up against the bike lane stripe as a way to get people out on their bikes. Of course, this may be a good thing if you think we don’t need more uneducated cyclists out there.
  3. You can’t attract new cyclists to a road like Jollyville without a bike lane stripe. Period. The automobile traffic moves too fast. A wide curb lane simply doesn’t provide the space that new cyclists think they need in a way which makes sense to them, coming from the world of the automobile. (We don’t make the right-hand lane up a hill twice as wide so trucks can pull to the side; we stripe another lane).
  4. If you accept riding on shoulders on 360, you should accept riding in bike lanes on Jollyville. The argumentative convulsions some Forsterites go through to defend shoulders from the same logic they use against bike lanes are breathtaking. (They do this, I think, because they know that even most Forsterites don’t want to share a lane at 65; the same anti-bike-lane reasoning with a few exceptions would logically apply to shoulder-riding).
  5. Most cyclists for whom bike facilities are built are not the expert cyclists that you and I might be. They are instead the novice cyclist that I used to be (and presumably you used to be).
  6. Even on low-speed roadways, utility for the population AS A WHOLE sometimes demands the channelization of low-speed traffic. For instance, Speedway and Duval north of UT – car speeds are 25-30; bike speeds are 10; this isn’t normally enough speed differential to justify separation, but the volumes of cars and bikes are both high, and the corridor’s thoroughput for both cars AND bikes is thus improved by partial separation of the modes.
  7. (this is from the link I gave a few days ago) – it is possible to have a better average passing distance on a roadway with a wide curb lane, but still have a better overall level of safety in passing distance with a bike lane. Whether this happens in practice is debatable – but it is a fact that you shouldn’t use “average passing distance” to compare the facilities.
  8. The idea (stolen from a semi-Forsterite) that we can easily get roads restriped with wide curb lanes is in reality not true. If you want space for bikes to be taken from car lanes, it generally has to be a bike lane. (I don’t know why this is, but it seems to be true, although Austin has an exception or two here).

CONS for bike lanes

  1. Car drivers do tend to think you need to stay in the bike lane (even when obstructed, unsafe, whatever – they usually can’t see the obstruction). Also, car drivers often think you should only ride on roads that have bike lanes. This problem exists with wide curb lanes too, by the way.
  2. Bike lanes are theoretically more obstructed than wide curb lanes. I don’t believe this to be true, but most people do, so I’m listing it here. For instance, Bull Creek doesn’t seem any less obstructed north of 45th where there are wide curb lanes. In Austin, at least, BOTH facilities need vast amounts of sweeping which they’re just not getting.
  3. Sometimes cyclists will stay in a bike lane when they need to leave it due to an obstruction or intersection approach. This is a sign of bad bike lane design in most cases and can be overcome, but is hard to get right, judging from how often it’s done wrong.
  4. Sometimes cyclists will stay in a bike lane when they should be leaving it to turn (the “turn left out of the far right lane” phenomenon). The problem here is that I see this happen on wide curb lanes fairly often as well. The only solution here is heavy enforcement.
  5. Bike lanes supposedly encourage wrong-way cycling. (Whatever happened to painting arrows, by the way? Jollyville didn’t get them…) – again, I see this often with wide curb lanes too. Heavy enforcement and more arrows.

Protected bike lane on Guadalupe: Threat and menace

I rarely write about cycling any more and don’t have time to do so right now, what is ed but thankfully I came across a recent post by another blogger which captures, melanoma very insightfully, all of the problems with this facility except for the “hundreds of pedestrians crossing the bike lane to get to their bus stop” issue.

It’s from a blogger I never read before: Off The Beaten Path, excerpt:

Any barrier that separates the cyclist visually from other traffic effectively hides the cyclist. This is counterproductive to safety. Moving cyclists out of the roadway altogether, on separate bike paths, is even more dangerous, because drivers don’t look for (or cannot see) cyclists off to the side.

There’s much more, including great images which really make the point well.

Article link here: Bike To Work 3: Separate Or Equal?

SCB: Speed Is Not The Problem

A lot of folks (especially Stuart Werbner and Preston Tyree, who normally do a lot of good work for the cycling community) fell hard for the position that “the problem on Shoal Creek Boulevard isn’t the bike lanes, it’s the traffic speed”. Since this position continues to rear its ugly head in discussions before and after yesterday’s meeting, I thought I’d address it here.

The key is that all other things being equal, higher car speeds do indeed result in less safety for nearby cyclists and pedestrians. This is unquestionably true.

The problem is that all things aren’t equal. This picture shows a cyclist trying to pass a parked vehicle at the same time he is being passed by a moving vehicle. It doesn’t matter if the passing vehicle is going 45 or 25; if the cyclist veers out unexpectedly into the through lane and is hit, they’re in bad, bad, BAD shape. (Note: you have to imagine that the stripe between the 4-foot ‘bike lane’ and 6-foot ‘parking lane’ isn’t there to match the current conditions on SCB).

Likewise, this infamous accident happened despite the fact that the conflicting vehicle’s speed was 0 MPH and the vehicle which ended up killing her wasn’t going very fast either.

On the other hand, hundreds of cyclists use Loop 360 every day with no conflicts with motorists. Automobile speed in the through lanes of that roadway is typically around 60 MPH.

What can we conclude? Traffic engineering seeks to avoid presenting users with unexpected conflicts; and having a cyclist veer out into the travel lane when the motorist in that lane thinks they’re not going to have to is the very definition of unexpected. A safe pass by a car going 40 is far preferrable to a collision with a car going 30.

How does this apply to Shoal Creek Boulevard? It’s clear to me at least that the original city plan probably wouldn’t have reduced automobile speeds much, but definitely would have resulted in fewer conflicts with cyclists who need to leave the bike lane to get around obstructions. As on Loop 360, if you rarely need to leave the bicycle facility, you don’t need to worry as much about the speed of the cars in the lane next to you.

Another thing Preston in particular got wrong was the theory that riding on Shoal Creek is ‘easy’ once you ‘learn’ how to pass. Even for an experienced cyclist like myself, the conflict with motorists during a pass is irritating (the motorists don’t understand why I go into the travel lane and are sometimes aggressive in expressing their displeasure). For a novice cyclist, it’s likely to be so intimidating that they will (unwisely) stay in the far-too-narrow space between the white stripe and the parked car, and someday soon somebody’s going to get killed that way.
Finally, of critical importance to the City of Austin is the following paragraph, excerpted from a detailed analysis of the Laird case in Boston:

The City might be held negligent for creating what is called in legal language an “attractive nuisance” — that is, a baited trap. Ample evidence exists that the City of Cambridge had been notified of the hazards of bike lanes in the “door zone” before the Massachusetts Avenue lane was striped, yet the City continued to stripe them.

This is basically why Shoal Creek Boulevard doesn’t have bike lanes today, it has a “multipurpose shoulder”. Unknown whether this will do enough to shield Austin from liability in the event of an accident, but cyclists ought to think about this when you decide to ride on this facility.

Shoal Creek Meeting Is Done

Largely as expected – council members want to remove the islands, and then we’re going to talk some more about what to do. Some indications that they’re either not willing to admit or not capable of understanding that a compromise solution is impossible for this roadway. Neighborhood people largely against the curb extensions but still adamant that parking on both sides must be preserved — which means that we’re back to bike lanes with parking in them, hich pretty much the entire rest of the world views as an oxymoron.

Here’s the letter I just sent to the three council members on the subcommittee:

Councilmembers:
I watched most of the meeting today while working at my desk, and had a couple of comments:

1. 2-way on-street bike lanes are not accepted in traffic engineering circles and have not for quite some time. They will not be an option for Shoal Creek Boulevard unless you want to override your staff.

2. Bike lanes down the median – same story.

3. A reminder: We already know there is no way to reconcile “parking on both sides” with “car-free bike lanes” on this street. There is insufficient width. Either one or more bike lanes must be abandoned, or one or more sides of parking must be abandoned.

Comments that you made in regards to #3 were especially disappointing – the failure of the previous council was in attempting to avoid this painful choice, which MUST be made. EITHER car-free bike lanes OR parking on both sides – you cannot have both. I would argue that the correct choice is to preserve on-street parking on ONE side of Shoal Creek Boulevard – this is not an unreasonable imposition on residents (my own neighborhood has highly restricted on-street parking; many streets allow it on one side and a few not at all).

Regards,
Mike Dahmus
(old email address removed)

Update from 2017: Yes, some people are actually pushing for 2-way one-side bike lanes on this roadway now, incredibly, the “bike lanes as stupid glorified sidewalks that are actually more dangerous even if they don’t feel more dangerous” fad is back!.

Letter to Council on Shoal Creek Debacle

A subcommittee of the City Council is getting some kind of an update on the Shoal Creek Debacle. I just sent this email to them.


Dear Mayor and councilmembers:
My name is Mike Dahmus, and I served on the Urban Transportation Commission from 2000 through 2005. I cast the lone vote in opposition to the plan which (with modifications) ended up being constructed on Shoal Creek Boulevard. During my terms on the UTC, I served as the lone member who utilized both an automobile and a bicycle to commute to work — i.e., I’m not a pure cyclist, and I’m not a pure driver. I used Shoal Creek Boulevard as part of my bicycle commute for years and occasionally drove it as well.

I understand you’re going to address this issue in a subcommittee meeting this week, and I thought I should comment.
For those of you who don’t bicycle; Shoal Creek Boulevard is, without hyperbole, the most important route in the city for bicycle commuters. (It has a lot of recreational traffic as well, of course). It forms the spine of the route between northwest Austin and central Austin – alternate routes either are far too hilly for normal use (to the west) or do not connect with routes which can get cyclists across the Mopac/183/360 barrier.

Years back, Shoal Creek’s turn came up in the “let’s do what every other city does and put up no-parking signs in our bike lanes” process. Since the bike program staff at the time knew that Shoal Creek had long blocks and (some) short driveways, they offered a compromise plan which would have allowed parking on one side of the road, with smaller-than-typical bike lanes on both sides. This plan was opposed by the neighborhoods, for whom on-street parking was the priority over through cyclist travel.

Years ago, thanks to neighborhood pressure, Shoal Creek Boulevard was reclassified from a minor arterial to a residential collector (an inappropriately low classification by engineering standards). This allowed the neighborhood to then push back against that eminently reasonable plan to allow parking only on one side of the street (neighborhood partisans could declare that SCB was a ‘residential street’ and that therefore parking was more important than through traffic). The bike program plan was rejected thanks to a few neighbors who valued both-sides on-street parking more than cyclist safety.

At this point, as I’m sure many of you remember, the neighborhoods got Councilmember Goodman’s approval to start a planning process which ended with the absurd plan by Charles Gandy which none of your engineers would sign their name to, and which made Austin a laughingstock in other cities around the country. The modified version of that plan (removing the stripe between the ‘bike lane’ and the parking area) is nearly as ludicrous, but since it’s not marked as a ‘bike lane’ is nominally acceptable to engineers, I suppose.

The Shoal Creek Boulevard plan as implemented is a liability problem for the city of Austin (although not as bad as the original Gandy “10-4-6” plan would have been, since city engineers were smart enough to remove the “bike lane” designation). Sufficient space does not exist for a cyclist to safely pass parked cars and remain in the bike lane, yet drivers in the through traffic lane expect them to do so. This is a textbook example of bad traffic engineering (when one street user performs a safe and legal manuever, another street user should not be caught by surprise).

This isn’t about the curb islands, by the way. The safety obstacle for cyclists is parked cars. The curb islands must be passed in a fairly narrow space, but there’s zero chance that one of them is going to open their door while you’re passing it.

But what the curb islands and striping HAVE done is encourage more people to park on the street; increasing the frequency of the street user conflict which will eventually result in a serious injury – a car passing a cyclist while the cyclist is passing a parked car.

This entire process was nothing more than an abrogation of responsibility by the City Council. Your job is to make decisions, not to encourage a make-believe consensus when none can be found. There simply is no way to reconcile both-sides on-street parking with car-free bike lanes (and, by the way, the rest of the world views parking in bike lanes as an oxymoron). A decision either way would have been better than the mess you left us with — and cyclists are getting hurt already as a result.

I urge you to learn from this horrible mistake, and remember that your job is to make the tough decisions. Shoal Creek Boulevard has already been ruined for bicycling commuters – please don’t take this precedent anywhere else.

Regards,
Michael E. Dahmus



Commuting To Riata

I had a nice conversation with Jonathan from Another Pointless Dotcom while doing some work last night, and it came to light that he works in the same complex I did for about a year and a half. This reminded me to share with him my old slideshow of that commute, which I’ve probably never mentioned on the blog. I also then chatted about it this morning with my current cow orker who has a lot of experience in the area. Since this might be of general interest to people who work in the area, I’ll initiate this new Bicycle Commuting category with this oldie-but-goodie.

Riata is a cautionary tale of any number of my hot buttons, including the problems that frontage roads cause transit and pedestrians, neighborhoods being irresponsible, developers getting to claim credit for being ‘near’ transit when it’s not feasible to actually use, high tech offices and apartment complexes metastasizing along sprawl corridors rather than being downtown where they ought to be, etc. There’s at least a few thousand employees of various companies in there now – probably still down from the pre-bust peak.

The key things to remember about commuting to Riata, which is halfway between Duval and Oak Knoll on the north/east side of US 183 are:

  1. Use Jollyville. Now with bike lanes!
  2. When transitioning to Riata Trace Parkway, your choices are to go all the way up to Oak Knoll and come in the back way, or go over on Duval to the 183 frontage, and go in that way. In the morning, the northbound 183 frontage is very civilized and not a problem.
  3. When going home in the afternoon, you’ll want to use the TI/Oak Knoll back way. Don’t mess with 183 then.
  4. Think about using the bus for a boost uphill in some mornings, if you’re like the (old) me and commuting from central Austin.
  5. Decide whether you want to cross Mopac on Spicewood or Steck. My current cow orker prefers Steck all the time; I prefer Steck uphill and Spicewood downhill. Depends on your tolerance for the stress of the crossing at Mopac/Spicewood versus the speed you’ll give up at the 4-way stop on Steck.

(Technical details: I wrote the crappy slideshow script which reads pseudo-XML a long time ago and have never touched it since; it BARELY works; don’t look at it cross-eyed or you might break the internet).

Bicycling Is Very Safe

While doing a bit of preemptive research for the comments for the last entry, I stumbled across this article which does, by far, the best job of laying out comparative risk for cycling and other activities (like driving) that I’ve ever seen. Highly recommended.

Helmet science (for real)

Here’s an interesting paper on bike helmet design. Should be mandatory reading no matter which side of the debate you fall on, especially if you like to repeat stories about how a helmet ‘saved [some person’s] life’.

(Note for the record that I’m a skeptic; I wear one when mountain biking but never else, and won’t go on rides that require them, because I believe (and am backed up by real-world data) that biking isn’t that dangerous; that helmets haven’t had much impact on head injuries; and that wearing helmets helps perpetuate the myth that biking is too dangerous to do regularly.)

Shoal Creek Update – May 17, 2005

I biked home from work on Tuesday (Too bad it’s Bike To Work Week, Not Bike From Work Week!) and went down Shoal Creek from Anderson to 41st. Report at the end.

The Chronicle has covered the recent brou-ha-ha, and kudos on the title. I have submitted a crackpot letter (check in a couple of days) which attempts to correct the misinterpretation of Lane’s excellent soundbite (the obstructions he refers to are the parked cars, not the curb extensions).

The ride home was pretty good, actually. About five passing manuevers were necessary, and on two of them I had a motorist stuck behind me; and neither one showed evidence that they were perturbed. Definitely above par for the new striping. I wish I could believe that the motorists are getting the message about the necessity to take the lane to get around parked cars, but the comments from the neighbors at that meeting lead me to believe that I was just lucky to get a couple of reasonable motorists this time.