Board packet · transit data quality · checked 2026-10-07
Cincinnati Metro
Grade B · 82.3 / 100
Down 0.3 points since 2026-10-06 (B to B).
What this grade measures
The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.
Progress this period
Since the previous compatible check, 1 finding was no longer reported:
- 1 of 116 trips scheduled during the sampling window had no live predictions.
This records feed state, not who made a change or why.
What needs attention next
Three improvements, in priority order, each sized so the board can see what it is approving:
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Estimated 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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Estimated 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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Estimated effort: A field at a time; not urgent.
Riders and need behind these fixes
- No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
- Ohio as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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
- 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
- Feed evidence
- Some files leave out fields that GTFS asks for but does not require.
- Next action
- Review the flagged fields and fill in the ones your riders would use.
- 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
Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/cincinnati-metro/. Rubric v1.4, validator 8.0.1.