Posts about London

Transit

London's spider maps

by Michael Perkins   •   September 25, 2009 11:20 am

Transport for London has these great bus maps that show routes traveling in all directions from major transit nodes.

Liverpool Street map from Transport for London. Click to enlarge (PDF).

These maps, known as "spider maps," are more abstract than the station-oriented bus maps Metro posts in stations and recently put online. They combine several useful features:

• A local area walking map, showing the location of the different bus stops keyed to a table of routes;
  
• A schematic route map for the bus, showing routing to other transit nodes in the area;
  
• A table of routes leaving from that node, either daytime or nighttime routes.

These maps, Metro's station area maps, Los Angeles Metro's "12 Minute" maps (discussed here), and improved bus schedules are all created by CHK America, Inc.

There are some challenges with this mapping method:

• You have to name the "dots". Could DC residents agree on what to call the many new places we'd have to represent as a dot on a map? Or would the dot names become conglomerations, like some Metro station names? Bus stops do have names today, typically the name of the cross street, so perhaps those could suffice.

• Our bus service seems more complicated. Some routes only travel certain times or have "turn-back" service. For example, there are some Metrobus routes that operate only two or three trips a day. Is it better or worse to put them on the map?

• Our buses are not as frequent as London's. This kind of map is most useful if the rider only has to worry about routing and not schedule. Once a rider has to worry about bus schedule and timetables, it's likely this won't be enough information. Perhaps the line widths could vary to convey frequency information.

Despite these challanges, spider maps make it very easy for someone to easily find the bus line to get from a station to any destination. Maps like these could be very valuable in the Washington region, as they are in London.

Transit

Bus on-time performance: It matters what you measure

by Michael Perkins   •   June 17, 2009 12:58 pm

Every month, Metro's customer service committee looks at a presentation on operating statistics, including a chart showing the latest bus "on-time performance" percentage. That percentage reflects the number of buses that arrive within a certain time before or after the published schedule—usually around 73-75%. However, on its own, this number doesn't give management enough information to effectively maintain bus quality. In addition, it doesn't capture important elements of bus performance, like bus bunching.

Photo by aussiegall.

If the on-time percentage improves or degrades, without looking any further, could Metro say why? If the percentage degrades drastically, could the Board do anything other than ask management to do a better job? Management needs to be able to identify trends, detect problems with individual routes or trips, and focus their attention on the areas that might need more resources or oversight.

The single on-time performance percentage also does not identify problems with bus bunching, especially on frequent routes. Imagine a bus line that is supposed to have service every ten minutes, but experiences bunching. Take five buses in a row starting at 8am (see top line in the figure), bunch the middle three together and spread the other two out (see bottom line in the figure). This is a worst case, but under Metro's on-time percentage rules, all of these buses are considered "on-time," because each bus is no more than two minutes ahead of or seven minutes behind schedule.

The green bar shows the range of times the 8:20 bus could arrive and still be considered on-time. A passenger arriving just on time for the 8 am bus will have just missed it, as it left two minutes early, and will have to wait until 8:17 for the next bus. That's a wait of just over seventeen minutes for a bus that's supposed to come every ten!

London looks at bus on-time measuring differently. Because the bus lines in London are operated by private contractors, it's very important for the local transit authorities to accurately measure on-time performance because there are real financial incentives or penalties involved. They measure how often buses pass by certain points on the network and track the "excess waiting time." All that time you have to wait for a bus that's running late or is bunched with others is added up and averaged over the route, and the excess waiting is compared to how much you'd normally have to wait assuming you come to the bus stop randomly. The reports for bus performance are published on the web.

In our example above, the average scheduled wait time is five minutes, and there are two buses you'd have to wait on average eight minutes, so the excess waiting is six minutes total, about 1.5 minutes per bus, or about 30% extra. (Under the London system, buses don't get credit for making you wait less than average.) This makes it easy to see when high-frequency buses are not meeting the required headways, and London applies this calculation to all buses that are supposed to come every 12 minutes or better. They even post the information on the web quarterly.

Metro should adopt London's system to measure on-time performance. The current measurement does not work for frequent buses. The London model focuses on the rider experience, compares various bus routes' performance, and gives a sense of the magnitude of the problem. In addition to this change for high-frequency bus routes, Metro should start regularly reporting on-time performance figures for all bus routes, as part of the monthly ridership report. They should also highlight the worst performing lines for each jurisdiction. If the problem is somehow Metro's fault, the route can receive the appropriate management attention. More likely, traffic congestion or other factors are at fault. In that case, data in hand, Metro Board members could make their case with state and local transportation officials to make transit operation a higher priority on corridors that are experiencing poor performance.

By identifying and improving poor performing bus lines, we can get people moving to their destinations more quickly, and reduce operating costs. Faster travel speeds and more regular schedules would drive up ridership, improving Metro's bottom line and allowing more service with the same local subsidy. Metro should revise the way they present performance metrics to make it possible.