Archive | September, 2017

Not the Suburb of the Future

Several people have asked me to respond to landscape architect Alan Berger’s NYTimes piece on “The Suburb of the Future.”  The piece invites us to imagine a series of technologies that will allow all of us to live on large plots of land spreading out across the landscape.  It’s worth reading, because it captures a lot of what goes wrong when architects posit a purely aesthetic notion of urbanism without running the numbers or discussing the full impacts.

(It also contains that self-ridiculing term “what Millennials want,” which in the absence of data means “what I want Millennials to want.”  Most people can’t predict what they’ll want later in life, and their parents and grandparents can only do this by assuming, perilously, that their children are copies of themselves who will follow the same life trajectory that they did.)

There are basic geometry problems with uncontrolled sprawl that Alan Berger is not discussing, and that his vision does nothing to address.  These include the long travel distances which consume more transport capacity and cause more emissions, as well as the removal of so much land from agriculture, flood protection, and the environment generally.  There is also the severe problem of induced travel demand from driverless vehicles, which will expand the demand for road space.

My own city, Portland, has achieved its desirability largely through it’s urban growth boundary constraining sprawl.  If Alan had had his way 40 years ago, the magnificent and relatively new vineyard region just outside of our city, and Oregon’s best agricultural land, would all be covered with houses by now.

Oregon wine country

Oregon’s wine country just outside of Portland. It exists only because our 1972 limits on sprawl kept us from paving it.

 In short, sprawl still has all of the usual negative impacts, and because these problems are not aesthetic, making sprawl more beautiful is not really the point.
Personally, I live in a detached house because am into gardening, so I would never argue that everyone should live in apartments.  In our existing suburbia there can still be plenty of places for people who genuinely want low-density living to have it.  But there is not enough room for it to continue to be promoted as the only way to have a normal life.

 

 

 

 

Helsinki: A Transit Map by Jug Cerovic

A while back I did a post on the subway maps of the Paris-based Serbian designer Jug Cerovic.  His style is to look for distinguishing features in the geometry of the network structure, and highlight these to give a sense of order.

He has a new one of Helsinki …

helsinki-metro-map-v-1-3

… but the cool thing is not just the map but his explanation of his design process, which I highly recommend.

 

Bus Network Design is a “Hot Trend”!

Longtime readers know I’m suspicious of “hot trends,” but it’s great to see that bus network design is finally having its moment in the limelight. The respected public policy magazine Governing has a nice feature by Daniel Vock on bus network redesign.  It happens to feature two projects that we worked on, Columbus and Houston, and it has some quotes from me, but it would be a good article even without those things.

There’s one mistake in the piece.  Vock writes, “Plus, a well-designed bus network can lead to fewer trips because riders have to transfer less to get to their destinations.”  I think he means boardings rather than completed trips, but in any case, our network designs sometimes increase transferring, even as they reduce travel time.

But it’s a good read.

 

 

Fare Policy vs Ticketing Technology: San Francisco Edition

Many, many times, I’ve asked a transit agency’s leaders about their fare policy, and been told instead about their ticketing technology.  “Are you thinking about fare structure?” I ask.   “Yes, we’re on it!”  they say. “We’re working on this fabulous smartcard!”  Don’t trust a fare expert who can’t distinguish the policy decisions that set fares and the technologies that implement them.

Arielle Fleisher of SPUR has a good piece on fare policy in the Bay Area, which will be useful to anyone in multi-agency regions in North America.[1] Describing Clipper, the smartcard shared by almost all of the region’s 27 transit agencies, Fleisher writes:

There is no denying that the Clipper card is a magical piece of plastic. Since its debut in 2010, Clipper has made it much easier for people to switch between different transit systems and travel throughout the region. But if you look under Clipper’s hood, it quickly becomes apparent that the card’s magic masks a complex web of transit farclipperLogoLarge.pnges, passes and policies that ultimately limit its effectiveness. Put simply, a close look reveals that the Bay Area has a fare policy problem.

Back in the 80s and 90s, when I worked in the Bay Area, there was no “hood” to look under or “mask” to hide behind.  The mess was in everyone’s faces.  The many transit agencies required their own paper tickets or passes, and your only hope of moving freely across agency boundaries was to carry numerous rolls of quarters.

As the Bay Area considers the next generation of Clipper, Fleisher rightly warns of the risk that the region’s leaders will focus on making the technology cool rather than making the fares logical.  She enumerates five problems a multi-agency fare policy should solve:

  1. Disparate fares make using transit confusing.
  2. Separate fares for different agencies are a problem when one agency substitutes its service for another’s, as happens during disruptions.
  3. There isn’t a single pass that employers can purchase for their staffs.
  4. The system penalizes trips that happen to require multiple operating agencies.  (And note that some agencies still charge for connecting between services of the same agency!)
  5. The system makes it hard to do coherent discounting for low-income persons.

To which I can only say, yes!  And yes, we were yelling about all this 30 years ago.  The smartcard “solved” this problem only for relatively fortunate people.  If you don’t have to think about what you’re spending, you can just buy a Clipper card and wave it everywhere.  So there’s a risk of elite projection, in that many decision makers, who tend to have above average incomes, no longer experience the problem in their daily lives, the way everyone did back in the pre-Clipper days.

Still, the fare problem in a multi-agency region is genuinely hard.  If it weren’t, we’d have solved it long ago, because technology was never the real barrier.   Consolidating all the agencies into one isn’t the answer.  The point is to have clear boundaries and clear relationships across those boundaries.   But as long as there are multiple agencies, each agency has its own budget to balance.  Introducing new inter-agency fares costs money for each agency, as more fares have to be shared with other agencies that were part of each person’s trip.  Unless there is some new funding, the money has to come from raising the base fare, which is one of the most unpopular things a transit agency can do.  Integrated fares, when they happen, will be a cost item. They always are.

And as I can’t emphasize too strongly, every time you tell a transit agency to use its limited funds to do something other than run service, you’re telling them to cut service.

Even if you don’t live in the Bay Area, Fleisher’s article is a good read.  Chapter 11 of my book Human Transit also explores fare issues.  And if you’re interested in the dynamics of how a big North American metro deals with having 27 transit agencies, and why that might not be a bad thing, there’s my article on seamlessness, itself a response to an excellent SPUR paper on the subject.  (And again: if you want to see how influential, respected, and popular a local policy institute can be, you should learn about SPUR!)

 

 

[1]  The transit agency structure that I describe here is mostly a North American concept.  Elsewhere, the problems described here arise between operating companies (publicly or privately owned) that have the right to set fares and keep fare revenue while also getting subsidy from a government transport authority — a so-called “net cost” contract.”  The new best practice is “gross cost” contracts, where the government keeps the fare revenue.  This lets the government authority control the fare policy decision, because only its own revenue is at stake.  (It also lets the government design a coherent network.)