Showing posts with label bad bike lanes. Show all posts
Showing posts with label bad bike lanes. Show all posts

07 November 2018

How Bad Can A Bike Lane Be?

How bad are the Middle Street bike lanes in Portsmouth, New Hampshire?

Not having ridden them, I don't really know.  But I can tell you this:  They've been panned by both motorists and cyclists.  Oh, and school kids aren't crazy about them, either.


Drivers made at least one of the usual criticisms:  They took away two of "their" lanes.  Perhaps more to the point, though, the bike paths force them, as one driver pointed out, to cross the double yellow line dividing northbound from southbound traffic when passing.  Also, the buses don't have a place to pull over when picking up or discharging passengers.



The pupils' dislike of the lanes was observed by attorney Charles Griffin.  At a meeting of the city's Parking and Traffic Safety Committee, he recounted his own informal survey, taken from his car.  He sat at one intersection between 7:50 and 8:20 am--the time during which most kids are going to school--on 15 mornings. "On two days, there were two students;  on seven days there were (sic) one student; on six days, no students at all. Most kids who rode their bikes to school, he said, used the sidewalk instead of the bike lane.  "I suspect they did because they didn't feel safe" using the lane "because it's too close to traffic," he speculated.

This was a poignant criticism, from the city's standpoint, because one of the arguments used to sway reluctant community members was that the lanes "would result in significant numbers" of kids riding to and from school, according to Griffin.

As an educator, I understand that young people often know more than we realize.  That point was underscored by cyclist Roger Peterson who complained about debris, including wet leaves, in the lane.  On his ride to the meeting at City Hall, he said, he also saw recycle bins scattered throughout the lane.

But if that were the only problem with the lanes, it could be fixed by maintenance. His and other cyclists' main issue, he said, is that the lanes are "very narrow and restrictive." Before the lanes were built, Peterson said, Middle Street "seemed to be one of the safest roads in the city."  The street was "wide enough" for cyclists "to avoid traffic and for traffic to avoid the bicycles," he explained.

"It's puzzling as to why a bicycle lane was put in there," he addded.

I could make--and have made--the same criticisms, almost verbatim, about some of the bike lanes I've ridden here in New York and other American locales.  Sometimes it is actually safer to have enough room on the street for cyclists and motorists to maneuver around each other than it is to have a lane that restricts both cyclists' and motorists' movements.  Moreover, making turns--especially right turns--or going straight through an intersection when motor vehicles (especially trucks) are turning right is actually more dangerous when a cyclist has to leave a bike lane than it is if he or she is riding continuously along a street or road.

The worst part is that such lanes actually increase tensions between cyclists and motorists:  The latter believe that  lanes "take" "their" roadway away from them, while the former become frustrated with motorists' impatience.  This could lead to city planners and administrators deciding that no bicycle infrastructure project is worthwhile and to removing whatever good infrastructure might have been created.

As I said previously, I've never ridden the Middle Street bike lanes.  So, in all fairness, I don't want to suggest that they are worse than other lanes, including some I've ridden.  But I can't recall hearing of another lane that received such resounding criticisms from both cyclists and motorists.  And those criticisms are an accurate reflection of the misconceptions--and, sometimes, sheer folly--behind the planning and building of bike lanes.

06 November 2017

When Using "Bicycle Infrastructure", Be Sure To Take "Proper Precautions"!

Sometimes the bicycle infrastructure we get is worse than no bicycle infrastructure.  Three lawsuits that have been filed, and another that was recently settled, in San Diego bear this out.

Eight months ago, Clifford Brown won a $4.85 million for injuries he sustained in a crash on a tree-damaged sidewalk.  City officials had been notified about the damage five months before the September 2014 crash, which left Brown with several lost teeth, torn spinal cord ligaments and brain damage that has rendered him incapable of functioning independently.  

In San Diego, as in other cities, cyclists sometimes use sidewalks because they feel safer on them then on streets that are designed for vehicular traffic and thus have no shoulders, or even passing or parking lanes.  Cyclists might also feel safer on sidewalks than on some bike lanes, especially one like the Balboa Avenue path where a man who has filed one of the pending lawsuits crashed head-on into another cyclist.  

That man, Douglas Eggers, suffered injuries similar to Brown's.  His suit alleges that the accident resulted because the lane, which runs along the north side of Balboa, is built only for eastbound traffic.  According to the suit, the city should have built that lane wider, with a divider in the middle, to accommodate bicycle traffic going both ways, or a separate westbound bike lane on the south side of Balboa, one of the city's busiest thoroughfares.  

