Public rider information
Data methodology
The short version
Every rider-facing result identifies its source, observation time, confidence, and unavailable state.
Measure catalogue
Every published measure has a stable identifier, version, population, window, unit, coverage, eligibility rule, interpretation limit, and links to its sources.
Service reliability and regularity
- On-time percentage
The share of selected final provider predictions no more than five minutes early or late relative to schedule; arrivals are not independently measured.
- Unit
- percent of selected final feed predictions
- Window
- Route summaries: rolling 30 days. Route-hour evidence: recent 14-day scan.
Version last-prediction-within-ten-minutes-v1 · network-reliability:on-time-percentage
- Average settled delay
The arithmetic mean delay of selected final provider predictions; negative values are early and positive values are late.
- Unit
- seconds, displayed in minutes
- Window
- Rolling 30-day route-health window.
Version last-prediction-within-ten-minutes-v1 · network-reliability:average-delay
- How late the worst 5 in 100 settled predictions were
Sort selected final predicted delays from least to greatest. This is the delay where about 5 predictions in 100 were equally late or later in the published route window.
- Unit
- seconds, displayed in minutes
- Window
- Rolling 30-day route-health 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.
- Unit
- percent of scheduled bus trips
- Window
- Last seven completed service dates.
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.
- Unit
- seconds, displayed in minutes
- Window
- Eligible completed service days in the latest 30 days.
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.
- Unit
- percent of realtime prediction points
- Window
- Current quality: trailing 30 minutes. Historical quality: completed service-day aggregates.
Version realtime-prediction-timetable-match-v1 · network-quality:prediction-timetable-match-coverage
- Confirmed current operator notices
The number of connected official notices classified for current display from the published timing or the disclosed source-presence policy. Notice display does not confirm physical service impact or restoration.
- Unit
- official notices
- Window
- Point-in-time notice display, evaluated against complete current timing lists or the disclosed source-presence policy.
Version operator-published-alert-periods-v2 · 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.
- Unit
- stop records
- Window
- Current imported schedule snapshot; this is not a time-period total.
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.
- Unit
- route records
- Window
- Current imported schedule snapshot; this is not a count of trips in a period.
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.
- Unit
- location records
- Window
- Current municipal dataset snapshot; opening hours and seasonal periods are not the counting window.
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.
- Unit
- locations, not individual fountains
- Window
- Current municipal dataset snapshot; seasonal availability is not the counting window.
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.
- Unit
- classified records out of all washroom records
- Window
- Current imported amenity snapshots.
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.
- Unit
- stop records
- Window
- Current ward-boundary and schedule snapshots.
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.
- Unit
- route records
- Window
- Current ward-boundary and schedule snapshots.
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.
- Unit
- location records
- Window
- Current ward-boundary and municipal dataset snapshots.
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.
- Unit
- locations, not individual fountains
- Window
- Current ward-boundary and municipal dataset snapshots.
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 are calculated from the current published schedules and street-routing data. Otranspo does not invent a fallback itinerary.
Wheelchair and step-free choices are checked for every suggested leg. Missing accessibility information remains 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.
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.
Technical record
Methods, assurance checks, and release evidence for people who need to inspect them.
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.