DCist T-Shirts
dcistshirt.jpg
About DCist

DCist is a website about Washington, D.C. More

Editor: Sommer Mathis Publisher: Gothamist

About | Advertising | Archive | Contact | Mobile | Photos | Staff | Subscribe

Categories
DCist Exposed Photography Show -- Feb 20-Mar 7
Favorites
Contribute

Latest tip:

There is a suspicious package being investigated near 12th and D St SW, in front of the new Homel [more]

 

Latest link:

 

Latest Photo:

 

Recent Comments
Subscribe
Use an RSS reader to stay up to date with the latest news and posts from DCist.
Overheard
Voting Rights
Public Calendar
Links

November 7, 2006

DCist Beta Test: Metro's NextBus

2006_11_07Nextbusscnsht.JPG
In the caveman days of our youth, waiting for the bus was a simple exercise in patience. Stand there long enough and it would come...usually. However, in our current world of streaming, real time, to-the-minute, live updates, the wait has become as infuriating as a dial-up internet connection. Metro is working to ease our transit ADD, however, with a new system that provides live updates to riders via web-enabled cell phones or other handheld devices like Treos or BlackBerrys, or of course, your computer. The system is currently available system-wide on Metrorail, and on seven pilot Metrobus routes throughout D.C., Virginia, and Maryland.

After the jump, we give the system a test run. We are interested in your experiences too, so be sure to leave a comment with your cheers or jeers!

Screenshot taken from NextBus's web site

While information is now provided about both train and bus arrival times, the systems are a little different. On Metrorail, WMATA has basically given riders access to the same information posted on the LED displays that hang over platforms. To access train information on a handheld device, go to http://wmata.com/mobile and select "Next train information." Pretty straightforward.

With no similar tracking system already in place, figuring out Metrobuses was a little more difficult. Metro has been installing GPS tracking devices on its entire bus fleet for more than a year. With that project near completion, Metro uses computer modeling to track buses on their routes. The system considers the actual position of a bus, its intended stops, and typical traffic patterns along the route to estimate arrivals. This estimate is updated constantly as new information comes in. For information about bus arrivals, the site is http://wmata.nextbus.com/wmata for both handhelds and computers. You can even get a live map of where each bus along the route is actually located. The system is currently up and running on the 90, 92 and 93 in the District, Virginia's 9A and 9E routes, and Maryland's F4 and F6. The plan is to continue to roll out new routes in the coming months, though there is no timetable.

We took the system for a test run this weekend and found it to work fairly well. A quick check of the WMATA web site let us know that we did not have to rush out the door and double-time it to the nearest Green Line stop, since we would miss the next train no matter what. When we did get to the station, the train arrived right about when we were told it would.

We had similar luck with the 92 bus on U Street. Our handheld prediction for the bus' arrival was correct to within a few minutes (though nowhere near the arrival time posted on the paper schedule at the stop). However, had we not been able to borrow a friend's Treo, it would not have been so easy. We called the NextBus phone number posted at bus stops, which is supposed to guide you to your bus' arrival time. Unfortunately, we could not get the pleasant computerized voice on the other end of the line to find our bus. At that point, we were transferred to Metro's customer service center, which offered to provide us with the same arrival time posted on the paper schedule. Not helpful.

Our only other complaint is the separate online sites for bus and train information via handheld. But perhaps as Metro brings other routes online and works out the kinks in the program, they will consolidate all the information onto one site.


Email This Entry







Advertisement: DCist Continues Below!

Comments (12)

So all those staffers with their fancy Treo's should be all set for their bus rides home from the happy hours on the hill huh? Nevermind us without such devices...

 

I used to use the system 4 years ago when it was testing, I think it was the 38 bus from Farragut Square to Ballston. I found it very handy and I would use it at work when I was getting ready to leave the office.

 

Rob - This works on any WAP enabled phone, which means pretty much any phone made in the last ~3 plus years.

http://wmata.nextbus.com/wmata/wirelessConfig/internetEnabledPhones.jsp

 

Also very useful for people who can check for their ride home from work at the office computer, when their bus home doesn't come very regularly (for me, the 54). If only the 54 was part of the program.

 

#2,
I used it as well, but unfortunately for me it was extremely unreliable. I work near Courthouse metro, and would attempt to take 38B to Ballston to transfer to another bus home to Alexandria. If 38B was on time, I could make the connection and get home quicker. If it wasn't on time, I'd be hanging around at Ballston for 30 minutes, so in that case it would quicker to run across the street, get on Metro@Courthouse, and take 2 metro lines and a bus home. The bus shelter had an ETA display, but it rarely worked. Usually I just took the longer train/bus route, because it was more reliable. The last straw was one night during a snowfall, waited 40 minutes, a 38B never came, so I gave it up forever.

 

too bad I've NEVER seen anyone on the bus with a blackberry.

 

I see people with Blackberries on the bus all the time. I realize for a lot of industries in DC (e.g. non-profits) the Blackberry is still a status symbol within the organization, but for a lot of other industries, (e.g. law firms, lobbyists, etc.) everyone from the mailroom guy up has one.

And besides, as pointed out above, if your cell phone weighs less that 5 pounds, chances are it's web-enabled and can work with this system.

 

Yea, but web service for web enabled phones with many service providers (Verizon, for instance) costs about $6 a month extra. There's not many other good uses of the web on a phone with only an alphanumeric pad and a 1" diagonal screen that I can think of worth warranting the $6 charge.

 

Maybe you just don't ride the right bus rottofest? The 30 series is jam packed with Crackberries, and I'd seen plenty on other lines too.

 

For plain old mobile phone users, I found it better to point my phone to the ADA link http://wmata.nextbus.com/wmata/wireless/miniRoute.shtml?a=wmata

If you use the one supposedly designed for WAP enabled phones then it makes you choose a specific route. However, if you're standing at Vermont and U and want to go to Adams Morgan you could take the 90 or the 92. It makes you pick one route and only gives you the time for that one. Then you'd have to go back and try the other route to see which one was coming next.

The ADA website is just a text site so it worked perfectly on my mobile phone and it tells you to pick your beginning and ending stop and shows all the routes and next bus times that'll take you there.

 

you can just leave the "Bus route" field blank and it'll give you all of the routes that service the location.

 

Why the hell doesn't the system support SMS? It's 2006, for goodness sake-- just let me text "92 bus" to short code WMATA or somethhing and have it return a text message showing its location and predicted arrival times for the next three major stops. Screw WAP.

 
Post a comment (Comment Policy)

2003-2009 Gothamist LLC. All rights reserved. Terms of Use & Privacy Policy. We use MovableType.

Site Meter