Michael Cizaukas, who filed one of the other lawsuits, was launched into a move most BMXers would admire when he was thrust into the air from a section of a bike lane buckled by a tree.  Not being a BMXer, though, he was thrown from his bike and, as a result, suffered fractured bones, a separated shoulder, muscle tears, hearing loss and a concussion in the May 2016 incident.

Warning: Shock Hazard!


Unfortunately, I've heard of crashes like the ones Brown, Eggers and Cizaukas endured.  But the third lawsuit filed I'm going to mention involves something I never before would have envisioned:  injuries sustained at a bicycle parking rack.  Oh, but it gets even better: Jasper Polintan says he's suffered damage to his upper extremities and other injuries that have reduced his earning capacity when--get this--he was electrocuted while locking his bike to a city rack.

His suit alleges that the city didn't properly install, maintain or provide adequate safeguards for that rack. In preliminary responses to Polintan's, Cizaukas' and Eggers' cases, however, attorneys for the city say that officials were unaware of the problems and the injured cyclists didn't take "proper precautions."

Sometimes, it seems, "proper precautions" involve simply avoiding bike lanes and much else of what's offered up as "bicycle infrastructure" in too many places.

09 March 2017

As I Was Saying...

If you've been reading this blog, you know that I am, in general, not a big fan of bike lanes.  At least, I don't like bike lanes as they're (mis)conceived, designed, constructed, regulated and maintained here in New York, and in too many other US locales.

And I have another peeve about bike lanes--again, mainly about the ones here in the Big Apple.  One of my posts from a few days ago began with it:

One of the reasons I don't like to use bike lanes, at least here in New York, is that motor vehicles frequently pull in and out, and sometimes park, in them.

Well, wouldn't you know it...This is what I encountered while riding to work this morning:



A few weeks ago, a new bike lane opened on the north side of Hoyt Avenue, the wide boulevard that straddles the entrance to the RFK Memorial Bridge.  Traffic is westbound, one-way on the north side, above which the bridge's pedestrian-bike lane arcs.  (Traffic is eastbound one-way on the south side.)  The lane runs eastbound--in the direction opposite the traffic.  There are two rationales for that, I guess:  1.) The lane is intended, at least in part, to provide access to the bridge's pedestrian/bike lane; and 2.) The lane is "protected", meaning that there are pylons separating it from the motorized traffic.

Although the lane hasn't been open for very long, this wasn't the first time I've seen a vehicle parked in it.  Worse, I've seen a truck or van in the lane, and another motorized vehicle on the sidewalk: There are maintenance and storage facilities in the real estate around the bridge pillars. 

Woe betide the cyclist who unwittingly turns on to the lane: If both the lane and the sidewalk are blocked, there is no choice but to ride in the traffic lane--against traffic--or to make a U-turn back on to 26th Street, which is one-way. If the sidewalk is free, a cyclist can use it as long as some highway cop with too much time on his hands isn't looking to meet his ticket quota for the month.

For the time being, I think I will take the route I had been taking most days before the lane opened:  I will ride up 23rd Street to the south side of Hoyt Avenue, turn at 27th Street, cross under the bridge overpass and access the bridge's pedestrian/bike lane from there.

I must say, though, that in spite of the obstacle, I had a pleasant commute.  As you can see in the photo--which I hastily took with my cell phone--it was a beautiful morning.  And, when I stopped to take the photo a nice young lady named Rachel--who probably thought I was looking at a GPS or some other app-- asked whether I was trying to find something.  I explained what I was doing and told her about this blog.  And she told me about some rides that might start soon on Randall's Island, where she works--and through which I ride during my commute!

06 March 2017

What's Worse Than A Bad Bike Lane? Bad Bike Lane Regulation!

One of the reasons why I don't like to use bike lanes, at least here in New York, is that motorized vehicles frequently pull in and out, and sometimes park in them.  I've even seen drivers use bike lanes for passing.

The problem is that if a car pulls in, or parks, in the lane, there is no room for you to get around it, especially if the lane is "protected", i.e., has a barrier between it and the street.  At least, if only a painted line separates you from the street, you can veer into the traffic lane.  

Another problem is that drivers often pull into the lane without warning--and, it seems, without looking to see whether cyclists are in the lane. If you are riding in the street and someone makes a sudden turn, you most likely can move over or shift into another lane.  You don't have that option in a bike lane--again, especially a "protected" one. 

I did not notice such problems when I recently rode bike lanes in Paris and Montreal:  Drivers in those cities seem more cognizant that bike lanes are for, well, bikes.  That, or the regulations that prohibit motor vehicles are more strictly enforced.  

