Author Archive | Jarrett

Some Reads on the Maintenance Crisis

The one-day shutdown of the Washington DC Metro is a useful call to arms about the dreadful state of maintenance in some of the US’s major rapid transit systems — a subset of a larger issue about deferred maintenance in all kinds of infrastructure.  If it seems like this makes the US like the developing world, NPR reminds us that most developing world metro systems are in much better shape.  (My Moscow correspondent Ilya Petoushkoff was also quick with an email reminding me that when even one Moscow subway lines go down, emergency bus lanes are created with Jersey barriers.)

The Washington Post’s Philip Kennicott is also fine on how the subway’s failure ties to great themes of US urban decay.

I have no opinion about the wisdom of DC Metro CEO Paul Wiedefeld’s decision to shut down the subway for a day to inspect faulty wires, except that it seemed sudden and left little time for preparation.  Its attention-grabbing effect was unmistakable, and perhaps that was necessary to shock everyone into understanding the urgency of the problems. But it doesn’t appear to have been a PR stunt: the system’s faulty wiring had already caused a fatality, and sure enough, the one-day shutdown to inspect these wires turned up even more dangerous ones.

But do read this Vox piece by Libby Nelson on how transit agencies can be more honest with their customers, including on Twitter.  Bravo to the Bay Area Rapid Transit for telling customers the truth about the problems facing the agency — which is to say, facing the region.

San Jose and Silicon Valley: Follow our VTA “Next Network” Project

VTA3One of our big projects this year is a Transit Ridership Improvement Program for the Santa Clara Valley Transportation Authority, which serves San Jose and Silicon Valley in California.  A key piece of that will be the “Next Network,” to be implemented in 2017 with the opening of the BART extension into San Jose.  The Next Network is about more than accommodating BART.  It’s also a chance for citizens to help the agency think about its network design priorities.

I’m happy to announce that the project website is now live, and that our first report, called a Choices Report, can be downloaded here.

A Choices Report is our preferred term for what is often called, tediously, an “existing conditions” report.  (Has anyone ever looked forward to reading about “existing conditions”?)  The report does cover existing conditions — the performance of the transit service in relation to the markets it serves — but with an eye toward revealing insights that lead to a better understanding of the real choices an agency faces.

The Choices Report will form the background for a series of three network alternatives that will be shared with the public over the summer.  The whole point of those alternatives is to encourage you to think about different paths VTA could take.  A final network plan is expected near the end of this year, to be implemented when BART opens in July 2017.

The public conversation in this project is not a thing we do on the side.  It’s the whole point of the study.  We need robust public participation in this project to help sift the alternatives and make sure we’re heading in a direction that the community can support.  So please, if you live in the region, bookmark the project page, and watch for updates there and here.

My Washington Post Piece

It’s here.  Twitter’s favorite quote from it is:

Cities have relatively little space per person. Cars are big. Big things don’t fit in little spaces.

In short, it’s all, always about geometry, which technology will never change…

To predict the future, we need to think carefully about what’s permanent and what may be fleeting. Fashions and tastes are fleeting, but geometric facts are permanent. Fifty years from now, our sense of what’s sexy or hip or green will be very different, but big things still won’t fit in small spaces.

 

Luxembourg: A New Official Frequency-based Map

Maps that help people see which services are coming soon are remarkably rare in Europe, for a variety of complex reasons.  Some European systems have such high frequency overall that it may seem unnecessary, but there are usually still significant frequency contrasts that matter.

luxemburg map jug cerovic

Now, there’s a great example out of Luxembourg.  The Paris-based Serbian designer Jug Cerovic has been featured here before, for his interest in making networks clearer by emphasizing a core geometric idea.  Not just for beauty, but as a way of combatting the mental overload that complex maps can cause.

Luxembourg’s transit system has just rolled out an official network map by Cerovic.  It highlights frequency with wide lines, including such details as how wide frequent lines split into narrow infrequent ones.  (Detailed PDF is here.)

unnamed-3

Obviously this is a diagram, seeking network clarity rather than precise fit with local geography. The core geometric idea is the pentagon, a feature of the Luxembourg CBD that he uses, but not to excess, in arranging patterns. He explains his design process here.

UPDATE:  For comparison, this was the previous map. (H/t @ParadiseOxford)

Luxembourg map old

Keys to Great Airport Transit

Toronto’s new high-fare, elite train between downtown and the airport is a failure in ridership terms, so it’s a good moment to talk about transit to the airport in general.

This critique by Cherise Burda of Ryerson University, one of the Toronto line’s few regular riders, pretty much sums up why the Toronto Union Pearson Express is doing so poorly:  Fares too high (CAD $27.50 one way) for a line that just doesn’t connect the airport to enough places.

