← All agencies

Feed status · checked 2026-08-01

Johnson County Transit

Based on the feed this agency publishes

Service mode Bus

FDCBA

67.3 / 100

unchanged since 2026-07-31

Catalogued in Kansas.

Covers 152 daysAccessibility gapsFlexible serviceRealtime not yet published

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 16 hours ago; last changed 37 days ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

Realtime quality was not measured this run. It does not count against the grade.
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

Fix 01

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

641 of 641 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

Fix 02

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

1946 of 1946 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

Fix 03

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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

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: 641 of 641 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

Agency: Johnson County Transit
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 641 of 641 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/johnson-county-transit/?finding=scorecard_wheelchair_boarding_unknown#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.

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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
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. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 152 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: 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 Trillium a fix request

This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.

Hi,

Our GTFS feed (Johnson County Transit) scored D (67.3 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 641 of 641 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/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 1946 of 1946 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/

3. 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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/johnson-county-transit/

Score by category

Correctness74.0 / 100

The MobilityData validator flagged 7 kinds of issue across 676 instances (0 error, 629 warning, 47 informational).

Freshness100.0 / 100

Service data covers the next 152 days.

Rider experience31.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

Not scored 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 641 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.

520 (green)
495 (green)
487 (green)
475 (green)
404 (green)
403 (green)
402 (green)
401 (green)
United Drop and Ride (green)
C (orange)
B (white)
A (yellow)

Routes in Johnson County Transit's feed
Route	Type	Line color
520 Strang Line Express	Bus	green
495 95th Street	Bus	green
487 87th Street-MTC	Bus	green
475 Quivira-75th Street	Bus	green
404 Metcalf-Downtown	Bus	green
403 Antioch-Olathe	Bus	green
402 Johnson-Quivira	Bus	green
401 Metcalf-Plaza	Bus	green
United Drop and Ride	Bus	green
C Link C	Bus	orange
B Link B	Bus	white
A Link A	Bus	yellow

List every stop

Rosehill Road WB
Monrovia Street WB
Quivira Road WB
87th Street & Goddard Street WB
87th Street & Switzer Street WB
Central Resource Library (87th & Farley St)
87th Street & Grant Street WB
Santa Fe Drive & Grandview Avenue WB
Santa Fe Drive & Shawnee Drive WB
Santa Fe Drive & Newton Street WB
Metcalf & 77th SB
Nall Avenue & 75th Street WB
Nall Avenue & 71st Street WB
Nall Avenue & 67th Street WB
Nall Avenue & 63rd Terrace WB
ON METCALF AT 110TH NORTHBOUND FARSIDE
ON STATE LINE AT 95TH SOUTBOUND NEARSIDE
ON 95TH ST AT MISSION WESTBOUND NEARSIDE
ON 47TH AT WYANDOTTE WESTBOUND NEARSIDE
ON OAK AT TRUMAN RD NEARSIDE NB
ON 11TH AT CENTRAL WESTBOUND
ON MINNESOTA AT 10TH WESTBOUND
ON MINNESOTA AT 11TH WESTBOUND
ON MINNESOTA AVE AT 7TH STREET WB
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
KCI Airport Terminal
MISSION TRANSIT CENTER BAY #6
MISSION Transit CENTER BAY #4
Nall Avenue & 63rd Street EB
Nall Avenue & 67th Street EB
Nall Avenue & 71st Street EB
Nall Avenue & Tomahawk Road EB
Metcalf & 77th NB
Santa Fe Drive & Newton Street EB
Santa Fe Drive & Shawnee Drive EB
Santa Fe Drive & Antioch Road EB
Santa Fe Lane EB
Grant Street EB
Central Resource Library (87th & Farley St)
Switzer Street EB
Ballentine Street EB
Quivira Road EB
Monrovia Street EB
Rosehill Road EB
Westchester Square (87th & Noland Rd)
Haskins Place EB
Candlelight Lane EB
Greenway Lane EB
Lackman Road EB
Allman Road EB
Maurer Road EB
Renner Road
City Center Drive
Maurer Road WB
Allman Road WB
Lackman Road WB
Alden Street WB
Acuff Lane WB
Candlelight Lane WB
Pflumm Road WB
Westchester Square (87th & Hauser Ct)
ON 75TH AT TROOST WESTBOUND
ON 75TH AT HOLMES WESTBOUND
ON 75TH AT OAK WESTBOUND
ON 75TH AT MAIN WESTBOUND
ON 75TH AT WYANDOTTE WESTBOUND
ON 75TH AT BROADWAY WESTBOUND
ON 75TH AT JEFFERSON WESTBOUND
ON 75TH AT MADISON WESTBOUND
ON 75TH AT WARD PKWY WESTBOUND
ON 75TH AT WYOMING WESTBOUND
ON STATE LINE AT 7532 STATE LINE SOUTHBOUND
ON STATE LINE BETWEEN 76TH & MEADOWLAKE SB
ON STATE LINE AT 79TH SOUTHBOUND
ON STATE LINE AT 7920 SB
ON STATE LINE AT 82ND STREET SOUTHBOUND
ON STATE LINE AT 83RD SOUTHBOUND
ON STATE LINE AT 84TH TERRACE SOUTHBOUND NEARSIDE
ON STATE LINE BTWN AT 85TH TERR & 85TH ST NB
ON STATE LINE AT 83RD NORTHBOUND
ON STATE LINE AT 82ND SPRINT NORTHBOUND
ON STATE LINE AT 8015 NORTHBOUND
ON STATE LINE AT 79TH NB
ON STATE LINE AT MEADOWLAKE TERR NORTHBOUND
ON STATE LINE AT MEADOWLAKE NORTHBOUND
ON 75TH AT STATE LINE EASTBOUND
ON 75TH AT WARD PKWY EASTBOUND
ON 75TH AT MADISON EASTBOUND
ON 75TH AT JEFFERSON EASTBOUND
ON 75TH AT OAK EASTBOUND
ON 75TH AT HOLMES EASTBOUND
ON 115TH AT KOHL'S ACCESS RD EB
ON METCALF AT W 105TH NB
ON METCALF AT W 105TH SB
119TH & METCALF WALMART
ON CENTRAL AT 18TH EASTBOUND
ON CENTRAL AT 16TH EASTBOUND
ON CENTRAL AT WILSON EASTBOUND
ON CENTRAL AT 13TH EASTBOUND
ON CENTRAL AT 12TH EASTBOUND
ON CENTRAL AT BETHANY EASTBOUND
ON CENTRAL AT 10TH EASTBOUND
ON CENTRAL AT 9TH EASTBOUND
ON CENTRAL AT COY EASTBOUND
ON CENTRAL AT PYLE EASTBOUND
ON CENTRAL AT 11TH EB
ON 18TH AT CENTRAL SOUTHBOUND FARSIDE
EAST VILLAGE - BAY B
ON CENTRAL AT VALLEY EB
ON MINNESOTA AT 8TH WESTBOUND
ON MINNESOTA AT 9TH WESTBOUND
ON 47TH AT MISSION EASTBOUND
ON 47TH AT ADAMS EASTBOUND
ON ROE AT 51ST SB
ON ROE AVE AT JOHNSON DRIVE NORTHBOUND FARSIDE
ON ROE AT 53RD TER NORTHBOUND
ON ROE AT 48TH NORTHBOUND
ON W 48TH AT ROE LANE EASTBOUND
ON W 47TH AT FONTANA EASTBOUND
ON W 47TH AT ALHAMBRA EASTBOUND
ON W 47TH ST AT REINHARDT EASTBOUND
ON W 47TH AT S 6TH TER WESTBOUND
ON W 47TH AT S 9TH STREET WESTBOUND
ON W 47TH AT ROE LANE WESTBOUND
ON ROE AT 48TH SOUTHBOUND
ON ROE AT W 53RD SOUTHBOUND
ON W 47TH AT BELINDER RD EASTBOUND
ON ROE AT 51ST NORTHBOUND
ON 7TH ST AT SPLITLOG NB
ON RAINBOW AT 4140 RAINBOW SB
ON RAINBOW AT 43RD NORTHBOUND
ON RAINBOW AT LUTHERAN CHURCH NORTHBOUND
ON RAINBOW AT OLATHE BLVD NORTHBOUND
ON 7TH AT REYNOLDS NORTHBOUND
ON STATE LINE AT 88TH ST SOUTHBOUND FARSIDE
ON 7TH AT TENNY NORTHBOUND
ON 95TH ST AT NALL EASTBOUND NEARSIDE
ON 7TH AT OHIO NORTHBOUND
ON 95TH ST AT NALL WESTBOUND NEARSIDE
ON 7TH AT ORVILLE NORTHBOUND
ON METCALF AT 95TH ST SOUTHBOUND FARSIDE
ON 7TH AT TAUROMEE NORTHBOUND
ON METCALF AT 95TH ST NORTHBOUND NEARSIDE
ON 7TH AT BARNETT NORTHBOUND
ON STATE LINE AT 90TH SOUTHBOUND
ON RAINBOW AT 46TH NORTHBOUND
ON RAINBOW AT 45TH NORTHBOUND
JOHNSON COUNTY COMMUNITY COLLEGE CARLSEN CENTER
OAK PARK MALL PARK AND RIDE
ON PERSHING AT MAIN EB
ON 11TH BETWEEN CHARLOTTE AND HOLMES WESTBOUND
11TH AT CHERRY
ON 11TH/PETTICOAT LANE AT MAIN WESTBOUND
ON OAK AT 12TH NORTHBOUND FARSIDE
ON TROOST AT 51ST SB
ON TROOST AT 75TH NORTHBOUND
ON 11TH AT OAK WESTBOUND
KU EDWARDS
ON PENNSYLVANIA AT 12TH SOUTHBOUND
ON 12TH AT LOCUST EASTBOUND
ON GRAND AT PERSHING FARSIDE NORTHBOUND
ON GRAND AT 22ND NORTHBOUND NEARSIDE
ON GRAND AT 19TH NORTHBOUND
ON 11TH AT WASHINGTON WESTBOUND NEARSIDE
ON 47TH AT JEFFERSON EASTBOUND NEARSIDE
ON 39TH AT KU MED CENTER EASTBOUND
ON 119TH AT LOWELL WESTBOUND NEARSIDE
ON 119TH AT LOWELL EASTBOUND
ON 119TH AT HEMLOCK WESTBOUND NEARSIDE
ON W 119TH AT HEMLOCK EASTBOUND NEARSIDE
ON 119TH AT GRANT WESTBOUND FARSIDE
ON 119TH AT HAYES EASTBOUND
ON W 119TH AT FARLEY WESTBOUND FARSIDE
ON 119TH AT FARLEY EASTBOUND FARSIDE
ON 119TH AT GRANT EASTBOUND
ON 119TH AT SWITZER WESTBOUND FARSIDE
ON 119TH BETWEEN GOODARD AND SWITZER WESTBOUND
ON 119TH AT NIEMAN EASTBOUND
ON 119TH AT NIEMAN WESTBOUND
ON 119TH AT INDIAN CREEK PARKWAY EASTBOUND
ON 119TH AT INDIAN CREEK PARKWAY WESTBOUND
ON METCALF AT 110TH SOUTHBOUND
ON W 119TH AT QUIVIRA EASTBOUND
ON RENNER BLVD AT 113TH SOUTHBOUND / AMAZON
ON RENNER BLVD AT 113TH NORTHBOUND / AMAZON
ON W 75TH AT 11200 W 75TH STREET WESTBOUND FARSIDE
ON JOHNSON DR AT BROADMOOR ST EASTBOUND
ON JOHNSON DR AT LAMAR EASTBOUND NEARSIDE
ON MARTWAY DR BETWEEN WOODSON & OUTLOOK EB
ON MARTWAY BETWEEN OUTLOOK & WOODSON WB
ON JOHNSON DR AT LAMAR WESTBOUND FARSIDE
ON JOHNSON DRIVE AT BROADMOOR WESTBOUND
ON SANTA-FE AT K-7 HIGHWAY WESTBOUND
ON SANTA FE AT K-7/PARKER EASTBOUND FARSIDE
ON SANTA FE AT LOGAN EASTBOUND
ON SANTA FE AT LOGAN WESTBOUND FARSIDE
ON SANTA FE AT PINE EASTBOUND
ON SANTA FE AT PINE WESTBOUND FARSIDE
ON SANTA FE AT KANSAS CITY ROAD EASTBOUND
ON SANTA FE AT KANSAS CITY ROAD WESTBOUND
ON SANTA FE AT BUCHANAN EASTBOUND NEARSIDE
ON SANTA FE AT BUCHANAN WESTBOUND
ON SANTA FE AT CHURCH EASTBOUND
ON SANTA FE AT CHURCH WESTBOUND NEARSIDE
ON SANTA FE AT RIDGEVIEW EASTBOUND NEARSIDE
ON SANTA FE AT RIDGEVIEW WESTBOUND FARSIDE
ON E SANTA FE AT LINDENWOOD EASTBOUND
ON E SANTA FE AT LINDENWOOD WESTBOUND
ON ANTIOCH AT 64TH TERR NORTHBOUND NEARSIDE
ON ANTIOCH AT 95TH NORTHBOUND FARSIDE
ON ANTIOCH AT 95TH SOUTHBOUND NEARSIDE
ON SHAWNEE MISSION PARKWAY AT CRAIG EASTBOUND
ON STRANG LINE AT 118TH NORTHBOUND NEARSIDE
ON STRANG LINE AT 118TH SOUTHBOUND NEARSIDE
ON STRANG LINE AT W 116TH NORTHBOUND NEARSIDE
ON STRANG LINE AT 116TH SOUTHBOUND
ON STRANG LINE RD AT RANDALL NORTHBOUND
ON STRANG LINE AT RANDALL SOUTHBOUND NEARSIDE
ON STRANG LINE ROAD AT W 112TH SOUTHBOUND
ON RAINBOW AT 43RD AVE SOUTHBOUND
ON RAINBOW AT 44TH AVE SOUTHBOUND
ON W 47TH ST AT ADAMS WESTBOUND
ON OAK AT 13TH NORTHBOUND NEARSIDE
ON RENNER BLVD AT 112TH SOUTHBOUND / EPA
ON RENNER BLVD AT 116TH ST NB
ON COLLEGE BLVD AT LACKMAN ROAD WESTBOUND FS
ON RENNER BLVD AT 112TH ST NB
ON COLLEGE BLVD AT STRANGLINE ROAD WESTBOUND
ON COLLEGE BLVD AT LAKEVIEW AVE EASTBOUND
ON COLLEGE BLVD AT S GREENWOOD ST WESTBOUND FS
ON COLLEGE BLVD AT LACKMAN EASTBOUND
ON COLLEGE BLVD AT PFLUMM ROAD WESTBOUND
ON COLLEGE BLVD AT STRANG LINE ROAD EASTBOUND
ON COLLEGE BLVD AT HAUSER ST WESTBOUND
ON COLLEGE BLVD AT S GREENWOOD ST EASTBOUND
ON COLLEGE BLVD AT WESTGATE ST WESTBOUND
ON COLLEGE BLVD AT PFLUMM RD EASTBOUND
ON W 75TH STREET AT QUIVIRA ROAD WESTBOUND
ON COLLEGE BLVD AT HAUSER ST EASTBOUND
ON NIEMAN ROAD AT 74TH STREET SOUTHBOUND
ON COLLEGE BLVD AT WESTGATE / CAMPUS DR EB
ON NIEMAN ROAD BETWEEN 72ND AND 71ST SOUTHBOUND
ON NIEMAN RD AT 75TH ST NB
ON NIEMAN ROAD AT 67TH ST SOUTHBOUND NEARSIDE
ON NIEMAN RD AT 74TH ST NB
ON NIEMAN ROAD AT 75TH STREET SOUTHBOUND NS
and 391 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	67.3	first check
2026-07-30	67.3	no change
2026-07-31	67.3	no change
2026-08-01	67.3	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-31.

Same feed file as 2026-07-31; 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.

Everything we checked

13 findings, ordered by severity.

Show every finding

Warning1946 instances
1946 of 1946 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)
Warning641 instances
641 of 641 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)
Warning564 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)
Warning45 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning16 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning4 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.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Info562 instances
About 562 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)
Info34 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info5 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · 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.

Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).

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 152 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) 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 1946 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 152 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

45 of 636 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 152 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 74 / 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 100 / 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 32 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers 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 badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

[![Johnson County Transit GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/johnson-county-transit/badge.svg)](https://gtfsscorecard.org/agency/johnson-county-transit/)

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/johnson-county-transit/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.

GTFS Scorecard. (2026). Johnson County Transit GTFS feed-quality record, dated 2026-08-01 (grade D (67.3/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 a1c0c5de96ee…). https://gtfsscorecard.org/data/artifacts/johnson-county-transit/2026-08-01.json

@misc{gtfsscorecard-johnson-county-transit-2026-08-01,
  title        = {Johnson County Transit GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/johnson-county-transit/2026-08-01.json}},
  note         = {Checked 2026-08-01; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (67.3/100)}
}

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