San Francisco

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.)

San Francisco Bay Area: “Transportation Camp” coming to North Bay

From our good friends at Trillium Solutions, a cool company that does a range of IT solutions for transit agencies:

Transportation Camp is coming to Rohnert Park on October 20. The format of Transportation Camp is an "unconference" focused around transit and technology.
The event will serve the dual purpose of kicking off the Fall conference for CalACT, California's state transit association. Transit operators, activists, and technologists can come together to solve problems.
When: October 20, 2015. Coffee and muffins at 8:30. Event at 9:30. Sessions at 11. Happy hour afterwards.
WhereDoubleTree hotel in Rohnert Park, 2 hours from SF by Golden Gate Transit's 101 bus (we'll provide a shuttle from the Rohnert Park stop to the DoubleTree).
I very much hope to see you there! Please register if you can make so that we know how many to expect.

Explainer: On Transit “Integration” or “Seamlessness”

When you hear the word integration in conversations about transit, it usually means making it easy to make trips that involve multiple transit agencies that are geographically connected or entangled.  Another common word is seamlessness, which I like because it evokes the image of a well-made complete object.

(Tip: Anglo-Saxon words like seamlessness usually sound less obscure and bureaucratic than Latin-derived words like integration, because it’s easier to see how the parts of the word fit together to make the meaning.)

The San Francisco Bay Area has long been one of North America’s most difficult integration challenges, so it’s a good laboratory for exploring the issue.  If you can get transit integration right in the Bay Area, you can probably do it anywhere.  The Bay Area’s particular challenge is that it has no recognized central city.  Instead, it’s named after an obstacle, the Bay, and its geography of bays and hills provides natural psychological divides.  Wherever you live in the Bay Area, most of the Bay Area is “across the water” or “over the hills” from you, and this matters enormously to how people perceive issues as local or regional.  (Los Angeles, mostly a city of vast continuous basins, could not be more opposite.)

Screen Shot 2015-08-03 at 11.31.30 AM

The San Francisco Bay Area, with county lines


Fig1-WholeBayArea BS2_REV3_040915

Map of Bay Area transit agencies (SPUR)

The region’s wildly respectable good-government institute, SPUR, recently released a friendly and readable report on the topic, Seamless Transit, primarily authored by Ratna Amin and Sara Barz.  It’s a superb report, because it focuses relentlessly on the obvious “seams” that impede travel and liberty for the transit customer. In particular:

  • The report discusses practical integration problems like navigation and fare payment, explores different solutions suitable to each, and tries to show how much can be achieved without huge mergers.
  • The report points out bleedingly obvious solutions politely enough that not everyone will hear the subtext, which is “Why wasn’t this done 50 years ago?”  The lack of a customer-oriented regional transit map is in this category.  Such maps as exist are more like diagrams of turf — the sort of map you include in a peace treaty.  They’re designed to clarify what agency controls what rather than help people understand their travel options.
  • There is little discussion of creating a giant regional transit agency, or indeed of mergers in general. The report accepts that while the existing patchwork is not what anyone would design from scratch, it is achieving a balance between the ability to work over a large area and the ability to act locally on local issues.  Too many integration discussions jump too quickly to hugeness as the answer.

A typical old regional transit diagram, showing areas of turf but no sense of what service might be useful (no indication of frequency, for example).  (MTC)

For decades, it’s been easy to propose that some grand merger of agencies would solve problems of integration, but the obvious problem was you would have to merge the whole Bay Area into one transit authority serving almost 8 million people, in a region around 100 miles long.  That population would mean little citizen access to the leadership, while the huge area would mean that people planning your bus routes may be working in an office 50 miles away.  It just doesn’t work when the sense of  citizenship is as understandably decentralized as it is in the Bay Area.

What’s more, if you value transit-intensive core cities, places like San Francisco and Oakland, or if you want your city to be more like those places, you have an especially strong reason to want local control.  These places need more transit than the whole region wants on average, so they struggle to get adequate service from the regional transit agency, whose decisions will tend to converge on the average regional opinion.   (See Chapter 10 of Human Transit for a through tour of this issue and why it’s geometrically inevitable.)

