GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-01

Metro Transit

Grade C · 79.3 / 100

Up 2.3 points since 2026-07-31 (C to C).

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 up 0.4
  • Freshness up 10.0
  • Rider experience no change
  • Realtime quality up 0.5

Top three things to fix

  1. Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

    The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

    Effort: Usually a vendor support ticket.

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

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
The trip updates realtime feed failed during sampling.
Next action
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
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

NTD GTFS readiness: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make 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 provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Different (allowed). 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. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 0, 1, 2, 4, 5, 6, 10, 11 to NTD ID 50027, and keep the feed value stable. Do not change it solely to make the two values equal.

The bar this score answers to

A local transit-data support resource 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-08-01
Service window
48 days of service data remain. Last service date 2026-09-18.
Feed version
1785337767
Location
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.3, validator 8.0.1.