Public rider information
Data methodology
Every rider-facing result identifies its source, observation time, confidence, and unavailable state.
Measure catalogue
Every published measure has a stable identifier, version, formula, scope, exclusions, uncertainty, and links to its sources.
Service reliability and regularity
- On-time percentage
The share of settled arrival observations no more than five minutes early or late.
Version last-prediction-within-ten-minutes-v1 · network-reliability:on-time-percentage
- Average settled delay
The arithmetic mean delay of settled arrival observations; negative values are early and positive values are late.
Version last-prediction-within-ten-minutes-v1 · network-reliability:average-delay
- How late the worst 5 in 100 settled arrivals were
Sort settled arrival delays from least to greatest. This is the delay where only about 5 arrivals in 100 were equally late or later in the published route window.
Version last-prediction-within-ten-minutes-v1 · network-reliability:p95-delay
- Scheduled-trip position coverage
The share of scheduled bus trips with at least one archived realtime position carrying the same route, trip, and service date.
Version scheduled-trip-position-observation-v1 · network-reliability:trip-position-coverage
- High-frequency excess predicted wait
The difference between waiting time implied by settled predicted arrival spacing and waiting time implied by scheduled spacing for eligible high-frequency route–stop hours.
Version settled-predicted-excess-wait-v1 · network-regularity:excess-predicted-wait
Evidence quality and current disruptions
- Prediction-to-timetable match coverage
The share of published realtime prediction points that can be joined to an official scheduled trip and stop time.
Version realtime-prediction-timetable-match-v1 · network-quality:prediction-timetable-match-coverage
- Confirmed active operator notices
The number of connected official operator notices whose source-published active interval is active at the time of the snapshot.
Version operator-published-active-interval-v1 · network-disruptions:confirmed-active-notice-count
Regional inventory and amenities
- Imported transit stops in the region
The number of stop records in the currently imported regional GTFS schedule.
Version city-current-inventory-v1 · city-inventory:stop-count
- Imported transit routes in the region
The number of route records in the currently imported regional GTFS schedule.
Version city-current-inventory-v1 · city-inventory:route-count
- Imported Ottawa public washroom locations
The number of location records in the currently imported City of Ottawa public-washroom dataset.
Version city-current-inventory-v1 · city-inventory:washroom-count
- Imported Ottawa drinking-water locations
The number of location records in the currently imported City of Ottawa drinking-water dataset.
Version city-current-inventory-v1 · city-inventory:drinking-water-location-count
- Washroom wheelchair-status evidence coverage
The number of imported public-washroom records whose source publishes a supported wheelchair-access status, shown against all imported public-washroom records.
Version regional-washroom-wheelchair-status-v1 · amenity-evidence:wheelchair-status-coverage
Ward inventory
- Transit stops in a ward
The current imported GTFS stop count assigned to a sourced City of Ottawa ward boundary.
Version ward-counts-v1 · ward-inventory:stop-count
- Scheduled routes serving a ward
The number of current imported routes linked to at least one stop assigned to the ward.
Version ward-counts-v1 · ward-inventory:route-count
- Public washroom locations in a ward
The current imported City of Ottawa public-washroom locations contained by a sourced ward boundary.
Version ward-counts-v1 · ward-inventory:washroom-count
- Drinking-water locations in a ward
The current imported City of Ottawa drinking-water locations contained by a sourced ward boundary.
Version ward-counts-v1 · ward-inventory:drinking-water-location-count
Departures and predictions
Scheduled departures come from the currently imported OC Transpo and STO GTFS service calendars. A realtime departure is shown only when a trip update from the matching operator can be matched to the scheduled trip and stop.
Cancellation and skipped-stop relationships are displayed explicitly. Failed, malformed, unexpectedly empty, stale, or partially failed feeds are not called healthy. When live data is missing, the schedule remains labelled scheduled.
Trip planning and accessibility
Trip plans come from the configured OpenTripPlanner graph built from the imported transit feed and routing data. Otranspo does not invent a fallback itinerary.
Wheelchair and step-free preferences are sent to the routing engine. Each returned leg retains the source accessibility state; missing states remain unknown.
Public report patterns
Individual reports are private. Public patterns include only moderator-confirmed non-safety and non-operator reports grouped by category and route, with at least five reports in each cohort.
A public count is community-submitted evidence, not an operator-confirmed incident count.
Operational status
Status is computed from direct probes of the database, current migrations, imported schedule, routing engine, independent realtime feeds, durable worker, email, storage, geocoder, and required configuration. Optional components degrade independently.
Reliability method correction
On 4 August 2026, the on-time method changed from counting repeated archived predictions to one settled observation per arrival: the last prediction within ten minutes of scheduled time, evaluated with a two-sided five-minute window. On the same archive, the result changed from 86.7% to 77.4%. This is a correction to the method, not evidence that service changed on that date.