Feed status · checked 2026-08-01
Knoxville Area Transit (KAT)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Tennessee.
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 75 minutes ago; last fetch returned HTTP 404.
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 agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
1154 of 1154 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
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
2506 of 2506 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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
- 1154 of 1154 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
- Feed evidence
- 2506 of 2506 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- feed_info.txt is missing its start/end dates
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
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. 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. 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. 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. Self-check a feed before you publish.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
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. 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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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.
Score by category
The MobilityData validator flagged 11 kinds of issue across 340 instances (0 error, 334 warning, 6 informational).
Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
12 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 11, 12, 19, 20 Central Street, and more).
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.
935 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cumberland Ave WB @ Market St", "Cumberland Ave WB @ Locust St", "Cumberland Ave WB @ 11th St", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
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 1154 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.
- 10 (white)
- 13 Beaumont Connector (yellow)
- 16 Cedar Bluff Connector (green)
- 17 (teal)
- 19 (green)
- 20 Central Street (red)
- 21 (green)
- 22 Broadway (red)
- 23 (green)
- 24 (green)
- 30 (teal)
- 31 (red)
- 32 (green)
- 33 (yellow)
- 34 Burlington (green)
- 40 (green)
- 41 Chapman Highway (red)
- 42 (green)
- 44 (orange)
- 45 (yellow)
- 81 (orange)
- 83 (green)
- 85 Blue Line Trolley (WKD) (blue)
- 90 (purple)
| Route | Type | Line color |
|---|---|---|
| 10 10 Sequoyah Hills | Bus | white |
| 11 11 Kingston Pike | Bus | red (no shape in feed) |
| 12 12 Western Avenue | Bus | green (no shape in feed) |
| 13 Beaumont Connector | Bus | yellow |
| 16 Cedar Bluff Connector | Bus | green |
| 17 17 Sutherland/Bearden | Bus | teal |
| 19 19 Lakeshore/Lonas Connector | Bus | green |
| 20 Central Street | Bus | red |
| 21 21 Lincoln Park | Bus | green |
| 22 Broadway | Bus | red |
| 23 23 Millertown/Fairmont | Bus | green |
| 24 24 Inskip/Breda | Bus | green |
| 30 30 Parkridge | Bus | teal |
| 31 31 Magnolia Avenue | Bus | red |
| 32 32 Dandridge Avenue | Bus | green |
| 33 33 Martin Luther King Jr Avenue | Bus | yellow |
| 34 Burlington | Bus | green |
| 40 40 South Knoxville | Bus | green |
| 41 Chapman Highway | Bus | red |
| 42 42 UT/Fort Sanders Hospitals | Bus | green |
| 44 44 University Park | Bus | orange |
| 45 45 Vestal | Bus | yellow |
| 81 81 Orange Line Trolley (WKD) | Bus | orange |
| 83 83 Green Line Trolley (WKD) | Bus | green |
| 85 Blue Line Trolley (WKD) | Bus | blue |
| 90 90 Crosstown Connector | Bus | purple |
| 82 82 Orange Line Trolley (SAT) | Bus | orange (no shape in feed) |
| 84 84 Green Line Trolley (SAT) | Bus | green (no shape in feed) |
| 86 Blue Line Trolley (SAT) | Bus | blue (no shape in feed) |
List every stop
- Cumberland Ave WB @ Market St
- Cumberland Ave WB @ Locust St
- Cumberland Ave WB @ 11th St
- Cumberland at James Agee
- Cumberland Ave WB @ 16th St
- Cumberland WB before 18th Street
- Cumberland WB mid-block before 22nd Street
- Kingston Pike WB Mid-block before Concord
- Kingston Pike WB @ Lindsay Pl
- Kingston Pike WB @ 2nd Presbyterian Ch
- Kingston Pike WB @ Calvary Baptist
- Cherokee Blvd SB @ Kituwah Tr Outbound
- Keowee SB After Cherokee Blvd
- Keowee Ave WB @ Talahi Dr Outbound
- Keowee Ave WB @ Kenesaw Ave
- Keowee at Kenesaw
- Keowee Ave EB @ Talahi Dr
- Keowee Ave EB @ Cherokee Blvd
- Cherokee Blvd NB @ Kituwah Tr
- Kingston Pike EB @ Calvary Baptist
- Kingston Pike EB @ Crescent Bend Arm H
- Kingston Pike EB @ Alcoa Hwy
- Cumberland EB at the Commons
- Cumberland Ave EB @ 21st St
- Cumberland Ave EB @ Melrose Pl
- Cumberland Ave EB @ Volunteer Blvd
- Cumberland at Phillip Fulmer
- Cumberland Ave EB @ Esterbrook Rd
- Cumberland Ave EB @ Poplar Pl
- Main St EB @ Walnut St
- Trolley Super Stop on Main at the CC Bldg
- State St WB at Church Avenue
- Kingston Pike WB @ Laurel Church
- Kingston PIke WB @ Oakhurst
- Kingston Pike WB@ Scenic Dr
- Kingston Pk. at Lyons View
- Kingston Pike WB @ Forest Park
- Kingston Pike WB @ Mercedes Pl
- Kingston Pike WB @ Mohican St
- Kingston Pike WB @ Cemetery Rd
- Kingston Pike WB and Westwood
- Kingston Pike WB @ Bearden Elem
- Kingston Pike WB @ Bearden Rd
- Kingston Pike at Old Weisgarber
- Kingston Pike WB @ Kingston Pointe
- Kingston Pike WB @ Westfield Rd
- Kingston Pike WB past Papermill Rd.
- Kingston Pike WB @ Wesley Rd
- Kingston Pike WB @ Wellington Dr
- Kingston Pike WB @ West Hills Crossing Shopping Center
- Morrell Rd SB @ WTMall
- Morrell Rd SB @ Gleason Dr
- Gleason Dr WB @WTMall
- Gleason Dr WB@ West View Towers
- West Town Mall
- West Town between Belk & Pk Gar
- Ray Mears Blvd WB @ Winston Rd
- Ray Mears WB @ VA Clinic
- Ray Mears Blvd. at Dowtown West
- Kingston Pike WB past Downtown West Blvd.
- Kingston Pike before Gallaher View
- Kingston Pike WB @Gallaher View RD
- Walmart
- Kingston Pike EB Mid-block just past Walker Springs
- Kingston Pike EB @ Bearden High School
- Kingston Pike EB @ Downtown West Blvd
- Ray Mears Blvd. past Downtown West
- Ray Mears Blvd EB @ Winston Rd
- Gleason Dr EB @ Forest Oak Dr
- Gleason Dr EB Mid-block before Morrell
- Morrell Rd NB mid-block before Kingston Pike
- Morrell Rd NB @ Mall Entrance
- Kingston Pike EB Mid-block past Morrell
- Kingston Pike EB past Wellington Dr.
- Kingston Pike EB@ Wesley Rd
- Kingston Pike EB@ Gulf Club Rd
- Kingston Pike EB @ Albunda Drive
- Kingston Pike EB @ Deane Hill Dr
- Kingston Pk. at Northshore
- Kingston Pike EB @ Agnes Rd
- Kingston Pike EB @ Bearden Elem
- Kingston Pike EB past Westwood
- Kingston Pike EB @ Mohican St
- Kingston Pike EB @ Homberg Dr SW
- Kingston Pike EB @ Newcom
- Kingston Pike EB Mid-Block before Old Kingston Pike
- Kingston Pk. at Western Plaza
- Kingston Pike EB @ Kingston Park Dr
- Kingston Pike EB @ Scenic Dr
- Kingston Pk EB at Oakhurst
- Kingston Pike EB at Cherokee Blvd
- Hall of Fame Dr NB Mid-Block before Summitt Hill
- Summit Hill Dr EB @ 1100 Studio Apartments
- Summit Hill EB @ Lula Powell East Entrance
- Family Justice Center
- Change Center NB on Harriet Tubman St
- Winona St Northbound before Magnolia
- Magnolia WB at Jessamine
- Magnolia Ave WB @ Frazier St
- 5th Ave WB @ Lamar Street
- 5Th WB at King
- 5th Ave WB @ Cooper St
- Arthur St SB @ Callaway St
- Boyd St NB @ McGhee Ave
- Boyd St NB @ University Ave
- University Ave WB @ Dora St
- College at University
- Middlebrook Pike WB @ Clyde St
- Food City Western at 21st in Parking Lot
- Cherokee Health
- College St NB @ Moses St
- Knoxville College Dr WB @ K.C. Ent
- Knoxville College Dr WB @ Reynolds St
- Reynolds St WB at Wilkins St.
- Reynolds St WB Mid-Block past Wilkins
- Reynolds St WB @ Western Ave
- Western Ave WB @ Ridgebrook Ln
- Western Ave WB @ Majors Ave
- Beaumont Av EB @ Giffin St
- Beaumont Ave EB @ Bowling Ave
- Beaumont Ave EB @ Toms St
- Toms St NB @ Journolman Ave
- Oldham Ave EB @ Reed St
- Oldham Ave EB @ McSpadden St
- Virginia Eastbound After McSpadden
- Virginia Eastbound @ Elm St
- Johnston St Northbound @ Tennessee Ave
- Johnston St Northbound @ New York Ave
- New York Ave Westbound @ Burnside St
- Burnside St NB @ Louisiana Ave
- Burnside St NB @ Delaware Ave
- Delaware @ Gloria Garner St.
- Delaware Ave WB @ Sherman St
- Sherman St NB @ Texas Ave
- Texas Ave WB @ McPherson St
- Texas Ave WB before Minnesota Ave
- Western Avenue @ Industrial Parkway Outbound
- Industrial Pkwy N Bound
- Industrial Parkway East @ Sycamore Inbound
- Sycamore @ McPherson
- McPherson@Texas
- Texas Ave EB @ Sherman St
- Sherman St SB @ Delaware Ave
- Delaware at Stonewal
- Delaware Ave EB @ Burnside St
- Burnside St SB @ Louisiana Ave
- Burnside St SB @ New York Ave
- Burnside St SB @ Tennessee Ave
- Tennessee Ave @ Johnston St
- Virginia Ave Westbound near Elm St
- Virginia Westbound BeforeMcSpadden
- McSpadden St SB @ Oldham Ave
- Oldham Ave WB @ Reed St
- Oldham Ave WB @ Jourolman Ave
- Toms St SB @ Beaumont Ave
- Beaumont Ave WB @ Bowling Ave
- Keith Avenue WB @ Giffin St
- Western Ave EB @ Majors Ave
- Western EB Ridgebrook Ln
- Reynolds St EB Before Wilkins
- Reynolds St EB @ Brandau St (shelter)
- Knoxville College Dr EB @ K.C. Ent In
- College at University
- University Ave EB @ Dora St
- University Ave EB @ Boyd St
- Douglas Ave EB @ Cansler Ave
- Boyd St SB @ Deaderick Avenue
- Callaway Ave EB @ Arthur St
- 5th Ave EB @ Cooper St
- 5th Ave EB @ Broadway St
- 5th Ave EB @ King St
- Magnolia Ave EB @ Randolph St
- Magnolia EB at Jessamine
- Winona St Soundbound After Magnola Ave
- Change Center SB on Harriet Tubman
- Family Justice Center
- Summit Hill Dr WB @ Bell St
- Summit Hill Dr WB @ Patton St
- Hall of Fame Dr SB Mid-Block before Church
- Health Department Dameron
- Wray St @ Baxter Ave
- Baxter Ave WB @ Elm St
- Beaumont Ave WB @ Beaumont Elmen Sch
- Beaumont at Reed
- Beaumont Ave WB @ College St
- Beaumont Ave WB @ Toms St
- Western Ave EB @ News Sentinel Dr
- Cherokee Health
- 21st St SB @ Middlebrook Pike
- Middlebrook Pike WB @ Sutherland
- Middlebrook Pike WB @ Mingle Ave
- Middlebrook Pike WB Before Loraine St
- Public Works Complex
- Morris at Liberty
- Middlebrook Pike WB @ Clove Ln
- Middlebrook Pike WB at Lonas Dr
- Middlebrook Pk WB @ KUB
- 3rd Creek Rd SB Before Middlebrook WB Mid-block
- Middlebrook Pk EB @ Mold Design @ KUB
- Middlebrook Pike EB @ Lonas Dr
- Middlebrook EB Past Clove Ln
- Middlebrook Pike EB @ Liberty
- Middlebrook Pike EB @ Loraine St
- Middlebrook Pike EB Before Glenn
- State Office Bldg.
- Middlebrook Pike EB @ Sutherland Ave
- Western Ave WB @ Reynolds St
- Beaumont Ave EB @ College St
- Beaumont at Reed
- Beaumont Ave EB @ Boyd St
- Beaumont Ave EB @ Baxter Ave
- Baxter Ave EB @ Wray St Inbound
- Baxter Ave EB @ Central Ave
- Walbrook Dr WB past Walker Springs
- Bridgewater Rd NB before Cross Park Dr
- Cross Park Dr WB @ Cross Creek Dr
- Ten Mile Rd WB @ Grayland Drive
- Ten Mile Rd WB @ Rhodora Rd
- Ten Mile Rd WB @ Park Village Rd
- Park Village Dr NB past Ten Mile
- Park Village at Woodpark
- Fox Lonas WB @ Knoxville Catholic High
- Cedar Bluff Rd SB @ Dutchtown Rd
- Cedar Bluff Rd SB @ Sherrill Blvd
- Sherrill Blvd WB @ Christian Academy
- Sherrill Blvd WB @ Park West Blvd
- Parkwest Hospital
- Park West Blvd. @ Physicians Plaza
- Park West Blvd EB Mid-Block before Cedar Bluff
- Cedar Bluff Rd SB Mid-Block before Kingston Pike
- N Seven Oaks NB Mid-Block Before Noth Peters
- Windsor Square
- N Peters Rd EB @ Market Place Blvd
- N Peters Rd EB Before Cedar Bluff
- Park West Blvd WB at Park 40 North
- Park West Blvd. @ 9333 Block
- Parkwest Hospital
- Park West Blvd WB @ Sherrill Blvd
- Sherrill Blvd EB @ Park Forty Blvd
- Sherrill Blvd EB @ Cedar Bluff Rd
- Cedar Bluff Rd NB @ New Dutchtown
- Cedar Bluff at Fox Lonas
- Fox Lonas Rd EB @ Park Village Dr
- Park Village Dr SB @ Woopark Ln
- Park Village Dr SB Mid-Block Before Ten Mile
- Park Village Dr SB @ Ten Mile Rd
- Ten Mile Road EB at Rhodora Road
- Ten Mile Rd EB @ Cross Creek Dr
- Cross Creek SB @ Cross Park
- Bridgewater Rd SB after Cross Park Dr
- and 904 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
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 56.8 | first check |
| 2026-07-30 | 56.8 | no change |
| 2026-07-31 | 56.8 | no change |
| 2026-08-01 | 56.8 | 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
15 findings, ordered by severity.
Show every finding
- Warning2506 instances
2506 of 2506 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)
- Warning1154 instances
1154 of 1154 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)
- Warning155 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)
- Warning110 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning29 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning29 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)
- Warning7 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Finding code: missing_feed_info_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · 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)
- Info3 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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)
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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 2506 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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.
- 155 of 1154 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 clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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 49 / 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 85 / 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 45 / 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.
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/knoxville-area-transit-kat/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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.