Feed status · checked 2026-08-23
Transit Authority of River City (TARC) Fixed Route
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-22
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 47 minutes ago; last changed 19 days ago.
Measured 4 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.
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
1370 of 1370 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
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
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
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.
⏱ Usually an export-tool fix, not hand editing.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
- 1370 of 1370 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
- The feed contains no fare information.
- Next action
- 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.
- 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 stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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. See this feed's finding-clearance log.
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. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · 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. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 139 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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
- Live-arrival data covered 100% of scheduled trips in the sampled window.
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 8 kinds of issue across 8395 instances (0 error, 8394 warning, 1 informational).
Service data covers the next 139 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (71, 72, 76, 81).
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.
1341 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cane Run @ Rattermans", "Cane Run @ Bridwell", "Cane Run Rd @ Terry Rd", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 97.0% of vehicles on their route; predictions ran a median of 0s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 1370 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.
- 01 (red)
- 10 (red)
- 20 (teal)
- 03 (red)
- 04 (red)
- 05 (teal)
- 71 (gray)
- 72 (gray)
- 76 (gray)
- 08 (teal)
- 81 (gray)
- 93 (green)
- 94 (red)
- 99 (green)
| Route | Type | Line color |
|---|---|---|
| 01 Broadway – Bardstown | Bus | red |
| 10 Dixie Highway | Bus | red |
| 20 Eastern Parkway | Bus | teal |
| 03 Preston Highway – West Market | Bus | red |
| 04 Fourth Street – New Cut | Bus | red |
| 05 Portland – Poplar Level | Bus | teal |
| 71 New Albany – IUS | Bus | gray |
| 72 Clarksville | Bus | gray |
| 76 Jeffersonville | Bus | gray |
| 08 Shelbyville Road – Taylor Boulevard | Bus | teal |
| 81 Downtown – Zorn | Bus | gray |
| 93 UPS UofL Shuttle | Bus | green |
| 94 Cardinal Shuttle | Bus | red |
| 99 UPS West Louisville Shuttle | Bus | green |
List every stop
- Cane Run @ Rattermans
- Cane Run @ Bridwell
- Cane Run Rd @ Terry Rd
- Greenbelt Highway @ Raggard Rd
- Veterans @ Towne Center
- Veterans @ Sam Gwin
- Veterans @ Broadway
- Veterans @ Sam Gwin
- Algonquin Parkway @ Cypress
- Algonquin Parkway @ Beech
- Algonquin Pkwy @ Wilson
- Algonquin Pkwy @ Pacific
- Algonquin Pkwy @ S 35th
- Bono @ Graybrook
- Pearl @ Summit
- Pearl @ Cherry
- Pearl @ Summit
- Pearl @ Oak
- Bono @ Graybrook
- Jeffersonville Towne Center
- Algonquin Parkway @ S 35th
- S 34th @ Southern
- Dr Wm G Weathers @ Bohne
- 35th @ Sherill
- Wilson @ Algonquin
- Algonquin Parkway @ Cane Run
- Algonquin Parkway @ Beech
- Algonquin Parkway @ Cypress
- Shawnee Park Broadway
- W Oak @ S 12th
- W Oak @ S 10th
- Crittenden @ Eastern Parkway
- Cardinal @ Brook
- W Oak @ S 10th
- W Oak @ S12th
- Cardinal @ 1st
- S Jackson @ E Oak
- Northwestern Pkwy @ Portland
- S 34th @ Broadway
- S 34th @ Greenwood
- S 34th @ Hale
- S 34th @ Dumesnil
- Southern @ S 34th
- Southern @ Beech
- Southern @ Catalpa
- W Hill @ S 11th
- Poplar Level @ Thurston
- Poplar Level @ Audubon Plaza
- Poplar Level Rd @ Hess
- Poplar Level Rd @ Audubon Medical
- Poplar Level Rd @ Thurston
- Muhammad Ali @ 3rd
- Muhammad Ali @ 4th
- 7th @ W Hill
- Southern @ Catalpa
- Southern @ Beech
- Southern @ S 32nd
- Southern @ S 34th
- S 34th @ Kirby
- S 34th @ Dumesnil
- S 34th @ Hale
- S 34th @ Greenwood
- S 34th @ Broadway
- Market @ S 2nd
- Bank @ N 37th
- Bank @ N 35th
- Bank @ N 34th
- Rockford @ Skylark
- Rockford @ Saddlebrook
- Rockford @ Dover
- Rockford @ Imperial
- Rockford @ Duane
- Rockford @ Graston
- Rockford @ Dohn
- Rockford @ Rockford Plaza
- Rockford @ Stonestreet
- Dixie @ Garrs
- Taylor @ Longfield
- Taylor @ Queen
- Taylor @ Thornberry
- Winkler @ Algonquin Parkway
- Winkler @ 4th
- Eastern Parkway @ Speed School
- Eastern Parkway @ Emil
- Eastern Parkway @ Bradley
- Eastern Parkway @ Preston
- Eastern Parkway @ Shelby
- Eastern Parkway @ Delor
- Eastern Parkway @ Burnett
- Eastern Parkway @ Poplar Level
- Eastern Pkwy @ Castlevale
- Eastern Pkwy @ Barrett
- Eastern Pkwy @ Baxter
- S 6th @ W Chestnut
- 4th @ Friendship House
- Eastern Parkway @ Barrett
- Eastern Parkway @ Castlevale
- Eastern Pkwy @ Poplar Level
- Eastern Pkwy @ Burnett
- Eastern Parkway @ Delor
- Eastern Parkway @ Shelby
- Poplar Level @ Eastern Parkway
- Poplar Level @ Clarks
- Eastern Parkway @ Preston
- 4th @ St Catherine
- Eastern Parkway @ Bradley
- Eastern Parkway @ Concord
- Eastern Parkway @ Crittenden
- Eastern Parkway @ Speed School WB
- Winkler @ S 4th
- 4th @ Ormsby
- Dixie @ Crums SB
- Dixie @ Garrs
- Dixie @ Heaton
- 4th @ Magnolia
- Rockford @ Stonestreet
- Rockford @ Lynn Lea
- Rockford @ Graston
- Rockford @ 2317
- Rockford @ Van Hoose
- Rockford @ Imperial
- Rockford @ Dover
- Rockford @ Saddlebrook
- 4th @ Hill
- Rockford @ Clarion
- Rockford @ Cane Run
- Old Rockford @ Cane Run
- 4th @ Lee
- W Broadway @ S 4th
- Herr @ Wesboro
- Herr @ Crossmoor
- Herr @ Graymoor
- Herr @ Boxwood
- Herr @ Westport
- Westport @ Lyndon
- Westport @ Ormsby
- Westport @ Westcreek
- Westport @ Westport Middle School
- 4th @ Cardinal Blvd
- Westport @ McDowell Center
- Westport @ Redleaf
- Westport @ Hermitage
- Westport @ Langdon
- Westport @ Goose Creek
- Westport @ Westport Plaza
- Westport @ Hurstbourne
- Westport @ Stonebridge
- Westport @ Graystone Manor Pkwy
- Springhurst @ Westport
- Fischer Park @ Target
- Shelburne Park @ Fischer Park
- 4th @ Stansbury Park
- Algonquin Pkwy @ Dixie
- Algonquin @ 7th St
- Algonquin @ Sharp
- Algonquin @ Colorado
- Algonquin @ Winkler
- Algonquin @ Colorado
- Algonquin @ Sharp
- Algonquin @ 16th St
- Algonquin @ McCloskey Ave
- 4th @ Industry
- Westport @ Westport Circle
- Westport @ Goose Creek
- Westport @ Langdon
- Westport @ Hermitage
- Westport @ Redleaf
- Westport @ McDowell Center
- Westport @ Westcreeke
- Westport @ Ormsby
- Westport @ Lynn
- Westport @ Herr
- Herr @ Boxwood
- 4th @ Winkler
- Herr @ Graymoor
- Herr @ Wilder Elementary
- Herr @ Wesboro
- Herr @ Ballard High School
- 4th @ Heywood
- Dixie Hwy @ Dixie Garden Dr
- Dixie @ Barrett
- Dixie @ Valley Station
- Dixie @ Meijer
- Dixie @ Stonestreet
- Dixie @ Park Place Mall (NB)
- Dixie @ East Pages
- Dixie @ Oak Park
- Dixie @ Fury Way
- 3rd @ Central Station Blvd
- Dixie @ Dixie Manor
- Dixie @ Blanton
- Dixie @ Trent
- Dixie @ Meyers
- Dixie @ Upper Hunters Trace
- Dixie @ Rockford
- Dixie @ San Jose
- 7th @ Weller
- 7th @ Lincoln
- 7th @ Industry
- 7th @ 11th
- 7th @ Davies
- 7th @ Jordan
- 7th @ Hill
- 7th St @ Chestnut
- 8th St @ Chestnut
- S Roy Wilkins @ W Muhammad Ali
- 7th @ Industry
- S Roy Wilkins @ W Muhammad Ali
- 7th @ Weller
- Dixie @ Stewart Lane
- Dixie @ San Jose
- Dixie Hwy @ Rockford Ln
- Dixie @ Lewiston
- Dixie Hwy @ Upper Hunters Trace
- Dixie @ Meyers
- Dixie @ Trent
- Dixie @ Lower Hunters
- Dixie @ Dixie Manor
- Taylor @ Queen
- Dixie @ Greenwood
- Dixie @ Fury
- Dixie @ Oak Park
- Dixie @ Maryman
- Dixie @ W Pages
- Dixie @ Park Place Mall
- Dixie @ Johnsontown
- Dixie @ Citation
- 3rd @ Collins
- Dixie @ Valley Station
- Dixie @ Ashby
- Dixie @ Dixie Gardens
- 3rd @ Evelyn
- 3rd @ Whitney
- Dixie @ Algonquin Parkway
- 3rd @ Southern Heights
- 3rd @ Wellington
- 3rd @ Woodlawn
- 7th @ Algonquin
- Shawnee Park @ Northwestern Pkwy
- S 3rd @ Tenny
- Bluegrass @ Hazelwood
- Churchmann @ St. Jude
- Bluegrass @ Hazelwood
- New Cut @ Orchard
- New Cut @ Park
- S 3rd @ Kingston
- New Cut @ Palatka
- New Cut @ 3rd Sreet Road
- New Cut @ Southside
- 3rd @ Southland
- and 1120 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 72.5 | first check |
| 2026-08-07 | 72.5 | no change |
| 2026-08-22 | 72.5 | no change |
| 2026-08-23 | 72.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-08-22.
Same feed file as 2026-08-22; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning7751 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)
- Warning1370 instances
1370 of 1370 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)
- Warning256 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)
- Warning252 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning128 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)
- Warning5 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)
- Warning1 instance
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)
- 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
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)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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).
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 139 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 5837 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 139 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 28 days, with 17s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran right on the schedule, and stayed within 208s nine times in ten. They were on time (about a minute early to five late) 88.8% of the time. 97.0% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 139 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 56 / 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 100 / 100
- 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-river-city-tarc-2662/2026-08-23.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-23. 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.