Main findings
Feeds by primary province / territory
Grouping uses data_sources.csv. A primary province is not a complete service-area boundary. Blank values are shown as interregional / unspecified.
Largest feeds by route records
Record counts reflect how providers encode branches and directions. They are not ridership or service-quality rankings.
Explore all feeds
Open a feed for its full date timeline, route and date filters, weekday/month comparisons, hourly departures, duration distributions, stop plot, calendar changes and quality checks. Reports are self-contained HTML files and work offline.
| Feed / detailed report | Province | Routes | Stop records | Templates | Analysis interval | Reference date | Departure equivalents* | Supplied errors |
|---|
*Reference dates may differ; this column is not a like-for-like national ranking. Counts include nominal departure slots where exact_times=0. Each detailed report separates exact and nominal counts.
Date ranges need interpretation
123 of 138 feeds encode departures on 27 January 2025. The other 15 require a different reference date; some supplied schedules are from earlier years. This collection is not a synchronized snapshot of all Canadian service on one date.
Each report prioritizes explicit feed_info.txt start/end dates. When absent, bounds are inferred from weekly-active calendar rows and added dates for services referenced by trips. All-zero placeholder calendar ranges do not establish continuous service. Dates outside a feed's interval are unknown. No source data have been updated from the internet.
A future end date is a field in an old schedule snapshot; it does not confirm current or future routes. In particular, multi-year horizons must not be interpreted as a continuous archive of observed vehicle movements.
Quality and geographic data
The supplied validator notices are retained separately from the new structural checks in each report. No source errors were repaired. The GeoPackage uses EPSG:3347 and contains stops and trip-linked line features; its shapes layer must not be counted as unique transit routes. The accompanying methodology says geometry was simplified with a 250-metre tolerance.
The original metadata report says 139 feeds. This local corrected package contains 138 GTFS archives; the May correction notice removes the rider_express metadata row because that feed was not in the release. The file inventory, rather than the older report total, determines this analysis.
Download analysis tables
- Feed summary CSV — counts, date bounds and reference-day metrics.
- Daily service timeline CSV — every analyzed date for each feed, with exact and nominal counts separated.
- Route summary CSV — route attributes and reference-day service/duration metrics.
Detailed reports also export route-filtered timelines and date-specific route tables. Keep the overview and agency_reports folder together when sharing this report collection.
Methods and provenance
All supplied GTFS ZIPs are read once as separate namespaces. Extracted ZIPs are analyzed; the outer distribution archive is not counted again. Service calendars and exceptions are evaluated daily. Frequency windows use start-inclusive/end-exclusive intervals: exact_times=1 yields scheduled starts; exact_times=0 or blank yields nominal slots only. Stop-time templates for frequency trips are not counted as additional fixed trips. Trip durations are first departure to final arrival, with missing or negative durations excluded.
Initial inspection uses 27 January 2025 when that feed has service. Otherwise it uses the earliest date with maximum encoded departure equivalents. Long intervals open at a 61-day window around that inspection date; “Full horizon” reveals all analyzed dates. Statistical summaries always describe their visible range. Route counts, stop records and trip templates are not fleet counts, actual journeys, or unique national infrastructure.
Source: Statistics Canada, Canadian Public Transit Network Database (2025), released January 31, 2025; correction May 7, 2025. Local metadata: Metadata_Report_Canadian_Public_Transit_Network.pdf, data_sources.csv, validation_summary.csv and corrections_details_may_2025.txt. Provider attribution and archive SHA-256 fingerprints are included in each detailed report.
Technical reference: GTFS Schedule specification. These outputs do not establish historical GPS positions, service adherence, ridership or present-day availability.