← All agencies

Feed status · checked 2026-10-07

Kansas City Area Transportation Authority (KCATA)

Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified

Service mode Tram + Bus

FDCBA

25.5 / 100

unchanged since 2026-10-06

Cataloged in Missouri.

Feed expiredAccessibility gapsRealtime access needed

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.4, validator 8.0.1.

Checked for changes 39 minutes ago; last changed 39 minutes ago.

Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.

How we measured this

Confidence in this measurement: provisional.

Realtime quality was not measured this run. It does not count against the grade.
The configured feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead. Publisher ownership of the configured URL is not verified.

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

About this feed

Kansas City Area Transportation Authority (KCATA)’s published feed lists 30 routes (tram / light rail and bus), 5,377 scheduled trips and 2,300 stops. Its service dates run from 2026-07-12 through 2026-10-03. The published file last changed on 2026-08-06.

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool

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

This one is about the feed as a whole, so there is no share of it to count.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

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

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

Fixing this covers all 2,300 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

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

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

Fixing this covers all 5,377 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Riders and need behind these fixes

This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
Missouri 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.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
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

Agency: Kansas City Area Transportation Authority (KCATA)
Finding: scorecard_feed_expired
Feed evidence: Service data ended 4 day(s) ago.
Why it matters: When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.
Requested change: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/?finding=scorecard_feed_expired#finding-handoff

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.

Fix 01 · Read the fix guide for scorecard_feed_expired
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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 was 4 days ago.
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: No fare information is published in the feed.
Realtime information: Realtime-feed availability and live-arrival coverage are not known from this scorecard.

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.

Hi,