Do you think that specialized airport trains are the key to high transit mode share to an airport?  Think again.   What matters is not just the service to downtown, but the whole transit network and the airport’s position in it.  Where can you get to on that network, and how soon?  (A true assessment of this issue would have included bus services too, of course.)  London’s Heathrow, for example, has a high-fare express train very much like Toronto’s, but it also has a slower train that makes more stops for a lower fare, and a subway line that makes even more stops and serves even more places.  Those lines connect to more services, and are therefore more useful to far more people.

Basic math:  1000 airport employees using an airport service every day are more ridership than 100,000 air travelers using it, on average, maybe a couple of times a year.

This is the simple reason that airport transit politics are so frustrating.  Everyone wants to believe in transit to the airport, because they might ride it a few times a year.  But to create a great airport train (or bus) for air travelers, you have to make it useful to airport employees too  That generally means a service that’s an integral part of the regional transit network, not a specialized airport train.

The other key issue is that most airports are cul-de-sacs.  It’s hard for a line to continue beyond the airport unless it’s underground, and this is another huge limitation on an airport service’s ability to serve a sufficiently diverse market.  If you can afford it, aspire to be like Sydney, whose rapid transit system tunnels under the airport so that it can continue beyond it without branching. And if you’re a rare airport like Seattle’s, where surface transit can stop at the terminal but continue onward, so much the better.

So again, here are the keys to great transit to the airport, for travelers and employees:

  • Total travel time matters, not just in-vehicle time.  Airports are citadels of impatience.  Travel time matters hugely, but travel time is not just in-vehicle time (the time you’ll see advertised) but total time including waiting.  That’s why the advantage of making few stops is wildly exaggerated. To accurately measure real travel time, add the in-vehicle travel time to half the waiting time, where the latter is governed by frequency. You may find that a more frequent train that stops more often (and is therefore useful to more people) comes out ahead even for the downtown-to-airport traveler.
  • Combine air travelers and airport employees on the same train/bus, and appeal to an economically diverse range of air travelers, not just the elite.  This is a case of the general principle that transit thrives on the diversity of trips for which it’s useful, not on specialization.  If elites want a nicer train, give them first class cars at higher fares, but not a separate train just for them.  (And as always, elite services are a good role for the for-profit sector.)  As always, the more people of all kinds you can get on a train or bus, the more frequently you can afford to run it, which means less waiting, and the lower the fare you need to charge.
  • Connect the airport to lots of places, not just downtown, by providing a total network.  It’s the total transit system at the airport, not just the airport-downtown express line, that determines who can get there, and how quickly.  And the total network requires connections — another reason to care about frequency.
  • Don’t interfere with the growth of other services.  Airport terminals are still not huge destinations by citywide standards, so don’t sacrifice other major markets to serve them.  Toronto’s airport train, for example, not only carries few people but creates issues for higher-ridership services with which it shares track. Another common problem is the branch into the airport that cuts frequency and capacity on a mainline, even though the mainline’s demand is much higher than the airport’s (San Francisco, Vancouver).
  • If you can afford it, go via the airport instead of terminating there.   Most airports are large-scale cul-de-sacs, and like every cul-de-sac, they say: “I want only as much transit service as I can justify all by myself.”  So if you can tunnel under the airport and serve it on the way to other places, as in Sydney, you will often end up with much better service for all your airport users, employees and travelers alike.

 

 

How Vague Should Plans Be?

How specific or vague should a transit plan be, before it’s announced?  And what kinds of specificity matter?

It’s easy for a journalist to say that a plan is short on specifics, but all plans are short on specifics.  If included every detail, you’d have construction drawings, escrow arrangements, employee work shifts, and so on. But that’s a lot of work, so you don’t do it until you’re sure you want to proceed.

Good planning starts at high altitude and proceeds downward through levels of detail until it’s ready to happen “on the street.”  In transit, for example, it’s best if you first do big-picture city or regional plans, then implement these through local area or corridor plans, then implement these with more detailed design, then implement those with construction drawings or timetables.  Finally you implement those by actually building or operating the proposed thing.

As you descend in altitude, you may hit a fatal flaw. You may have to back up to a higher altitude to see a way forward.  But without altitude at first, you can’t see the big picture, and if you go into detail too soon, there’s a risk that the whole point of the plan gets lost as you quibble over a parking space.

