Author Archive | Jarrett

sorting out rail-bus differences

Here's a crucial passage from the book I'm working on, though it may will end up in the next book rather than this one [Human Transit].  The topic is emotive, so I'm trying to be very carefully factual here.  I welcome your critiques in comments.  If you disagree on a matter of fact, please provide a reference to a source. 

In 2009, the then-popular [but now defunct] blog the Infrastructurist asked its readers whether streetcars are better than buses, and why.  Readers came up with 36 responses (listed verbatim here) that formed a good summary of popular perceptions about the rail-bus distinction.

Of the 36 reasons, only six refer to an intrinsic difference between bus and rail technologies.  All the others fall into two categories, which I’ll call misidentified differences and cultural feedback effects

Misindentified Differences

In your city, the rail system has lots of differences from the buses, including technological differences. But that doesn’t mean that all these distinctions are true rail-bus distinctions.  For example:

  • Propulsion: electric vs internal combustion.   In most North American cities that have both bus and rail, the rail is electric but the buses use internal combustion (diesel, “clean diesel,” or various forms of natural gas).  Electric motors have obvious advantages – in emissions, noise, acceleration, and comfort – but none of these are true rail vs. bus differences.  Rail can be run by internal combustion, and buses can be electric.  If you want to compare your electric rail option with a bus option, compare it to electric trolleybuses.  If you want to compare your internal-combustion buses with a rail option, compare them to internal-combustion rail options such as the Diesel Multiple Unit (DMU).
  • Mixed-flow vs exclusive-lane operation.  Transit speed and reliability are mostly a result of how much you stop and what can get in the way.  Rail is more often run in exclusive rights of way, but some streetcars run in mixed traffic and some buses run in exclusive lanes.  Monorails never get stuck in traffic, but neither do buses in Brisbane, Australia’s busway system.  Most city buses can get stuck in traffic, but so can any streetcar, tram, or light rail vehicle that runs in a mixed traffic lane.  (A major problem for BRT in North America is that people keep taking junkets to Latin America, where BRT is powerful but the economic context is too different, rather than to Brisbane, where they could see high-end BRT working in a wealthy city.)
  • Off-board “proof of payment” fare collection vs. “pay the driver” fare collection.  Fare-collection style has big psychological effects.  “Pay the driver” slows down boarding and is a greater hassle for all concerned.  Some rapid transit sytstems (rail and bus) provide paid areas with faregates, eliminating this delay.  The other solution is “proof of payment,” which means that you buy a ticket on the platform (or already have a valid ticket) but you only show it if a roving “fare inspector” asks to see it.  If you don’t have one, you pay a fine.  Rail is more likely to use “proof of payment” than buses, but there are exceptions both ways, and there’s no necessary link between the rail-vs-bus choice and the fare collection system.  High-capacity bus systems are beginning to shift to “proof of payment” fare collection to eliminate fare-related boarding delay.  UPDATE: San Francisco now uses proof of payment on its entire bus system.
  • Frequency and Span.  Your whole rail transit system may be frequent, while some your buses aren’t, and in that case, you’ll naturally associate frequency with rail.  As we saw here, a good Frequent Network map, which shows both frequent rail and frequent buses, will clear up that confusion.  Buses can be very frequent, while some rail services can run infrequently or peak-only.  (We usually call those commuter rail.)

Cultural Feedback Effects

A community’s attitudes toward rail and bus technologies can easily affect they way they are operated and presented.  In short, people who believe that rail is better than buses will tend to act in ways that make that belief true.  For example;

  • Differences in investment or care.  A community that believes that buses are only for poor people, or that rail is the mode of the future, will under-invest in buses as opposed to rail, producing a difference in quality that will reinforce that belief.  It may also hold bus operations staff to lower standards than rail staff, and encourage other cultural differences between bus and rail operations that become real for the customer, but are not intrinsic to the bus-rail distinction.
  • Perceptions of permanence.  If you don’t stop to think about it, rails in the street will make a service feel permanent, especially if you’re used to hearing people tell you that rails imply permanence.  History clearly shows that rail systems do stop running if their market disappears.  True permanence lies in the permanence of the market, and that lies in the pattern of development [See Human Transit Chapter 14].
  • Perceptions of legibility.  The notion that a bus might do something unpredictable and a railcar won’t is also a cultural feedback effect, typically the result of insufficiently clear and compelling information about the bus network.  It is quite possible to build bus services with such a high level of investment in infrastructure, such as stops and stations, that the routing is as obvious as a rail line’s would be; the Los Angeles Orange Line bus rapid transit system is a good example. 
  • Regulatory differences.  Government regulation often enforces different rules for road transport as opposed to rail transport.  These regulations are themselves a kind of cultural feedback, differences in habit and history between agencies that regulate roads and those that regulate rail.  By enforcing different standards and safety requirements, these regulations can cause outcomes that amplify the apparent difference between road-based and rail-based transit. 
  • Different potential for mission-creep.  If you build a stretch of road for a busway, there’s always a danger that somebody might try to open it to cars.  If you don’t trust your government to protect the stated purpose of a facility, this can be a major decision factor.  This issue applies, however, to the narrow range of cases in which a road or lane is being built that could be useful to cars but is closed to them.  It is not an issue where the proposal is to reallocate existing roadspace from cars to transit, nor when building a higher-end busway whose design makes it useless to cars even if they were allowed on it.

