Jeff Kaufman
unread,Feb 15, 2015, 12:44:53 PM2/15/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nextbus-a...@googlegroups.com
A common scenario when working with bus predictions:
* Look in the app.
* See a bus for the stop in 5min and 45min.
* Walk to the stop.
* Look in the app.
* See only a bus for the stop in 40min.
This generally happens for two different scenarios:
a) They missed the bus. Maybe it was a little early or they were a
little late, but it's not coming.
b) Nextbus stopped predicting a bus at that time. I don't know why
this happens, but it seems to happen relatively often for me on the
MBTA for buses that haven't left the starting point yet.
In the case of (a) they should give up on their bus, in the case of
(b) they might want to keep waiting.
I'd like to distinguish cases (a) and (b) in my UI, and right now all
I'd be able to do is look at stops farther along the route and see if
nextbus was predicting stops for those. This is kind of awkward and
error prone, though. Much nicer would be if Nextbus could add a flag
to the predictionsForStop command like includeNegative=true that would
include in the predictions for a stop which buses had recently passed
by.