← Back to the full scorecard

Board packet · transit data quality · checked 2026-09-02

GO Transit (Metrolinx)

Grade B · 87.2 / 100

Unchanged since 2026-09-01.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

  1. Give each route a distinct short or long name.

    Two or more routes share the same name. Riders can't tell the routes apart in apps.

    Estimated effort: One field per route.

  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.

    Estimated effort: A few minutes per flagged stop.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Some rider-facing names are in ALL CAPS or all lowercase.
Next action
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/go-transit-metrolinx/. Rubric v1.3, validator 8.0.1.