Our GTFS feed (Kansas City Area Transportation Authority (KCATA)) scored F (25.5 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
   What: Service data ended 4 day(s) ago.
   Finding code: scorecard_feed_expired
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expired/

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 2300 of 2300 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 5377 of 5377 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Hi Kansas City Area Transportation Authority (KCATA) team,

Service data ended 4 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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. Set feed_end_date in feed_info.txt 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/

Score by category

Correctness42.0 / 100

The MobilityData validator flagged 11 kinds of issue across 3851 instances (0 error, 3851 warning, 0 informational).

Freshness0.0 / 100

Service data ended 4 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience22.8 / 100

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 not published.

Accessibility0 / 100

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

Realtime qualityNot yet measured

This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.

Routes and stops

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

This feed has 2300 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.

101 (white)
107 (white)
11 (white)
12 (white)
18 (white)
TMAX (white)
201 (white)
21 (white)
210 (purple)
229 (white)
23 (green)
238 (white)
24 (white)
25 (white)
27 (white)
28 (white)
PMAX (white)
31 (white)
35 (white)
39 (white)
47 (white)
50 (green)
550 (white)
57 (white)
STCR (teal)
63 (white)
71 (white)
75 (white)
85 (white)
9 (white)

Routes in Kansas City Area Transportation Authority (KCATA)'s feed
Route	Type	Line color
101 State	Bus	white
107 7th Street - Parallel	Bus	white
11 Northeast-Westside	Bus	white
12 12th Street	Bus	white
18 Indiana	Bus	white
TMAX Troost MAX	Bus	white
201 North Oak	Bus	white
21 Clevland-Antioch	Bus	white
210 Front Street	Bus	purple
229 Boardwalk-KCI	Bus	white
23 23rd Street	Bus	green
238 Meadowbrook	Bus	white
24 Independence	Bus	white
25 Troost	Bus	white
27 27th Street	Bus	white
28 Blue Ridge	Bus	white
PMAX Prospect MAX	Bus	white
31 31st Street	Bus	white
35 35th Street	Bus	white
39 39th Street	Bus	white
47 Martin Luther King Jr.	Bus	white
50 Brookside-Main	Bus	green
550 Lee's Summit Express	Bus	white
57 Wornall	Bus	white
STCR KC Streetcar	Tram / light rail	teal
63 63rd Street	Bus	white
71 Prospect	Bus	white
75 75th Street	Bus	white
85 Paseo	Bus	white
9 9th Street	Bus	white

List every stop

ON GARDNER AVE AT N CENTURY AVE
ON NORFLEET AT NE 40TH SB
ON 11TH AT CENTRAL WESTBOUND
ON 6TH AT ANN SOUTHBOUND
ON MINNESOTA AVE AT 7TH STREET EB
ON MINNESOTA AT 10TH WESTBOUND
ON MINNESOTA AT 11TH WESTBOUND
ON STATE AT 41ST TERRACE WESTBOUND
ON 47TH AT MINNESOTA SB
ON STATE AVE AT 32ND STREET EB
ON MINNESOTA AVE AT 7TH STREET WB
REMOVEJAN2019 ON STATE AT 38TH EASTBOUND
ON MINNESOTA AT 10TH EASTBOUND
ON MINNESOTA AT 9TH EASTBOUND
ON MINNESOTA AT 8TH EASTBOUND
ON BROADWAY AT 8TH SOUTHBOUND
ON 12TH AT WASHINGTON WESTBOUND
ON STATE AVE AT CAMPUS DR WB
ON STATE AVE AT CAMPUS DR EB
ON MINNESOTA AT 12TH ST WB
ON MINNESOTA AT 13TH ST WB
ON MINNESOTA AT 14TH WB
ON MINNESOTA AT 16TH ST WB
ON MINNESOTA AT 18TH ST WB
ON HOEL PKWY AT STATE AVE NB
ON MINNESOTA AT 18TH ST EB
ON MINNESOTA AT 16TH ST EB
ON MINNESOTA AT 14TH ST EB
ON MINNESOTA AT 13TH ST EB
ON MINNESOTA AT 12TH ST EB
ON MINNESOTA AT 11TH ST EB
ON STATE AVE AT 94TH ST EB
ON VILLAGE WEST PKWY AT SUNFLOWER LANE SEB
ON VILLAGE WEST PKWY AT PRAIRIE CROSSING SEB
ON VILLAGE WEST PKWY AT CABELA DR SB
ON STATE AVE AT 92ND EB
ON STATE AVE AT 86TH ST EB
ON ARMSTRONG AT 5TH WB
ON STATE AVE AT 82ND EB
ON VILLAGE PKWY AT PRAIRIE CROSSING WB
ON VILLAGE WEST AT SUNFLOWER LANE NWB
ON MINNESOTA AT 5TH EB
ON STATE AVE AT WASHINGTON EB
ON STATE AVE AT HOEL PKWY EB
ON ARMSTRONG AT 4TH WESTBOUND
ON STATE AVE AT 24TH WESTBOUND
ON STATE AVE AT 86TH WESTBOUND
ON STATE AVE AT 89TH WESTBOUND
ON STATE AVE AT 94TH WESTBOUND
ON STATE AVE AT 24TH EB
ON STATE AVE AT WASHINGTON WB
ON STATE AVE AT 32ND ST WB
ON 47TH ST AT MINNESOTA AVE NB
ON STATE AVE AT 95TH WESTBOUND
ON STATE AVE AT 89TH EB
ON 11TH AT LYDIA WESTBOUND NEARSIDE
ON STATE AT 29TH ST WESTBOUND
ON STATE AVE AT 37TH ST EASTBOUND
ON STATE AVE AT 34TH ST EASTBOUND
ON STATE AVE AT 31ST EASTBOUND
ON STATE AVE AT 29TH ST EASTBOUND
ON STATE AVE AT 31ST WESTBOUND
ON STATE AVE AT 34TH WESTBOUND
ON STATE AVE AT 37TH WESTBOUND
ON JAMES ST AT RIVERVIEW AVE SB
ON JAMES AT LYON EASTBOUND
ON W 9TH ST AT LYON AVE WB
ON JAMES AT RIVERVIEW NORTHBOUND
ON MINNESOTA AT 8TH WESTBOUND
ON MINNESOTA AT 9TH WESTBOUND
ON 7TH AT STEIN NORTHBOUND
ON 7TH AT CHEYENNE NORTHBOUND
ON 7TH AT MIAMI NORTHBOUND
ON BROADWAY AT 8TH NORTHBOUND FARSIDE
ON 6TH AT MINNESOTA SOUTHBOUND
ON JAMES STREET AT 346 JAMES STREET NWB
ON JAMES ST AT 346 JAMES ST EASTBOUND
ON MINNESOTA AT 5TH WB
ON STATE AT 41ST TERRACE EASTBOUND
ON 7TH BETWEEN ANN AND BARNETT SB
ON 7TH AT TOURAMEE SOUTHBOUND
ON 7TH AT ORVILLE SOUTHBOUND
ON 7TH AT SPLITLOG SOUTHBOUND
ON 7TH AT NORTHRUP SOUTHBOUND
ON 7TH AT TENNY SOUTHBOUND
ON 7TH AT REYNOLDS SOUTHBOUND
ON 7TH AT CENTRAL SOUTHBOUND
ON 7TH AT LOWELL SOUTHBOUND
ON 7TH AT PACIFIC SOUTHBOUND
ON 7TH AT KANSAS SOUTHBOUND
ON 7TH AT OSAGE SOUTHBOUND
ON 7TH AT MIAMI SOUTHBOUND
ON 7TH AT CHEYENNE SOUTHBOUND
ON 7TH AT METROPOLITAN SOUTHBOUND
ON RAINBOW AT 35TH SOUTHBOUND
ON RAINBOW AT 36TH SOUTHBOUND
ON RAINBOW AT 39TH SOUTHBOUND FARSIDE
ON RAINBOW AT OLATHE BLVD SOUTHBOUND
ON RAINBOW AT 43RD SOUTHBOUND
ON RAINBOW AT 43RD NORTHBOUND
ON RAINBOW AT LUTHERAN CHURCH NORTHBOUND
ON RAINBOW AT OLATHE BLVD NORTHBOUND
ON RAINBOW AT 39TH NORTHBOUND NEARSIDE
ON RAINBOW AT 36TH NORTHBOUND
ON RAINBOW AT 35TH NORTHBOUND
ON 7TH AT OSAGE NORTHBOUND
ON 7TH AT KANSAS NORTHBOUND
ON 7TH AT PACIFIC NORTHBOUND
ON 7TH AT LOWELL AVE NORTHBOUND
ON 7TH AT CENTRAL NORTHBOUND
ON 7TH AT REYNOLDS NORTHBOUND
ON 7TH AT TENNY NORTHBOUND
ON 7TH AT OHIO NORTHBOUND
ON 7TH AT ORVILLE NORTHBOUND
ON 7TH AT TAUROMEE NORTHBOUND
ON 7TH AT BARNETT NORTHBOUND
ON RAINBOW AT 46TH NORTHBOUND
ON RAINBOW AT 45TH NORTHBOUND
ON 43RD AT BOOTH WESTBOUND
ON 43RD AT FISHER WESTBOUND
ON 43RD AT MINNIE WESTBOUND
ON MISSION AT SENECA SOUTHBOUND
ON MISSION AT 45TH AVE SOUTHBOUND
ON 47TH AT MISSION EASTBOUND
ON 47TH AT ADAMS EASTBOUND
ON RAINBOW AT SW BLVD SOUTHBOUND
ON RAINBOW AT SW BLVD NORTHBOUND
On 43RD AT STATE LINE EB NS
ON ROANOKE AT 45TH NB
ON ROANOKE AT 46TH SB
On 47th at Jefferson EB Nearside
On 47th at Central EB Farside
ON W 47TH ST AT JC NICHOLS PARKWAY EB NS
ON 47TH AT WYANDOTTE WB NS
ON 47TH AT BROADWAY WB FS
ON 43RD AT FAIRMOUNT EB
ON 47TH AT JEFFERSON WB FS
ON 7TH ST AT SPLITLOG NB
ON 7TH ST AT MINNESOTA NB
ON RAINBOW AT 3948 RAINBOW SB
ON RAINBOW AT 4140 RAINBOW SB
ON 43RD AT FAIRMOUNT WB
ON ROANOKE AT TERRACE SB
On 43RD AT STATE LINE WBFS
ON ROANOKE AT TERRACE NB
ON ROANOKE AT MERCIER SB
ON ROANOKE AT MERCIER NB
ON ROANOKE AT 45TH SB
ON INDIANA AT 24TH TERR NB
ON BENTON AT 47TH TERR NORTHBOUND
ON INDIANA AT 45TH NORTHBOUND
ON INDIANA AT 43RD NORTHBOUND
ON INDIANA AT 41ST NORTHBOUND
ON INDIANA AT 39TH NORTHBOUND NEARSIDE
ON INDIANA AT 37TH NORTHBOUND
ON INDIANA AT 35TH NORTHBOUND
ON INDIANA AT 33RD NORTHBOUND FARSIDE
ON INDIANA AT LINWOOD NORTHBOUND
ON INDIANA AT 31ST NORTHBOUND
ON INDIANA AT 29TH NORTHBOUND FARSIDE
ON INDIANA BETWEEN VICTOR AND 28TH NORTHBOUND
ON INDIANA AT 27TH NORTHBOUND
ON INDIANA AT 23RD NORTHBOUND
ON INDIANA AT 20TH NORTHBOUND
ON 18TH AT PROSPECT WESTBOUND
ON 18TH AT BROOKLYN WESTBOUND
ON 18TH AT EUCLID WESTBOUND
ON 18TH AT WOODLAND WESTBOUND
ON 18TH AT HIGHLAND WESTBOUND
ON 18TH AT VINE WESTBOUND
ON 18TH BETWEEN PASEO & GROVE WESTBOUND
ON 18TH AT LYDIA WESTBOUND
ON 18TH AT FOREST WESTBOUND
ON GRAND AT 17TH NORTHBOUND FARSIDE
ON INDIANA AT 24TH TERR SB
ON 18TH AT FOREST EASTBOUND
ON 18TH BETWEEN GROVE AND PASEO EASTBOUND
ON 18TH AT VINE EASTBOUND
ON 18TH AT EUCLID EB
ON 18TH ST AT BROOKLYN EASTBOUND
ON 18TH AT PROSPECT EASTBOUND
ON TRUMAN AT INDIANA EASTBOUND FARSIDE
ON INDIANA AT 20TH SOUTHBOUND
ON INDIANA AT 23RD SOUTHBOUND
ON INDIANA AT 27TH SOUTHBOUND
ON INDIANA AT 28TH SOUTHBOUND
ON INDIANA AT 29TH STREET SOUTHBOUND
ON INDIANA AT 31ST SOUTHBOUND
ON INDIANA AT LINWOOD SOUTHBOUND
ON INDIANA AT 33RD SOUTHBOUND
ON INDIANA AT 35TH SOUTHBOUND FARSIDE
ON INDIANA AT 37TH SOUTHBOUND
ON 39TH AT INDIANA SOUTHBOUND NEARSIDE
ON INDIANA AT 41ST SOUTHBOUND
ON INDIANA AT 43RD SOUTHBOUND
ON INDIANA AT 45TH SOUTHBOUND
ON INDIANA AT BENTON SOUTHBOUND
ON BENTON AT 47TH TERR SOUTHBOUND
ON CLEAVER II BLVD AT CLEVELAND EASTBOUND
ON 18TH AT BENTON EASTBOUND
ON 18TH AT INDIANA EASTBOUND
ON 18TH AT INDIANA WESTBOUND
ON 18TH AT WALROND WESTBOUND
ON 18TH AT BENTON WESTBOUND
ON E 68TH TERR AT MYRTLE WB
ON 18TH AT WALROND EASTBOUND FARSIDE
ON BENTON AT INDIANA NORTHWESTBOUND
ON 12TH AT BENNINGTON WESTBOUND
ON 12TH AT BELMONT WESTBOUND
ON 12TH AT TOPPING WESTBOUND FARSIDE
ON 12TH AT OAKLEY WESTBOUND
ON HARDESTY AT WINNER NORTHBOUND FARSIDE
ON 9TH AT DENVER WESTBOUND
ON 9TH AT VAN BRUNT WESTBOUND
ON 9TH AT JACKSON WESTBOUND
ON 9TH AT CLEVELAND WESTBOUND NEARSIDE
ON 9TH AT BALES WESTBOUND
ON 9TH AT BENTON WESTBOUND FARSIDE
ON 9TH AT BELLEFONTAINE WESTBOUND
ON 9TH AT OLIVE WESTBOUND
ON 9TH AT BROOKLYN WESTBOUND
ON 9TH AT EUCLID WESTBOUND
ON 9TH AT WOODLAND WESTBOUND
ON 11TH BETWEEN CHARLOTTE AND HOLMES WESTBOUND
ON 11TH AT CHERRY WESTBOUND
ON MARYLOU WMS AT HIGHLAND EB
ON 9TH AT WOODLAND EASTBOUND
ON 9TH AT EUCLID EASTBOUND
ON 9TH AT BROOKLYN EASTBOUND FARSIDE
ON 9TH AT OLIVE EASTBOUND
ON 9TH AT BELLEFONTAINE EASTBOUND
ON 9TH AT BENTON EASTBOUND FARSIDE
ON 9TH AT BALES EASTBOUND
ON 9TH AT CLEVELAND EASTBOUND FARSIDE
ON 9TH AT JACKSON EASTBOUND
ON 9TH AT ELMWOOD EASTBOUND
ON 9TH ST AT VAN BRUNT EASTBOUND FARSIDE
ON 9TH AT DENVER EASTBOUND
ON 12TH BETWEEN HARDESTY & DRURY EB
ON 12TH AT TOPPING EASTBOUND
ON 12TH AT BELMONT EASTBOUND
ON 12TH AT BENNINGTON EASTBOUND
ON 12TH AT EWING EASTBOUND
ON WINCHESTER AT 12TH TERR SOUTHBOUND
ON WINNER RD AT 10TH ST SOUTHWESTBOUND
ON HARDESTY AT TRUMAN NB
ON 10TH AT TROOST EASTBOUND FARSIDE
ON HARDESTY AT TRUMAN SB
ON 18TH AT HIGHLAND EASTBOUND
ON ELLA FITZGERALD AT BASIE ST WESTBOUND
and 2050 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 2 checks — unchanged since 2026-10-06.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-06	25.5	first check
2026-10-07	25.5	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-06 to 2026-10-07 (2 checks)	`0638a6cf49b9`	2026-10-03	Current rubric: see the trend above
2026-08-06 to 2026-08-07 (2 checks)	`0638a6cf49b9`	2026-10-03	F, 54.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-10	`f5ee076c271f`	2026-10-03	F, 53.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-07-01 to 2026-07-09 (8 checks)	`2a49be565673`	2026-07-11	F, 27 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-06-30 (12 checks)	`017ac8b99a35`	2026-07-11	F, 25.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-06.

Same feed file as 2026-10-06; the published zip did not change.

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

Everything we checked

17 findings, ordered by severity.

Show every finding

Error1 instance
Service data ended 4 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning5377 instances
5377 of 5377 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning3685 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2300 instances
2300 of 2300 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning105 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning27 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning17 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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning9 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide for feed_expiration_date7_days · 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide for route_color_contrast · 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 for trip_coverage_not_active_for_next7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info2256 instances
About 2256 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 for scorecard_stop_names_all_caps · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. Service data expired 4 days ago, so FTA would find the link out of date.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Not ready: Service data expired 4 days ago, so FTA would find the link out of date.
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) Not checked yet: This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

