GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-20

GO Transit (Metrolinx)

Grade B · 83.9 / 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. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

    Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Effort: Often a bulk fix in your scheduling software.

  2. Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.

    Some stops sit far from the route line they belong to. Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.

    Effort: A few minutes per flagged stop.

  3. Add feed_contact_email or feed_contact_url to feed_info.txt.

    feed_info.txt lists no contact email and no contact URL. Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Effort: One field, set once in export settings.

Key facts

Feed URL
https://assets.metrolinx.com/raw/upload/Documents/Metrolinx/Open%20Data/GO-GTFS.zip
Last checked
2026-07-20
Service window
46 days of service data remain. Last service date 2026-09-04.
Feed version
20260716095607
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.