← All agencies

Feed status · checked 2026-08-02

Cincinnati Metro

Based on the feed this agency publishes

Service mode Tram + Bus

82.6 / 100

unchanged since 2026-08-01

Catalogued in Ohio.

Covers 125 days

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 47 minutes ago; last changed 3 days ago.

Measured 4 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 9 snapshots.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool

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.

⏱ Usually one export setting.worth about +8 points in its category

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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

  2. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

  3. Review the flagged fields and fill in the ones your riders would use. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 125 days.
Published accessibility data
Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
One or more realtime feeds were reachable; live-arrival coverage is not known.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness60.5 / 100

The MobilityData validator flagged 9 kinds of issue across 13735 instances (0 error, 13732 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 125 days.

Rider experience85.9 / 100

100% of stops state wheelchair accessibility (2% marked accessible, 98% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility100 / 100

100% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 25 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 10, 11, 16, 20, and more).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 3379 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("3RD ST 508", "3RD ST 640", "3rd ST. WEST OF BRENT SPENCE BRIDGE", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime quality100.0 / 100

Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 3513 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 1 (teal)
  • 10 (teal)
  • 100 (teal)
  • 11 (teal)
  • 12 (yellow)
  • 16 (teal)
  • 17 (orange)
  • 19 (orange)
  • 2 (yellow)
  • 20 (teal)
  • 21 (teal)
  • 22 (yellow)
  • 23X (yellow)
  • 24 (teal)
  • 25 (yellow)
  • 27 (teal)
  • 28 (teal)
  • 29X (yellow)
  • 3X (yellow)
  • 30 (yellow)
  • 31 (teal)
  • 32 (teal)
  • 33 (orange)
  • 36 (teal)
  • 37 (teal)
  • 38 (yellow)
  • 4 (orange)
  • 40 (yellow)
  • 41 (teal)
  • 43 (orange)
  • 46 (teal)
  • 47 (teal)
  • 49 (teal)
  • 5 (teal)
  • 50 (yellow)
  • 51 (orange)
  • 52X (yellow)
  • 53 (teal)
  • 6 (teal)
  • 61 (teal)
  • 64 (teal)
  • 65 (yellow)
  • 67 (teal)
  • 70 (yellow)
  • 71X (yellow)
  • 74X (yellow)
  • 75X (yellow)
  • 77 (teal)
  • 78 (orange)
  • 8 (yellow)
  • 81 (yellow)
  • 82X (yellow)
  • M+ (teal)
Routes in Cincinnati Metro's feed
RouteTypeLine color
1 Mt. AdamsBusteal
10 Erie AvenueBusteal
100 Streetcar - OTR - BanksTram / light railteal
11 Madison RoadBusteal
12 Madisonville CommuterBusyellow
16 Spring Grove / DalyBusteal
17 Hamilton AvenueBusorange
19 Colerain AvenueBusorange
2 Madeira CommuterBusyellow
20 Winton RoadBusteal
21 Harrison AvenueBusteal
22 Glenway / MadisonBusyellow
23X Forest Park ExpressBusyellow
24 MLK / BeechmontBusteal
25 Mt. Lookout CommuterBusyellow
27 Beekman / LinnBusteal
28 East EndBusteal
29X Milford ExpressBusyellow
3X Montgomery ExpressBusyellow
30 Beechmont CommuterBusyellow
31 Taft / McMillanBusteal
32 West 8th StreetBusteal
33 Glenway AvenueBusorange
36 Price Hill / UptownBusteal
37 MLK / Westwood NorthernBusteal
38 Uptown CommuterBusyellow
4 Montgomery RoadBusorange
40 Montana CommuterBusyellow
41 North Bend RoadBusteal
43 Reading RoadBusorange
46 AvondaleBusteal
47 Avondale - OakleyBusteal
49 FairmountBusteal
5 Blue AshBusteal
50 River Road CommuterBusyellow
51 Westwood - AvondaleBusorange
52X Harrison ExpressBusyellow
53 St. Bernard - OakleyBusteal
6 Queen City AvenueBusteal
61 Galbraith RoadBusteal
64 WestwoodBusteal
65 Western HillsBusyellow
67 Kemper RoadBusteal
70 UC ConnectorBusyellow
71X Kings Island ExpressBusyellow
74X Colerain ExpressBusyellow
75X Anderson ExpressBusyellow
77 DelhiBusteal
78 Vine StreetBusorange
8 Blue Ash / Silverton CommuterBusyellow
81 Mt. Washington CommuterBusyellow
82X Eastgate ExpressBusyellow
M+ MetroPlusBusteal
List every stop
  • 1435 E Galbraith Westbound
  • 1438 E Galbraith Eastbound
  • 3RD ST 508
  • 3RD ST 640
  • 3rd ST. WEST OF BRENT SPENCE BRIDGE
  • 3RD ST & EGGLESTON AVE
  • 3RD ST & SMITH ST
  • 3RD ST & SYCAMORE ST
  • 3RD & WALNUT
  • 3RD ST & WALNUT ST
  • 4TH ST & MAIN ST
  • 4TH ST & PIKE ST
  • 4TH ST & PLUM ST
  • 4TH ST & POSTAL AL
  • 4TH ST & RACE ST
  • 4TH ST & SYCAMORE ST
  • 4TH ST & VINE ST
  • 4TH ST & WALNUT ST
  • FIFTH THIRD BANK MADISONVILLE 2
  • FIVE MILE RD & NIMITZVIEW DR
  • FIVE MILE RD & WOODCROFT DR
  • 5TH ST & ELM ST
  • 5TH ST & FOUNTAIN SQUARE
  • 5TH ST & LAWRENCE ST
  • 5TH ST & PIKE ST
  • 5TH ST & SYCAMORE ST
  • 5TH ST & VINE ST
  • 6TH ST & ELM ST
  • 6TH ST & MAIN ST
  • 6TH ST & PLUM ST
  • 6TH ST & RACE ST
  • 6TH ST & RUTH LYONS ALY
  • 6TH ST & SYCAMORE ST
  • 7TH & CENTRAL AVE
  • 7TH ST & PLUM ST
  • 7TH ST & RACE ST
  • 7TH ST & SYCAMORE ST
  • 7TH ST & VINE ST
  • EIGHT MILE RD 1932
  • EIGHT MILE RD & BEECHMONT AVE
  • EIGHT MILE RD & NORTHPORT DR
  • EIGHT MILE RD & RIOVISTA DR
  • EIGHT MILE RD & SHENSTONE DR
  • 8TH ST 4321
  • 8TH ST 4332
  • 8TH ST & ACADEMY AVE
  • 8TH ST & ACADEMY AVE
  • 8TH ST & CHEAPSIDE ST
  • 8TH ST & CLANORA DR
  • 8TH ST & CLANORA DR
  • 8TH ST & DALTON AVE
  • 8TH ST & DALTON AVE
  • 8TH ST & DEPOT ST
  • 8TH ST & DEPOT ST
  • 8TH ST & ELBERON AVE
  • 8TH ST & ELBERON AVE
  • 8TH ST & ENRIGHT AVE
  • 8TH ST & ENRIGHT AVE
  • 8TH ST & FREEMAN AVE
  • 8TH ST & FREEMAN AVE
  • 8TH ST & GREENWICH AVE
  • 8TH ST & GREENWICH AVE
  • 8TH ST & HARRIS AVE
  • 8TH & HARRIS AVE
  • 8TH ST & HERMOSA AVE
  • 8TH ST & HERMOSA AVE
  • 8TH ST & KENNEDY WAY
  • 8TH ST & KIRBERT AVE
  • 8TH ST & KIRBERT AVE
  • 8TH ST & LINN ST
  • 8TH ST & LINN ST
  • 8TH ST & MCLEAN ST
  • 8TH ST & MCPHERSON AVE
  • 8TH ST & MCPHERSON AVE
  • 8TH ST & OVERLOOK AVE
  • 8TH ST & ROSEMONT AVE
  • 8TH ST & ROSEMONT AVE
  • 8TH ST & STATE ST
  • 8TH ST & STATE AVE
  • EIGHT MILE RD & SUMMITRIDGE DR
  • 8TH ST & SUNSET AVE
  • 8TH ST & SUNSET AVE
  • 8TH ST & WALNUT ST
  • 8TH ST & WOODLAWN AVE
  • 8TH ST & WOODLAWN AVE
  • 9TH ST & CENTRAL AVE
  • 9TH ST & CHEAPSIDE ST
  • 9TH ST & PLUM ST
  • 9TH ST & RACE ST
  • 9TH ST & VINE ST
  • 9TH ST & WALNUT ST
  • AIKEN HIGH SCHOOL
  • AIKEN HIGH SCHOOL
  • ALAMO AVE 3325
  • ALBERT AVE & APPLEGATE AVE
  • ANDERSON FERRY RD & CROOKSHANK RD
  • ANDERSON FERRY RD & CROOKSHANK RD
  • ANDERSON FERRY RD & SIDNEY AVE
  • ANDERSON FERRY RD & SIDNEY AVE
  • ANDERSON CENTER STATION P&R
  • ANDERSON CENTER DR AT ANDERSON STATION
  • APPLEGATE AVE & ALBERT ST
  • APPLEGATE AVE & ALTA VISTA AVE
  • APPLEGATE AVE & GLENMORE AVE
  • Appleton Street past Madison Road
  • APPLEGATE AVE & MAYFAIR AVE
  • Appleton Street at Minot Avenue
  • APPLEGATE AVE & ROBB AVE
  • ARBORCREST DR & SORRENTO DR
  • ARBORCREST DR & SORRENTO DR
  • ARLINGTON ST 1350
  • ARLINGTON ST & COLERAIN AVE
  • ARLINGTON ST & SPRING GROVE AVE
  • ART MUSEUM DR & MT ADAMS DR
  • ART MUSEUM DR & MT ADAMS DR
  • ASHTREE DR & FIRTREE CT
  • ASHTREE DR & MONTEREY CT
  • ASHTREE DR & MONTEREY CT
  • AUBURN AVE & BODMANN AVE
  • AUBURN AVE & BODMANN AVE
  • AUBURN AVE & EARNSHAW AVE
  • AUBURN AVE & EARNSHAW AVE
  • AUBURN AVE & MASON ST
  • AUBURN AVE & MCCORMICK PL
  • AUBURN AVE & MCCORMICK PL
  • AUBURN AVE & MCGREGOR AVE
  • AUBURN AVE & MCGREGOR AVE
  • AUBURN AVE & MCMILLAN ST
  • AUBURN AVE & MCMILLAN ST
  • BALTIMORE AVE & BRINKMEIER AVE
  • BALTIMORE AVE & BRINKMEIER AVE
  • BALTIMORE AVE & CARLL ST
  • BALTIMORE AVE & CARLL ST
  • BALTIMORE AVE & MCHENRY AVE
  • BALTIMORE AVE & MERREL AVE
  • BALTIMORE AVE & MERRILL AVE
  • BALTIMORE AVE & PRESIDENT DR
  • BALTIMORE AVE & MCHENRY AVE
  • BALTIMORE AVE & WERON LN
  • BALTIMORE AVE & WERON LN
  • BALTIMORE AVE & WESTWOOD NORTHERN
  • BALTIMORE AVE & WESTWOOD NORTHERN
  • BALTIMORE AVE & YOAST AVE
  • BALTIMORE AVE & YOAST AVE
  • BANK ST 821
  • BANNING RD & BOLEYN DR
  • BANNING RD & BOLEYN DR
  • BANK ST & DALTON AVE
  • BANK ST & DALTON AVE
  • Bank St past Dalton Ave
  • Bank St near Dalton Ave
  • BANK ST & FREEMAN AVE
  • BANK ST & FREEMAN AVE
  • BANK ST & LINN ST
  • BANNING RD & LOCUST VIEW LN
  • BANNING RD & LOCUST VIEW LN
  • BANK ST & PATTERSON ST
  • BANK ST & PATTERSON ST
  • BASSETT RD & HAWTHORNE AVE
  • BEACON RD 1230
  • BEACON ST 1237
  • BEACON RD 1737
  • BEACON ST & BEECHMONT AVE
  • BEACON RD & BEECHMONT AVE
  • BEACON ST & GLADE AVE
  • BEACON RD & GLADE AVE
  • BEACON ST MT WASH REC CENTER
  • BEACON ST & SHERMAN AVE
  • BEACON RD & SHERMAN AVE
  • BEACON RD & SHORT DR
  • BEACON ST & SHORTS DR
  • BEECHMONT AVE 2351
  • BEECHMONT AVE 2352
  • BEECHMONT AVE 2500
  • BEEKMAN ST 3111
  • BEEKMAN ST 3210
  • BEEKMAN ST 3441
  • BEEKMAN ST 3442
  • BEECHMONT AVE 6774
  • BEECHMONT AVE 6775
  • BEECHMONT AVE 6881
  • BEECHMONT AVE 6900
  • BEECHMONT AVE 7729
  • BEECHMONT AVE 7825
  • BEECHMONT AVE & ASBURY RD
  • BEECHMONT AVE & BEACON ST
  • BEECHMONT AVE & BEACON ST
  • BEECHMONT AVE & BEECHMONT CIRCLE
  • BEECHMONT AVE & BELLEMEADE CT
  • BEECHMONT AVE & BELLEMEADE CT
  • BEECHMONT AVE & BONNIE DR
  • BEECHMONT AVE & BONNIE DR
  • BEECHMONT AVE & BRACHMAN AVE
  • BEECHMONT AVE & BRACHMAN AVE
  • BEECHMONT AVE & BURNEY LN
  • BEECHMONT AVE & BURNEY LN
  • BEECHMONT & CAMPUS LN
  • BEECHMONT AVE & CAMPUS LN
  • BEECHMONT AVE & CHURCH PL
  • BEECHMONT AVE & CHURCH PL
  • BEECHMONT AVE & COLLINSDALE AVE
  • BEECHMONT AVE & COLLINSDALE AVE
  • BEECHMONT AVE & CORBLY ST
  • BEECHMONT AVE & CORBLY ST
  • BEECHMONT AVE & CRESTVIEW PL
  • BEEKMAN ST & DREMAN AVE
  • BEEKMAN ST & DREMAN AVE
  • BEEKMAN ST & ELMORE ST
  • BEEKMAN ST & ELMORE ST
  • BEECHMONT AVE & ELSTUN RD
  • BEECHMONT AVE & ELSTUN RD
  • BEECHMONT AVE & FOREST RD
  • BEECHMONT AVE & FOREST RD
  • BEEKMAN ST & HOPPLE ST
  • BEEKMAN ST & HOPPLE ST
  • BEEKMAN ST & KNOX ST
  • BEEKMAN ST & KNOX ST
  • BEECHMONT AVE & MEARS AVE
  • BEEKMAN ST & MILLVALE CT
  • BEEKMAN ST & MILLVALE CT
  • BEEKMAN ST & MOOSEWOOD AVE
  • BEEKMAN ST & MOOSEWOOD AVE
  • BEECHMONT AVE & MORROW ST
  • BEECHMONT AVE & NEW ENGLAND CLUB DR
  • BEECHMONT AVE & NORDICA LN
  • BEECHMONT AVE & NORDICA LN
  • BEECHMONT AVE & PADDISON RD
  • BEECHMONT AVE & PADDISON RD
  • BEEKMAN ST & PULTE ST
  • BEEKMAN ST & PULTE ST
  • BEECHMONT AVE & RANCHVALE DR
  • BEECHMONT AVE & REDFIELD PL
  • BEECHMONT AVE & ROXBURY ST
  • BEECHMONT AVE & SALEM RD
  • BEEKMAN ST & SUTTER AVE
  • BEECHMONT AVE & TALLBERRY DR
  • BEECHMONT AVE & TALLBERRY DR
  • BEECHMONT AVE & TOWNE CENTER WY
  • BEEKMAN ST & TREMONT ST
  • BEECHMONT AVE & VOLL RD
  • BEECHMONT AVE & VOLL RD
  • BEECHMONT AVE & WILMER AVE
  • BEECHMONT AVE & WILARAY TER
  • BEECHMONT AVE & WILARAY TER
  • BEECHMONT AVE & WITT RD
  • BEEKMAN ST & YONKERS AVE
  • BEEKMAN ST & YONKERS AVE
  • BELMONT AVE & BLUESPRUCE LN
  • BELMONT AVE & BLUESPRUCE LN
  • BELMONT AVE & MONTICELLO AVE
  • and 3263 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — unchanged since 2026-08-01.

2026-07-25: 70.02026-07-30: 82.62026-08-01: 82.62026-08-02: 82.6
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2570.0 first check
2026-07-3082.6 up 12.6
2026-08-0182.6 no change
2026-08-0282.6 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality no change

What changed in this feed

Overall grade and score held steady since 2026-08-01.

Same feed file as 2026-08-01; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

What changed over time

On 2026-07-25 this feed started at grade D. On 2026-07-30 the grade moved from D to B. As of 2026-08-02 it holds grade B.

A plain-language history of this feed, newest first.

  • 2026-07-30 Grade went D to B, freshness rose 65 points.

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Warning10335 instances

    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.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3329 instances

    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.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning56 instances

    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.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning8 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3 instances

    Some stops sit far from the route line, going by the feed's own distance values.

    Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.

    Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

    Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    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.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info3311 instances

    About 3311 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info1 instance

    Future calendar (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    Future feed (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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 your 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.
shapes.txt covers your trips Ready
All 10899 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Awarded

This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.

GTFS conformance mark for Cincinnati Metro

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 125 days.
Accessible Met
States wheelchair access on 100% of stops and 100% of trips.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Realtime reliability

The realtime feed responded on 92.5% of 200 checks over the last 34 days, with 14s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Clears the Google and Apple Maps four-week coverage bar. This feed has 125 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 60 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 100 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 86 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Cincinnati Metro GTFS data quality grade: B

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/cincinnati-metro/2026-08-02.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-02. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.