shapes.txt covers your trips Ready: All 5377 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

Two requirements remain for this feed to earn the conformance mark. Service data expired 4 days ago. 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 Not yet: Service data expired 4 days ago.
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.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.

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 42 / 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 0 / 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 23 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Access needed to measure: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Missouri portfolio: the same scorecards for every feed we track in that group, on one free page.

For programs that support several agencies

This scorecard and the board one-pager for Kansas City Area Transportation Authority (KCATA) are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.

The report for Kansas City Area Transportation Authority (KCATA) uses the same numbers as this page: grade F (25.5 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.

One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.

See the program report bundle

See a sample bundle report: a real agency's current grade, with placeholder branding.

A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified. Read how the grade is calculated.

Similar feeds in Missouri

Other scorecards in Missouri, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/"><img src="https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/badge.svg" width="320" height="58" alt="Kansas City Area Transportation Authority (KCATA): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Kansas City Area Transportation Authority (KCATA): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/badge.svg)](https://gtfsscorecard.org/agency/kansas-city-area-transportation-authority-kcata/)

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/kansas-city-area-transportation-authority-kcata/2026-10-07.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-10-07. 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.

GTFS Scorecard. (2026). Kansas City Area Transportation Authority (KCATA) GTFS feed-quality record, dated 2026-10-07 (grade F (25.5/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 0638a6cf49b9…). https://gtfsscorecard.org/data/artifacts/kansas-city-area-transportation-authority-kcata/2026-10-07.json

@misc{gtfsscorecard-kansas-city-area-transportation-authority-kcata-2026-10-07,
  title        = {Kansas City Area Transportation Authority (KCATA) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/kansas-city-area-transportation-authority-kcata/2026-10-07.json}},
  note         = {Checked 2026-10-07; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade F (25.5/100)}
}

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