Many North American regions are seeing conflict around this issue, and are evolving a fascinating range of solutions.  Many of these solutions involve additional funding from the cities that want more transit than the regional average.

Some core cities are proud to have their own city-controlled transit systems separate from what regional agencies do (San Francisco, Toronto, Chicago).  Some pay their regional transit agency for a higher level of service in the core city (Seattle).  Some run their own transit systems overlaid, often messily and confusingly, on the regional one (Washington DC).   Many more core cities are going to face this issue soon, especially if regional politics continue to polarize on urban-exurban lines.

Apart from the issue of urban-exurban differences in the need for transit, there are also real challenges when a single transit agency becomes enormous, especially if it provides local service over a vast geographic area.  Los Angeles is a great example.   As an undergraduate in the 1980s, living in the region, I marveled at what I assumed to be the stupid chaos of provincialism.  The region had a big transit agency, which has evolved into what we now call LA Metro, but many cities within the region ran their own transit systems, which were tangled up in each other, and with the regional agency, in complex ways.  As an undergraduate, I assumed that progress would mean merging all this into one giant agency that could provide the same product everywhere.

And yet: in those days, everyone hated the regional agency, but loved their city ones.  And there were good reasons for that that weren’t anyone’s fault, and still aren’t today.  You could get your city’s transit manager on the phone, but not the regional one.  Small city governments can fix a bus route and put up a new bus shelter in the time it would take the regional agency to organize the right series of meetings.  Again, nobody’s at fault there; these are natural consequences of smallness and bigness — in corporations as well as in governments.

Which is why, even in Los Angeles, the trend is not toward mergers.  Today, many city systems in the county are doing excellent work at their local scale.  LA Metro has improved massively as well, of course, but its costs are still high; more important, it’s still very big and therefore inevitably feels distant to many people — again, not the fault of the folks working there.

Meanwhile, a clearer negotiated boundary between regional and city functions is slowly starting to emerge.  One idea, for example, is that a key role of city systems is to run services that don’t meet regional standards for ridership, but that the locals feel to be important.  The division of labor among agencies is not what anyone would design from scratch.  But great work has been done over the years to build clearer relationships, or what I will call, later in this post, “good fences.”

City-operated transit is growing more popular in North American for another excellent reason:  Most of transit’s ability to succeed is already controlled by city government: specifically the functions of land use planning and street design.  If a city government feels in control of its transit, it is more likely to exercise those other functions in ways that support transit rather than undermine it.  San Francisco’s recent decision to combine traffic and parking functions with transit under one city agency shows a new way of thinking about the need to get this right, but it would be impossible if San Francisco relied on a big regional agency for its transit service.  Whenever someone proposes to turn a city transit system over to a consolidated regional agency, I have to point out that integrating in one dimension (between geographically adjacent services) means disintegrating in another (between key functions of city government.)

So there’s no simple answer.  City control creates a nasty patchwork of geographic integration problems across adjacent cities in a region.  The big regional agency has a different integration problem, which is with the land use and street design functions of municipal governments that don’t control their transit and therefore have trouble caring about it.  Whichever thing you integrate, you’re disintegrating the other.

What’s the answer?  It’s for each region to feel its way through the inevitable tensions to its own solution.  But I’d propose we start with this truism from Robert Frost:

Good fences make good neighbors.

Neighbors have an easier time being friendly if they have a very clear agreement about where their boundary is.  Collaborating with your neighbor to mark the boundary, and fence it if need be, is a peacemaking gesture.  This is as true of neighboring landowners as it is of nations.  And it’s certainly true of transit agencies.

What does it mean to have a clear sense of boundary?

It’s not just that both sides agree where the boundary is.  It’s also that it’s easy for both sides to live with the boundary, and work across it as need be.  For nations, it’s much easier to manage a boundary that runs across a natural barrier, so that the natural boundary reinforces the agreed boundary — the Rio Grande River between the US and Mexico, say, or the Great Lakes along the US-Canada border.  The worst possible national boundary is something like the 49th parallel, the US-Canada border in western North America, an arbitrary line that runs perpendicular to most mountains and valleys.  Only the extreme friendship and cultural affinity between the two countries makes this boundary workable.

