Public methodology register
Bus speed between timepoints
- Version
- settled-reliability-patterns-daily-v1
- ID
- route-segments:running-speed
Definition
- Definition
- How fast buses actually moved between two consecutive timepoints of a route, next to the speed the timetable planned for the same segment.
- Formula
- Segment ends are the stops the timetable marks as timepoints. When it marks every stop, the trip is cut about every 1 kilometre. Observed time = arrival at the end minus arrival at the start. Speed = distance times trips divided by total time, in kilometres per hour. Slow trip: took at least 1.5 times the scheduled time.
- Units
- kilometres per hour, with the count of trips
- Population
- Trips that reached both ends of a segment between two consecutive timepoints, from settled final predictions.
- Measurement window
- The 28 most recent completed service days, by calendar date in Ottawa.
- Coverage
- Only days the daily rollup computed. Days with partial feed capture and days when the live trip numbers did not match the timetable are left out and listed.
- Publication eligibility
- Segments shorter than 300 metres or 1 minute are not measured. A segment needs at least 20 trips before a speed is shown.
- Scope
- Every bus route segment with enough trips, by the same hour bands as bunching.
- What this number can support
- Compare the observed speed with the scheduled speed on the same segment. Distance is a straight line between stops, so both speeds are lower than the road speed.
Implementation status
- Source candidate
- Implemented in this source candidate.
- Public production
- This metric version has not been independently verified in the public production deployment.
The daily calculation is implemented in this source candidate (worker rollup, migration 0396). Public production verification for this version is not yet recorded.
Sources and identifiers
- Method
settled-reliability-patterns-daily-v1Daily reliability-pattern method - Current API
reliability-patternsBunching, slow segments and on-time by hour
Exclusions
- OC Transpo O-Train lines are left out: the operator publishes no live train positions, so their arrivals repeat the timetable.
- Times over 4 times the schedule plus 10 minutes are treated as data errors and left out. A stop a trip visits twice is never a segment end.
Uncertainty and interpretation
- Arrival times are the last prediction made no earlier than 10 minutes before the scheduled time, not a recorded door opening.
- Distance is the straight line between stops along the trip, not the road, so speeds are lower than true road speeds. Use them to compare segments, not to check speed limits.
Current evidence
No registered drill-down record is available for this metric. The public page remains the current presentation source.
Change history
No registered material change is recorded for this metric version.