Grist in the mill

Winter gets me thinking about how our streets are unforgiving. While riding on streets covered with fresh snow I sometimes imagine what would happen if I make a small mistake. Don't get me wrong, I don't mind slipping on snow. And Toronto winter streets are often clear of snow. When there is snow or ice, little slips sometimes happen but I just keep going. There's a difference in feelings of comfort, however, between slips on quiet side streets and slips on main arterial streets where we are typically forced into a narrow space between parked and moving cars. On arterial roads it feels like I'm grist in the mill, being ground into flour. Here we are an annoyance to drivers, but provide a valuable service of "friction" to calm traffic down. This seems to be our lot as Toronto cyclists.

Forgiving highways

The concept of "forgiving roads" first arose amongst traffic engineers as a way to design roads to forgive mistakes made by drivers. The reason our highways have wide shoulders and grassy areas with few obstacles, for example, is to allow wide enough clear zones to bring vehicles to controlled stops if they leave the road. If for someone were to accidentally drive off the road they would have lots of room to slow down. It was only natural for traffic engineers to start applying the forgiving highway principles to all rights-of-way. During the 1966 National Highway Safety hearings, national road safety expert Kenneth Stonex, who began his career at General Motors sought to apply the highway principles to urban streets. In this way North American urban environments began to be reshaped entirely for the automobile.

“What we must do is to operate the 90% or more of our surface streets just as we do our freeways… [converting] the surface highway and street network to freeway road and roadside conditions,” Stonex testified. It sounded logical at the time… and a great political solution, because the responsibility for fixing the problem once again fell on government, not the individual. We dove deep into the Forgiving Highway philosophy and still have not come up for air.

Why should forgiving roads only apply to auto drivers?

While highways have been designed so that drivers can maintain a high speed in relative safety, urban streets that are forgiving in this sense completely ignore the safety of everyone who isn't in a car. An urban street that accounted for people walking and cycling would require much different parameters. There is no way a pedestrian or a cyclist can compete with the speed of drivers. And yet urban streets are too complex to match highway driving. There are too many intersections with decisions to make to allow drivers to reach highway speeds. We are left in an awkward position where drivers complain of urban streets of being too congested and slow but engineers still have a predilection towards enabling drivers' ability to go fast. Drivers can still reach speeds - during the non-congested times of day - that are clearly unsafe. Cyclists are still forced to bike in the narrow space between parked cars and streetcar tracks, which only gets narrower and more dangerous in winter. Pedestrians are forced to scurry across crosswalks in the hope that drivers see them. That's not useful for anyone. The streets, instead, should be forgiving enough so that the most vulnerable person is able to safely use it, with a very low risk of death. Too much to ask?

The dark age of cycling advocacy is over

Cycling advocacy, however, has only recently begun to become more vocal in asking for an alternative to roads that prioritize high speed motor traffic. Cycling advocacy went through its own "dark age" when it was dominated by a ultra-libertarian and elitist ideology called "vehicular cycling" which put all the onus on cyclists to keep up with motor vehicles around them. All unfit, slow, young, old cyclists be damned. Harold Munn, who invented the term, defined vehicular cycling as "The task is to convince [cyclists] to operate their bicycles as they do their automobiles."

"Say what you will about vehicular cycling, but nobody is going to argue that it’s “forgiving," writes Bill Lindeke, in an excellent article on very same topic of forgiving streets for all. Lindeke read Bruce Epperson's interesting history of the vehicular cycling ideology (at least interesting for a bike nerd). Vehicular cycling was born in the United States in the 70s and 80s when the idea of creating bikeways had a stillbirth, leaving just university town Davis, California with a network of bikeways. The advocates and planners in Davis, Epperson describes as being a "third stream of egalitarians", alongside the vehicular cyclists and a middle stream of pragmatists.

Epperson writes that in Davis, the planners and advocates emphasized the vulnerable:

The third-streamers openly advocated policies that specifically targeted the weakest and most vulnerable bicyclists and involuntary users who rode strictly out of need, not choice. Together, these comprised cycling’s lowest common denominator, and for the third stream planners, they formed the yardstick by which to measure success or failure. If high-end recreational cyclists couldn’t live with their solutions, well, there were lots of other sports in the world they could turn to.

Lindeke asks the key questions that North American cities are only now beginning to ask:

Do you design bike lanes with the assumption that all the cyclists will be fast, efficient, well-trained, and “educated” about how to ride in traffic? Or do you design bike lanes for people who will move slowly, dawdle, and are perhaps younger or older or riding in groups? Do you design lanes for people who occasionally fall down?

Cycling advocacy in North America has made a sharp turn away from elitism of vehicular cycling and has started demanding cities designed for the vulnerable, the dawdlers, the old, the young. And some cities like New York, Portland, Chicago have heard the call. Toronto?

Councillor Vaughan has expressed his concern that the entertainment district (which includes Richmond and Adelaide) should be more than "thoroughfares" and need to be "destinations" as well. Though Vaughan doesn't mention it in this article, he has been championing the conversion of Richmond and Adelaide to two-way streets as the means by which to create a "destination". The two-way streets conversion may preclude the installation of separated bike lanes, and conversely, separated bike lanes would make a conversion to two way much harder.

This urge for two way streets doesn't hold much water. We only need to look at Manhattan where one way streets reign. The streetview photo above is of Broadway where the car lanes have been reduced to provide a meridian for safer walking and a separated bike lane as a safe, comfortable space for people to bike.