All that is true of transit agencies as well.  Let’s talk first about local networks, and then, separately, about the relationship between networks of different scales.

Boundaries between Adjacent Local Transit Agencies

A bank of hills or a water body means that there are limited points of access across the boundary, called chokepoints, and this in turn means people are used to going out of their way to cross that point.  That means, in turn, that a well-placed transit connection point adjacent to the bridge or pass is an easy place for transit agencies on the two sides to converge.

On the other hand, a boundary that runs across a flat expanse of urban area, so that many people are literally across the street from the other side, is a problematic transit boundary.  In this case there is decentralized demand in all directions crossing the boundary at many points.  This makes it harder to bring both agencies to a shared focal point for connections between the agencies.  It also means there are lots of relatively short trips flowing over the border, and these benefit from a continuous network of service rather than an interrupted one.  As in many US states, California transit agency boundaries tend to default to county lines, and where these create that problem, it’s a mess for transit.

Some of this wisdom is already encoded in the boundaries of the East Bay agency AC Transit.  Near the Bay, the border between Alameda and Contra Costa counties cuts across dense urban fabric, so it would be an awful place for a transit network to end from the point of view of either side.


Fig1-WholeBayArea BS2_REV3_040915_0

Regional transit map, with boundary between Alameda and Contra Costa Counties highlighted red. Note that AC Transit extends across boundary next to the bay (SPUR report)

Recognizing this, AC Transit was constructed to unite the two sides of the county line where the urban fabric was continuous, while dividing from other agencies along natural hill and water boundaries, even where the latter are not county lines.  This is an important example for many US regions where counties are the default planning units, and arbitrary boundaries drawn in the 19th century (or before) risk turning into walls that sever transit access.

For AC Transit, the “good fences” solution was to put the border in a place that worked well for both sides — worked well for transit customers, that is, not for anyone’s desire for turf or empire.  That tends to mean looking for the natural chokepoint and putting the boundary there.

This observation also helps to clarify the city transit option.  Even in big urban areas, some cities have a geography that makes it easy for much of the transit to be city-controlled, typically because of natural chokepoints along the edges that help isolate the city-scale network from the regional one.  On the other hand, if the city boundary is logically pierced by long, straight local transit corridors that logically function both within the city and beyond it, a municipal network is less viable.

Screen Shot 2015-08-03 at 12.59.36 PMBurbank, California is a good example of a city where most main streets are parts of much longer logical lines running deep into adjacent cities, so its city limits would make especially poor transit boundaries.  Burbank therefore profits from its reliance on LA Metro, which runs long, continuous lines across city boundaries many of them converging on Burbank’s downtown.  The regional network is also, logically, the local one.

Screen Shot 2015-08-03 at 1.00.05 PMNearby Pasadena (considered together with Altadena) has good geography for a larger city role.  It has hill barriers on three sides — only the east edge is really continuous with other dense urban fabric — so fewer of its internal corridors necessarily flow into other cities.  (Tip: cities whose density is so low that they might as well be wilderness as far as transit is concerned — San Marino in this case — count as natural barriers to some degree.)  Another important feature is that Pasadena has a frequent regional rapid transit line running through, so its local lines don’t need to extend far out of the city to make regional connections.

So Pasadena could run most of its local transit system if it wanted to, because a logical network would consist mostly of internal routes.  Burbank could not, because most of its local service is logically proivded by routes that continue beyond the city limits.

Do not cite me saying that Pasadena’s transit should be more local.  I am not saying anything about what the regional-local balance should be in these cases, but merely observing how the geography makes the opportunities larger or smaller.  One value of Pasadena being served by the regional agency, for example, is that it can eventually be part of a larger high-frequency grid, with all the liberty that brings.

Local – Regional Transit Boundaries

All that is about what happens between local networks.  But another “good fence” can be a clear division of labor between local and regional services.   Regional services that are designed as rapid transit (widely spaced stations for fast operation between them, relying on local transit connections to get closer to most destinations) do not need to be the same agency as the local service meeting them; in fact, this can be a very clean “fence.”  Obviously you have to work on the specific problems of integration: information, fares, etc., just as adjacent local agencies do.  But there’s little need to merge or change boundaries in these situations.

