Call-prep brief · checked 2026-08-23

Metro Transit - City of Madison

Grade A · 92.5 / 100

Unchanged since 2026-08-22.

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 no change
Rider experience no change
Realtime quality no change

Top three things to fix

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.
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.
Trim past service periods the next time you export.
Many of the feed's trips don't run at all in the next 7 days. It usually means old service periods are still in the export, making the feed bigger and harder to check.
Effort: One setting in most export tools.

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

Agency: Metro Transit - City of Madison
Finding: mixed_case_recommended_field
Feed evidence: Some rider-facing names are in ALL CAPS or all lowercase.
Why it matters: ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/metro-transit-city-of-madison/?finding=mixed_case_recommended_field#finding-handoff

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 104 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 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. 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 1 to NTD ID 50005, and keep the feed value stable. Do not change it solely to make the two values equal.

Key facts

Feed URL: http://transitdata.cityofmadison.com/GTFS/mmt_gtfs.zip
Last checked: 2026-08-23
Service window: 104 days of service data remain. Last service date 2026-12-05.
Feed version: S072_202608111342
Location: 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.3, validator 8.0.1.