GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Metro Transit

Grade B · 80.1 / 100

Down 0.4 points since 2026-07-08 (B to B).

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

What changed since the last check

  • Correctness no change
  • Freshness down 1.6
  • Rider experience no change
  • Realtime quality no change

Top three things to fix

  1. 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.

  2. Turn on 'remove unused shapes' (or the like) in your export tool.

    The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.

    Effort: One setting.

  3. Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.

    100 of 243 sampled vehicle positions were far from their assigned route (worst: 11521262 m). A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.

    Effort: A vendor support ticket with the trip ids attached.

    Agencies here usually clear this within about 1 week (based on 31 observed fixes).

NTD certification readiness: Ready

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 48 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is 0, 1, 2, 4, 5, 6, 10, 11; your National Transit Database ID is 50027. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 50027 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

The state transit-data program is MnDOT Transit. Minnesota's statewide transit program and data resources.

Key facts

Feed URL
https://svc.metrotransit.org/mtgtfs/gtfs.zip
Last checked
2026-07-09
Service window
43 days of service data remain. Last service date 2026-08-21.
Feed version
1782920971
State
Minnesota

Part of the Minnesota portfolio: see where this agency sits among the state's feeds before the call.

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