Feed status · checked 2026-08-23
County Connection (CCCTA)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-22
Catalogued in California.
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 58 minutes ago; last changed 2 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 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
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 (the file itself is absent) 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
Review the flagged fields and fill in the ones your riders would use.
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.
⏱ A field at a time; not urgent.worth about +8 points in its category
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
241 of 1222 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 +5 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- 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
- Feed evidence
- Some files leave out fields that GTFS asks for but does not require.
- Next action
- Review the flagged fields and fill in the ones your riders would use.
- 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
- 241 of 1222 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
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.
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. See this feed's finding-clearance log.
Review the flagged fields and fill in the ones your riders would use. · 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.
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.
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 80.3% of stops and 100% 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 62 instances (0 error, 56 warning, 6 informational).
Service data covers the next 139 days.
80% of stops state wheelchair accessibility (80% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
80% of stops state accessibility (80% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
27 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 10, 11, 14, 16, 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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 1222 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)
- 10 (teal)
- 11 (gray)
- 14 (gray)
- 15 (teal)
- 16 (gray)
- 17 (teal)
- 18 (teal)
- 19 (teal)
- 20 (teal)
- 21 (teal)
- 28 (teal)
- 301 (purple)
- 310 (purple)
- 311 (gray)
- 314 (gray)
- 315 (purple)
- 316 (gray)
- 320 (purple)
- 321 (purple)
- 335 (purple)
- 35 (teal)
- 4 (gray)
- 5 (gray)
- 6 (teal)
- 601 (gray)
- 602 (gray)
- 605 (gray)
- 606 (gray)
- 611 (gray)
- 612 (gray)
- 613 (gray)
- 615 (gray)
- 616 (gray)
- 619 (gray)
- 622 (gray)
- 623 (gray)
- 625 (gray)
- 626 (gray)
- 635 (gray)
- 636 (gray)
- 7 (gray)
- 9 (teal)
- 91X (orange)
- 92X (orange)
- 93X (orange)
- 95X (orange)
- 96X (orange)
- 97X (orange)
- 98X (orange)
- 99X (gray)
| Route | Type | Line color |
|---|---|---|
| 1 Rossmoor/Shadelands | Bus | teal |
| 10 Concord BART/Clayton Rd | Bus | teal |
| 11 Concord BART/Pleasant Hill BART | Bus | gray |
| 14 Concord BART/Walnut Creek BART | Bus | gray |
| 15 Concord BART/Pleasant Hill BART | Bus | teal |
| 16 Martinez Amtrak/Concord BART | Bus | gray |
| 17 Concord BART/North Concord BART | Bus | teal |
| 18 Martinez Amtrak/Pleasant Hill BART | Bus | teal |
| 19 Martinez Amtrak/Concord BART | Bus | teal |
| 20 DVC/Concord BART | Bus | teal |
| 21 Walnut Creek BART/San Ramon | Bus | teal |
| 28 Concord BART/Amtrak | Bus | teal |
| 301 Walnut Creek BART/N Via Monte | Bus | purple |
| 310 Concord BART/Clayton Rd | Bus | purple |
| 311 Concord BART/Walnut Creek BART | Bus | gray |
| 314 Concord BART/DVC | Bus | gray |
| 315 Concord BART/Bel Air Dr | Bus | purple |
| 316 Martinez Amtrak/Pleasant Hill BART | Bus | gray |
| 320 DVC/Concord BART | Bus | purple |
| 321 Walnut Creek BART/San Ramon | Bus | purple |
| 335 Dublin BART/San Ramon | Bus | purple |
| 35 Dublin/Pleasanton BART/San Ramon | Bus | teal |
| 4 Walnut Creek BART/Broadway Plaza | Bus | gray |
| 5 Walnut Creek BART/Creekside Dr | Bus | gray |
| 6 Lafayette BART/Orinda BART | Bus | teal |
| 601 Rossmoor/WCI | Bus | gray |
| 602 Walnut Blvd/WCI | Bus | gray |
| 605 Creekside/WCI | Bus | gray |
| 606 Miramonte High/OIS/Orinda BART | Bus | gray |
| 611 Oak Grove Middle/Concord BART | Bus | gray |
| 612 Pine Hollow Middle/Concord BART | Bus | gray |
| 613 Oak Grove Middle/Concord BART | Bus | gray |
| 615 Concord High/El Dorado/Concord BART | Bus | gray |
| 616 Oak Grove Middle/Concord BART | Bus | gray |
| 619 Oak Grove Middle/Pleasant Hill BART | Bus | gray |
| 622 Cal High/Pine Valley Middle | Bus | gray |
| 623 Monte Vista High/Annabel | Bus | gray |
| 625 Acalanes High/Lafayette BART | Bus | gray |
| 626 Saint Mary's College/Lafayette BART | Bus | gray |
| 635 Bollinger Canyon/Camino Tassajara | Bus | gray |
| 636 Broadmoor/Dublin/Pleasanton BART | Bus | gray |
| 7 Pleasant Hill BART/Shadelands | Bus | gray |
| 9 DVC/Walnut Creek BART | Bus | teal |
| 91X Concord Commuter Express | Bus | orange |
| 92X Pleasanton ACE/Mitchell Dr | Bus | orange |
| 93X Walnut Creek BART/Antioch BART | Bus | orange |
| 95X San Ramon/BART Walnut Creek | Bus | orange |
| 96X BART Walnut Creek/Bishop Ranch | Bus | orange |
| 97X Dublin BART/Bishop Ranch | Bus | orange |
| 98X Martinez Amtrak/Walnut Creek BART | Bus | orange |
| 99X Martinez Amtrak/North Concord BART | Bus | gray |
List every stop
- Meadow Rd and Meadow Crest Ln
- Mountain View Blvd and Mynah Ct
- Court St and Ward St
- Pacheco Blvd and Arreba St
- Pacheco Blvd and Bush St
- Pacheco Blvd and Peach St
- Pacheco Blvd and Santa Fe Ave
- Pacheco Blvd and Ace Truckbox Center Martinez
- Pacheco Blvd and Morello Ave
- Pacheco Blvd and Morello Ave
- Pacheco Blvd and Camino Del Sol
- Pacheco Blvd and Arthur Rd
- Pacheco Blvd and Carolos Dr
- Pacheco Blvd and Pacheco Manor Dr
- Pacheco Blvd and Center Ave
- Pacheco Blvd and Center Ave
- Pacheco Blvd and S Buchanan Cir
- Pacheco Blvd and N Buchanan Cir
- Pacheco Blvd and Contra Costa Health Services Discovery House
- Pacheco Blvd and Arthur Rd
- Pacheco Blvd and Camino Del Sol
- Pacheco Blvd and Morello Ave
- Pacheco Blvd and Refinery Rd
- Pacheco Blvd and Howe Rd
- Pacheco Blvd and Shell Ave
- Pacheco Blvd and Bush St
- Pacheco Blvd and Arreba St
- Pine St and Susana St
- Court St and Green St
- Court St and Marina Vista Ave
- Escobar St and Alhambra Ave
- Martinez Amtrak
- Palmer Rd and Sylvan Rd
- Palmer Rd and Hawthorne Dr
- Palmer Rd and Mountain View Blvd
- San Miguel Dr and Mountain View Blvd
- San Miguel Dr and Hillview Ter
- San Miguel Dr and Shady Glen Rd
- San Miguel Dr and Adeline Dr
- San Miguel Dr and St Lukes Lutheran Church
- San Miguel Dr and Milton Ave
- Solano Way and Imhoff Rd
- S Main St and Crest Ave
- S Main St and Rudgear Rd
- Stone Valley Rd and Alamo Ranch Rd
- Stone Valley Rd and Miranda Ave
- Stone Valley Rd and Stonecreek Pl
- Tice Valley Blvd and Byron Park
- Tice Valley Blvd and Westborough Ln
- Tice Valley Blvd and Olympic Blvd
- Tice Valley Blvd and Montecillo Dr
- Tice Valley Blvd and Castle Hill Ranch Rd
- Tice Valley Blvd and Crest Ave
- Tice Valley Blvd and Tice Valley Ln
- Pleasant Hill BART
- Pleasant Hill BART
- Pleasant Hill BART
- Pleasant Hill BART
- Pleasant Hill BART
- Danville Park andRide
- Camino Ramon and San Thomas Way
- Camino Ramon and El Capitan Dr
- Camino Ramon and Saint Patricks Dr
- Camino Ramon and Greenbrook Dr
- Camino Ramon and Baldwin Dr
- Camino Ramon and Saint Patricks Dr
- Camino Ramon and El Capitan Dr
- Camino Ramon and San Thomas Way
- Camino Ramon and Sycamore Valley Rd
- Camino Tassajara and Sycamore Valley Rd
- Camino Tassajara and Messian Pl
- Camino Tassajara and Shady Creek Dr
- Camino Tassajara and Sherburne Hills Dr
- Camino Tassajara and Creekside Ave
- Camino Tassajara and Tassajara Village
- Camino Tassajara and Tassajara Ranch Dr
- Camino Tassajara and Wood Ranch Dr
- Diablo Rd and Green Valley Rd
- Diablo Rd and El Cerro Blvd
- Diablo Rd and Arroyo Dr
- Diablo Rd and Green Valley Shopping Center
- Diablo Rd and El Pintado
- Green Valley Rd and Compo Via
- Green Valley Rd and Donna Ln
- Railroad Ave and Love Ln andLinda Mesa Ave
- Railroad Ave and Prospect Ave
- Railroad Ave and Love Ln
- San Ramon Valley Blvd and Sonora Ave
- San Ramon Valley Blvd and Danville Town andCountry Shopping Center
- San Ramon Valley Blvd and Livery-Mercantile
- San Ramon Valley Blvd and Ridgeland Dr
- San Ramon Valley Blvd and Ridgeland Dr
- San Ramon Valley and Sycamore Square
- San Ramon Valley Blvd and Bank Of America
- San Ramon Valley Blvd and Sonora Ave
- Stone Valley Rd and Monte Vista High
- Sycamore Valley Rd and Brookside Dr
- Sycamore Valley Rd and Greenbrook Dr
- Tassajara Ranch Dr and Center Way
- Tassajara Ranch Dr and Blackstone Dr
- Tassajara Ranch Dr and Blackstone Dr
- Tassajara Ranch Dr and Blackstone Dr
- Tassajara Ranch Dr and Mountain Ridge Dr
- Tassajara Ranch Dr and Zenith Ridge Dr
- Dublin Blvd and Civic Plz
- Dublin Blvd and Dublin Ct
- Village Pkwy and Kimball Ave
- Village Pkwy and Davona Dr
- Village Pkwy and Brighton Dr
- Village Pkwy and Tamarack Dr
- Village Pkwy and Amador Valley Blvd
- Dublin Pleasanton BART
- Lafayette BART
- Acalanes Ave and Nogales St
- Acalanes Rd and Valente Dr
- Acalanes Rd and Hidden Valley Rd
- Camino Diablo and Stanley Blvd
- El Nido Ranch Rd and Upper Happy Valley Rd
- El Nido Ranch Rd and Lizann Dr
- Happy Valley Rd and Upper Happy Valley Rd
- Happy Valley Rd and Rose Ln
- Happy Valley Rd and Franklin Ln
- Happy Valley Rd and Panorama Dr
- Happy Valley Rd and Mt Diablo Blvd
- Hidden Valley Rd and Blackthorn Dr
- Hidden Valley Rd and Crest Rd
- Moraga Rd and Silver Springs Rd
- Moraga Rd and Oliver Ct
- Moraga Rd and Moraga Blvd
- Moraga Rd and Mt Diablo Blvd
- Moraga Rd and Brook St
- Moraga Rd and O'Conner Dr
- Moraga Rd and Herman Dr
- Moraga Rd and Tanglewood Dr
- Mt Diablo Blvd and Mt Diablo Ct
- Mt Diablo Blvd and Hampton Rd
- Mt Diablo Blvd and Stuart St
- Mt Diablo Blvd and Brown Ave
- Mt Diablo Blvd and Second St
- Mt Diablo Blvd and First St
- Mt Diablo Blvd and Moraga Rd
- Mt Diablo Blvd and Acalanes Rd
- Mt Diablo Blvd and Paulson Ct
- Mt Diablo Blvd and Lafayette Reservoir Recreational Area
- Mt Diablo Blvd and Village Center
- Mt Diablo Blvd and Gallagher
- Mt Diablo Blvd and Mountain View Dr
- Mt Diablo Blvd and Moraga Rd
- Mt Diablo Blvd and Golden Gate Way
- Mt Diablo Blvd and Second St
- Mt Diablo Blvd and Golden Gate Way
- Mt Diablo Blvd and Willow Dr
- Mt Diablo Blvd and Hampton Dr
- Mt Diablo Blvd and Carol Ln
- Mt Diablo Blvd and Mt Diablo Ct
- Mt Diablo Blvd and First St
- Pleasant Hill Rd and Hwy 24
- Rohrer Dr and Merriewood Dr
- St Mary's Rd and Acampo Dr
- St Mary's Rd and Hope Ln
- St Mary's Rd and Glenside Dr
- St Mary's Rd and Saint Mary's Ballfields
- St Mary's Rd and Woodview Dr
- St Mary's Rd and Lafayette Community Center
- St Mary's Rd and Rohrer Dr
- St Mary's Rd and Driftwood Dr
- St Mary's Rd and Cattle Chute Rd
- St Mary's Rd and Cattle Chute Rd
- St Mary's Rd and Driftwood Dr
- St Mary's Rd and Rohrer Dr
- St Mary's Rd and Lafayette Community Center
- St Mary's Rd and Glenside Dr
- St Mary's Rd and Glenside Dr
- St Mary's Rd and Hope Ln
- St Mary's Rd and Avalon Ave
- Stanley Blvd and Acalanes High School
- Upper Happy Valley Rd and Oleander Dr
- Upper Happy Valley Rd and N Peardale Dr
- Upper Happy Valley Rd and Rahara Dr
- Upper Happy Valley Rd and Los Arabis Dr
- VA Clinic
- Alhambra Ave and Wildcroft Dr
- Alhambra Ave and Macalvey Dr
- Alhambra Ave and John Muir Rd
- Alhambra Ave and Phylis Ter
- Alhambra Ave and Alhambra Way
- Alhambra Ave and Walnut Ave
- Alhambra Ave and K St
- Alhambra Ave and G St
- Alhambra Ave andC St-Contra Costa Regional Medical Center
- Alhambra Ave and Bertola St
- Alhambra Ave and Allen Dr
- Alhambra Ave and Jones St
- Alhambra Ave and Mellus St
- Alhambra Ave and C St-Contra Costa Regional Medical Center
- Alhambra Ave and F St
- Alhambra Ave and Franklin Creek
- Alhambra Ave and J St
- Alhambra Ave and Walnut Ave
- Alhambra Ave and Franklin Canyon Rd
- Alhambra Ave and Forest Way
- Alhambra Ave and Lindsey Dr
- Alhambra Ave and Wildcroft Dr
- Alhambra Ave and Glenview Dr
- Alhambra Ave and Benham Dr
- Alhambra Ave and Roanoke Dr
- Alhambra Ave and Starbucks
- Alhambra Ave and Devon Ave
- Arnold Dr and Muir Parkway Offices
- Arnold Dr and Fig Tree Ln
- Arnold Dr and Holiday Hills Dr
- Arnold Dr and Glacier Dr
- Arnold Dr and Milano Way
- Arnold Dr and Holiday Hills Dr
- Arnold Dr and Fig Tree Ln
- Arnold Dr and Muir Parkway Offices
- Berrellesa St and Mellus St
- Berrellesa St and Jones St
- Berrellesa St and Robinson St
- Berrellesa St and Soto St
- Howe Rd and Parkway Dr
- Howe Rd and Contra Costa Housing Choice Voucher Office
- Howe Rd and Buena Vida Ct
- Morello Ave and Arnold Dr
- Morello Ave and Midhill Rd
- Morello Ave and Marie Ave
- Morello Ave and Gilrix Ct
- Morello Ave and Marie Ave
- Morello Ave and Village Oaks Dr
- Morello Ave and Arnold Dr
- Muir Rd and Center Ave
- Muir Rd and Center Ave
- Muir Rd and Sweetwater Dr
- Muir Rd and Fountainhead Ct
- Muir Rd and Glacier Dr
- Muir Rd and Fountainhead Ct
- Muir Rd and Sweetwater Dr
- St Mary's College
- Moraga Rd and Moraga Way
- Moraga Rd and Alta Mesa Dr
- Moraga Rd and Corliss Dr
- Moraga Rd and Devin Dr
- Moraga Rd and Ascot Dr
- Moraga Rd and Kendall Cir
- Moraga Rd and Buckingham Dr
- Moraga Rd and Campolindo Dr
- Moraga Rd and Via Granada Dr
- Moraga Rd and Via Granada Dr
- Moraga Rd and Campolindo Dr
- Moraga Rd and Buckingham Dr
- and 972 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 | 76.2 | first check |
| 2026-08-07 | 76.2 | no change |
| 2026-08-22 | 83.0 | up 6.8 |
| 2026-08-23 | 83.0 | 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-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.
What changed over time
On 2026-08-06 this feed started at grade C. On 2026-08-22 the grade moved from C to B. On 2026-08-22 the check no longer reported: some route lines list the same point twice in a row; some service calendars in the feed have already ended; some rider-facing names are in ALL CAPS or all lowercase; on some trips the stops fall along the route line in a different order than the schedule lists. As of 2026-08-23 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-08-22 Grade went C to B, correctness rose 16 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning241 instances
241 of 1222 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)
- Warning53 instances
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
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · 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 (the file itself is absent)
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
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)
- Info3 instances
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)
- Info2 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)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · 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) Different (allowed)
- Your feed's agency_id is 2; your National Transit Database ID is 90078. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 2 to NTD ID 90078, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 1553 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 80% 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 80% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 1 of 1215 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 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.
In Tennessee, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (4 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 80% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 1553 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 78 / 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 88 / 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/county-connection-cccta-2421/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.