Ottawa and Gatineau
Source coverage varies by operator. A published schedule does not prove live service; check each source and date before relying on it.
Source coverage
Partial
Partial
Official static GTFS is imported with its checksum and service dates.
Imported schedule checked Oct 9, 2026, 1:03 a.m. Service dates in this source: from Oct 9, 2026 through Nov 9, 2026.
Open source record ↗Bus trip updates can provide predictions. O-Train departures remain timetable-only.
Latest source response: 129 records. Checked Oct 10, 2026, 12:15 a.m.
Official notices are shown when the source is usable. Missing intervals, severity, or stop identifiers remain unpublished.
Latest source response: 24 records. Checked Oct 10, 2026, 12:15 a.m.
Open source record ↗Not available
Paths are shown only when the active official timetable publishes station pathways. A parent station or nearby platform does not prove a usable transfer path.
The active official archive omits the pathways file. Checked Oct 8, 2026, 8:31 p.m. This is a source-data gap, not proof that no physical path exists.
Open source recordNot available
OC Transpo does not publish live O-Train vehicle positions or arrival predictions to the feed Otranspo receives.
Capability rule checked Aug 21, 2026.
Each capability has a separate state for each operator. The state uses the latest stored source check. It never turns a missing source into a zero.
Official static GTFS is imported with its checksum and service dates.
Imported schedule checked Oct 9, 2026, 1:03 a.m. Service dates in this source: from Oct 9, 2026 through Nov 9, 2026.
Open source record ↗Bus positions are published. OC Transpo does not publish live O-Train positions.
Latest source response: 238 records. Checked Oct 10, 2026, 12:15 a.m.
Bus trip updates can provide predictions. O-Train departures remain timetable-only.
Latest source response: 129 records. Checked Oct 10, 2026, 12:15 a.m.
Official notices are shown when the source is usable. Missing intervals, severity, or stop identifiers remain unpublished.
Latest source response: 24 records. Checked Oct 10, 2026, 12:15 a.m.
Open source record ↗Paths are shown only when the active official timetable publishes station pathways. A parent station or nearby platform does not prove a usable transfer path.
The active official archive omits the pathways file. Checked Oct 8, 2026, 8:31 p.m. This is a source-data gap, not proof that no physical path exists.
Open source recordCity washrooms, water, park-and-ride, and selected stop records exist. Entrances, pathways, and every amenity placement are not complete.
Current imported evidence: 6,092 records across the named dataset scope. Latest check: Oct 9, 2026, 11:34 p.m.
Open source record ↗Bus arrival evidence is published only for observed service with its sample and date window. Rail reliability is unavailable.
Historical evidence: 6,866,947 settled arrival observations across published route cohorts. Computed Oct 9, 2026, 11:33 p.m.
Open source recordThe 24 official Ottawa ward polygons are imported with source evidence.
The latest stored source check is delayed. Last useful check: Aug 4, 2026, 10:43 a.m.
Open source record ↗The municipal elected-official source is imported, but recipients are disabled when its freshness check fails.
The latest stored source check is delayed. Last useful check: Aug 4, 2026, 7:16 p.m.
Open source record ↗Anonymous reports are accepted. Public aggregates require privacy thresholds and moderation.
Capability rule checked Aug 21, 2026.
OC Transpo does not publish live O-Train vehicle positions or arrival predictions to the feed Otranspo receives.
Capability rule checked Aug 21, 2026.
Official static GTFS is imported with its checksum and service dates.
Imported schedule checked Oct 9, 2026, 1:03 a.m. Service dates in this source: from Oct 7, 2026 through Dec 2, 2026.
Open source record ↗Standard vehicle positions are supported. A missing or stale feed is shown as unavailable, not zero.
Latest source response: 30 records. Checked Oct 10, 2026, 12:15 a.m.
Standard trip updates are supported, but a trip without a usable update stays scheduled-only.
Latest source response: 30 records. Checked Oct 10, 2026, 12:15 a.m.
Standard service alerts are supported. The page names stale or unavailable provider evidence.
The source responded with no records Oct 10, 2026, 12:15 a.m; this does not prove that the service or issue does not exist.
Paths are shown only when the active official timetable publishes station pathways. Proximity and shared names are never substituted for path evidence.
The active official archive omits the pathways file. Checked Oct 8, 2026, 8:31 p.m. This is a source-data gap, not proof that no physical path exists.
Open source recordCommunity-mapped amenities are available with OSM attribution. They are not presented as City-verified.
The latest stored source check is delayed. Last useful check: Aug 13, 2026, 7:04 p.m.
Open source record ↗Reliability is published only for observed routes and days with adequate evidence.
Historical evidence: 2,123,614 settled arrival observations across published route cohorts. Computed Oct 9, 2026, 11:33 p.m.
Open source recordThe 19 official Gatineau electoral-district polygons are imported with source evidence.
The latest stored source check is delayed. Last useful check: Aug 13, 2026, 7:02 p.m.
Open source record ↗District representatives are shown only where the official civic record can support them.
The latest stored source check is delayed. Last useful check: Aug 13, 2026, 7:02 p.m.
Open source record ↗Anonymous reports are accepted. Public aggregates require privacy thresholds and moderation.
Capability rule checked Aug 21, 2026.
Otranspo does not cover a Gatineau rail service or infer train data from another operator.
Capability rule checked Aug 21, 2026.
Capability and source contracts last checked 2026-08-21. Live feed outages are shown on the Status and Alerts pages.
Language coverage and community reviewThese counts describe rows in each active official archive. A zero or omitted file is a source-data fact, not proof that an entrance, pathway, level, or transfer does not exist in the real network.
Each operator keeps its own help, data terms, service dates, civic geography, and correction path.
Ottawa
Gatineau
Otranspo cannot create train locations or predictions that OC Transpo does not publish. You can edit a request, choose an official or custom recipient, and open it in your own email app. Nothing is sent by Otranspo.
OC Transpo does not publish live O-Train positions in the public feed Otranspo can use. You can ask the City to publish them in a stable, reusable format.
This is your message. Edit it before opening your own email app. Otranspo does not send it, track delivery, or speak for you. Write to one relevant recipient; do not use this tool for mass email, harassment, or personal or sensitive information.
