Transit
More details could improve Metro's trip planner itineraries
Programs like Metro's trip planner can make riding transit easier for new riders and seasoned commuters alike. But the way that trips are shown has a huge impact on the effectiveness of the data.
A few weekends ago, I needed to travel downtown for Transportation Camp. Since I don't often make the trip, I decided to use Metro's trip planner to see when I would need to leave in order to get to the event for its 10 am start. The result was not very helpful.
I chose the option to plan a trip arriving by 9:30 to account for trackwork scheduled for the Orange Line and also for the walk to the venue. As you can see, the trip planner told me to expect a travel time of 1 hour and 36 minutes. That's a long time. A lot longer than it should be, in fact.
The problem lies in the way Metro's trip planner deals with "arrive by" queries. When users try using the "arrive by" tool, the planner tool gives riders the trip arriving closest to (but not after) the time specified. That sounds good on the surface, but let's consider my trip.
If you look at the results closely, you'll see that the trip planner has me wait 40 minutes at New Carrollton station. If I transferred directly from the bus to the Orange Line, I would arrive at Foggy Bottom station at 8:55, which is 35 minutes too early. Instead of telling me this, the planner just makes it look like I have no option but to wait 40 minutes at New Carrollton.
That kind of information can turn riders off. Why take a trip that will take over an hour and half when you could probably drive it in a half hour?
What would be particularly helpful would be to show each possible permutation of a trip, especially when connections are involved. Metro's trip planner deals with this by returning each as a separate itinerary. For example:
- Board a bus at 9:10. Exit at the Metro stop at 9:25. Take a Green train at 9:30.
- Board a bus at 9:10. Exit at the Metro stop at 9:25. Take a Green train at 9:36.
- Board a bus at 9:10. Exit at the Metro stop at 9:25. Take a Green train at 9:42.
I think a format like this would be more helpful. The trip Metro actually planned for me is outlined in red.
I've also included (in yellow highlighting) one arrival after the "arrive by" time. This allows for trips that arrive within a reasonable time. For example, if I want to arrive by 9:30, and there's a train that gets me there at 9:31, that's probably okay, and a trip I might want to know about.
Other itineraries should be substantially different from the first (since it's showing all options). In this example, there's really only one other feasible option, and that's to travel by way of the Green Line.
An itinerary like this would allow riders to better plan their trips. Perhaps arriving early isn't a good option. In that case, they know they have time to stop off for coffee, or perhaps that they could wait for a later bus and still arrive within a reasonable time.
WMATA's arrive by function used to return all sorts of gibberish to achieve "alternate" itineraries, including trips that went past where you wanted to go and then had you change vehicles and return. These days, Metro has modified their planner so it does better, though it still leaves a lit to be desired.
Metro's trip planner and other trip planning applications could be better by showing more options. I know my graphics leave a little to be desired, but it's the principle I'm trying to illustrate.
Do you have thoughts for ways to improve trip planning?
Comments
- Community stories show the shift to a walkable lifestyle
- Young kids try to assault me while biking
- Focus transportation on downtown or neighborhoods?
- Some are pushing to limit sidewalk cycling
- Where is downtown Prince George's County?
- Metro bag searches aren't always optional
- Endless zoning update delay hurts homeowners










Another option (admittedly in the "more info" category) that I've seen is to have a line at the bottom of each trip segment in smaller print that says "next train 8:38" so you know what kind of delay you'd have if you missed the transfer.
by RichardatCourthouse on Feb 3, 2012 12:29 pm • link • report
The planner really gets in trouble when Metro closes stations. For example, select "rail only," and go try to plan a trip from Vienna to the Smithsonian tomorrow, when Rosslyn will be closed. Instead of providing information about the anticipated shuttle services, the planner returns a message of no available service. While allowing both rail/bus options will include the 38B, among others, the planner still acts as if Metro isn't running its shuttle service, and reads as if the trains just aren't running. That's a waste, particularly since the shuttle bus service has actually been pretty reliable.
by worthing on Feb 3, 2012 12:31 pm • link • report
Having a 'next train/bus departing at X time' as Richard suggests would be a significant upgrade. Someone has to hit various 'plan to arrive 5/10 minutes later' options to guess at when a later connection might be, whereas having that information presented would be handy. Sometimes you have flexibility and it is not so important to arrive by a narrow time period, which the current system provides for.
by DCster on Feb 3, 2012 1:04 pm • link • report
by charlie on Feb 3, 2012 1:05 pm • link • report
Having said that I've been using Google transit directions quite a bit. I like seeing on a map what my trip is going to look like. It's also pretty good at showing you options that require more walking, but might be faster. On Android phone, it also gives GPS navigation directions, telling you when to get off the bus for instance.
by Steven Yates on Feb 3, 2012 1:19 pm • link • report
People that are more experienced riding Metro and other bus lines don't need trip planner as much. Maybe a tweak here and there is needed, but otherwise it is good as is.
by Cassidy on Feb 3, 2012 1:25 pm • link • report
by Cassidy on Feb 3, 2012 1:29 pm • link • report
Regardless, the trip planner shouldn't be telling you to wait while three trains pass you by, period.
Google Transit can't always be trusted either - the B30 data is messed up and thinks it takes 10 minutes to get from Greenbelt to BWI.
@charlie, the trip planner is very useful and lots of people use it. I would not be surprised if it is the most used part of the wmata website. Also how can you have a transit agency website without a trip planner?
by MLD on Feb 3, 2012 1:48 pm • link • report
by David R. on Feb 3, 2012 2:08 pm • link • report
by David R. on Feb 3, 2012 2:12 pm • link • report
by charlie on Feb 3, 2012 2:59 pm • link • report
No, I don't have the numbers specifially, but WMATA says it's a popular feature:
http://www.wmata.com/about_metro/news/PressReleaseDetail.cfm?ReleaseID=3994
1.7 million hits per month and TBD says the whole site gets 3.5 million hits a month:
http://www.tbd.com/blogs/tbd-on-foot/2011/11/wmata-com-the-evolving-history-of-the-d-c-metro-website--13506.html
Based on your crackerjack speculation we can determine it's probably useless though!
by MLD on Feb 3, 2012 3:36 pm • link • report
by charlie on Feb 3, 2012 4:26 pm • link • report
by MLD on Feb 3, 2012 4:43 pm • link • report
However, I think that number, in isolation, is pretty useless. How many of those searches result in Met ro trips. You clearly don't think it is 1:1 ration. 1:10? 1:100? Or it the trip planner just being hit with a lot of spam bots?
For as long as I've been reading GGW, people try to find ways to fix the trip planner. Spatial based maps seem more popular. I did personally give up using it back when it required "Street" or "road" as part of the address -- no idea whether it still does.
by charlie on Feb 3, 2012 6:34 pm • link • report
It's not perfect, but I've learned how to make it work for me over the years.
by Jazzy on Feb 4, 2012 8:08 am • link • report
by Lackadaisi on Feb 5, 2012 6:59 am • link • report
by The Civic Center on Feb 5, 2012 7:59 am • link • report
by Falls Church on Feb 5, 2012 12:07 pm • link • report
Some apps do have trip planners that do Metro station to station only, because that's easy.
by MLD on Feb 5, 2012 3:35 pm • link • report
Good point. I tried plugging in the above trip in google maps and it performed somewhat better on routing (although still didn't seem to give the shortest possible time) and the interface was way better than wmata's trip planner. My guess is that if you want improvements, it would be much easier to get Google to make them than WMATA. Google is inherently interested in making quality products if for no other reason, as a matter of pride. WMATA lost all sense of pride decades ago. Also, obviously, Google has a financial incentive to make sure their products are top notch.
Here's what google told me (1 hour 12 mins). :
Transit directions to Foggy Bottom Metro Station
Crescent Rd & Gardenway
Greenbelt, MD 20770
S Crescent Rd & Garden WY
G13
Bus towards Greenbelt Station
8:10am - 8:19am (9 mins, 16 stops)
Greenbelt Metro Dr & Cherrywood Ln
Walk to Greenbelt Metro Station
About 1 min (15 mins to make transfer)
Greenbelt Metro Station
Green
Subway towards Branch Ave
8:34am - 9:02am (28 mins, 12 stops)
L'Enfant Plaza Metro Station
Blue
Subway towards Franconia Metro
9:14am - 9:22am (9 mins, 6 stops)
Foggy Bottom Metro Station
by Falls Church on Feb 5, 2012 4:07 pm • link • report
by Geoffrey Hatchard on Feb 8, 2012 9:20 pm • link • report
Add a Comment