Two way street conversion is a popular idea amongst some progress urbanist types. Former mayor David Miller recently repeated the same refrain to a cycling advocate friend (they bumped into each other on the street and started discussing bike lanes). Miller, like Vaughan, presented the same notion that Richmond and Adelaide need to be converted to two way streets create destinations and that the bike lanes would prevent that from happening. This notion is not the consensus. Matt Blackett of Spacing recently spoke eloquently on CBC Radio in defence of the importance of separated bike lanes on Richmond and Adelaide.

Manhattan is full of one way streets and has the liveliest street life of any city in North America. New York City has been working on calming its busy network of one way streets for the last few years, including adding plazas, meridians, and separated bike lanes. As far as I know, they haven't converted any of the one way streets, bucking the conventional wisdom of two-way conversions.

Converting a street to two way is not a guarantee of creating destinations, if that were true then Bathurst and Dufferin would be great streets to hang out on. Nor do one way streets in themselves automatically result in dead street life. If that were true, then neighbourhoods across the city would be outraged with their one way residential streets.

There are plenty of ways to add life to a street; to make it more comfortable to walk or bike on. Instead of sticking to a tired trope, let's look at the whole range of options.

Councillor Adam Vaughan told the press yesterday, in regards to the news that the Environmental Assessment on Richmond and Adelaide bike lanes will be starting, that he is willing to consider bike lanes but that "he hasn’t made up his mind. The entertainment district needs to be considered as a destination, not just a series of thoroughfares". (Thanks to Tino for photo of Sherbourne.)

Vaughan hasn't made up his mind yet? Bike lanes are "thoroughfares"?! Bike lanes for Richmond and Adelaide have been in the City's Bike Plan for 12 years (some say it came up even earlier). Let's take a look back over the last 12 years.

2001 Bike lanes are proposed for Richmond and Adelaide in the Bike Plan (appendix, map).

2001 Bike Plan makes a promise that "All Toronto residents will be within a five minute bicycle ride to the bikeway network." The Bike Plan plans a grid of bike routes throughout the entire city. Even then there are gaps, even downtown. Progress is slow right from the start.

2001-present A smattering of bike lanes are built (and some stopped and some removed), most of them in the suburbs where roads are wider and don't require taking out car lanes.

2009 Councillor Kyle Rae declares Bloor at Yorkville a "destination" and didn't think bike lanes were "appropriate" (in his speech supporting bike lanes on Jarvis). The sidewalks are expanded and no bike lanes planned nor installed, despite protest from cycling advocates.

2009 A Ward 20 Cycling Committee is formed with the help of Councillor Vaughan's office. Many of the committee members eventually leave because of Vaughan's reportedly heavy-handed involvement but not before producing a report (see below).

2010 The City's Cycling Unit holds packed public meeting on the Bike Plan of over 200 people in February in Metro Hall. Dan Egan, manager of the Cycling Unit, outlines their priorities for the downtown bikeway network for 2010-2011. He mentions staff will advance Richmond and Adelaide bike lanes in their spring report to Public Works and Infrastructure Committee. The March report mentions nothing about bike lanes on Richmond and Adelaide. It's not clear why not? As a Miller-controlled committee, PWIC could have pushed for bike lanes on Richmond and Adelaide. It often happens that staff won't propose something if they know a local councillor is opposed.

2010 The Ward 20 Cycling Committee goes "rogue" and produces a report requesting protected bike lanes on Harbord, University and Richmond/Adelaide.

2010 Rob Ford wins election that fall.

2010 Councillor Denzil Minnan-Wong proposes cycle tracks for downtown, including Richmond/Adelaide.

2011 Vaughan sends letter to residents condemning "barricaded" bike lanes and accusing the Bike Union of not working with the local "community". Through a Vaughan initiated process the community didn't identify any east-west street through the city's core. It's not clear how Vaughan defines "community" but presumably it doesn't include people who commute to work in the area or who have to travel through the ward.

2011 Vaughan won't consider bike lanes on the well-used bike corridor, John Street, because he says it is meant to be a destination and not a transportation corridor (much as he's saying now about Richmond and Adelaide). Vaughan doesn't advance request to make alternative route on Peter/Soho safer crossing at Queen St.

2012 City Council approves an Environmental Assessment for Richmond and Adelaide.

2012 At the Harbord Village Residents Association meeting on bike lanes, Vaughan says to the group "Now when we build bike lanes they must be separated. Painted lanes are good but they aren't safe enough. My son needs something safer than just painted bike lanes." And he also says "People in this neighbourhood [Harbord] cycle but they can't do it safely. We don't accept such unsafe conditions for drivers, nor for pedestrians, but we accept it for cyclists. We need to change that."

2013 Richmond and Adelaide EA begins.

If Vaughan sees the big benefit of cycle tracks for the safety of cyclists, why hasn't he yet supported cycle tracks on Richmond and Adelaide? They were in the plan since 2001 and Vaughan was a major powerbroker when Miller was mayor. Richmond and Adelaide weren't brought to PWIC during that whole time.

And if Vaughan thinks Richmond and Adelaide aren't appropriate for bike lanes, then where? Richmond and Adelaide are nicely situated between two cycling corridors, King and Queen, but don't have the major drawback of streetcar tracks. The staff creating the Bike Plan were unable to find any other streets south of College that were useful for bike lanes.

Toronto seems to have a quite particular opposition to bike lanes by some progressives. The codeword is "destination", and it's been applied to a major arterial such as Bloor and now Richmond and Adelaide as a reason for not installing bike lanes. It's as if somehow the arterial road will cease to being a major street and turn into a residential street.

Vaughan says he supports cycle tracks. When will Vaughan make up his mind about Richmond and Adelaide?