GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-19

Union Pearson Express (UP Express)

Grade B · 83.6 / 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. Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

  2. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

    The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Effort: A small file for most flat-fare systems.

  3. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.

    Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.

    Effort: Usually an export-tool fix, not hand editing.

Key facts

Feed URL
https://assets.metrolinx.com/raw/upload/Documents/Metrolinx/Open%20Data/UP-GTFS.zip
Last checked
2026-07-19
Service window
168 days of service data remain. Last service date 2027-01-03.
Feed version
20260707085359
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.