Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires

Feed status · checked 2026-07-09

Kansas City Area Transportation Authority (KCATA)

Based on the feed this agency publishes

FDCBA

27.0 / 100

down 0.4 since 2026-07-08

Ahead of 4% of all tracked agencies and 8% of large agencies. Operates in Missouri.

Expires in 2 daysAccessibility gapsNo realtime feed

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

Checked for changes 18 minutes ago; last changed 7 days ago.

Top things to fix

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

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.

⏱ One export setting.worth about +78 points

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

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

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.

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

Fix 03

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

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.

⏱ Often one default setting in your export.worth about +15 points

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

Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.

Re-export with a validity window that reaches at least 60 days out. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.

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 (27.0 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export with a validity window that reaches at least 60 days out.
   What: Service data runs out in 2 day(s).
   Validator notice: scorecard_feed_expiring_soon
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expiring_soon/

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

3. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
   What: 5901 of 5901 trips don't say whether the vehicle is wheelchair accessible.
   Validator notice: 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 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/

Score by category

Correctness43.5 / 100

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

Freshness3.3 / 100

Service data runs out in 2 day(s). Publish an updated feed soon or riders will lose trip planning.

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.

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

This feed has 2293 stops.

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 2043 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 20 checks — down 0.4 since 2026-07-08.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-06-19	30.1	first check
2026-06-20	29.7	down 0.4
2026-06-21	29.2	down 0.5
2026-06-22	28.8	down 0.4
2026-06-23	28.4	down 0.4
2026-06-24	28.0	down 0.4
2026-06-25	27.6	down 0.4
2026-06-26	27.2	down 0.4
2026-06-27	26.7	down 0.5
2026-06-28	26.3	down 0.4
2026-06-29	25.9	down 0.4
2026-06-30	25.5	down 0.4
2026-07-01	30.3	up 4.8
2026-07-02	29.9	down 0.4
2026-07-04	29.1	down 0.8
2026-07-05	28.7	down 0.4
2026-07-06	28.2	down 0.5
2026-07-07	27.8	down 0.4
2026-07-08	27.4	down 0.4
2026-07-09	27.0	down 0.4

What changed since your last check

Correctness no change
Freshness down 1.7
Rider experience no change

What changed in this feed

Overall score fell 0.4 points since 2026-07-08.

Same feed file as 2026-07-08; 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-06-19 this feed started at grade F. On 2026-07-01 it cleared equal_shape_distance_diff_coordinates. As of 2026-07-09 it holds grade F.

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

2026-07-01 Score rose 5 points, correctness rose 12 points.

Everything we checked

Warning5901 instances
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.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning3687 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2293 instances
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.
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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning93 instances
Some scheduled trips travel implausibly fast between stops.
Usually a typo'd stop time; riders get impossible arrival estimates.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · 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.)
Validator rule: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning16 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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)
Warning10 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.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning9 instances
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 7 observed fixes).
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning4 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
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.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · 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 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 24 observed fixes).
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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 route colors don't contrast with their text color.
Route badges become unreadable, especially for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
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.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info2250 instances
About 2250 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 (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info1 instance
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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 with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (210, 23, 50, STCR).
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.
1036 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ON VILLAGE WEST PKWY AT SUNFLOWER LANE SEB", "ON VILLAGE PKWY AT PRAIRIE CROSSING WB", "ON VILLAGE WEST PKWY AT PRAIRIE CROSSING SEB", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Some fixes we can make for you

These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.

Recased shouting stop names 2250 changes
For example: VILLAGE WEST WALMART -> Village West Walmart

Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip

NTD certification readiness Needs attention

This feed is close to NTD-ready. Service data runs out in 2 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 2 days; renew before you certify.

agency_id matches your 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.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.

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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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. Service data runs out in 2 days; renew to qualify. 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 runs out in 2 days; renew to qualify.
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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 2 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.

How this agency maps to the standards

A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.

Correctness 44 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
Freshness 3 / 100: The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
Rider experience 23 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
Realtime quality Not yet published: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.

[![Kansas City Area Transportation Authority (KCATA) GTFS data quality grade: F](https://gtfsscorecard.org/data/artifacts/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-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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-07-09 (grade F (27.0/100), rubric v1.1, gtfs-validator 8.0.1, feed sha256 2a49be565673…). https://gtfsscorecard.org/data/artifacts/kansas-city-area-transportation-authority-kcata/2026-07-09.json

@misc{gtfsscorecard-kansas-city-area-transportation-authority-kcata-2026-07-09,
  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-07-09.json}},
  note         = {Checked 2026-07-09; rubric v1.1; gtfs-validator 8.0.1; grade F (27.0/100)}
}

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