-
Notifications
You must be signed in to change notification settings - Fork 4
API requirements
Chun Ho Chow edited this page Jul 12, 2018
·
2 revisions
- each bus/train time point (at a station) needs to be associated with the scheduled time
- "linearisation" of GPS data. Instead of passing the raw GPS points, the data should be passed as which stations/stops the vehicle is at / in between.
- Status at each time for each vehicle: at stop X, or between stop X and Y
- We actually don't really care about how far along the route between two stations the vehicle is, unless we want to do it to the granularity level of "this intersection is always a mess". But that is definitely for the far future.
- how to handle service disruptions/reroutings?