Kansas City Area Transportation Authority (KCATA)

What changed since the last check

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

Fixed since the last check (1 finding):

• Service data runs out in 1 day(s). (scorecard_feed_expiring_soon)

Top three things to fix

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

   Service data ended 0 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

   Effort: Usually one export setting; export on a schedule so it never lapses again.

2. Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. 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.

Ready to send to the agency

Hi Kansas City Area Transportation Authority (KCATA) team, Service data ended 0 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. 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-187/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 11 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Needs attention

Service data runs out in 11 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-11

Service window

Feed has expired. Last service date 2026-07-11.

Feed version

June 2026_20260604