Saul Blumenthal reports NextBus, the service the T is using to provide arrival data, just dramatically expanded the number of routes with information available to riders.
The MBTA isn't running the user-facing services (NextBus, etc) themselves, instead supplying a raw XML data feed for other services to use to make the magic happen. They rate-limit the number of times any one user can request data and repeated violations of this limit is cause for blacklisting. While it is still possible that this will overwhelm their servers, it does seem like they have done the right things to minimize the chances of that.
Why are the North Shore buses from the Lynn garage - 25 routes, #411- #468, the only ones not now available in the NextBus service? These are some of the longest routes (35-40 miles round trip) in the system.
They promised the entire system would be available by the end of summer, so for whatever reasons, those didn't make this cut (maybe it's because they are so long? More data they have to figure out?).
I just wanted to send the group a quick note to let you know that we plan on rolling out real-time information for a significant number of additional routes next Monday.
I live on the 72 bus (trackless trolley). When I choose that route, the only choice for an outbound destination is Belmont Center -- which is only served by this route on Saturday night and Sunday. (It's now Monday morning rush hour.) Times predicted for the next outbound trip at my stop are 31 minutes from now, and 81 minutes from now. In fact, the rush hour schedule is every 20 minutes. Of course, if they're really talking about the next bus to Belmont Center, that won't be for 5 days, 10 hours, and 30 minutes.
Inbound predictions were similarly screwed up.
Looks about as useful as the highway traffic predictions that now come from California.
Huh - I've emailed repeatedly and even phones about the fact that all of a sudden SMS messaging hasn't worked all this week, but gotten no response whatsoever. Given what service on the 66 has been like this week, this kind of sucks.
I used this service in Emeryville, CA, last fall during a work trip. The stops had the stop number posted and all the info about how to call/text to get timing for the Emery-Go-Round. I think it will be a cold day in hell before the MBTA gets that far, since most stops here don't even post a schedule. But I'm looking forward to trying out the texting service for my regular stops. And on a cold rainy night I'll be happy to check the NextBus site before walking out of the office any earlier than necessary.
Comments
Thats been the case for a few
Thats been the case for a few weeks now. Whats baffling is that the MBTA website still only has the first 5 routes.
Not quite
A few weeks ago, they released the second set of routes that included the 57, but not the 64.
They now have the 64 listed. It looks like the third wave that covers nearly every route is now out.
Not nearly every route, if you live/work in Quincy
Information for only one of the 17 routes that pass through Quincy (2-- routes) is available
Yep, only the 245 was
Yep, only the 245 was available. What about the 15 other Quincy buses?
slashdotted
I would imagine they're very worried about the launch of this service
right on the mbta site. It will be very popular. Bet the server goes down.
The MBTA isn't running the
The MBTA isn't running the user-facing services (NextBus, etc) themselves, instead supplying a raw XML data feed for other services to use to make the magic happen. They rate-limit the number of times any one user can request data and repeated violations of this limit is cause for blacklisting. While it is still possible that this will overwhelm their servers, it does seem like they have done the right things to minimize the chances of that.
Why are the North Shore buses
Why are the North Shore buses from the Lynn garage - 25 routes, #411- #468, the only ones not now available in the NextBus service? These are some of the longest routes (35-40 miles round trip) in the system.
Just a guess
They promised the entire system would be available by the end of summer, so for whatever reasons, those didn't make this cut (maybe it's because they are so long? More data they have to figure out?).
From MassDOT
From MassDOT --
http://groups.google.com/group/massdotdevelopers/browse_thread/thread/8ceca1917459fefa/3c367f4e7390a67a?#3c367f4e7390a67a
Not working at all right
I live on the 72 bus (trackless trolley). When I choose that route, the only choice for an outbound destination is Belmont Center -- which is only served by this route on Saturday night and Sunday. (It's now Monday morning rush hour.) Times predicted for the next outbound trip at my stop are 31 minutes from now, and 81 minutes from now. In fact, the rush hour schedule is every 20 minutes. Of course, if they're really talking about the next bus to Belmont Center, that won't be for 5 days, 10 hours, and 30 minutes.
Inbound predictions were similarly screwed up.
Looks about as useful as the highway traffic predictions that now come from California.
Send an e-mail to
Send an e-mail to . I have gotten quick replies in the past.
Quick replies?
Huh - I've emailed repeatedly and even phones about the fact that all of a sudden SMS messaging hasn't worked all this week, but gotten no response whatsoever. Given what service on the 66 has been like this week, this kind of sucks.
or post problems
or post problems here.
http://groups.google.com/group/massdotdevelopers
seanh
next bus
I used this service in Emeryville, CA, last fall during a work trip. The stops had the stop number posted and all the info about how to call/text to get timing for the Emery-Go-Round. I think it will be a cold day in hell before the MBTA gets that far, since most stops here don't even post a schedule. But I'm looking forward to trying out the texting service for my regular stops. And on a cold rainy night I'll be happy to check the NextBus site before walking out of the office any earlier than necessary.