GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-19

Oakville Transit

Grade D · 64.5 / 100

First check for this agency, so there is no trend yet.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

No category changes since the last check.

Top three things to fix

  1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    1124 of 1124 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Effort: A column in stops.txt; your scheduling software likely has it.

  2. Add feed_info.txt with feed_start_date and feed_end_date to your export.

    feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Effort: Two fields, set once in export settings.

  3. Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Missing timepoint value (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

Key facts

Feed URL
https://www.arcgis.com/sharing/rest/content/items/d78a1c1ad6a940009de8b68839a8f606/data
Last checked
2026-07-19
Service window
48 days of service data remain. Last service date 2026-09-05.
Location
Ontario, Canada

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.2, validator 8.0.1.