All this is to say that the SPUR report is excellent, but that the organization of transit agencies, and especially of their boundaries or seams, needs to respect the geography of demand — as inherited county lines in the US do not always do.

We’ve also arrived at a more realistic notion of “seamlessness.”  There will always be seams in a transit journey, just as there will always be the need to make connections.  The conversation should not be about how to get rid of seams but how to put them in the right places, so that they work for both sides, and how to manage them so that travelers can flow through them easily.

Another way of thinking about the geographic issues I’ve been laying out here is that if you require a connection to continue your trip, there should be a rich payoff in terms of destinations you can reach.  The same is true for any hassles created by seams.  It’s like planes: it’s a drag to change planes, and especially to change between airlines, but it’s kind of cool, while you are changing planes, to look at the departure planes and think about all the other places you could also get to via this connection.  What’s more, all those connections are crucial to making your flights viable for the airline, even if you don’t use them.

The logic of connections is the logic of good seams in general.  They happen in places where it’s already logical for transit services to be discontinuous — either because of a natural boundary or because of a clear division of labor between regional and local service.  Those “good fences”, once found, can make for happy neighboring transit authorities, which will find it easy to work together for the sake of the customer’s liberty.

Sure, let’s regionalize the right things: fare media, information systems.  (An often-neglected one is service change dates, so that timed connections between agencies don’t get broken because the agencies change their schedules at different times.)  Some mergers may make sense, such as between BART and Caltrain to create a regional rapid transit agency.

Big transit agencies and little ones are both excellent things.  The trick is to get the fence right.


UPDATE: For a book-length academic analysis reaching a similar view, see Donald Chisholm: Coordination without Hierarchy.  1992, UC Press.  H/t David King.

San Francisco: A world-class transit map unveiled

A few years ago we assisted San Francisco Municipal Transportation Agency in rethinking how they talk about the various services they operate.  Our key idea was to classify services by tiers of frequency, while also distinguishing, at the highest frequency only, between faster and slower services.  In extensive workshops with staff, we helped the agency think through these categories and the names to be used for them.

It's great to see the result coming out on the street.  The old-fashioned term "limited," for example, been replaced by "Rapid," a new brand that emphasizes speed and reliability improvements as well as frequency and widely spaced stops.  

But the biggest news is that a new network map, by Jay Primus and David Wiggins, is about to debut.   Don't open it yet!!  Before you do, look at it in a fuzzy small image:


Notice how much information you can get just from this fuzzy picture.  Most transit maps are total nonsense at this resolution, but in this one, even though you can't even see the legend, you can see the structure.  All you need to know is that bigger, brigher lines are more useful lines, because they tend to be faster or more frequent.  In other words, this works just like any coherent street or map (paper or online) in which the faster roads are more visually prominent.  Any good map is legible at multiple levels of attention, including very zoomed out like this, and in loving detail of every right and left, which you'll also admire if you zoom into the massive PDF.

Why has it taken so long for transit maps to get this clear?  Well, first of all, you have to figure out that frequency, not speed, is the primary equivalent of speed in a highway map.  Highways and streets can all be ranked by their design speed, but in transit, frequency trumps speed in determining most kinds of utility, and speed distinctions matter most where frequency is already high.

(The exception, high speed but low frequency service, tends to be commuter rail and commuter express bus service.  That service is so intrinsically specialized and complex that it makes a complete mess if you put it on the map with the all-day frequent routes.  These ephemeral routes must be faded out; on this new map they are the weakest lines of all.  The previous map was chaotic precisely because it used the strongest color — red — for these most specialized and ephemeral services, concealing the structure of interdependent service that is running all the time and that vastly more people will use.)

What are the other barriers to maps of this clarity?  Well, you have to decide whether your goal is information (helping people understand their options) or marketing (which at its worst means deliberately confusing people so that they do you want them to do).   I have always argued that in transit, clear and beautiful information is the best marketing, but many professional marketers disagree.  

This map is glorious because it's 100% information.  Services aren't highlighted because someone thinks that they serve "target markets" or "more important demographics", for example.  Everything is mapped, and named, according to its potential usefulness to anyone.  The more diverse the range of people who'll find a service useful, the brighter the line is.

