Call-prep brief · checked 2026-08-02

Cincinnati Metro

Grade B · 82.6 / 100

Unchanged since 2026-08-01.

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

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Effort: Usually one export setting.
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.
Review the flagged fields and fill in the ones your riders would use.
Some files leave out fields that GTFS asks for but does not require. Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Effort: A field at a time; not urgent.

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 route lines list the same point twice in a row.
Next action: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
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: Cincinnati Metro
Finding: equal_shape_distance_same_coordinates
Feed evidence: Some route lines list the same point twice in a row.
Why it matters: Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Requested change: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
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/cincinnati-metro/?finding=equal_shape_distance_same_coordinates#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 125 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 METRO; your National Transit Database ID is 50012. 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 METRO to NTD ID 50012, and keep the feed value stable. Do not change it solely to make the two values equal.

Key facts

Feed URL: https://www.go-metro.com/uploads/GTFS/google_transit_info.zip
Last checked: 2026-08-02
Service window: 125 days of service data remain. Last service date 2026-12-05.
Feed version: gtfs_20260816-20261205_20260729
Location: Ohio

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