nextbus (89 and 101!!!!)
Aug. 26th, 2010 10:37 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
aquaflame16.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
davis_squareGuess what I discovered?!
The 89 and 101 are now on nextbus!
Woohoo!
The system is still a little confused by the two routes for the 89, see stop listing here, but it works.
(The main problem with this confusion is that you can't currently use the end point stations for predictions, but if you try it just says "no current predictions" so you might think it's not working for that bus when it's just that stop. I have no idea whether this will be fixed or not. The 101 seems to be having a bit of the same problem in a few spots.)
If anyone doesn't know about NextBus, it is a real-time arrival predictor for buses, and it is amazingly helpful for bus travelers. (I believe it now covers all buses in this area, and possible all buses system-wide. The 89 and 101 were not on until recently, so I'm super excited that they've been added now.)
You can access it on the nextbus website, by text, phone call (# is listed on website prediction page), or various smartphone apps.
(It can be a little confusing to learn to use it by text msg, but once you figure it out and get some stops saved it's awesome. This is what I do.
ETA: I've played around with it and discovered that the stops between Davis and Powderhouse DO work for the 89 if you use the proper stop numbers, for example by looking them up on the 96 list.
So Davis busway 5104; CollegeAve@Hall 5019; College@Kidder 5020
If you're texting you can specify route initially like this "nbus mbta r89 5019" will give you the 89 at College@Hall.
Then once you've looked up any stop once you can save it as anything you like and then use that to look up that route at that stop. (I keep a list in the notepad of my phone of saved stops, which I call things like bsq89 or 96porter.)
The 89 and 101 are now on nextbus!
Woohoo!
The system is still a little confused by the two routes for the 89, see stop listing here, but it works.
(The main problem with this confusion is that you can't currently use the end point stations for predictions, but if you try it just says "no current predictions" so you might think it's not working for that bus when it's just that stop. I have no idea whether this will be fixed or not. The 101 seems to be having a bit of the same problem in a few spots.)
If anyone doesn't know about NextBus, it is a real-time arrival predictor for buses, and it is amazingly helpful for bus travelers. (I believe it now covers all buses in this area, and possible all buses system-wide. The 89 and 101 were not on until recently, so I'm super excited that they've been added now.)
You can access it on the nextbus website, by text, phone call (# is listed on website prediction page), or various smartphone apps.
(It can be a little confusing to learn to use it by text msg, but once you figure it out and get some stops saved it's awesome. This is what I do.
ETA: I've played around with it and discovered that the stops between Davis and Powderhouse DO work for the 89 if you use the proper stop numbers, for example by looking them up on the 96 list.
So Davis busway 5104; CollegeAve@Hall 5019; College@Kidder 5020
If you're texting you can specify route initially like this "nbus mbta r89 5019" will give you the 89 at College@Hall.
Then once you've looked up any stop once you can save it as anything you like and then use that to look up that route at that stop. (I keep a list in the notepad of my phone of saved stops, which I call things like bsq89 or 96porter.)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2010-08-26 03:39 pm (UTC)Yet another reason why the T really should be calling it 89 and 89A or something!
Hmm. I played around with it a little and it seems the stops numbers in that area DO work for the 89, they're just not listed! So try pulling the stop numbers off the 96 and that should work. (Including the Davis busway 5104.)
"Also, I just tried sending a text message for stop 02736 (ball square); it asked me to reply with which route I wanted, 89 or 80; when I said 89, it gave me data on the next Route 1 bus coming to Mass Ave "@Btlph", wherever that is. So, um, sadly, not quite ready for prime time yet, it seems."
That's . . . weird!
I used it this morning, so I know it works, but I had saved the stop already.
Try specifying the route initially, like this: "nbus mbta r89 2736" and see if that works?