Intrinsic Bus-Rail Differences

When we set aside those two categories and look at the differences that really follow, intrinsically, from the rail-bus distinction, there appear to be seven, and only the first three of them are always to rail’s advantage:

  • Capacity.  Where demand is high, rail can serve that demand at a higher ratio of passengers to on-board staff, which means that once you absorb the (often large) construction cost, you will be able to offer greater capacity for a given operating cost.  A transit vehicle that’s too crowded to board doesn’t meet any of our seven desires for useful service, so this point is often decisive in favor of rail.
  • Ride quality.   Ride quality in buses is improving, and guided busways may give buses an even more rail-like feel, but new rail systems will probably always have an advantage with their smoother running surface.   Is the smooth ride of rail indispensible to a useful network?  This can be a tough question whose answer may vary from one community to another.
  • Limited energy-efficiency and emissions consequences tied to the difference between tires and steel wheels.  Again, the primary factor governing energy-efficiency and emissions is propulsion (electric vs internal combustion), which is not intrinsic to the rail-bus difference.  However, there is a small range of differences that arise from the physics of steel-on-steel vs tire-on-road operation, and that favor the former.
  • Noise from wheel friction.  Most noise impacts are due to internal combustion, which either rail or buses may use, so that’s a misidentified difference.  Rail transit lines that intersect streets may be required to install noisy crossing signals — a valid response to the extreme weight of commuter rail trains but more controversial as applied to light rail.  These regulatory requirements may be cultural feedback effects.  But rail has a further noise disadvantage that really is intrinsic: the tight fit between steel wheel and rail causes noisy friction when going around curves, especially when going fast. 
  • Some variable cost differences.  Broadly speaking, bus-based projects that use portions of existing roadway will be much cheaper than building rail for those same segments would be.  Beyond that, costs for bus vs. rail projects can be hard to compare.  Capital costs for rail include vehicles, while a busway is sometimes run with an existing bus fleet.  Certain bus-rail comparisons in certain corridors may turn up significant differences in operating cost that may be valid in that situation, but need to be checked carefully to ensure that they assume the same factors on both sides.
  • Maneuverability around obstacles is a specific issue for rail in mixed traffic, usually light rail or streetcars.  In mixed traffic, minor obstructions routinely occur in a lane, especially if the lane is adjacent to on-street parking.  People stop in the lane to make deliveries, get into and out of taxis, and parallel-park.  Accidents and breakdowns happen.  If these events block a streetcar, the streetcar is stuck.  A bus, in the same situation, can often go around the obstruction and continue.
  • Ability to extend existing infrastructure.  If you’ve already built rail on a large portion the length of a travel corridor, it may be logical to build rail on the rest, so as not to create a technologically required connection.  On the other hand, busways can often eliminate extra connections because buses can run through the busway but then flow out onto ordinary streets.  In each case, an advantage goes to the technology that makes better use of the infrastructure that already exists, whether road or rail.

Of course, in a particular transit debate, you may not have all of the choices that I’ve articulated here.   Still, it’s important to remember that most of the things you hear about why rail is better than buses are not true in the abstract, as facts of geometry or physics that follow from intrinsic differences between roads and rails. 

It may very well be that rail is culturally better than buses in your city, in which case all you’re really saying is that people in your city think rail is better than buses and will therefore tend to act in ways that make that true.  If you’re interested in appealing to your current population, and motivating them to make investment decisions based on their current perceptions about the benefits of rail, that may even be a good reason to build rail even if you don’t need its intrinsic benefits. 

But if you’re thinking in longer-range terms, don’t forget:  Attitudes, assumptions and perceptions will change over time.  Physics and geometry won’t.

UPDATE!  See endnotes for this post here!

denmark’s cost-containment rockstar

Michael Todd has a disappointing article in Miller McCune arguing that High Speed Rail projects are likely to go over budget.  His justification is, well, that they're large capital projects, and large capital projects often go over budget.  Yes, they do.  But this isn't an argument against high speed rail or any other major capital project.  It's an argument for better approaches to cost estimation and control. 