So when a plan is announced, don’t jump to quickly to saying it lacks enough detail.  We planners spend a lot of time trying to figure out exactly what to be specific about, and what can be left vague for now.  Not out of any desire to mislead, but because it’s impossible to talk about all the details at once, and too expensive to study them all at an early stage.  We rely on well-honed instincts:  Which details are most likely to erupt into a problem — technical or political — down the line?  Which other details can be noted and honored but left to a later phase to refine?  These are some of the hardest calls that planners make.

Preliminary BQX AlignmentFor example, I sympathize with the proponents of the recently announced Brooklyn-Queens Streetcar in New York, including the estimable Sam Schwartz, (“Gridlock Sam” at the New York Daily News) who advised the Mayor on the project and is also a leading advocate.  Since it was announced a couple of weeks ago, civic leaders have lined up to support it but many leading transit advocates and urbanists have challenged the project, or at least raised hard questions about it.

I have been on both sides of these issues.  But while every plan is going to be vague, it’s important to notice which parts are specific and which parts are vague, because this can signal something important about how the plan is likely to change as it goes through later stages of refinement.

The mayor’s press release, including the map shown here, spends most of its length talking about why a certain area needs transit, and asserts that a streetcar is the answer.  It assumes that “streetcar” will make us like the project before we know much about what it does.  The release does include a set of travel time claims, but it doesn’t say much about:

  • Frequency, which governs how long you’ll wait before you can even begin.  (An ideal travel time estimate would always include half of that wait.)
  • Connections, notably which subway lines the service would connect to.  The curves on the map suggest but don’t imply any particular path, which would run on particular streets and connect with particular subway stations.  I’m sure I’m not the only person who spent a while on Google Earth trying to figure out what these sensuous curves might mean in reality.
  • Reliability, which generally requires exclusive right of way.  The mayor’s press release says “majority of the line” is protected from car traffic.  Other sources have told me anything from 70% or 100%.   If it’s not 100%, it matters which 50-99% we’re talking about.  Transit advocates have good reasons to be concerned about this.  There are cases where transit can mix briefly with traffic and not be much affected – typically when the traffic is very low because the street is just for local access.  But what tends to emerge out of the political process is exactly the opposite: Where traffic is bad, it’s politically hard to take a lane for transit, so transit ends up with exclusive lanes that disappear precisely where they are needed most.  This is a very important part of the history of both streetcars and Bus Rapid Transit in the US.
  • Fares. What will they be, and will it be free to transfer to the rest of the transit system, so that people can get to the 95+% of the city that’s not on this line?

If you just love streetcars, and want a streetcar, then these sound like the petty concerns of people who can’t see or trust your grand vision.  But if you want an efficient transit network that liberates people to access opportunity, these things are paramount.

If the main goal of a project is to build a piece of technology, this sets up a risk that when hard choices have to be made down the line, the speed, frequency, and reliability will be sacrificed later in the project, as the “details” are being worked out.    Suspicion about this is understandable, when you consider how slow and unreliable many US streetcars have turned out to be.

So how vague should a plan be?  It’s a tough call.  You have to be vague about something, but from that, people may reach judgments, fair or not, about what your priorities are.

For Reporters Disparaging Transit Projects, “Far” Isn’t Far

If you’ve ever wondered what well above and well below mean, as opposed to far above and far below, Dan Weikel and Ralph Vartebedian at the Los Angeles Times have quantified it for us, in an article about the California High Speed Rail project.

Rail officials also say the latest cost estimate for the entire 500-mile project has been reduced from $68 billion to $64 billion, well below the $98 billion projection from several years ago, but still far above initial estimates of less than $40 billion.

I’d always assumed that  far was further than well.  But no, by their math, well is $34 billion but far is as little as $24 billion.   Well is further than far.

So now, anytime someone uses far or its relatives to imply extremes — “the furthest corners of the earth” etc,, you can ask:  Sure, they may be the furthest, but are they the wellest?

Is Infrastructure Still about “Awe”?

Allison Arieff in the New York Times thinks the problem with our infrastructure planning is lack of “awe”:

[Dave] Eggers’s proclamation that the Golden Gate [Bridge] is beloved because it’s outrageous and weird may fly in the face of just about everyone’s attitude about infrastructure, but it also gets at exactly what we should be feeling about bridges and tunnels.

Awe.

American infrastructure is deferred home maintenance on a massive scale. We just keep putting it off until something major — and often catastrophic — happens, and then it ends up costing twice as much as it would have had we taken care of it proactively. This is a bad strategy — yet it’s the strategy that seems to define United States infrastructure.

There is no awe. There are issues of structural integrity. There are mind-blowing cost overruns. Accidents. Sinkholes. Problems with bolts.