Of course, it doesn't show everything, but that's also why it's clear.  I'm sure I will be bombarded with comments pointing out that they don't show how San Francisco's network connects to the wider region's, and that they don't show how transit integrates with cycling, walking, private transit, Segways, and whatever else.  Including too much non-transit information is also a great way to make transit maps confusing.  This map is just what it is, a map of San Francisco's fixed route transit network.  It's also, in my experience, one of the best in the world, something even the world's best transit systems could learn from.  

silicon valley: bus rapid transit that’s faster than driving?

Screen Shot 2014-11-13 at 10.50.18 AM

El Camino Real BRT Alignment


Silicon Valley is easily viewed as a  car-oriented place, where tech giants rule from business parks that are so transit-unfriendly that they have had to run their own bus systems to bring employees from afar.  But one interesting transit project is moving forward: the El Camino BRT, a proposed  rapid transit line connecting Palo Alto and central San Jose. 

El Camino Real ("the Royal Road") is a path defined by Spanish missionaries as they spread north through California. It lies close to the old railroad line now used by Caltrain, and the two facilities combined  determined the locations of the pre-war transit-oriented downtowns that still form the most walkable nodes in the area.  

Today El Camino is the spinal arterial of the San Francisco peninsula, passing through or near most of the downtowns.   This spine continues across Silicon Valley, through Palo Alto, Mountain View, Sunnyvale, Santa Clara and finally downtown San Jose.   (The BRT will not extend the full length of the peninsula, because it is a Santa Clara County project and the county ends at Palo Alto.  However, successful projects do get extended sometimes.)   In Silicon Valley, too, the corridor is far enough from Caltrain that they are not competing.  Caltrain will always be faster but probably less frequent than the BRT, optimized as it is for much longer trips including to San Francisco.

In land use terms, the project corridor is ideal territory for transit – lots of employment and commercial destinations, with strong anchoring institutions at each end.   But while the path is historic, the modern street was designed with a singular focus on auto travel time, as a six-lane divided boulevard. Auto and transit travel times continue to increase substantially as more people come to live and work in the corridor, and even more population and employment growth is forecast for the coming decades.  

Santa Clara VTA and the FTA released the Draft Environmental Impact Report for this project last week, detailing multiple alternatives relating to the extent of dedicated lanes and street configurations. The purpose and need statement tidily summarizes the rationale for this investment:

El Camino Real is an important arterial in Santa Clara County and on the San Francisco Peninsula. However, El Camino Real is predominantly auto-oriented, and streetscape amenities are limited. There are widespread concerns regarding congestion, appearance, and safety, and a general public perception exists that the corridor is not well planned. Exacerbating current conditions, Santa Clara County is expected to experience substantial growth in the next 30 years from 2010 to 2040. If no improvements are implemented, heavy demand will potentially be placed on the existing transportation infrastructure, which is planned to increase by only 5 to 6 percent. 

Screen Shot 2014-11-13 at 11.40.10 AM

