Here’s why transport maps should show service frequency

An extract from a map of the Greater Paris rail network – with no frequency in sight. Image: RATP.

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. Until 2012, the map appeared on the agency website and in printed materials, including signage at stops, all over the region.  

Image: Jarrett Walker/Seattle QA Network

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 colour to visually distinguish three classes of road: freeways, local arterials, and other streets. We all use this hierarchy to organise 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:

Image: Jarrett Walker.

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

So – how do 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’d suggest, are the most important indicators of “major-ness”, because they are the answers to the question: "Does this service exist when I need it?" This is 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 transport 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 specialised 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.  

The solution

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 specialised 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. Los Angeles also had such a map which captured other distinctions, including rapid vs local buses, bus vs rail, and even multiple transit agencies.

But it's also not hard to highlight the Frequent Network, even in a more complex map of the entire system. The Minneapolis-St. Paul Metro Transit map used to show the maddening complexity of its whole system. But it also used 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 published a nice frequent network diagram. Here’s a chunk of it:

Image: Metro Transit.

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

Jarrett Walker is an international consultant in public transit network design and policy, based in Portland, Oregon. He is also the author of “Human Transit: How clearer thinking about public transit can enrich our communities and our lives”.

This article was originally published on his blog in 2010, and is reposted here with permission. All images courtesy of the author.

 
 
 
 

CityMetric is now City Monitor! Come see us at our new home

City Monitor is now live in beta at citymonitor.ai.

CityMetric is now City Monitor, a name that reflects both a ramping up of our ambitions as well as our membership in a network of like-minded publications from New Statesman Media Group. Our new site is now live in beta, so please visit us there going forward. Here’s what CityMetric readers should know about this exciting transition.  

Regular CityMetric readers may have already noticed a few changes around here since the spring. CityMetric’s beloved founding editor, Jonn Elledge, has moved on to some new adventures, and a new team has formed to take the site into the future. It’s led by yours truly – I’m Sommer Mathis, the editor-in-chief of City Monitor. Hello!

My background includes having served as the founding editor of CityLab, editor-in-chief of Atlas Obscura, and editor-in-chief of DCist, a local news publication in the District of Columbia. I’ve been reporting on and writing about cities in one way or another for the past 15 years. To me, there is no more important story in the world right now than how cities are changing and adapting to an increasingly challenging global landscape. The majority of the world’s population lives in cities, and if we’re ever going to be able to tackle the most pressing issues currently facing our planet – the climate emergency, rising inequality, the Covid-19 pandemic ­­­– cities are going to have to lead the way.

That’s why City Monitor is now a global publication dedicated to the future of cities everywhere – not just in the UK (nor for that matter just in the US, where I live). Our mission is to help our readers, many of whom are in leadership positions around the globe, navigate how cities are changing and discover what’s next in the world of urban policy. We’ll do that through original reporting, expert opinion and most crucially, a data-driven approach that emphasises evidence and rigorous analysis. We want to arm local decision-makers and those they work in concert with – whether that’s elected officials, bureaucratic leaders, policy advocates, neighbourhood activists, academics and researchers, entrepreneurs, or plain-old engaged citizens – with real insights and potential answers to tough problems. Subjects we cover include transportation, infrastructure, housing, urban design, public safety, the environment, the economy, and much more.

The City Monitor team is made up of some of the most experienced urban policy journalists in the world. Our managing editor is Adam Sneed, also a CityLab alum where he served as a senior associate editor. Before that he was a technology reporter at Politico. Allison Arieff is City Monitor’s senior editor. She was previously editorial director of the urban planning and policy think tank SPUR, as well as a contributing columnist for The New York Times. Staff writer Jake Blumgart most recently covered development, housing and politics for WHYY, the local public radio station in Philadelphia. And our data reporter is Alexandra Kanik, whose previous roles include data reporting for Louisville Public Media in Kentucky and PublicSource in Pittsburgh, Pennsylvania.

Our team will continue to grow in the coming weeks, and we’ll also be collaborating closely with our editorial colleagues across New Statesman Media Group. In fact, we’re launching a whole network of new publications, covering topics such as the clean energy transition, foreign direct investment, technology, banks and more. Many of these sectors will frequently overlap with our cities coverage, and a key part of our plan is make the most of the expertise that all of these newsrooms combined will bring to bear on our journalism.

Please visit citymonitor.ai going forward, where you can also sign up for our free email newsletter.


As for CityMetric, some of its archives have already been moved over to the new website, and the rest will follow not long after. If you’re looking for a favourite piece from CityMetric’s past, for a time you’ll still be able to find it here, but before long the whole archive will move over to City Monitor.

On behalf of the City Monitor team, I’m thrilled to invite you to come along for the ride at our new digs. You can follow City Monitor on LinkedIn and on Twitter. If you’re interested in learning more about the potential for a commercial partnership with City Monitor, please get in touch with our director of partnerships, Joe Maughan.

I want to thank and congratulate Jonn Elledge on a brilliant run. Everything we do from here on out will be building on the legacy of his work, and the community that he built here at CityMetric. Cheers, Jonn!

To our readers, on behalf of the City Monitor team, thank you from all of us for being such loyal CityMetric fans. We couldn’t have done any of this without you.

Sommer Mathis is editor-in-chief of City Monitor.