The first design proposed for the Golden Gate was, writes Eggers, “the strangest, most awkward and plain old ugly bridge anyone had every seen … people compared it to an upside-down rat trap.” (Here is what it looked like.) The public demanded something better — and they got it.

A century later, we’ve lost our collective faith in the power of great projects like the Golden Gate, not to mention our trust in the government to fix a pothole on time and on budget, let alone create an inspiring bridge. How can we restore that faith in possibility?

I’ve lived in cities with awe-inspiring infrastructure (San Francisco, Sydney, Vancouver, Paris) but now I’m based back in my original hometown, Portland.  And Portland is the perfect riposte to Arieff’s obsession with awe.

Portland is “awesome” but not the least bit awe-inspiring.  If you want to gape at the spiritual grandeur of human works, strike us off your list.   Our monuments, bridges, and major buildings are all modest and even gentle.  Many are beautiful but none are magnificent.  Our city is so human-scale that we just don’t need to build very big things.  For some related reason, we also have no need for a dramatic, soaring tower with a rotating restaurant and observation deck.

We don’t need the tower, because we have hills and mountains.  Portland manifests a particular reaction to a natural setting: not the desire to compete with it by creating infrastructure of comparable grandeur, but a humility toward it, a happiness that comes from dwelling in its shadow, and letting it give us all the awe we may need.

Nature now awes us in another respect: We’ve been warned to expect an appalling earthquake in which thousands of us would probably die, because our infrastructure isn’t designed to survive it.  Of our 12 river bridges, for example, only the newest one is pretty assured of not collapsing (a second is now under construction.)  Countless brick and concrete buildings and highway ramps are likely to go.  Arieff dismisses the small mindedness of “problems with bolts,” but bolts are exactly what’s going to kill us.  Telling Portland to spend money on awe instead of bolts could be a pretty direct threat to our lives.

The bigger lesson of Portland is you can build a great city by learning to take pleasure in the actual functioning of things, and the resulting liberty and happiness of people.  Pioneer Courthouse Square, for example, is pleasant but not awe-inspiring, and the real reason to love it is that it’s so massively useful for all kinds of happy and liberating purposes.  In our better moments, we feel that way about our transit system.  Function, especially when it engenders liberty and opportunity as functional transit does, can be a higher delight than awe, and a more durable one.

The other problem with awe is that it’s so often about the power of some people over others.  Versailles and Imperial Vienna are awe-inspiring, but the awe has a purpose: to make you accept your place in a hierarchy of power and privilege.   The medieval cathedral was a gathering place (like our civic squares) and an honest monument to human spirituality, but the awe you feel there is also meant to make you defer to the authority of your local priest and the Pope.   Awe and intimidation are the same thing in slightly different light.

So perhaps we should be suspicious of awe, with its reverberations of power and grandiosity.  Delight and pleasure are are better aesthetic selling points, but at our best, as in Portland in its better moments, even these things arise from functionality, safety, usefulness to vast spectra of people.  And the infrastructure that best does all those things may not be awe-inspiring, in the same way that Portland isn’t.

Let us create affordable and inclusive delight wherever we can find it, but let’s be sure that advocates of function are in the room, reminding us of the urgent human rights and ambitions that only functional infrastructure can support.  Appeals to awe, in particular, are not how we build that room.  Historically, awe’s purpose has mostly been the opposite: to keep people outside, mouths agape at the magnificence, while their betters plan their destiny.

Richmond: Bus Rapid Transit Line Approved

The Richmond (Virginia) city council has approved plans for a Bus Rapid transit line running east-west through the core of the city — the starting point for a more robust transit network for the whole city and potentially the region:

richmond pulse

Like all starter lines, it focuses on a small part of the city, and these projects always raise questions about the city-wide benefits. What’s in it for you if you don’t live or work near the line?

One answer to that concern is that a good core transit line produces all kinds of benefits across the city. By running a busy corridor more quickly and reliably, resources are freed up to run more effective local services.  Like all rapid transit lines, this one will depend heavily on improved local bus service, and improved local bus service will mean better mobility for people not on the rapid line.

That’s all very nice in the abstract, but what’s the specific plan? Fortunately, the people of Richmond will have the chance to help forge that plan in the coming year. We are now working with City of Richmond, GRTC and the local office of planning firm Michael Baker International on the Richmond City Transit Network Plan.  This effort, to develop specific ideas for a better local bus network, will include many opportunities for citizens to consider the choices themselves and share their ideas and priorities.

So if you’re worried about whether your neighborhood will be well served by the future transit system, get ready to join a conversation about exactly that.  Plans for major transit infrastructure are never total transit plans, any more than a main street is a total street network.   The real network planning starts now.