Kansas City Area Transportation Authority (KCATA)

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 2 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

   Agencies here usually clear this within about 1 week (based on 61 observed fixes).

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   2293 of 2293 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.

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

   5901 of 5901 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

Ready to send to the agency

Hi Kansas City Area Transportation Authority (KCATA) team, Service data runs out in 2 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/

Copy this note from the full scorecard.

NTD certification readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 10 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Needs attention

Service data runs out in 10 days; renew before you certify.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

http://www.kc-metro.com/gtf/google_transit.zip

Last checked

2026-07-09

Service window

2 days of service data remain. Last service date 2026-07-11.

Feed version

June 2026_20260630

State

Missouri