Feed status · checked 2026-08-01
Central Ohio Transit Authority (COTA)
Based on the feed this agency publishes
Service mode Bus
down 0.3 since 2026-07-31
Catalogued in Ohio.
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 5 hours ago; last changed 32 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
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
2949 of 2949 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
5435 of 5435 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.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
- 2949 of 2949 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 5435 of 5435 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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. Self-check a feed before you publish.
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. Self-check a feed before you publish.
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 36 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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
The MobilityData validator flagged 5 kinds of issue across 8516 instances (0 error, 8516 warning, 0 informational).
Service data covers the next 36 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
2887 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("HANSON ST & E MAIN ST", "W MOUND ST & S WAYNE AVE", "MORSE CROSSING & EASTON WAY", 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.
Fares are applied to trips.
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 2949 stops.
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 (red)
- 2 (red)
- 3 (black)
- 4 (black)
- 5 (black)
- 6 (red)
- 7 (red)
- 8 (red)
- 9 (black)
- 10 (red)
- 11 (black)
- 12 (black)
- 21 (black)
- 22 (black)
- 23 (red)
- 24 (black)
- 25 (black)
- 31 (black)
- 32 (black)
- 33 (black)
- 34 (red)
- 35 (black)
- 41 (green)
- 42 (green)
- 43 (green)
- 44 (green)
- 45 (green)
- 46 (green)
- 51 (green)
- 52 (green)
- 61 (green)
- 71 (green)
- 72 (green)
- 73 (green)
- 74 (green)
- 75 (green)
- CMAX (red)
- 102 (black)
- ZOO (black)
| Route | Type | Line color |
|---|---|---|
| 1 KENNY/LIVINGSTON | Bus | red |
| 2 E MAIN/N HIGH | Bus | red |
| 3 NORTHWEST/HARRISBURG | Bus | black |
| 4 INDIANOLA/LOCKBOURNE | Bus | black |
| 5 W 5TH AVE/REFUGEE | Bus | black |
| 6 SULLIVANT | Bus | red |
| 7 MT VERNON | Bus | red |
| 8 KARL/S HIGH/PARSONS | Bus | red |
| 9 W MOUND/BRENTNELL | Bus | black |
| 10 E BROAD/W BROAD | Bus | red |
| 11 BRYDEN/MAIZE | Bus | black |
| 12 MCKINLEY/FIELDS | Bus | black |
| 21 HILLIARD ROME | Bus | black |
| 22 OSU-RICKENBACKER | Bus | black |
| 23 JAMES-STELZER | Bus | red |
| 24 HAMILTON RD | Bus | black |
| 25 BRICE | Bus | black |
| 31 HUDSON | Bus | black |
| 32 N BROADWAY | Bus | black |
| 33 HENDERSON | Bus | black |
| 34 MORSE | Bus | red |
| 35 DUBLIN-GRANVILLE | Bus | black |
| 41 CROSSWOODS-POLARIS | Bus | green |
| 42 SHARON WOODS | Bus | green |
| 43 WESTERVILLE | Bus | green |
| 44 EASTON | Bus | green |
| 45 NEW ALBANY | Bus | green |
| 46 GAHANNA | Bus | green |
| 51 REYNOLDSBURG | Bus | green |
| 52 CANAL WINCHESTER | Bus | green |
| 61 GROVE CITY | Bus | green |
| 71 HILLIARD | Bus | green |
| 72 TUTTLE | Bus | green |
| 73 DUBLIN | Bus | green |
| 74 SMOKY ROW | Bus | green |
| 75 ARLINGTON/1ST AVE | Bus | green |
| CMAX | Bus | red |
| 102 POLARIS PKWY/N HIGH | Bus | black |
| ZOO COLUMBUS ZOO | Bus | black |
| AirConnect COTA AirConnect | Bus | black (no shape in feed) |
| 201 SMARTRIDE NEW ALBANY - RED | Bus | red (no shape in feed) |
| 202 SMARTRIDE NEW ALBANY - BLUE | Bus | black (no shape in feed) |
List every stop
- E 11TH AVE & N 4TH ST
- E 11TH AVE & N 4TH ST
- E 11TH AVE & DAUGHERTY AVE
- E 11TH AVE & DAUGHERTY AVE
- E 11TH AVE & ESSEX AVE
- E 11TH AVE & ESSEX AVE
- E 11TH AVE & N GRANT AVE
- E 11TH AVE & N GRANT AVE
- E 11TH AVE & N HIGH ST
- E 11TH AVE & N HIGH ST
- E 11TH AVE & INDIANOLA AVE
- E 11TH AVE & INDIANOLA AVE
- E 11TH AVE & JEFFERSON AVE
- E 11TH AVE & JEFFERSON AVE
- W 12TH AVE & N HIGH ST
- 1333 FIELDS AVE
- 1333 FIELDS AVE
- 1374 POLARIS PARKWAY
- OPPOSITE 1411 S HAMILTON RD
- 1443 GEORGESVILLE RD
- 1527 LEONARD AVE
- STATE RTE 161 & AMBLESIDE DR
- STATE RTE 161 AND BEECHCROFT
- STATE RTE 161 AND BEECHCROFT RD
- STATE RTE 161 AND CLEVELAND AVE
- STATE ROUTE 161 & FOREST HILLS BLVD
- STATE ROUTE 161 & FOREST HILLS BLVD
- STATE RTE 161 & KARL RD
- STATE RTE 161 & KARL RD
- STATE RTE 161 AND MAPLE CANYON AVE
- STATE RTE 161 AND MAPLE CANYON AVE
- STATE ROUTE 161 & OAK KNOLL DR
- STATE ROUTE 161 & NORTHERN WOODS LN
- STATE RTE 161 AND PARKVILLE ST
- STATE RTE 161 N SVC RD & PONDEROSA
- SR 161 SVC RD & PONDEROSA
- STATE RTE 161 & SATINWOOD DR
- STATE RTE 161 AND SHARON WOODS BLVD
- STATE RTE 161 AND SPRING RUN DR
- STATE RTE 161 AND TAMARACK BLVD
- 1670 HARRISBURG PIKE
- 1770 HILLIARD ROME RD
- 1785 HILLIARD ROME RD
- E 17TH AVE & CLEVELAND AVE
- E 17TH AVE & HAMILTON AVE
- 1800 WATKINS RD
- 1800 WATKINS RD
- 181 W BRIDGE ST
- W 1ST AVE & ASHLAND AVE
- W 1ST AVE & AVONDALE AVE
- W 1ST AVE & AVONDALE AVE
- W 1ST AVE & ELMWOOD AVE
- W 1ST AVE & FAIRVIEW AVE
- W 1ST AVE & GLENDALE AVE
- W 1ST AVE & GLENN AVE
- W 1ST AVE & GRANDVIEW AVE
- W 1ST AVE & LINCOLN RD
- W 1ST AVE & NORTHWEST BLVD
- W 1ST AVE & OAKLAND AVE
- W 1ST AVE & OXLEY RD
- W 1ST AVE & OXLEY RD
- W 1ST AVE & VIRGINIA AVE
- W 1ST AVE & VIRGINIA AVE
- W 1ST AVE & WESTWOOD AVE
- W 1ST AVE & WYANDOTTE RD
- 2056 WATKINS RD
- 209 HIGHFIELD DR
- 2100 TREMONT CENTER
- 2197 WATKINS RD
- 2200 OLENTANGY RIVER RD
- 2425 BETHEL RD
- 298 HAMILTON RD
- 2997 S HIGH ST
- 300 HILLIARD-ROME RD
- 3158 AGLER RD
- 3243 ALLEGHENY AVE
- 346 HUTCHINSON AVE
- 3990 E FIFTH AVE
- S 3RD ST & E BROAD ST
- W 3RD AVE & CAMBRIDGE BLVD
- W 3RD AVE & CAMBRIDGE BLVD
- W 3RD AVE & EDGEHILL RD
- N 3RD ST & E GAY ST
- S 3RD ST & E MAIN ST
- W 3RD AVE & MEADOW RD
- W 3RD AVE & NORTON AVE
- W 3RD AVE & NORTHWEST BLVD
- W 3RD AVE & OXLEY RD
- W 3RD AVE & OXLEY RD
- W 3RD AVE & PARKWAY DR N
- S 3RD ST & E TOWN ST
- 4018 E FIFTH AVE
- 40 JAMES RD
- E LIVINGSTON & SOUTH HAMILTON RD
- 44 HUTCHINSON AVE
- 4875 SINCLAIR RD
- 4875 SINCLAIR RD
- N 4TH ST & E 15TH AVE
- N 4TH ST & E 18TH AVE
- N 4TH ST & E 2ND AVE
- N 4TH ST & E 5TH AVE
- N 4TH ST & E 7TH AVE
- 803 N 4TH ST
- N 4TH ST & E 9TH AVE
- 4TH ST & ALDEN AVE
- N 4TH ST & E GAY ST
- S 4TH ST & E CAPITAL ST
- N 4TH ST & CHITTENDEN AVE
- N 4TH ST & CLINTON ST
- N 4TH ST & DETROIT AVE
- S 4TH ST & E INNIS AVE
- S 4TH ST & E JENKINS AVE
- N 4TH ST & E LANE AVE
- N 4TH ST & LINCOLN ST
- S 4TH ST & E MARKISON AVE
- N 4TH ST & MAYNARD AVE
- S 4TH ST & REEB AVE
- S 4TH ST & SOUTHWOOD AVE
- N 4TH ST & E SPRING ST
- S 4TH ST & E TOWN ST
- S 4TH ST & E WELCH AVE
- S 4TH ST & E WOODROW AVE
- S 4TH ST & E WOODROW AVE
- 500 S CLEVELAND AVE
- 500 N NELSON RD
- 5054 PARKCENTER AVE
- 5139 PARKCENTER AVE
- 5275 GENDER RD
- 5550 BRITTON PKWY
- 5677 ALSHIRE RD
- E 5TH AVE & N 20TH ST
- E 5TH AVE & N 20TH ST
- 2200 W 5TH AVE
- 2200 W 5TH AVE
- E 5TH AVE & N 23RD ST
- 3706 E 5TH AVE
- 3925 E 5TH AVE
- 4301 E 5TH AVE
- 4301 E 5TH AVE
- 4569 E 5TH AVE
- 4700 E 5TH AVE
- 4700 E 5TH AVE
- 4800 E 5TH AVE
- E 5TH AVE & N 4TH ST
- E 5TH AVE & N 4TH ST
- E 5TH AVE & N 6TH ST
- E 5TH AVE & E 7TH AVE
- E 5TH AVE & E 7TH AVE
- E 5TH AVE & ALTON AVE
- E 5TH AVE & ALTON AVE
- W 5TH AVE & ARLINGTON AVE
- W 5TH AVE & ARLINGTON AVE
- W 5TH AVE & ASHLAND AVE
- W 5TH AVE & ASHLAND AVE
- E 5TH AVE & BASSETT AVE
- E 5TH AVE & BASSETT AVE
- W 5TH AVE & CAMBRIDGE BLVD
- W 5TH AVE & CAMBRIDGE BLVD
- E 5TH AVE & N CASSADY AVE
- E 5TH AVE & N CASSADY AVE
- E 5TH AVE & CLEVELAND AVE
- E 5TH AVE & CLEVELAND AVE
- W 5TH AVE & DENNISON AVE
- W 5TH AVE & DENNISON AVE
- W 5TH AVE & DOTEN AVE
- W 5TH AVE & DOTEN AVE
- W 5TH AVE & EASTVIEW AVE
- W 5TH AVE & EDGEHILL RD
- W 5TH AVE & EDGEHILL RD
- W 5TH AVE & FAIRVIEW AVE
- W 5TH AVE & FAIRVIEW AVE
- E 5TH AVE & FIELDS AVE
- E 5TH AVE & N GRANT AVE
- W 5TH AVE & GRANDVIEW AVE
- W 5TH AVE & GRANDVIEW AVE
- E 5TH AVE & N HAMILTON RD
- W 5TH AVE & HESS ST
- W 5TH AVE & HIGHLAND ST
- W 5TH AVE & N HIGH ST
- W 5TH AVE & N HIGH ST
- W 5TH AVE & HIGHLAND ST
- W 5TH AVE & HOLLY AVE
- E 5TH AVE & N JAMES RD
- E 5TH AVE & N JAMES RD
- E 5TH AVE & JOYCE AVE
- W 5TH AVE & KENNY RD
- E 5TH AVE & KRUMM AVE
- E 5TH AVE & KRUMM AVE
- W 5TH AVE & LAKE SHORE DR
- W 5TH AVE & LAKE SHORE DR
- E 5TH AVE & LEONARD AVE
- W 5TH AVE & LOWER CHELSEA RD
- W 5TH AVE & MICHIGAN AVE
- W 5TH AVE & MICHIGAN AVE
- W 5TH AVE & NEIL AVE
- W 5TH AVE & NEIL AVE
- E 5TH AVE & NORTHVIEW AVE
- W 5TH AVE & NORTHWEST BLVD
- W 5TH AVE & NORTHWEST BLVD
- E 5TH AVE & NORTHVIEW AVE
- W 5TH AVE & OLENTANGY RIVER RD
- W 5TH AVE & OLENTANGY RIVER RD
- W 5TH AVE & PERRY ST
- W 5TH AVE & PERRY ST
- E 5TH AVE & PARKWOOD AVE
- E 5TH AVE & RARIG AVE
- E 5TH AVE & RARIG AVE
- W 5TH AVE & SEAPORT DR
- W 5TH AVE & RUNAWAY BAY DR
- W 5TH AVE & RUNAWAY BAY DR
- E 5TH AVE & SAINT CLAIR AVE
- E 5TH AVE & SAINT CLAIR AVE
- W 5TH AVE & SEAPORT
- E 5TH AVE & STERLING AVE
- E 5TH AVE & STERLING AVE
- E 5TH AVE & TAYLOR AVE
- E 5TH AVE & TAYLOR AVE
- W 5TH AVE & TISDALE
- E 5TH AVE & WALTERS ST
- E 5TH AVE & WALTERS ST
- W 5TH AVE & WESTWOOD AVE
- W 5TH AVE & WESTWOOD AVE
- W 5TH AVE & WYANDOTTE RD
- W 5TH AVE & WYANDOTTE RD
- E 5TH AVE & N YEARLING RD
- E 5TH AVE & N YEARLING RD
- 6175 SAWMILL RD
- 6200 SAWMILL RD
- 6340 PRENTISS SCHOOL DR
- 790 SCIENCE BLVD
- 791 SCIENCE BLVD
- E 7TH AVE & STELZER RD
- 80 W BRIDGE ST
- W 9TH AVE & MEDICAL CTR DR
- AFRICA RD & POLARIS PKWY
- 3433 AGLER RD
- 3433 AGLER RD
- 540 AGLER RD
- AGLER RD & ASHPOINT ST
- AGLER RD & ASHPOINT ST
- AGLER RD & BRIDGEWALK ST
- AGLER RD & BRIDGEWALK ST
- AGLER RD & CLUB HOUSE DR
- AGLER RD & CLUB HOUSE DR
- AGLER RD & CORBAN COMMONS DR
- AGLER RD & GATEWOOD RD
- AGLER RD & N CASSADY AVE
- AGLER RD & GAHANNA PARK AND RIDE
- AGLER RD & LINCOLNSHIRE RD
- AGLER RD & PENDLETON PL
- and 2699 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.3 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 68.9 | first check |
| 2026-07-30 | 67.3 | down 1.6 |
| 2026-07-31 | 66.9 | down 0.4 |
| 2026-08-01 | 66.6 | down 0.3 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
- Realtime quality no change
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning8411 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)
- Warning5435 instances
5435 of 5435 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2949 instances
2949 of 2949 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning102 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 streets or point riders to the wrong corner.
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
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Warning1 instance
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2920 instances
About 2920 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
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · 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 36 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 COTA; your National Transit Database ID is 50016. 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 COTA to NTD ID 50016, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 5435 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 Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 36 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
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 100.0% of 200 checks over the last 34 days, with 12s 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 35 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 72 / 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 60 / 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 38 / 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.
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/central-ohio-transit-authority-cota/2026-08-01.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-01. 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.