On the other hand, it seems that cyclists in other American cities have experiences with bike lanes similar to the ones I and other cyclists have in New York.  Bob Collins, a blogger and news editor for Minnesota Public Radio, offers this:  "The biggest problem with bike lanes in the Twin Cities isn't cyclists; it's people who insist on parking their cars in them."



That statement is particularly notable because during the past few years, Minneapolis has stolen some of Portland's, as well as San Francisco's and New York's, thunder as a "bike friendly" city.  In 2015, Minneapolis was the only US municipality in Copenhagenize Design Company's index of the world's 20 most bike-friendly cities.  Montreal was the only other North American city on the list.

(Copenhagenize's previous indexes were published in 2011 and 2013.  I am guessing they will publish another this year, though I have seen no indication of that on their site.)

Anyway, Mr. Collins shows us that there is no end to the ignorance or hostility of lawmakers when it comes to cycling.  Some want, or claim to want, to make things safer for us.  Others simply don't want to upset drivers, who make up a much larger constituency than cyclists, or see us as renegades, scofflaws or worse.

I don't know which, if either, of those categories includes Minnesota State Representative Duane Quam.  Instead of working on regulations to keep motorists from driving or parking in bike lanes--or, for that matter, from texting or talking on cell phones while driving--he has the brilliant idea of limiting access to bike lanes and deterring young people from cycling.  


At least, that seems to be the intent of the bill he's filed with the State Legislature.  Among other things, it would require anyone who wants to use the bike lanes to take a safety course, register his or her bike and pay an annual $5 fee.

But the most absurd part of that bill stipulates that anyone who rides in a bike lane has to be at least 15 years old.  "It's not clear where people under 15--kids going to school comes to mind--are supposed to ride their bikes," Collins wryly notes.  He also notes another onerous aspect of the bill:  that it applies only to areas with "structures devoted to business, industry or dwelling houses situated at intervals of less than 100 feet for a distance of a quarter mile or more.  

In other words, as Collins astutely observes, it is aimed at Minneapolis and St. Paul.  Representative Byron comes from Byron, a town of 5063 residents--and no bike lanes.


28 December 2016

A "Bridgegate" For Cyclists?

I lived through a time when the word "nuclear" was almost invariably followed by "holocaust".

Then again, I also experienced a few air raid drills when I was in elementary school.  One of the first stern glares a Carmelite nun directed at me was in response to my innocent (well, maybe not-so-inncocent) question:  "How is this going to protect us from an atom bomb?"

(Of course, now everybody knows that this is what you do in case of a nuclear attack:


  • Duck under desk or table.
  • Curl up in foetal position.
  • Place head firmly between legs.
  • Then, kiss your ass goodbye.)
Anyway...just as "nuclear" went with "holocaust", it seems that these days, "bridge" is followed by "gate".  And "Bridgegate" is the first thing people think of when you mention the George Washington Bridge.

Traffic jams have been as much a part of the bridge's 85-year history as corruption has been a part of the politics on both sides of the bridge.  Most of those tie-ups, unlike the ones caused by Governor Christie's acolytes, are not deliberate.  Nor will the ones that will  probably come soon and plague the bridge for the nest seven years.

Actually, the Port Authority's renovation project began last year, when lead paint was removed from the lower deck.  Removal of said paint will continue, and most important of all, the vertical cables will be replaced.  The PA says it will try to time the work to cause the least possible inconvenience to commuters.

Just as the term "human being" meant "white man with property*" to the Founding Fathers, "commuters" means, in PA parlance, folks who drive into the city and, well, maybe those who take the bus.  So, for that matter, does "traffic".

Now, to be fair, the PA plans to improve access to the bridge's bike and pedestrian lanes.  Then again, almost anything would be an improvement over what exists:  Hairpin turns on the New York side of the lane on the south side of the bridge, and steep stairs on both sides to access the lane on the north side.  Worse yet, the stairs on the New York side can only be entered by crossing a heavily-trafficked street that has become a de facto exit lane for the bridge an the Cross-Bronx expressway, and for buses entering and leaving the George Washington Bridge bus terminal.

Image result for George Washington Bridge bike lane pinch points
It's like this on a good day.

But those entrances aren't the worst part of the lanes.  For one thing, in more than three decades of biking (and, occasionally, walking) across the bridge, I have never seen both lanes open at the same time.  Worst of all, though, is that each of those lanes is seven feet wide at its widest. At some pinch points--where, for example, towers are located--the lanes are considerably narrower.  And, of course, the structures that cause the "pinch" also make for very poor sight lines.  At times, I've wondered that collisions and conflicts between cyclists and pedestrians aren't more frequent than they are.

To give you some perspective:  The Federal Highway Administration recommends 14 feet for a two- way bike lane.  And the American Association of State Highway and Transportation Officials recommends 16 feet.  


In other words, the lanes are half as wide as is generally recommended.  And, just as the GWB is the nation's busiest commuter crossing for motorists, its bike and pedestrian lanes are also among the nation's busiest.

Now, are you ready for this?  The Port Authority's plans call for reconstructing the bike and pedestrian lanes.  The north lane will be designated for cyclists, and the south for pedestrians.  Sounds good so far, right?

Image result for George Washington Bridge pedestrian bike lane pinch points
New Jersey entrance to the bike/pedestrian lane on the south side of the George Washington B

And the bike lane will indeed be wider.  How much wider?  Check this out:  one foot.  So the new bike lane, according to the plan, will be 8 feet wide.  There is nothing to indicate that narrower "pinch points" won't be eliminated.  Perhaps they can't be.  But I have to wonder why, if the Port Authority is planning what is essentially a once-in-a-century project, it can't or won't build the bike and pedestrian lanes to modern standards. Instead, it plans to rebuild the lanes to the standards that existed in 1931, when the bridge opened.  

Now, I don't know much about the economics of major public works projects.  I can't help but to think, though, that in relative terms, it wouldn't cost much more to build a modern path than the one that's planned--and, better yet, to build  a bike path on a separate, lower lever from the pedestrian lane.  Certainly, doing so would cost less than building another lane as a stand-alone project at a later date.

Weissman's proposal would put 10-foot bike lanes to the side of the existing paths. Image: Neile Weissman
Artist's rendering of a possible bike laneconstructed at a lower level alongside the current lane on the north side, which would be reserved for pedestrians.

Oh--one other thing is planned in the reconstruction:  a fence, a.k.a. a suicide barrier, along each lane.  I'm not going to argue that such a barrier shouldn't be installed:  It's likely that most of the suicides that have occurred from the bridge were preventable.  I can't help but to wonder, though, whether the barriers will make riding or walking across the bridge feel even more claustrophobic than it already is at times.

20 December 2016

Turn, Turn, Turn (And We're Not Talking About The Byrds)!

Until recently, I believed most bike lanes were designed by people who don't ride bicycles.  You may think I'm cynical, but I've ridden on too many lanes that ended abruptly ("bike lanes to nowhere"), had poor sight lines, let cyclists out into the middle of major intersections or were, for various other reasons, simply not any safer than the streets they paralleled.

Now I'm starting to wonder whether lane designers are acting under orders to reduce the population of cyclists.  I guess, for them, that's the easiest way to appease motorists upset that we're "taking the road away from" them.  

I mean, what other reason is there for this?



Had the bike lane continued in a straight line, or simply ended at that intersection, it would be safer for anyone who has to turn left from that intersection.  Instead, a cyclist riding through that loop has to make two sharp left turns almost within meters of each other in order to go where one left turn would have taken him or her.

And studies have shown that left turns are significantly more dangerous than right turns for motorists.  (That is the reason why, for example, all United Parcel Service delivery routes are planned so that the drivers make only right turns.)  What sort of diabolical mind would force cyclists to make two such turns in succession?

This strange piece of transportation "planning" was inflicted on the cyclists of Nottingham.  I thought planners in England knew better.  Oh, well.


08 September 2016

The Bike Lane Follies Never End

Sometimes I feel as if I could devote an entire blog to bike lanes that are poorly conceived, constructed, simply useless or bad in any number of other ways.

I've seen some doozies here in New York.  But the worst I've seen in The Big Apple is, apparently, sane compared to some that have been constructed in other parts of the US and world.

Some of the lanes I hear about are almost comically bad because it's simply impossible to understand how they can be imagined even by someone who has never seen a bike in his or her life.  When I'm in a charitable mood, I tell myself that the designers of such lanes assume that bicycles and cyclists possess extraordinary powers that mortal drivers and cars can't even dream of.

I mean, some are built as if we can pedal through steel columns or even stronger stuff.  As an example, check out this gem posted on the blog of Bike Shop Hub in Tucson, Arizona:

 





 Unfortunately, there's more where that came from--or, at least, where I found that gem.  Scroll down the page I've linked and check out, in particular, the ones posted by Marlo Stimpson and David Common.

12 May 2016

More Bike Lane Follies

Writing yesterday's post got me to thinking, again, about some of the really bad bike lanes I've ridden. I'm talking about the kind that, if they don't enrage you because they put you in more danger than you would have experienced while riding with cars and trucks, they leave you scratching your head and wondering, "What were they thinking when they built this?"

Of course, some of those lanes aren't exactly built:  They were merely designated by some lines of paint and a few signs.  But there are the ones that make you wonder why anybody bothered to spend the time or money to build barriers or cut through parkland. 

Paths like those lead to nowhere.  I wrote about such a lane in an earlier post:



A year later, I showed another that ran under the elevated tracks of the IRT #1 train in upper Manhattan--and right into the pillars that support said tracks:


I guess I shouldn't complain, though.  No lane I've ridden is quite like this one:




It's in Exeter, England.  Hmm...Maybe the Brits have some sort of cycling we've never dreamed of here in the 'States.  Whatever it is, it's certainly stranger than riding down this bike lane:





It might be the only bike lane in the world designed for BMXers or downhill riders--though I still rather doubt that whoever conceived it has ever been anywhere near a bike!

11 May 2016

Bike Lane Follies, Here And Down Under

If you've been reading this blog for a while, you might have noticed that I am not enthusiastic, in general, about bike lanes. 

A separate bike lane, especially one that runs alongside traffic, is not intrinsically safer for cyclists than a traffic lane on a typical city or suburban street.  The biggest flaw in most bike lanes I've seen and ridden is that they're positioned so that it's all but impossible for cyclists, especially inexperienced ones, to turn or cross safely at major intersections.  This is particularly true for those lanes that, in effect, turn into the right-turn lane for motor vehicles at such intersections, or for those streets that have right-turn-only lanes that cross the bike lane.  Things are even worse for a cyclist making a left turn at such an intersection, as he or she must cross several lanes of traffic coming from different directions.  This particular hazard is exacerbated when traffic flows off a highway into the intersection.

There are also other hazards, such as pedestrians who use the bike lanes as sidewalks or who wander onto them while they're texting or talking on their phones.  Two of the worst lanes I've experienced for that are the portion of Manhattan's First Avenue lane below (south of) 14th Street and Brooklyn's Kent Avenue lane (the one that skirts the Williamsburg waterfront).  Both lanes are lined with stores, restaurants, clubs and bars.  The clubs and bars pose particular hazards, especially during evenings and weekends, with patrons staggering out to the lanes.  But even shoppers and restaurant-goers too often aren't paying attention to their surroundings as they walk, and sometimes talk, with others.  And, of course, the drinkers, shoppers and restaurant-goers often leave debris in the lane.

Not to mention the drivers who steer their vans and trucks into the lanes to make deliveries at those establishments--or the driver who  pulls in mistakenly, to make a turn or, on rare occasion, out of sheer malice.  And, yes, police officers who their cruisers in the lanes while they're having coffee.

But even worse than the hazards I've mentioned or lanes that are poorly-designed (or -constructed or -maintained) are those that are built in ignorance or defiance of regulations governing them.  One such lane is found in Melbourne, Australia:



Apparently, according to Austroad's guidelines (see p. 30, Figure 4.27) a bike lane should be 1.2 to 1.5 meters wide and be separated from the parking lane by a strip 0.4 to 1.0 meters wide.  The bike lane in the video clearly does not follow that principle.

A few years ago, I was "doored" in a similar lane not far from my apartment in Queens.  The marked bike lane was not in any way separated from the parking lane to the right of it.  Fortunately for me, I did not take a full facial hit; I took a glancing blow that left me looking like I was pregnant on one side for a couple of weeks.

Now, from what I understand, Austroad's guidelines are not law or in-any-other-way-binding policy, so perhaps the designer of the lane in the video was (in addition to a non-cyclist, most likely) possibly ignorant of them. 

Similarly, the Department of Transportation here in New York City has guidelines for bike lanes (pp.55-59) but they are essentially unenforceable.  To be fair, those guidelines include some of the flaws I have pointed out in this and other posts.  However, the guidelines call for physical barriers between two-way bike lanes and arterial streets, in addition to clear markings between one-way bike lanes and narrower streets.  I have ridden on bike lanes that fail to meet those criteria.  And, worse, those lanes include some of the other design flaws I've mentioned, particularly when it comes to turns and merges--or, worst of all, bike lanes that suddenly disappear.

The thing that rankles me most, though, is that even such dry technical documents as the ones issued by the Department of Transportation continue to blithely tout the "benefits" of bike lanes for cyclists as well as motorists.    A poorly-designed or -constructed bike lane helps no one and, if anything, only fuels anger and resentments between motorists and cyclists.