Re:Query Real-time SF Bus Locations With GeoFire 2.0
by dsl on Monday June 23, 2014 @03:21PM
(#7933937)
Lie is a strong word. What you are seeing likely the result of lost connectivity to the bus, which NextBus compensates for with dead reckoning. Busses also deviate from planned routes to deal with construction, head to depots, or other random things.
[ Parent
| on HN ]
Re:Query Real-time SF Bus Locations With GeoFire 2.0
by WalterSear on Monday June 23, 2014 @03:32PM
(#7934036)
That doesn't explain the ones that are continually leave the station, with the prediction constantly resetting as the bus doesn't leave. Or the ones that don't show up, and then the next one does, right on time.
If you don't know where something is, you don't know where it is. To give a number anyway is disengenuous, and breaks trust. To do it all the time, and call your data 'real-time' without caveat - lying may be a strong word for it, but it's still appropriate.
Re:Query Real-time SF Bus Locations With GeoFire 2.0
by thrownaway2424 on Monday June 23, 2014 @04:00PM
(#7934234)
NextBus always uses a straight-line estimate for the vehicle position within a few stops from the terminal. This is based on the departure times in the Muni published schedule. However, Muni operators and dispatchers do not adhere to this schedule in any way, so the estimates that NextBus gives near the beginning of Muni lines are pure fabrications. Lies, you might say.