This striking graph (which I couldn't locate in the report itself, but which is reproduced over at the TransForum blog), compares transit travel time among the four alternatives:

In the A4c alternative (the alternative with the greatest extent of exclusive lanes), a trip during the peak through the corridor would actually be faster on transit than driving, and dramatically faster than the same trip today.

The various alternatives' alignments are compared below:

Screen Shot 2014-11-13 at 11.35.00 AM


As usual with arterial BRT in the US, there will be some mixed-traffic segments, and the line will only be as realiable as its least reliable point.  Note that the alternatives seem to envision different responses to city limits, as though anticipating that as you get further west (which means wealthier, but also closer to big destinations like Palo Alto and Stanford University), support for exclusive lanes will decline.  It will be interesting to see if this is true, in a very educated polity, when the benefits are understood.  

replace stop signs with signals on major transit lines?

From Streetsblog's Aaron Blalick in San Francisco:

The latest of [San Francisco Municipal Transporation Authority]'’s efforts to speed up [major bus] lines to run into some neighborhood opposition involves its proposed replacement of stop signs with transit-priority traffic signals. Some Western Addition neighbors have protested a proposal to signalize five intersections on McAllister Street to speed up the 5-Fulton, one of the designated “Rapid” routes receiving upgrades under the Muni Forward program (also known as the Transit Effectiveness Project).

Initially, the complaints were driven by fears that signals would bring dangerous speeding to McAllister. Muni planners responded by holding more outreach meetings, and presented data showing that pedestrian injuries declined on similar streets after signals were added. They also say speeds won’t go up significantly, since signals will be synchronized for speeds below 20 mph.  [emphasis added]

Aaron emailed to ask my opinion, which is emphatically:  "Who could oppose something that's good for both pedestrian safety and transit speeds?"

Apparently, the remaining opposition is based on "feel":

Sean Kennedy, the SFMTA’s Muni Forward program manager, said the data seems to quelled some neighbors’ fears, but that the complaints have shifted. “What we hear is that there’s a lot of concern over the neighborhood feel,” he said. “And that’s something we can’t really dispute with facts. It’s an individual preference if people do or don’t like signals.”

So how much should we worsen transit, and maintain higher levels of pedestrian injury, for the sake of "feel"?

And how exactly does a signal change feel?  We're talking about small streets here, mostly striped with a single wide travel lane each way.  Will a signal make the street feel wider?  Are people associating signals with more traffic and just assuming signals will have that outcome?  Not if they're timed for transit rather than cars.  Well-timed signalization can be very effective at discouraging car traffic on transit-intensive streets, when that's the objective.

I spent a decade of my life as a San Francisco pedestrian, in dark ages when pedestrian safetly mattered a lot less than it does now.  Sure, it was nice to encounter a 4-way stop where stepping into the intersection was enough to stop traffic.  

But among global pedestrians like me, San Francisco is famous for very fast signal cycles, and it's not a place where you'll be ticketed for crossing on red if there's obviously nothing coming.  As a pedestrian, I find a few seconds of delay a small price to pay for a transit system that's actually respectful of its customers' valuable time, not to mention the high cost to the public of its drivers' time.  

Remember: If you want frequency, you want less delay, because that makes frequency cheaper!

quote of the week: the neglected american bus

In the six cases examined, we conducted off the record interviews with public officials, general managers, and thought leaders in each region. One of the consistent themes that emerged was that the bus systems and bus passengers were an afterthought. In every region – Chicago, New York, Boston, Minneapolis/St. Paul, Dallas/Ft. Worth, and the Bay Area – rail was the primary focus of virtually everyone we interviewed. We also found that maps of the regional transit networks tellingly either included a jumbled mess of bus routes behind a clean rail network, or ignored bus altogether.

It is likely this bias toward rail has very little to do with governance. But it does have a negative impact on transit delivery, particularly from a customer point of view. The vast majority of transit riders in the United States are on buses, so it would make sense to devote more resources and attention to them compared to rail riders, rather than less. Also, improvements to the bus network are likely to be less expensive than new rail expansions, and would be likely to yield substantially more net benefit per dollar. Yet while every region we visited had a new rail expansion either in planning or under construction, outside of New York none of the regions had any plans for regional bus networks, reorganization of existing bus systems, or major expansions of bus rapid transit (BRT).

Joshua Schank, President CEO,
Eno Center for Transportation
"The Case of the Neglected Bus"

I've certainly noticed, in my own work, that the aggressive, agency-wide commitment to building a complete access-maximizing transit system is stronger in cities that don't have much rail, or where rail is in early stages of development, as in Houston.  Key tools for total network legibility, such as Frequent Network branding, also seem to be spreading much more effectively in the midsized transit authorities than in the gigantic ones.

A while back I had a brief chat with a major airline CEO at an event.  He asked me: "So what's the future of transit.  It's rail, isn't it?"  I wanted to say: "So what's the future of aviation?  It's all intercontinental jumbo jets, isn't it?  

Or is it about people feeling free to go places?  In that case, the future of aviation is a network, where many types of vehicle have an essential role.  

should transit maps be geographical or abstract?

In some agencies, it goes without saying that transit maps should be geographically accurate.  Many agencies follow San Francisco Muni in superimposing transit lines on a detailed map of the city:

Sf frag

But research out of MIT suggests that we really need to see network structure, and that requires a degree of abstraction:

By putting alternate versions of the New York and Boston subway maps through the computer model, the researchers showed that abstract versions of the maps (as opposed to geographically accurate versions) were more likely to be easily understood in a single, passing glance. 

Here's their example:

Geographical accuracy obscures network structure.  Purely geographic maps show where service is but not how it works.  

This is why a number of best practice agencies publish both kinds of maps, sometimes even presenting them side by side.  The geographic map helps you locate yourself and points of interest in the city, but you need the structure map to understand how the system works.

All this is even more urgently true for bus network maps, where complexity can be crushing to the user.  When we streamline maps to highlight key distinctions of usefulness such as frequency, we often have to compromise on geographic detail.  Obviously the best maps fuse elements of the two, but you can always find the tradeoff in action.  The new Washington DC transit maps, for example, highlight frequency (and show all operators' services together) but there's a limit to the number of points of interst you can highlight when keeping the structure clear:  

Dc slice


Roy Nakadegawa, 1923-2013

Roy NakadegawaRoy Nakadegawa, a longtime San Francisco Bay Area transit advocate and board member for both AC Transit and BART, has passed away.  I remember him a soft-spoken but effective advocate who was able, as a professional engineer, to dig into details when they mattered.  

I also remember him as someone who really understood transit networks, and considered them more important than transit technologies.  You can get a taste of that from this 2008 kerfuffle (concerning a debate that I am agnostic on, personally).

From the joint AC Transit / BART press release:

Former AC Transit and BART director Roy Nakadegawa passed
away last Friday morning, August 23, 2013, at his home in Berkeley. 
Mr. Nakadegawa had been suffering from congestive heart failure for some time.

Mr. Nakadegawa served on the AC Transit Board for 20 years,
from 1972 to 1992.  He then served on the BART Board for 12 years from
1992 to 2004.  After he left the BART Board, he joined the Board of TRANSDEF
(Transportation Solutions Defense and Education Fund), a non-profit
environmental organization created by transit activists to advocate for better
solutions to transportation, land use and air quality problems in the San
Francisco Bay Area.  In all those positions he argued for cost-effective,
mobility improving transit.

Mr. Nakadegawa was an active attendee and participant in TRB
(Transportation Research Board) meetings and was well known and respected
around the world for his depth of knowledge about transit and its relation to
land use.  He was written up in the local press for the frugality of his
travel arrangements.  When Mr. Nakadegawa served on the AC Transit Board
of Directors, its members got an annuity when they left the Board.  For
many years, Mr. Nakadegawa generously donated his annuity payments to buy
prizes for AC Transit's local bus rodeo winners.

As a BART Director he consistently advocated for cost
effective transit administration, which spilled over into his own
campaigns.  In his re-election materials
for BART Director he was proud to point out that in November 2000, he garnered
the highest vote (over 91,000 voters) of five previous BART races and spent
less than a penny per vote.  Mr.
Nakadegawa tirelessly urged his fellow board members to consider innovative
uses of BART facilities as a non-traditional source of
revenue and improved customer access, resulting in the adoption of both
permanent and experimental parking program initiatives.

 He will also be
remembered for his role in advocating BART’s Earthquake Safety Program.  He helped to raise public awareness of this
critical program, resulting in the successful 2004 passage of a bond measure to
fund it.

Professionally, Mr. Nakadegawa had been a transportation
engineer for the City of Richmond and for many years served on the Board that
administers the civil engineering exam in California.  His career as a public sector engineer
reached a pinnacle in 1989 when he was elected National President of the Institute
for Transportation of American Public Works Association and later served as its
liaison to the American Public Transportation Association (APTA), the national
transportation advocacy group.  While
with BART Mr. Nakadegawa became an active member of APTA, serving on several
committees including its Policy and Planning; Advanced Technology, Governing
Board; and Transit Management and Performance committees.

Mr. Nakadegawa and his wife Judy were the quintessential
Berkeley couple, dedicated to peace, family, public service and folk dancing.

Cards and letters should be sent to:  Judy Nakadegawa
and family, 751 The Alameda, Berkeley, California  94707-1930.