-
Notifications
You must be signed in to change notification settings - Fork 6
[Archived] PointReliability, StopReliability, and SpeedViz V1
This doc describes the first bare-bones iteration of SpeedViz and Reliability. The purpose of this project is to have it fully implemented in a day, meaning that there will be trade-offs in terms of features and testing.
-
For a route, user can choose the route's direction (and branch, if applicable - for now each branch will be considered as another route). This will make all the stops in that direction visible.
-
For each stop, selecting it will populate reliability data in the bottom pane.
-
Each segment between two stops (in order) will have a line (going along the route's GeoJSON) that will be in red/yellow/green, in reference to its average speed in that segment. For simplicity, green means scheduled speed (or faster), yellow means 0.5 to 1.0, and red is for less than half.
- add some of the stuff as described in SpeedViz, StopState, and PointReliability proposals.
- A stop is just a PointReliability. We then choose one of the two clusters to display based on the stop's heading. Since we can get an ordered list of stops from Nextbus, we determine the heading based on the current stop and its next stop.
StopReliability {
route: Route
location: Coordinate
arrivals: [{
vehicle: Vehicle
time: String
}]
}
(same as a PointReliability object)
- For simplicity, we only care about the average speed between two stops. For this, we'll have to choose a direction, which will done by choosing the terminal stop (like Embarcadero / Balboa Park). We then get the StopArrivals from above, and then get the speeds by going through the stops keeping track of the VehicleIDs.