Nowhere does Todd justify the implication that high speed rail projects are at greater risk of cost overrun than, say, huge urban freeway tunnels such as Boston's Big Dig, Sydney's Cross-City Tunnel, or the likely tunnel in downtown Seattle's future.

But I'm grateful to Todd for linking to a very useful 2008 article by Ryan Blitstein on the work of Danish economist Bent FlyvbjergRead it.  It's a good overview of Flyvbjerg's important work on cost overruns and strategies for predicting them.  For more, see Flyvbjerg's book Megaprojects and Risk.   

Note, by the way, that the problem of cost overruns is conceptually separate from questions about why capital costs, predicted or not, are so high

sydney: it’s 10 pm, do you know where your buses are?

This won't amaze readers in places like San Francisco or Boston, which have had Nextbus.com for years. But it's an important step for Australia.  Realtime locations of Sydney's buses, via a new app by Flink Labs of Melbourne.

Syd buses realtime

Not sure what the colours mean.  They need to be colour-coded for inbound vs outbound, which otherwise can't be distinguished. 

Thanks to Chris Loader, who blogs about Australian public transport at Charting Transport, for the tip.

email of the week: should blue lines have blue buses?

From a longtime Canberra-based reader:

PB150032 In your latest post on [San Francisco] bus wrap art, you refer to your fondness for colour-coding of buses, etc for different service.  For instance in Canberra, this would see the Red Rapid using red coloured buses, the Blue Rapid using Blue coloured buses, and so on.
[JW:  The Red Rapid and Blue Rapid are the two frequent rapid corridors that connect the major dense nodes of Canberra to each other, with widely-spaced stops.  They are the top priority for bus lanes and other speed/reliability improvements.]
 
