Here is a Google Street View from before bicycle markings were painted:
Portland, yet! Well, Portlandia.
Often, flubs like this result from a construction crew’s having its own ideas about design, as in “oh, there’s a ramp from the sidewalk and my 5 year old rides on the sidewalk.” I don’t think that you would find this in the design drawings. Portland traffic engineering has its ideas about bicycle facilities which I may or may not agree with, but leading a bike lane extension into the curb when there is a shared-lane marking in the next block isn’t one, or at least that seems very improbable to me.
it is distressing that this happened, and that the city didn’t immediately correct it.
First, let’ define “undertaking”. That doesn’t mean that the vehicle is a hearse. It means that the vehicle passes between yours and the edge of the road when you are near the edge and turning toward it. Since the question mentions a left turn, the questioner is probably in a country where traffic keeps left by default and normally passes on the right. The term ‘undertake” is more commonly used in the British Isles than in North America in any case. But the question could apply to a left turn from the left side of a one-way street anywhere.
Usually, the driver who undertakes is at fault. Generally there is not room for another dual-track vehicle to pass between the turning vehicle and the edge of the roadway, though there may be room if more than one lane allows left turns, or room for a single-track vehicle (motorcycle, motorized bicycle, bicycle). A driver might also undertake on a highway shoulder or by driving off the road. In any of these cases, it is illegal.
Some countries place a bicycle lane or barrier-separated bikeway in the path of the turning traffic, and if the undertaking driver is a bicyclist, the turning driver is held at fault. The resulting conflict may be not mitigated at all, or mitigated in any of several ways — with warning signs, street geometry, street markings or traffic signals. The intention of this arrangement is to relieve bicyclists of the burden of mixing with motor traffic to travel straight through the intersection, and so, placing all of the responsibility for avoiding collisions on the motorist.
Because of the speed with which bicyclists travel, the turning driver is required to look to the rear to the side toward which he or she is turning, rather than only first merging to the lane position for the turn and then yielding to pedestrians who are standing on the corner or walking in the crosswalk. Looking to the rear imposes an additional task burden on the driver at a time where attention to the front and sides is also in demand, and may even be impossible, depending on the geometry of the intersection and the design of the turning vehicle. Unless drivers know to expect this conflict and mitigating factors are in place, this is a risky situation, often resulting in what is called in the USA a “right hook” collision. It also reduces the throughput of intersections by requiring additional waiting — sometimes by motorists, sometimes by bicyclists and sometimes by both.
How does the motorcycle balance itself? As shown in videos with the Road and Track article, the front fork is hinged so the front wheel can move forward, increasing trail — the distance of tire contact patch behind the steering axis. Then automated steering motions shift the mass of the machine and rider slightly side to side to maintain balance. The machine is also reported to be able to perform a conventional track stand, like those done by bicyclists — turning the front wheel at an angle to one side, and maintaining balance by propelling the machine forward and backward.
These capabilities require that the motorcycle have special control mechanisms, a computer on board to operate them, and sensors to report the machine’s orientation — which can be tricky on a single-track vehicle, because it can balance even when leaning into a turn. The Honda feature is described as for low speeds and when the motorcycle is stopped. That would avoid the issue with leaning. An internal-combustion engine would require a special and complicated transmission to drive the motorcycle subtly backward and forward on short notice. In any case, electrical motors are needed to adjust the fork angle and make subtle steering corrections. An all-electric motorcycle is simpler and can be used indoors, as shown in the videos in Road and Track. They show no exhaust pipe.
In a discussion on Facebook, Jim Lindner wrote:
Extending the wheel base and fork angle gives the ability to move the mass of the engine right and left, a form of weight shifting they likely did not count. A motorcycle has a bit more mass than a bicycle improving the resistance to change, but with a little leverage or sudden shift of load I think this system’s ability to correct will easily be overloaded.
This brings up the concept of the operational design domain: the range of conditions under which robotic features work. Automated-vehicle researchers and engineers use this concept. ODDs range from cruise control and anti-lock braking up through robotic crash avoidance for a vehicle otherwise under the control of a human driver, and onward to driverless operation under increasingly more challenging conditions.
The ODD for an automated two-wheeled vehicle does not include slippery surfaces or steering into a curb at a low angle unless it has sensors which allow it to avoid these hazards. To avoid falling over, it must avoid these conditions as a skillful human driver would. This capability is far in the future.
I don’t ride fast so I can participate safely in traffic. I participate in traffic so I can safely ride fast enough for my needs.
If I were to ride in the gutter, on the bike path, in the door zone, on sidewalks and cycle tracks, etc. I could reduce my risk (probably to an acceptable level) by traveling slowly – at near-pedestrian speeds. That slower speed would give me more time to react to the hazards present in those environments.
But I use my bike for purposeful travel. I don’t have time in my day to travel as far as I need to go, if I were constrained to moving only at near-pedestrian speeds. In order to get where I’m going in a practical amount of time, I need to be able to ride at the speeds I’m capable of sustaining on a bicycle. And I need to do it more safely than if I were in the gutter or on a bike path or in the door zone – I need the safety and convenience of the travel lane. That speed is what the travel lane is designed to accommodate, and that’s what the ordinary traffic laws are designed to enable.
If my choice of travel by bicycle is restricted to hazardous areas like gutters and bike paths and cycle tracks, I’ll choose another way to travel – something motorized so I don’t suffer those restrictions.
I’ve had criticism from an unusual side about the video below. The complaint, from another cyclist, was essentially that I was not following the rules of the road, not operating as the driver of a vehicle, by riding straight through in a right-turn lane. Most criticism about my cycling, and my cycling advice, comes from people who would rather that cyclists not have to ride on roads at all!
To answer this criticism, let me first provide some background.
Anyone who uses the roads in the Boston area , whether as a cyclist, motorist or pedestrian, soon discovers that the street markings often contradict the requirements of normal traffic movement. Of course this is what knowledgeable cyclists complain about as it applies to bike lanes — emphatically so in the Boston urban core, where there is rarely room for bike lanes outside the door zone. Door-zone bike lanes have been installed anyway ever since the Cambridge bicycle coordinator introduced them in the mid-1990s. (Now she has moved on to X-merges, bicycle sidewalks, jughandle left turns and bowling-alley bus stops, and the City of Boston is working to play catch-up.)
We don’t only have bike lanes in the door zone here, we have bike lanes in the taillight zone — like this one on Massachusetts Avenue in Cambridge.
Bike lane in taillight zone, Cambridge, Massachusetts
When I had the opportunity to ride in Albuquerque, New Mexico a couple of years ago, I had a real eye opener: I saw and rode on bike lanes which are mostly functional rather than dysfunctional. They are on streets without parking; motorists merge across them to turn right. I realized that bike lanes in the Boston area give others a bad name.
The Boston area has a terrible reputation for bad driving compared with other cities. In my opinion. strongly backed up by statistics, this reflects cultural differences rather than reality. There is somewhat of a chip-on-the-shoulder, butt-into-line attitude among many Boston drivers. It probably goes back as far as the Blueblood vs. Irish struggles for political power of a century and more ago. Some drivers feel a sense of entitlement and an emotional need for self-assertion. But the rudeness also at times reflects the practical need to get going. A Boston driver more often has blindly to inch out into the path of a vehicle which has the legal right of way, simply to get into the stream of traffic, than in most other American cities. A cyclist who doesn’t understand this will feel continually abused and endangered; a cyclist who understands the need to assert lane position and right of way finds Boston a very easy and safe place to ride. I describe how to be that cyclist, here.
The conflict between markings and traffic movements here in the Boston area didn’t begin with, and isn’t restricted to, bike lanes. It results in the first instance from an attempt to impose standard road markings and channelization on streets which are too narrow to accommodate them, or on multi-way intersections which are too complicated.
In order to accommodate parking, there are quite a few travel lanes too narrow even to fit a conventional dual-track motor vehicle. Here’s an example.
Narrow travel lane next to parking, Franklin Street, Framingham, Massachusetts.
There are also multi-way signalized intersections where traffic engineers threw up their hands and let traffic enter from more than one leg at a time and merge inside the intersection.
And now, zeroing in on the topic of this post, there are numerous situations where an empty right-turn lane parallels a congested through lane, and neither lane is wide enough for side-by-side lane sharing. Often there is also a receiving lane or shoulder after the intersection — as in the example shown in the video.
I completely agree that it is foolish and hazardous for cyclists to ride near the right side of a right-turn lane when headed straight across the intersection. That is the “coffin corner” situation that we lament when it kills a naive cyclist. But, on the other hand, I consider treating an empty right turn lane with a receiving lane or shoulder after the intersection as a dual-destination lane, and riding in its center or toward its left side, only to be a variation on the decades-old advice to choose lane position according to the rules of motion, and ignore the bike-lane stripe. I’m not alone in this, not at all. Installations formalizing this treatment have been made in a number of places in the USA. It is accepted under the Manual on Uniform Traffic Control Devices if shared-lane markings are used, though state laws generally still do not allow it. It is still in the experimental phase if a through bike lane is to be installed inside a right turn lane. That is documented on this page on the FHWA site.
Most importantly though, treating a right-turn lane as a dual-destination lane when it is empty, or lightly-used, or carrying slow traffic while the through lane is blocked, and riding at its center or left side does not violate the rule of destination positioning and does not lead the cyclist into a conflict. I yield when entering the lane (if there is any vehicle to yield to) and I never place myself to the right of right-turning traffic. I have never gotten into a hazardous situation by doing this. I must anticipate that a driver waiting in line in the through lane to the left may decide instead to turn right and enter the right-turn lane late. This is the same concern as when overtaking any line of stopped traffic, and the countermeasure is the same; stay far enough away from the stopped traffic to be able to avoid a merging vehicle.
In my opinion, the assertion that a cyclist should never ride centered or left in a right-turn lane when preceding straight across an intersection is rigid, legalistic, and impractical. But on the other hand, it doesn’t make sense everywhere, either as an informal practice or a standard treatment. That is why, in my opinion, a standard is needed to establish where it may be formalized, and education is needed, as always, so cyclists will be able to judge when it is advisable or inadvisable.
Further information: I’ve had the same issue raised about my advice on riding the 9th Avenue sidepath in Manhattan, and you may read about it in the documents, photo captions and video linked under the 9th Avenue heading here.
The same barrier can have more than one of the characteristics listed below, and they may be different for different types of vehicles.
Containment: The barrier prevents a vehicle from, for example, going over a cliff, or straying into oncoming traffic. Examples: curbs, guardrails, Jersey barriers.
Deflection: The barrier guides a vehicle that has gone off course back into the intended direction of travel. Examples: Jersey barriers, guardrails.
Threat: The barrier is hazardous in itself, so drivers shy away from it. Example: boulders, rigid bollards.
Sham: The barrier appears to pose a threat of damage to a vehicle but in fact is designed to minimize or avoid damage. Example: flex posts.
Stop: The barrier is intended to stop a vehicle approaching it.
Energy-absorbing: The barrier is designed to lengthen the time and so decrease the severity of an impact — same idea as with air bags or helmets. Examples. crash cushions, deformable barrier walls.
Warning: The barrier generates an audible or visual warning. Examples: rumble strips, proximity alarms.
Virtual: The barrier is established using signs, signals or markings and the laws which pertain to them.
A barrier may be benign for dual-track motor vehicles, yet overturn single-track vehicles. These can topple over a low guardrail or Jersey barrier. A sham barrier for dual-track vehicles such as a flex post can tangle with the pedal or leg of a bicyclist, becoming a threat barrier. Reflectorized pavement markers, which are little more than a virtual barrier for dual-track vehicles, can throw a bicyclist –see this video example.
These considerations are lost in the design of many bicycle facilities. Barriers that are hazardous to bicyclists are being used because they are normal traffic-engineering practice, sometimes only due to lack of knowledge but sometimes enforced through design standards.
On the other hand, a high railing with a handlebar rub strip can serve as an effective and safe deflection barrier for bicyclists, even though it may be too weak to contain a heavier dual-track vehicle.
In Orlando, Florida recently, I saw two other examples of misuse of barriers:
Flex posts used ahead of and behind a parallel parking space which had been reconfigured as a bicycle parking station. Motorists parking in the next spaces would expect a light, stopping impact if they moved too far forward or back at very low speed. The colloquial expression is “kissing bumpers.” Lacking this warning, a motorist already had backed up into the flex posts and damaged one of the bike racks. Here, rigid bollards or a guardrail would be appropriate.
Raised reflectorized pavement markers are being used on bike lane lines, neglecting the fact that bicyclists must enter and leave the bike lane, and often do best to ride along its edge. Nationally recognized guidelines specifically prohibit the use of raised markers here, for that reason.
The most common misused barrier for bicyclists is probably the low railing, which will topple a bicycle over. That is seen in many different varieties, ranging from the conventional Jersey barrier or guardrail to low wooden curbs lining boardwalks, to hand-height railings alongside paths.
Someone has watched my video of Grand Street, in Manhattan, and commented:
John, I watched the Grand Street video (which was kind of fun) but I couldn’t help but notice you are passing a lot of cars, which makes your average speed seem reasonable for the environment.
That average speed, including waits for traffic lights, was 5.5 miles per hour, half my usual. Yes, I do wait for the lights, though many New York bicyclists aren’t so patient.
Please have a look at the video so you can evaluate the rest of this post. Note especially the bus stopped in the street near the start of the video, because that will play in my comments.
Why were my riding companion John Schubert and I passing a lot of cars — and not only parked cars? The others were stopped cars. Even at 5.5 mph, you can pass stopped cars.
Grand Street is one block north of a major arterial, Canal Street, and carries overflow traffic arriving from New Jersey via the Holland Tunnel. In case you want more detail, I’ve posted photo gallery with maps online. I thank John Ciccarelli, John Schubert and Steve Faust, my companions in exploring Grand Street, for the commentary and photos which they contributed.
Here’s one photo, as an example — and you may click on it to see it in the photo gallery. That’s Steve Faust, in the yellow parka.
Trucks blocking the Grand Street bikeway
Grand Street passes through Manhattan’s Chinatown — accounting for the street vendors standing and walking in the bikeway near the end of the video. Grand Street also is where the infamous Chinatown intercity buses pick up and discharge passengers, to avoid paying to use the Port Authority terminal uptown.
Grand Street now has only one travel lane. A second lane was removed to create the bikeway. Whenever a bus stops — or any other vehicle stops in the travel lane — all other traffic stops and waits behind it. Traffic backs up for several blocks.
The bus drivers park the buses diagonally to prevent motorists from sneaking past and colliding with bus passengers, though this does not prevent bicyclists from sneaking past and colliding with bus passengers. You can see one of the buses parked diagonally near the start of my video.
The traffic backups, then, illustrate the law of unintended consequences. The backups result from the redesign that created the bikeway. Possibly, the designers thought that they would calm traffic by reducing Grand Street from two travel lanes to one, in the hope that the traffic from New Jersey would go elsewhere. It didn’t work. To calm traffic, you have to reduce the actual traffic, rather than to try to cram the same traffic onto a street which can’t accommodate it. Instead of calming traffic, the designers created traffic jams, increasing fuel consumption and air pollution.
My observation about traffic flow before the redesign is confirmed by an early, prototypical pre-Streetfilms video. The video stars Mark Gorton, the money man behind Streetfilms, and shows conditions on Grand Street before the redesign. Motor traffic flowed smoothly. Gorton shows vehicles stopped to load and unload, but they don’t block the street, with a second lane available for overtaking.
Gorton’s main concern is with width of the sidewalks, a valid concern in my opinion, though the sidewalks are in fact only narrow in some blocks, and Gorton takes his advocacy to the opposite extreme. He shows a Photoshopped example of how we need to “return control of the street to the communities that live here and the people that live here” by converting part of the roadway into an open-air restaurant — placing restaurant patrons elbow-to-rear-view mirror with moving motor vehicles, where the diners can enjoy a fine mix of food aromas and exhaust stench. This treatment reflects the influence of the “shared space” designs of British architect Benjamin Hamilton-Baillie. These treatments turn the entire street into pedestrian space, and tame motorists, because they can now safely travel only at pedestrian speed without killing pedestrians.
Tellingly, Mr. Gorton never mentions bicycling. Evidently, he had not yet discovered it.
“Return to the people” is code language for “take away space from motorized uses.” That is, to take control away from people who use motor vehicles and give it to “the people,” who all agree perfectly with the point of view expressed in the video. If that sounds vaguely Leninist to you, well, yes, I think so too. Ah, New York, where a wealthy hedge fund manager sounds off with Leninist rhetoric!
Real-world, American-style political pressures came to bear, and we now see the outcome. It’s rather clear that the community, some community — some people — residents, or business people, probably both, and for better or worse — wanted parking for motor vehicles, because there’s still nearly as much as before. On the other hand, Grand Street now has restricted loading zones — and not enough to meet demand. The business community either didn’t understand what would happen, or had too little political clout to demand more space.
Part of the street’s width was, however, “returned to the people” as a bikeway which is, in reality, a sidewalk extension, an outcome so predictable that I would have to laugh if the street hadn’t become such a traffic tangle, and if I weren’t required by law to ride on that sidewalk extension.
Bicyclists didn’t come out very well in this political exercise, and neither did motorists. Pedestrians came out best. They got their wider sidewalk, even if it is supposed to be a bikeway.
OK, now I’ve complained, so it’s my duty to offer a positive alternative.
Are you expecting a screed now on the joys of bicycling in Manhattan traffic on streets without any special treatment for bicyclists? Sorry to disappoint you, I’m not going to claim that Grand Street was a great street to ride on before the bikeway was constructed.
In my opinion, the Grand Street design is not thoroughgoing enough — not radical enough in one sense and not conservative enough in another. To make the street safe and attractive to bicyclists, including younger and less skillful ones, it would be necessary to displace through motor traffic to another street, and to get bicyclists out of the pedestrian zone. A way to accomplish that would be to traffic-calm Grand Street (or maybe another nearby parallel street) using barriers and diverters, more or less like the ones in Berkeley, California — so the street carries only light, local traffic.
In other words, transform the street into a neighborhood street, whose main purpose is local transportation at neighborhood-friendly speeds, like the bicycle boulevards in Berkeley — not a segregated mess, and not a pedestrian playground like upper Broadway in Manhattan. Many crosstown streets in Manhattan look promising for the treatment I propose, and are quite easy to ride now, even without intentional traffic calming.
If the volume of motor traffic were much lower, we might also consider widening the sidewalks where needed.
You may notice my heresy, from the point of view of segregationist bicycling advocates: some motor traffic must remain, as on the Berkeley streets, so the entire street doesn’t become a shared-space ped zone where pedestrians walk with abandon, and bicyclists have to play dodg’em.
John Schubert and I shot another video on Grand Street the same day. At the end of the video, you may view how motorists harassed us on a section without the bikeway, but while on the part with the bikeway, we waited over a minute for a Chinatown bus to unload, had to ride very slowly at one point behind a man with a food vending cart, and had to ride in the travel lane for several blocks where the bikeway was obstructed.
You might also have a look at this video by a unicyclist. It’s a bit shaky, but he comes to the same conclusions I do.
As a reader has commented on the Gilham Road, Eugene, Oregon raised bicycle lane in response to an earlier post, I’ve decided to follow up with some additional information about it.
Here’s a photo of the lane during installation.
Raised lane on Gilham Road, Eugene, Oregon
I thank former Eugene Bicycle Coordinator Diane Bishop for sending me the photo. Her comments in the e-mail which accompanied the photo in February, 2002 are as follows:
I’m curious if you have seen or used any raised bicycle lanes? We installed one this summer and have had mixed reviews from users. Mostly the motorists don’t like it because they are forced to slow down (the road curves around various median islands, etc, and the travel lanes are 10′ wide, dropping the comfortable speed to about 20-25mph). But I”ve also gotten mixed reviews from cyclists. Most really like it, but some are concerned about the slope between the bike lane and the car lane. I’ve attached a photo so you can see what we did. This was taken during construction so we hadn’t done the landscaping, finished the sidewalk, or done the lane line painting. The bike lane stripe is at the bottom of the sloped surface now. The bike lanes are concrete, the auto lanes are asphalt.
The photo was taken at the intersection in the Google map below, looking south.
Microsoft’s Bing mapping application offers a more detailed view, but you will have to open Bing separately to move around or zoom the view.
Microsoft Bing view of Gilham Road at Ayers Road, Eugene, Oregon
I responded to Ms. Bishop, as follows:
You asked me for my opinion, so here it is.
As much as political participation is important in our democratic process, I wouldn’t trust either bicyclists’ or motorists’ opinions of the facility. These opinions generally are swayed by perceived self-interest and don’t reflect professional training. Let’s consider the actual operational characteristics and crash rate.
I’m no fan of raised lanes (called “cycle tracks” in Europe). This design is common in early facilities installed in Europe, but now there is a heavy backlash against them, because studies have revealed them to have a much higher crash rate than riding in the street. The German ADFC has strongly opposed them for the past several years, since the study results came out. The ADFC recommends street-level bike lanes instead. [This press release] is typical of the ADFC position.
“Originally, cycle tracks were constructed to protect bicyclists from motor traffic. But since then, the number of studies which show that the risk of accidents is markedly higher on cycle tracks than on the streets has been growing. Bicyclists who are traveling on a two-way cycle track in an urban area on the left side of the street have 11.9 times the accident risk they would have on the streets. The cause of this danger is an incorrect political promotion of bicycling over the past few decades. In the past, travelers were segregated. Consequently, bicyclists and motorists could not see one another. At junctions, the bicycle traffic is directed onto the street, unexpected by the motorists. And so we have the typical urban bicycle accident. A bicyclist traveling straight ahead, struck by a turning motorist, is the most common type of bicycle accident involving a motor vehicle, states Stefan Brandtner, press contact for the All-German Bicycle Club (ADFC) Baden-Württemberg section.”
A survey of research on the accident rates of streets, bicycle paths and sidewalks is available on the Internet. And here are some links to specific studies posted on the Internet. Some (particularly Pasanen and Wachtel-Lewiston) are well-controlled for the same bicyclist population on the different types of facilities, while others are not, and so the difference in accident rates probably reflects to some degree that people who choose to ride on sidewalks generally are less skilled.
The Risks of Cycling by Dr. Eero Pasanen, Helsinki, Finland, higher car-bike collision rate for one-way sidepaths compared with streets, even though pedestrians are prohibited from the sidepaths (very similar to the installation shown). Extremely high rate of car-bike collisions with bicyclists crossing intersection on left sidepath.
A Survey of North American Bicycle Commuters, by Dr. William Moritz. Relative danger index 5.32 times as high on “other” facilities (mostly sidewalks) as on average of all facilities (mostly streets). Data include all crashes, not just car-bike collisions. Lower ratio than in previous study probably related to typically lower speed and overall higher crash rate of average commuters compared with avid adult cyclists.
On the facility shown, the bicyclist is confined to the space between the slope down to street level, and the pedal-catching curb on the other side. I don’t know exactly how wide the lane is in the installation shown, but it appears to be no wider than 5 feet, with no shoulders, and with shy distance from the curb at one side and the downslope at the other side, the lane’s effective width is much narrower. The AASHTO minimum for a one-way bicycle path is 6 feet, *with* 2 feet of clearance at either side.
So this facility is not wide enough for one bicyclist to overtake another comfortably, even less so for a bicycle to overtake an adult trike or cargo bike of the type Jan Vandertuin is making (last I knew) in Eugene. Even aside from these examples, the carrying capacity of this lane is seriously reduced by its being raised. When bicyclists ride at street level (with or without a bike lane) they may merge outside the bike lane as necessary if the bike lane becomes crowded. In this installation, they can drop down to the street only at the cost of an uncomfortable and somewhat hazardous descent and ascent over the sloped edge. In wet, or worse, icy weather, or if sand or trash has accumulated at the bottom of the sloped edge, a bicyclist could easily be toppled by it.
The raised lane on each side also is bound to be used for two-way travel, because bicyclists do not perceive it as part of the street, and because it is much less convenient to get to the raised lane on the opposite side than it would be to get to a street-level lane on the opposite side. Left-side travel, as the studies show, greatly increases the risk of car-bike collisions. Some bicyclists would choose to ride on a sidewalk anyway — consider a child who wanted to get from one house to another on the left side of the street in the photo — but I don’t like constructing a facility specifically for bicyclists which encourages this behavior (as opposed to a bike route or street-level bike lane, which encourages right-way travel).
Naive bicyclists may assume that they are being “protected” from overtaking traffic by a raised lane, but the lane will cause more crashes than it prevents — certainly so in the case of single-bike and bike-bike crashes and almost certainly so in the case of car-bike crashes, by constraining the bicyclists’ line of travel and leading to a false sense of security. There appears to be an intersection in the background where the raised lane does not go down to street level before and after the intersection to allow merges (is this correct?). The motorists, than, are constrained to make their right turns from the left lane and the bicyclists, except for those at the ends of the skills spectrum — who are well-trained in vehicular techniques or who, on the other hand, make left turns as pedestrians — are likely to turn left from the right lane.
Often the motivation for a particular bicycle facility design is to affect the behavior of *motorists* rather than bicyclists. The classic reason for this has been to make things easier for motorists by getting bicyclists off the road. But here the goal appears to be to make things *harder* for motorists and slow them down by narrowing the lane width they can use. There are many other traffic calming and enforcement measures to slow traffic down and reduce its volume without constructing a problematic bicycle facility.
Another motive for constructing bicycle facilities is often to encourage people to ride bicycles, but again, there are many alternatives in design, and an unsafe facility which is popular is the kind most likely to lead to crashes!
I DO like gently sloped curbs at the RIGHT edge of the area in which bicyclists ride. With such a curb (commonly used on Cape Cod and called the “Cape Cod berm” here in Massachusetts), the trash, sand, water and ice problems still occur but at least most of the time a bicyclist who has strayed off the road can go safely up over the curb.
It appears that there is also a drainage issue. With no storm grate in the bike lane, and a curb at the right side, the lane will only drain if it slopes toward the street. It may be properly sloped now, but concrete slabs tend to tilt after a few years.
Essentially, I don’t see any significant difference between this facility and a sidewalk as far as bicyclists are concerned, other than that pedestrians have a separate sidewalk. I favor traffic calming measures in residential areas, with bicyclists traveling on the street, wide outside lanes and sometimes bike lanes at street level (though bike lanes are often installed where they create turning and crossing conflicts, and other solutions would be preferable); also bicycle paths away from roads to fill in the “missing links” in a bicycle route network, as discussed in the Oregon bicycle plan. This is my honest opinion and I hope it doesn’t upset you too much!
And in turn, Ms. Bishop replied:
On your raised bicycle lane response: no, you didn’t upset me. I’m not sure I agree with some of your comments, but I’m here and can see the lane and use it and you haven’t had that chance. Now that we have had it installed for a while and I’ve had a chance to ride it on several occasions, I’ve begun thinking we probably won’t keep this in our “toolbox” of street treatments. However, there are some things that seem to be good. I haven’t done a video study of the lane usage yet because it was completed so late in the fall last year. I’ll be doing that this spring. If I come up with
anything useful, I’ll let you know.
We don’t get snow or ice here (well, MAYBE a sprinkling of snow that lasts about 1/2 hr. once a year) but we do get a lot of rain. I was concerned about the sloped surface being slippery, but I’ve found it surprisingly easy to ride in the rain. I’ve also tested running up and down the slope pulling various trailers and they track as smoothly I can’t tell the difference from riding on a flat surface, even when one trailer wheel is over the edge while I’m still on the flat bike lane surface. One of the concerns raised by the neighbors (that I haven’t seen materialize) was that the kids would be out there using the sloped surface for playing with their bikes and skateboards.
I think you may be right about less competent cyclists not thinking about merging down into the auto lane to make their left turn. I hadn’t anticipated that when we decided to build the lanes. But I don’t think it will lead to more 2-way riding for 2 reasons: we have sidewalks for those you mentioned who would only be traveling a few houses away and those sidewalks are more accessible; and also because the traffic is relatively light on the street where we have the raised bike lanes (its a neighborhood collector).
For your suggestions on why we might have tried the design, actually you were right about the traffic calming interest…some of our folks were looking for ways to reinforce other traffic calming methods they built into the project. However, *I* was more interested in trying out a bike facility that might appeal more to children in order to get them off the sidewalks (which I agree with you are much more dangerous than the street). Our hope was that we could get them out in the street area where they will be seen by the motorists and slightly separated so they would be willing to try it. Raising them slightly higher seems to have the added benefit that motorists can see them better. I”m not sure we really accomplished all that.
So, thanks for your ideas. Like I said, I don’t think we are going to do that design again, but it was an interesting experiment. We want to make this community even more bicycle-friendly than it is, so are willing to try different approaches. Unfortunately I had very little time to research the design and, while [State of Oregon Bicycle coordinator] Michael Ronkin had it in the state bike/ped plan, he couldn’t suggest people or communities to check with in Europe.
And in turn, I replied:
Thank you very much for your reply. From your description, the sloped surface between the bike lane and the roadway appears to be less severe than it appears in the photo.
On another topic: there is a very interesting citation of a rather old Eugene study in a paper by John Williams, Alex Sorton and Tom Walsh. Dr. Sorton has told me that the paper includes data on the crash risks on streets, sidewalks and off-road paths. I would be most interested in knowing more about the study and if possible, obtaining a copy of it. I would be willing to pay for copying expenses and offer a service in return: conversion of the study into computer-readable format as I have done with a several other studies including, most recently, the classic 1976 Bikecentennial study — which I have posted it on my site.
Mountable curbs have been suggested as a way to separate bike lanes or so-called “cycle tracks” from the rest of the street.
I am not in favor of such curbs. After all, any obstacle has hazard potential, and a mountable curb can have more than you would imagine.
As a cyclist rides along a mountable curb, tire “drift”, the slope and the offset front-tire contact patch make the bicycle hard to steer, so it must be held in a straight line by a continual effort. A similar issue with a different cause is discussed here.
Worse, if a mountable curb is slippery, it is no longer mountable, though it may deceptively still appear to be. The resulting fall may be a skidding-type fall or a diversion-type fall, in which the bicycle’s front wheel is swept to the side.
Trash, sand, snow or ice can accumulate along the curb. Installation of a curb-separated “cycle track” on a conventionally crowned roadway would require sloping the road surface away from the new curb to avoid this problem.
Even this unusual measure would not make snowplowing or street cleaning any easier, with an abrupt longitudinal change in elevation in the traveled way.
An approach used in Copenhagen is described here — a second line of drains at the curb (in the case shown, not mountable). The drains carry away standing water but does not solve the problems with trash, sand, refreezing water in the added, new gutter, snow clearance or street cleaning.
Cambridge, Massachusetts bicycle coordinator Cara Seiderman has shown a photo of a machine with a large, cylindrical, horizontal rotating brush used to clear snow from Copenhagen facilities. Perhaps this answers some of the issues with snow clearance and perhaps it also is used for street cleaning, but the expense is considerable, and the need for such equipment may not even be considered when a facility is constructed.
Snow clearance and ice melt issues on the 9th Avenue facility in New York City are described here; this is a barrier-separated rather than curb-separated facility, but the issues are similar. The bikeway here is wide enough that conventional snowplows could be used, but refreezing of meltwater from the windrow of snow between the bikeway and the street required heavy salting, and salt rusts bicycles.
So, is the prohibition of a barrier between a bike lane and the rest of the street in the AASHTO bike guide arbitrary? Does it only reflect issues with cyclists’ being able to enter and leave a bike lane, which can be addressed with a mountable curb? Not hardly.
Promotion of curb-separated bikeways, without considering the technical issues,or with “band” aid solutions such as mountable curbs, is all too typical of much bicycling advocacy.
This post supplements my previous post linking to documents about Davis bicycle facilities. Please bear in mind that Davis was the first community to introduce bike lanes in the USA, and that its bicycle program strongly favors conventional bike lanes, which are separated from the adjacent lane only by a painted stripe. However, I have found that the Davis documents uniformly and strongly recommend against bike lanes behind barriers or parked cars. Not only that, the recent warnings are more definite than the early ones. Some quotes, starting with the most recent and working backwards in time:
The early experiments included three different types of bike facilities (see examples at the top of this section):
bike lanes between car lanes and the parking lane (Third St.),
bike lanes between the parking lane and the curb (Sycamore Lane), and
bike paths adjacent to the street, between the curb and the sidewalk (Villanova Ave.).
The first bike lanes included all of these types, to test them in real life to see how effective they were. The on-road lanes worked best, the behind-parking lanes were the worst, and the adjacent paths were found to work in certain circumstances. This is an example of the wide level of experimentation that occurred during this period. Had the city tried to do extensive research without construction, it might have settled on an inferior design. And not having tried all three designs, it might not have recognized it as inferior, and the entire experiment could have been declared a failure.
Dale Lott (one of the early advocates for special bicycle facilities in Davis, who also conducted research as to their safety and effectiveness), “How Our Bike Lanes Were Born“, op-ed piece which appeared in the Davis Enterprise in 2003:
We insisted on some experiments that turned out well and some that were flops.
One flop was on the first block of Sycamore north of Fifth where we put bike lanes next to the curb with parking next to the auto travel lane. It looked great on paper, but was a mess on pavement. When cars turned into the University Mall driveway, they crossed the bike lane. Both driver and rider, whose view of each other had been obscured by the parked cars, had an emergency situation.
Because Davis pioneered the bike lane and other bicycle facilities in this country, it is not surprising that some “experiments” were less successful than others. One such example was the construction of “protected” bike lanes where motor vehicle and bicycle traffic was separated by a raised “buffer” or curbing. In some cases, the bike lane was established between the parking shoulder and the curb line (i.e. cars were parked on the left of the bike traffic lane). Needless to say, any “benefits” of such facilities were soon found to be outweighed by the many hazards created for their users.
Most such well-intentioned, but ill-fated designs were phased out long ago. However, some facility design decisions made decades ago were not so easy to remedy. The most pervasive example in Davis is the two-way bike path immediately adjacent to a roadway. Particularly problematic are single two-way paths located on only one side of the adjacent road. The problems associated with these designs have been described in any number of publications, and they are well illustrated at several locations in Davis. In spite of this documentation, some residents, city officials, and developers remain quite vocal in advocating such facilities when new construction is being planned and designed. The city and campus have attempted a variety of mitigation strategies to reduce the hazards or inefficiencies associated with these side paths, but many observers believe that continuing to build such facilities is wasteful at best.
Deleuw, Cather and Company.: Davis Bicycle Circulation and Safety Study. 1972 (excerpt — for complete document in three parts, see table of contents page.
…Protected lanes located between the parking shoulder and curb line have most positive separation. However, the parked cars create sight distance problems at driveways and intersections. Inability to cross streets in midblock in this type of treatment results in two-way usege which, in turn, leads to intersection problems described subsequently…
Sidewalk and Independent paths
Sidewalk pathways eliminate midblock bike-motor vehicle friction. However, frictional interference of pedestrians may discourage usage of these facilities as does frequent interruption by cross streets and driveways or meandering of the path. An additional problem is establishment of a visual relationship between motor vehicles on the sidewalk path on approaches to intersections…