GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Metro Transit - City of Madison

Grade B · 84.5 / 100

Down 0.3 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. 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. Remove retired stops from the export, or add them back to the trips that should serve them.

    Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

    Effort: A review pass in your scheduling software.

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

  3. Remove past service periods the next time you export the feed.

    Some service calendars in the feed have already expired. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Effort: One setting in most export tools.

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

NTD certification readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

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

agency_id and NTD ID: Not aligned. Your feed's agency_id is 1; your National Transit Database ID is 50005. 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 50005 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.

Key facts

Feed URL
http://transitdata.cityofmadison.com/GTFS/mmt_gtfs.zip
Last checked
2026-07-09
Service window
37 days of service data remain. Last service date 2026-08-15.
Feed version
S070_202605050858
State
Wisconsin

Part of the Wisconsin 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.