Tag Archives: transit maps

Short, clear station names vital to transit system wayfinding

WMATA map with long station names: "they're not station names, they're committee meeting minutes."

WMATA map with long station names: “they’re not station names, they’re committee meeting minutes.”

The folks at London Reconnections have a new podcast – On Our Line. The second episode features a long conversation with two experts on transit map design and understanding, Max Roberts and Peter Lloyd.

The discussion hits on several topics about the challenges in transit map design, particularly for complicated networks. They also discuss objective measures of success in design (e.g. timing users in finding their way from point A to b on a map) and the conflicts with graphic design ideas. Another challenge is the future of the paper map and the seemingly inevitable move towards electronic map displays of some kind.

A few anecdotes stood out to me:

Touch Screen Maps: These might seem to be an obvious technological solution to mapping challenges with complex networks, frequent service changes, language barriers, etc. New York installed some touch screen maps as a part of a pilot program in 2014; despite rave reviews, no one seemed to use them. The podcast conversation (at 37:50) hits on the problems: the ad-supported model means the kiosks look like ads. Perhaps more interesting is the embarrassment of a rider using the kiosk, requiring a level of interaction that physically signals to everyone else on the platform that ‘I don’t know where I’m going.’ A static, printed map allows for consumption of information in a less obvious manner.

Station Names: Asked for examples of the worst transit maps they could think of, WMATA’s marathon-length station names are an obvious choice (at 1:07:20). Short station names are important to efficient, clear, and effective wayfinding. Roberts on WMATA’s map: “some of the stations – they’re not station names, they’re committee meeting minutes.”

File that one under “it’s funny because it’s true.”

Using the map to influence routing: Roberts obliquely mentions working with WMATA (48 minutes in) on changing the map to encourage different routing, presumably a reference to adjusting the map in order to encourage Blue Line riders from Virginia to transfer and use the Yellow Line (with excess capacity) to travel into DC.

It’s one thing for the map (or trip planner) to influence your route; it’s another for that decision to be made by an algorithm completely removed from human interaction. With driverless cars, it’s still unclear how humans will react to navigating networks in that way – adjusting human behavior is challenging enough.

Metro highlights frequency in new bus map

This week, Greater Greater Washington highlighted WMATA’s latest iteration of their new bus map (as post on the first iteration is here), which opts for a diagrammatic representation of the bus network, highlighting frequent, all-day bus services over infrequent and irregulat coverage bus routes.

The new map is a huge improvement of the old one.  Digging through the archives, I found this post, with a screencap of roughly the same part of the city – just for the purposes of comparison.

The inspiration for posting about the shortcomings of the WMATA map back in 2010 came after reading Jarrett Walker’s blog.  Walker emphasizes the value of frequency, and the importance of highlighting frequent services in an operator’s communications, such as maps. WMATA’s old maps made no such distinctions – in fact, the map highlighted rather useless distinctions, such as whether or not a bus crossed state lines.

The timing of Metro’s release of the new map was fortuitous.  Last week, I had the opportunity to participate in Walker’s two-day transit network design course.  The exercises in the course force participants to deal with the trade-offs between conflicting goals, limited budgets, constrained geography, and the fundamental geometry of efficient transit service.

(Jarrett has posted reviews of the DC course here – I would definitely recommend the course both for those working on transit/transportation, as well as anyone interested in how cities function)

Frequency Mapping

Last week, Jarrett Walker had a great post illuminating the basic reasons for ‘frequency mapping,’ where a transit agency maps out transit routes that meet some threshold for frequent service (such as buses every 10 minutes, or 15 minutes, etc).

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.

We have some great examples of this in DC.  The entirety of the Circulator network is, in essence, a Frequent Network.  The Circulator aims for 10 minute headways, the routes are fairly simple and easy to understand, and thus people can look at the map and understand where the bus is and where it’s going.

WMATA’s bus map for DC, however, doesn’t make this distinction.  While there is a extra color designation for Metro Extra service (meeting the Frequent Network threshold), the other color distinctions merely show which jurisdiction the bus route operates in.

DC Bus Map WMATA crop

The distinction between which services operate only in DC (in red) and those which cross into Maryland (green) isn’t really important for a rider.  Furthermore, the overwhelming use of red for the DC routes makes it hard to follow those routes across the map, seeing where they turn and what streets they travel down.

DC Bus Map WMATA legend

Blue services with dashed lines, however, is indicative of MetroExtra (for some reason, a separate brand from Metro Express), and at least makes a effort at differentiation based on frequency – but that tends to get lost in the visual complexity of the overall map.

There’s a common phenomenon of ‘rail bias,’ (hat tip to The Overhead Wire) where riders will opt for riding a train rather than a bus.  However, rail systems tend to have several key attributes that make them more attractive – the investment in the infrastructure both enables and requires a high frequency of service, and the route structure is almost always simple enough to convey in an easily-understood diagram or map.

The lesson from Jarrett’s post is that simple mapping based on frequency can help address some of the perceived shortcomings of buses.  Even without addressing route structure, this is a relatively simple improvement in communication that helps riders a great deal.

Briefly noted

7000Series

Some items of note today: