I'm certainly not the first person who has noticed the strange use of sharrows in Seattle (for example, Elly Blue talked to Seattle Bike Blog's Tom Fucoloro on the topic in November), but I just can't get over how randomly placed they seem to be. Some of them do what's going on in the first picture, where they seem to tell people to pull up to the curb at intersections (again, from a safety and traffic flow standpoint, this is a bad idea). The sharrow pictured here is on a curving street in the Mt. Baker neighborhood, and it seems to be telling cyclists that we should get as close as possible to that bulb out so that cars can more easily make the curve. In both cases, the bike signage seems to indicate that your personal safety as a bicyclist rests on you getting out of the way of cars.
Bike infrastructure should not be about keeping bikes out of cars' way.
Signage like this perpetuates an idea that motorists should be able to travel as-fast-as-possible, that biking is nice, in its place.
Our streets are dangerous not because bikes and pedestrians "get in the way," but because this as-fast-as-possible mentality makes people outside of cars into externalities.
So what should bike infrastructure do?
Bike infrastructure should make riding a bike safer and easier. Infrastructure projects that take bikes out of car traffic only to dump them randomly back in when the paint or path stops do not accomplish this.
I was biking down in Portland recently, and it reminded me of just how big I feel when I'm biking in a city that has accommodated transport cycling. My body on my bike takes up the street, I'm not being pushed to the side and allowed to travel only where it's convenient for motorists. I love seeing sharrows that are out in the middle of the traffic lane, where they should be, rather than shifting along the street according to the expected movement of cars.
When I see a sharrow painted over a pothole or otherwise leading me into a dangerous situation, I wonder where it went wrong. Was it the worker painting the thing that decided to place it there? Was it a city planner who decided to place it there? And then I think, why would a design like this get approved? Is it because the people who made the decision to install this signage weren't thinking about how bicyclists would be using it, but about how placing bike infrastructure on these streets would affect property values?

Rock on.
ReplyDeleteI particularly like:
"Bike infrastructure should not be about keeping bikes out of cars' way."
...but wonder about the line between that and keeping people on bikes safer or more comfortable by removing them from potential conflicts... or at least just giving them a teeny tiny piece of right of way.
Thanks for the post!
Yeah, I think that a lot of it has to do with the fact that "safe" and "feels safe" are not necessarily the same thing. I know lots of people who feel really unsafe on bikes, but drive on freeways all the time. It seems like bike paths give people more of a sense of protection, but I think that it's a false sense cause at some point they are going to have to mingle with car traffic. If you only get honked at and menaced for two blocks instead of ten, is that really gonna be what gets you on a bike?
DeleteBack to rockin' on...
Even though I don't bicycle at this time, I read quite a bit of Streetsblog, and I do try to keep an eye out for cyclists. But the line about bicycle facilities affecting property values puzzled me. Would good bike lanes increase or depress property values? If one is worried about burglars, wouldn't thieves be more likely to use a car or truck (theirs or a stolen vehicle)? Kinda hard to schlep a big screen TV on a bike without drawing attention.
ReplyDeleteRegarding city employees being clueless about what cyclists really need--road crews travel around in trucks, and the workers are usually paid well enough to afford a car. I guess if the cyclists don't "ride herd" on the "public servants", no telling how they may interpret their instructions.
Right, about the placement of the symbols, my experience in LA was that city employees working on bike projects didn't necessarily have any experience with biking, so they didn't have much insight into functionality. So that could be a reason why the sharrows in Seattle are inconsistent. I also meant to suggest that if the point of putting in bike infrastructure is to raise property values, its functionality as an aid to the actual practice of cycling matters less. Or if the project was seen as a bad thing by property owners, perhaps they pressured the city to drop elements that would have made more sense from a user perspective.
DeleteSince I started studying bicycling in 2008, I've heard people describe bike infrastructure both as harmful to property values and as a tool for gentrifying urban neighborhoods. We know the U.S. has a long history of transportation infrastructure going into place as a stimulant to private development, and as bicycling gets to be seen more as a cosmopolitan activity and less as a mode of transport used by undesirables, I'm starting to hear more people associate things like bike lanes with the displacement of urban communities.
I agree with your premise - that the message shouldn't be for bikes to stay out of the way - I actually like Seattle's broad use of bike lane markings and sharrows.
ReplyDeleteIn the first picture, I have seen cars pull up to that intersection two-abreast, then causing a traffic hazard when the right-side car accelerates to get ahead or stomps on the brakes to get behind. Add a cyclist into the mix, and that intersection got really scary really fast. With the new markings, cars stay in a single file, and it gives the bicyclist a chance to build momentum up again when the light turns green.
Sharrows serve two functions to me: the lesser is to remind bicyclist to stay as far right as they feel safe (that's how the city code is written). But more importantly, it reminds car drivers to look out for bikes. Anything that raises awareness - especially awareness for both user groups - gets a thumbs up in my book.