Transit agencies put a lot of money and effort into network maps, but are these maps really doing the job in helping people understand their travel options?
Here's a slice of a typical well-intentioned map published by a transit agency, in this case King County Metro in Seattle. The map appears on the agency website and in printed materials, including signage at stops, all over the region.
(UPDATE: Over two years after this post was published, and a year after a similar argument appeared in Chapter 7 of my book Human Transit, King County Metro finally published a new map that responds to this post's critiquem and it's beautiful. Read the argument below, then see the new map here.)
The map above is not wrong, but it is misleading, and most of the transit agency maps I see are misleading in exactly the same way. The problem is that all of the bus lines on this map -- both the graphic of the line and the line number bullet -- look equally important.
If you look at almost any street map, a map designed for motorists or to give people a general sense of the shape of the city, you'll see clear signals that the lines on the map are not all equal. A Google street map of this same area, for example, uses simple line-weight and color to visually distinguish three classes of road: (a) freeways, (b) local arterials, and (c) other lesser streets. We all use this hierarchy to organize our understanding of the city, regardless of our means of travel.
If a street map for a city drew every road with the same kind of line and label, so that Interstate 5 looked no different from the smallest gravel cul-de-sac, we'd say it was a bad map. But it's not wrong, the mapmaker would say! No, it's not, but it's misleading. If we can't identify the major streets, we can't see the basic shape of the city, and without that, we can't really make use of the map's information.
The process of learning any network -- roads or transit or any kind of geography -- begins with identifying a few features as major, and then understanding how the other features fit around those. If you're looking a map of natural geography, you'll notice the big rivers and mountains before you notice the small ones. If you're looking at a highway map, you'll understand the big highways first, and later, only as needed, you'll study how lesser roads connect with those main highways. Transit customers and potential customers need the same ability to sort the mass of detail presented by a transit network.
So a transit map that makes all lines look equally important is like a road map that doesn't show the difference between a freeway and a gravel road.
On the map above, all the bus lines are solid blue lines with numbers. But in fact:
- Some of these lines have frequent all-day service. On these lines, a bus is probably coming in the next few minutes at almost any time of day.
- Some of these lines have infrequent all-day service. You'll get a bus there, but you may wait a while.
- Some of these lines are peak-only. If it's not rush hour, and you're not going in the peak commute direction, these lines don't exist for you.
- One of these lines, the 82, is a nighttime-only route. This line exists only when none of the others do, in the middle of the night.
What do we achieve by putting all of these lines on the same map, and making them look the same? Well, the most powerful message seems to be: these are all buses, and all bus services are alike. A key secondary impression is: This map is complicated because bus service is intrinsically complicated. You might get the same message if you look for bus stops in downtown and find a sign that looks like this:
The message seems to be the same across these multiple media: Buses are for people who like to sort through lists of three-digit numbers, and look at piles of numbers on maps. If you can't handle that kind of complexity, don't use the buses.
Is that really the message transit agencies want to send?
Now I can already hear one response to this question. Of course we want people to figure out how to use the buses, but that's what trip planning websites are for. Just tell us where you are, where you're going, and when, and our website will give you detailed instructions for your trip.
There are three responses to that.
- First, some of us are spatial navigators, and need to understand our trip on the map rather than as a list of steps. Well, maybe your website gives us a map of the trip, so that's maybe OK.
- Second, narrative instructions are brittle. They work if everything works perfectly, but if there's any kind of disruption, we're helpless. Only maps can show us where we are, and what our options are, at every moment of the journey.
- Third, narrative instructions do nothing to build a person's understanding of their transit network, and of their city. And if you want to feel free in your city, capable of moving about at will to do things you want to do, that's the kind of understanding you need.
That third and deepest kind of understanding is why people love the regular Manhattan grid. If you're at Eighth Avenue and 16th Street and want to go to Second Avenue at 73rd Street, anyone can figure out how to do that, and about how far it is, based on locally available cues. Part of the joy of this part of Manhattan is the sheer effortlessness of basic navigation, the ease with which a basic schematic map can be stored in your head, even if you're not a spatial navigator. It's a place where a pedestrian can feel free to go anywhere, in any direction, without being confounded by complexity.
Most cities are more complicated than Manhattan, and most transit systems are more complicated than their cities. But I contend that transit agencies have an obligation to push back against that complexity, to make their systems look as simple as possible, to give their citizens (not just their riders) the clearest possible image of how their system works. We may not need this understanding to follow your website's directions, but it will help us if our trip is disrupted and we have to improvise, and it's essential if we ever want to feel free to use the transit system spontaneously, for our own purposes.
OK, but how to we decide which routes are "major"?
This question may sound like a recipe for decades of focus groups, but in my experience, the answer may not be so complicated if we just consider the basics: frequency, span of service, speed, reliability and ease of access.
Frequency and span of service, I'm going to suggest, are the most important indicators of majorness, because they are the answers to the question: "Does this service exist when I need it?" Notice that this not a question about service quality, but rather about service existence. Until you've verified existence, all the other features of a service -- even speed -- are irrelevant details.
Conventional transit agency mapping advertises where the service exists but conceals when it exists, as though "when" were just a detail. In fact, when and where are equally important dimensions in determining whether a service can be said to exist at all.
In more practical terms, we know that in urban transit, frequency is an overwhelmingly important variable in determining usefulness. Modellers will tell you that the most onerous part of a transit trip -- in terms of the potential to discourage ridership -- is waiting. Frequency, of course, is the variable that governs waiting time. Frequency also determines whether connections are easy to make, and that in turn determines whether transit is really a network or just a pile of lines.
There are many degrees of frequency and span, but in general, most transit agencies' service can be sorted into three categories of usefulness based on these variables:
- The Frequent Network runs often enough that you don't have to plan your trip around a timetable. That typically means every 15 minutes or better all day, but it needs to be more frequent than that where aiming to serve relatively short trips -- as in the case of downtown shuttles for example. If you aren't willing to plan your life around a bus schedule, you are interested only in the Frequent Network.
- Infrequent All-day services are the rest of the service that runs all day. This network often relies on timed connections.
- Peak-only service exists only during the peak period. It mostly takes the form of long commuter-express routes that add lots of complexity to a system map but represent very specialized services for limited markets.
These three categories are useful in such completely different ways that I would argue they are at least as fundamental as the three basic categories of urban road -- freeway, arterial, and local -- that virtually all street maps clearly distinguish.
When these three utterly different services are drawn with the same line, as in most of today's system maps, you get chaos. The chaos may be colorful and visually appealing, but it still conceals the most basic information we need. The complexity of peak-only routes, for example, obscures the simple structure of the all-day network, and the even simpler Frequent Network gets hidden behind both.
My recommendation is simple: In a bus network, the three categories of usefulness above should be represented by three kinds of line: a visually strong line for the Frequent Network, a lesser solid line for the infrequent all-day service, and some kind of dashed line for peak-only. More fundamentally, the test of a map should be that anyone can see the Frequent Network standing out from the rest of the map, and that anyone can see the total all-day network -- frequent and infrequent -- standing out from the more complicated and specialized peak commuter express services.
One way to do this, of course, is to provide separate maps of just the Frequent Network. Portland's Tri-Met has had one of these maps for years, which looks like this. Los Angeles has such a map here, which is also interesting for the way it captures many other distinctions, including rapid vs local buses, bus vs rail, and even multiple transit agencies. (UPDATE: See also these examples from Leeds, UK; Curitiba, Brazil)
But it's also not hard to highlight the Frequent Network even in a more complex map of the entire system. Look at the Minneapolis-St. Paul map here (click on the middle tab, "Regional System and Downtown PDFs") and you'll see all the maddening complexity of the whole system. But you'll also see simple yellow highlights on certain of the lines -- both light rail and bus -- that run every 15 minutes or better all day. These are the Frequent Network, the structure of services that busy people can potentially count on. Metro Transit also publishes a nice frequent network diagram (here and click right tab). Here's a piece of it.
Frequent Network mapping is also important for its secondary audiences. If everyone who wanted good transit had access to this map, they could make decisions about where to locate that would gradually re-organise the city so that people who valued transit were close to good transit, thus making better use of the transit system's finite resources. The Frequent Network is potentially useful to anyone deciding where to live, where to shop, or where to start a business, and also the land use planners and developers who make the same location decisions. If you just show such people the map of all services, with no differentiation, they won't be able to identify which services would really be useful to them, and will thus be less likely to make good location choices.
I have done quite a bit of work on this topic over the years, and have contributed to Frequent Network mapping decisions in several agencies, including Metro Transit in Minneapolis - St. Paul. The idea encounters a lot of resistance, and isn't done in most of the places where I've proposed it. But I have yet to hear a clear argument for why it's a bad idea to highlight and market the network of high frequency services. I would love to hear such an argument, and perhaps a marketing and mapping expert will provide one in the comments.
UPDATE: Actually, I have heard two such arguments.
1. "Finances are uncertain, and we can't be certain we'll always be able to keep to a 15 minute headway." In fact, this happened in Portland last year, when budget crises forced the transit agency to cut some frequent lines to 17 or 20 minute frequency. But this objection has an easy answer. The Frequent Network lines in Portland are still the most frequent lines, and there's a clear intention to restore these frequencies as a priority. It is better to say "Sorry, but the budget is really bad and we're having to cut the Frequent Network to every 20 minutes or better" than it is to just abandon the Frequent Network brand, or to never create it out of fear of this contingency.
2. "Our staff is having trouble getting to consensus on exactly what the definition of "Frequent Network" should be. Every 15 minutes or every 12? Frequent even on Sunday or not? Frequent until 8 PM or until midnight? If we set the bar too low, Frequent Service won't mean much. If we set it too high, we won't have enough 'Frequent' lines to make the term worthwhile." Yes, this is hard, but compared to the benefits of helping customers identify the frequent services, the stakes of this debate are pretty minor. Make some decision, flip a coin if you have to, and move forward. In general, it's better to add frequent lines later than to delete them, so perhaps that argues for a stronger definition that gives you fewer frequent lines initially, but that also shows you how you can bring more lines into the Frequent Network with small additions of service that you can make as finances permit.