Feed status · checked 2026-08-01
Transit Authority of Northern Kentucky (TANK)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Kentucky.
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 67 minutes ago; last changed 19 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
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
809 of 809 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
2024 of 2024 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
Check the flagged stop times for transposed minutes.
Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.
⏱ A few minutes per flagged trip.worth about +8 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
- 809 of 809 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
- 2024 of 2024 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
- Some scheduled trips move faster between stops than a bus can.
- Next action
- Check the flagged stop times for transposed minutes.
- 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.
Check the flagged stop times for transposed minutes. · 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's last published service date is in 97 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
- Fare information is published using GTFS Fares v1.
- 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 7 kinds of issue across 156 instances (0 error, 152 warning, 4 informational).
Service data covers the next 97 days.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (64, 2X, 3701).
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.
53 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Winston at 43rd", "St Elizabeth Florence", "St Elizabeth Florence", 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.
Fares are applied to trips.
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 809 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.
- 1 (teal)
- 12 (teal)
- 16 (purple)
- 2X (teal)
- 25 (yellow)
- 25X (yellow)
- 3 (purple)
- 30X (yellow)
- 352 (black)
- 3701 (red)
- 39X (purple)
- 40X (yellow)
- 42X (yellow)
- 450 (black)
- 451 (black)
- 485 (black)
- 5 (purple)
- 552 (black)
- 553 (black)
- 64 (green)
- 652 (black)
- 7 (green)
- 751 (black)
- 752 (black)
- 8 (yellow)
- 851 (black)
| Route | Type | Line color |
|---|---|---|
| 1 Dixie Hwy/Florence | Bus | teal |
| 12 Bellevue/Dayton | Bus | teal |
| 16 West Newport/Fort Thomas | Bus | purple |
| 2X Airporter | Bus | teal |
| 25 NKU/Alexandria | Bus | yellow |
| 25X Alexandria Express | Bus | yellow |
| 3 Ludlow/Bromley | Bus | purple |
| 30X Fort Wright/Lake Park Dr Express | Bus | yellow |
| 352 Holmes HS #3 PM | Bus | black |
| 3701 Southbank Shuttle | Bus | red |
| 39X Petersburg Rd/South Hebron Express | Bus | purple |
| 40X Worldwide Blvd/North Hebron Express | Bus | yellow |
| 42X Florence Hub/Industrial Rd Express | Bus | yellow |
| 450 Holmes HS #2 PM | Bus | black |
| 451 Holmes HS #2 AM | Bus | black |
| 485 Holmes HS #5 PM | Bus | black |
| 5 Holman Ave/Fort Wright | Bus | purple |
| 552 Holmes HS #1 AM | Bus | black |
| 553 Holmes HS #6 PM | Bus | black |
| 64 | Bus | green |
| 652 Holmes HS #8 AM | Bus | black |
| 7 Madison Ave/Latonia | Bus | green |
| 751 Holmes HS #7 PM | Bus | black |
| 752 Holmes HS #9 PM | Bus | black |
| 8 Eastern Ave/Crestview Hills | Bus | yellow |
| 851 Holmes HS #4 PM | Bus | black |
List every stop
- Winston at 43rd
- Mall at Plaza
- Mall at Cayton
- Burlington at Mall
- Burlington at Houston
- Mall at Village at the Mall
- Merchants at Doering
- Doering at Florence Walmart
- Ted Bushelman at Doering
- Meijer at Woodspoint
- Spiral at Meijer
- Spiral at Turfway Commons
- Spiral at Beckfield College
- Thoroughbred at Turfway
- Hansel at Richman
- St Elizabeth Florence
- Steeple Chase at Turfway
- Turfway at Burlington
- Turfway at Crown Court Apts
- Turfway at Lloyd
- Dixie at Turfway
- Dixie at Turfway
- Turfway at Drexel
- Turfway at Curtis
- Steeple Chase at Turfway
- St Elizabeth Florence
- Hansel at Richman
- Thoroughbred at Turfway
- Spiral at Beckfield College
- Spiral at Turfway Commons
- Spiral at Meijer
- Meijer at Woodspoint
- Ted Bushelman at Doering
- Doering at Florence Walmart
- Merchant at Doering
- Mall at Village at the Mall
- Mall at Florence Square
- Mall at Cayton
- Mall at Plaza
- Florence Hub
- Aero Pkwy at Wendell Ford
- Turfway at Steeple Chase
- Turfway at Hansel
- Turfway at Turfway Access
- Wendell Ford at Amazon/DHL
- Donaldson at Airfield
- CVG Airport Terminal
- Donaldson at Mineola
- Lincoln at Spence
- Donaldson at Point Pleasant
- Spence at Kenton
- Donaldson at Point Pleasant
- Donaldson at Mineola
- Donaldson at Airfield
- Wendell Ford at Amazon Prime Air
- Aero Pkwy at Bosch
- Thoroughbred at Hansel
- Scott at 16th
- Scott at 17th
- Scott at 19th
- Scott at 20th
- Southern at Church
- North Bend at Coral
- North Bend at Barbara
- Langley at Hargrave
- 3680 Langley
- 3720 Langley
- 2431 Wright
- Wright at North Bend
- Conner at North Bend
- North Bend at Litton
- Limaburg at Cougar
- Limaburg Park and Ride
- Petersburg at Limaburg
- Petersburg at Ernst
- Petersburg at Hart
- Petersburg at Merrie
- Petersburg at Victory
- Petersburg at Elijah Creek
- Petersburg at Aviation
- Petersburg at Ridgedale
- Petersburg at Progress
- Petersburg at Terminal
- North Bend at Global
- North Bend at Worldwide
- Worldwide at North Bend
- 1190 Worldwide
- 1605 Worldwide
- 1155 Worldwide
- 1605 Worldwide
- 1180 Worldwide
- 1545 Worldwide
- 1200 Worldwide
- 1405 Worldwide
- 1500 Worldwide
- 1155 Worldwide
- 1600 Worldwide
- South Park at Sanctuary
- 1770 Worldwide
- 2266 South Park
- South Park at International
- International at Meridian
- 2030 Meridian
- North Bend at South Park
- North Bend at Global
- North Bend Park and Ride
- Main at Dixie
- Main at Banklick
- Main at Christian
- Dixie at Valley
- Mall at Mall Road Center
- Dixie at Circle
- US 42 at Sycamore
- Dixie at Riehl
- US 42 at Lacresta
- Dixie at Pinehurst
- US 42 at Freedom
- Dixie at New Buffington
- Industrial at Safeway
- 7970 Dixie
- Industrial at Carole
- Dixie at Industrial
- Empire at Industrial
- Empire at Dixie
- Empire at Schwan's
- Empire at Dixon
- Empire Dr at 80 Acres
- Empire at Bluegrass
- Empire at Empire Connector
- Empire at Empire Connector
- Empire at Bluegrass
- Empire Dr at 80 Acres
- Empire at Dixon
- Empire at Duro Bag
- Empire at Dixie
- Empire at Industrial
- Dixie at Industrial
- Industrial at Carole
- Dixie at New Buffington
- Industrial at Hillcrest
- Dixie at Pinehurst
- US 42 at Dream
- Dixie at Roger
- US 42 at Lacresta
- Dixie at St Jude
- US 42 at Diane
- Dixie at Shenandoah
- Mall at Mall Road Shopping Center
- Main at Christian
- Main at Banklick
- Turfway at Dixie
- Benham at 4th
- 4th at Kenton
- 4th at Boone
- York at 5th
- 4th at Main
- 6th at Monmouth
- Clay at 5th
- 6th at Saratoga
- Clay at 6th
- 6th at Berry
- 6th at Washington
- 6th at Dayton
- 6th at Overton
- 6th at McKinney
- 6th at Monroe
- 6th at Ervin
- 6th at Park
- 6th at Vine
- 6th at Maple
- 6th at Walnut
- 6th at Linden
- 6th at O Fallon
- 6th at Oak
- Fairfield at Foote
- Riviera at Bellevue Plaza
- Fairfield at Taylor
- Riviera at Fairfield
- Fairfield at Patchen
- Fairfield at Riviera
- Riviera at Fairfield
- Fairfield at Berry
- Riviera at Bellevue Plaza
- Fairfield at Taylor
- 6th at Oak
- Fairfield at Ward
- 6th at Linden
- 6th at O Fallon
- 6th at Maple
- 6th at Walnut
- 6th at Park
- 6th at Vine
- 6th at Monroe
- 6th at Ervin
- 6th at Overton
- 6th at McKinney
- 6th at Dayton
- 6th at Washington
- 6th at Berry
- 6th at Saratoga
- 6th at Clay
- Monmouth at 5th
- 6th at Main
- 3rd at Newport on the Levee
- 5th at Boone
- 5th at Kenton
- 5th at Benham
- 5th at Clark
- Clark at 4th
- 2nd at Benham
- Grand at Churchill
- Grand at Grand Towers Apts
- Carothers at Pavilion
- 4th at Columbia
- Carothers at Newport Plaza
- Central at 5th
- Monmouth at Carothers
- Central at 6th
- 11th at John
- 6th at Isabella
- 11th at York
- Isabella at 7th
- 11th at Columbia
- Isabella at 8th
- 11th at Isabella
- Isabella at 9th
- Isabella at 10th
- Isabella at 10th
- Isabella at 9th
- 11th at Central
- Isabella at 8th
- 11th at Columbia
- Isabella at 7th
- 11th at York
- Isabella at 6th
- 11th at John
- 5th at Central
- Carothers at Newport Shopping Center
- 5th at York
- Carothers at Newport Plaza
- Carothers at Pavilion
- Grand at Grand Towers Apts
- Grand at Churchill
- St. Elizabeth Fort Thomas
- Alexandria at Louie B Nunn
- Alexandria at Marshall
- Alexandria at Johns Hill
- Alexandria at ML Collins
- Alexandria at Johns Hill
- Alexandria at Louie B Nunn
- and 559 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 | 70.9 | first check |
| 2026-07-30 | 70.9 | no change |
| 2026-07-31 | 70.9 | no change |
| 2026-08-01 | 70.9 | 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
10 findings, ordered by severity.
Show every finding
- Warning2024 instances
2024 of 2024 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)
- Warning809 instances
809 of 809 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)
- Warning106 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning30 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning10 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)
- Warning4 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)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Info4 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · 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).
Trip-planning apps and regional data coordinators 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.)
Finding code: scorecard_no_feed_contact · 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
- Service data covers the next 97 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 2024 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 97 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 97 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 68 / 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 52 / 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/transit-authority-of-northern-kentucky-tank-2068/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.