Which I personally think is great in promotion of the service, making the service stand out – it also helps give a rapid bus (which isn't run solely on transitways) an identity akin to a light rail line.
 
However, I've always found that schedulers don't like it as it limits the general number of vehicles available to run a network. It also removes the ability to use a vehicle in one service type and have it continue its run on a rapid route – thereby removing a connection for some passengers  …  And I'm sure there's a whole stack of other reasons which schedulers and operators will through up in relation to this.
 
So, I guess the question is, given that this is more of an aesthetic improvement … do the benefits measure up to the costs?

Seoul, South Korea went a long way with this idea, branding all their buses with four colors that indicate different functions in the network (Trunk, Branch, Rapid, or Circulator).  Paint schemes are often used to distinguished closed Bus Rapid Transit [BRT] systems (systems where buses do not flow through onto other corridors, but remain confined within the BRT infrastructure.)
DSCN2405    DSCN2519
Los Angeles Metro has painted their fleet two colors, red for Rapid and orange for Local.  Even with two colors, the "Local" is problematic.  Orange really means "everything but Rapid," including limited-stop and freeway-express services that wouldn't satisfy anyone's definition of a "local."
And even so, sometimes you see an orange bus on a Rapid line, or vice versa.  I've never seen a painted color scheme where this never occurred; sometimes the dispatcher needs a red bus and all he has are orange ones.  Sometimes an orange bus breaks down and the nearest available spare is red.  You'd rather we didn't send out a bus at all? 

I do think, however, we could be doing much more with signage to highlight color-based brands. 

aaron renn on innovation

Aaron Renn at the Urbanophile has an especially fine piece on innovation, and the reasons it's hard to cultivate. 

If we consider the parable of the sower, we tend to think that the problem of innovation is not enough seeds. But the true big problem is not enough good ground. Every city and organization I know has tons of seeds raining down on them every day. I’m constantly amazed at the incredible innovative thinking and ideas that I come across in practically every city I visit. The problem is that most of those seeds are landing on the rocks or in the weeds.

But as a consultant, I was a little surprised by this:

Consultants … exist outside the org chart. To steal a phrase, they stand behind a “veil of ignorance” about their status in the hierarchy. Consultants take great pains to maintain this, which is one reason why consultants have such nebulous, generic titles. …

In fact, I hate to say this, but a lot of times all consultants do is talk to middle managers at the client and document up what they’re told for higher level consumption. That’s one reason middle management particularly despises consultants.

True, but this can also be why middle management sometimes loves consultants.  When I start exploring a client agency's issues, I sometimes find that some mid-ranking planners have already figured out what needs to be done, but aren't able to get their insight up through the layers to the executives.  My role is sometimes to be that conduit.  Obviously, I don't pass on ideas that I don't think make sense.  I'm expected to reach my own professional judgment about the best way to reach the agency's goals, and I do.  But if that judgment happens to match what certain mid-level staff already know, and sometimes it does, then yes, in presenting my recommendations to the executive I'm also presenting theirs. 

Obviously, the people above them who were blocking those ideas may not appreciate it, but this is why "middle management" is a relative and nebulous term, not unlike "middle class."

online “map movies”: useful?

Can animation help people understand their transit options?  The Rotherham Metro Borough Council in the UK has done some simple "map movies" that highlight the paths followed by buses and trains.  Here's a still:

Rotherham map movie still

Watch the actual animation here.

As they stand, they're limited in usefulness, as the icons move along the routes with no indication of frequency.  They certainly do advertise complexity, which is accurate; this looks like a very complicated network.

But it's easy to imagine taking this to the next step, showing by animation the scheduled paths of all the services in a transit system.  This would be especially helpful in helping citizens understand pulse systems, where the integrated scheduling pattern is an essential part of how the network gets you where your going.  Now that I think of it, I'm pretty sure this has been done, but I've never seen it on a public information website, which is the obvious next step.

comments of the week: against sustainability

Really, the comments are the best thing about this blog.  Distracted as I am by the book project, I dash off an idle post in 15 minutes, suggesting we might consider substituting the word durable for sustainable, and I get a rich lode of comments that expands the thought in several directions, argues pro and con, adds Dutch, French and Spanish points of view, and even finds its way back to antiquity, per Mark:

It seems we haven't really improved upon the Romans in this, as I think the three legs of Vitruvius's stool of good architecture and urbanism: commodity (well fitted to human needs); firmness (durability and resilience); and delight (self explanatory) pretty much cover it. In our discussions on sustainability and resilience we hardly say anything about delight/beauty forgetting that we have to love places to want to preserve them.

… and — in the same spirit of nothing having changed — ends (for now) with a fine evocation of apocalypse from frequent commenter Wad. 

The world we live in wasn't designed to be sustainable. Biological cells die and regenerate, soil becomes less fertile, land erodes, water evaporates, metals oxidize and species go extinct.

In the human-built realm, nations break away or are swallowed by conquest, empires fade away, languages appear and disappear and communities are settled and abandoned.

Stasis would be a wonderful alternative to the bleakness of chaos. Yet it has its own perils.

Agricultural societies that produced monocultures of a specialized crop suffered famine when some force disrupted growth cycles.

Supply regions specialize in the extraction of a good, but are blindsided when resources are exhausted. Industrial societies aren't immune, either. Economic policy in the Upper Midwest starts and ends around reactivating factories and producing more stuff again.

Sustainability itself is unsustainable.

But as with any satisfying apocalypse, you've got to care about what came before it.  So browse the whole comment thread!  More book snippets soon.

durable urbanism? durable transport?

Are you tired of the word "sustainable"?  Does it seem to lecture rather than inspire?  Does it feel defensive, perhaps even conservative in its suggestion that humans should have no higher ambition than to sustain?  Doesn't sustaining sound, at times, like endless, thankless work?

Well, in French the equivalent word is durable.  So in an idle moment I wonder: what if we used "durable" in English?  Durable urbanism.  Durable transportation.  Durable energy.  Durable lifestyles.

"Durable" shares many virtues with that more popular alternative, "resilient."  There's already a Resilient Cities movement, and an excellent book on Resilience Thinking.  

What I like about both words is they imply an intrinsic strength.  Sustainability implies the endless labor of sustainers, while durability and resilience are just features of the thing itself. 

But "durable," in particular, sounds strong, even masculine.  It's a quality sought in boots, storm windows and SUVs.  Guys want to be durable, and to live in a durable world.  They certainly don't want to be sustained.  (And let's face it, a lot of the people resisting sustainability are guys.)

Not sure.  Something to try, maybe.  

the connection-count test

As I look at the new metros being built in the developing world, I'm noticing some striking connection-count problems.  Consider Delhi, a city I know a bit:

Delhi metro frag

The full Delhi Metro network map is here, but this slice is the only part of the system where lines connect with one another. 

What's wrong with this picture?  Well, suppose you want to go from Shivaji Park, on the green line in the upper left of the image, to Khan Market, in the lower right.  That's right: three connections.

Developing a new metro in a crowded city is always an exercise in compromise, but I'm struck by how often one of the first compromises is network integrity, easily measured in the reasonableness of the number of connections required. 

In an idealised grid network, the maximum number of connections for almost any trip is one.  Plenty of real-world networks require two connections for a range of trips between secondary stations.  But requiring three is pretty remarkable. 

music video for subway map lovers

I’m advised that I’d like this subway-map-themed R.E.M. video, though R.E.M. is not really my thing.

Actually, it’s a nice test of whether you’re more interested in transit graphics than in transit!