Feed status · checked 2026-08-01
County Connection (CCCTA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
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 3 hours ago; last fetch returned HTTP 403.
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
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 931 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 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 (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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +8 points in its category
This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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
- Service data ended 931 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- 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 (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 rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 was 931 days ago.
- Published accessibility data
- Accessibility information is stated for 83.7% 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
This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 9 kinds of issue across 731 instances (0 error, 728 warning, 3 informational).
Service data ended 931 day(s) ago. Trip planners have likely already dropped this feed.
84% of stops state wheelchair accessibility (0% marked accessible, 84% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
84% 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 (1, 10, 15, 17, 18, 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.
1407 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("N California Blvd + Lacassie Ave", "Locust St + Civic Dr", "N Main St + Civic Dr", 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 1492 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 ROUTE 1 | Bus | teal |
| 10 ROUTE 10 | Bus | teal |
| 11 ROUTE 11 | Bus | gray |
| 14 ROUTE 14 | Bus | gray |
| 15 ROUTE 15 | Bus | teal |
| 16 ROUTE 16 | Bus | gray |
| 17 ROUTE 17 | Bus | teal |
| 18 ROUTE 18 | Bus | teal |
| 19 ROUTE 19 | Bus | teal |
| 20 ROUTE 20 | Bus | teal |
| 21 ROUTE 21 | Bus | teal |
| 28 ROUTE 28 | Bus | teal |
| 301 ROUTE 301 | Bus | purple |
| 310 ROUTE 310 | Bus | purple |
| 311 ROUTE 311 | Bus | gray |
| 314 ROUTE 314 | Bus | gray |
| 315 ROUTE 315 | Bus | purple |
| 316 ROUTE 316 | Bus | gray |
| 320 ROUTE 320 | Bus | purple |
| 321 ROUTE 321 | Bus | purple |
| 335 ROUTE 335 | Bus | purple |
| 35 ROUTE 35 | Bus | teal |
| 4 ROUTE 4 | Bus | gray |
| 5 ROUTE 5 | Bus | gray |
| 6 ROUTE 6 | Bus | teal |
| 601 ROUTE 601 | Bus | gray |
| 602 ROUTE 602 | Bus | gray |
| 605 ROUTE 605 | Bus | gray |
| 606 ROUTE 606 | Bus | gray |
| 611 ROUTE 611 | Bus | gray |
| 612 ROUTE 612 | Bus | gray |
| 613 ROUTE 613 | Bus | gray |
| 615 ROUTE 615 | Bus | gray |
| 616 ROUTE 616 | Bus | gray |
| 619 ROUTE 619 | Bus | gray |
| 622 ROUTE 622 | Bus | gray |
| 623 ROUTE 623 | Bus | gray |
| 625 ROUTE 625 | Bus | gray |
| 626 ROUTE 626 | Bus | gray |
| 635 ROUTE 635 | Bus | gray |
| 636 ROUTE 636 | Bus | gray |
| 7 ROUTE 7 | Bus | gray |
| 9 ROUTE 9 | Bus | teal |
| 91X ROUTE 91X | Bus | orange |
| 92X ROUTE 92X | Bus | orange |
| 93X ROUTE 93X | Bus | orange |
| 95X ROUTE 95X | Bus | orange |
| 96X ROUTE 96X | Bus | orange |
| 97X ROUTE 97X | Bus | orange |
| 98X ROUTE 98X | Bus | orange |
| 99X ROUTE 99X | Bus | gray |
List every stop
- Arnold Industrial Way + Industrial Way
- Center Ave + Raymond Dr
- Center Ave + Kaiser Dr
- Center Ave + Public Health Services California
- Howe Rd + Buena Vida Ct
- Muir Rd + Center Ave
- Bishop Ranch 15
- Hartz Ave + Prospect Ave
- Boulevard Way + Nicholson Rd
- Boulevard Way + Saranap Ave
- Boulevard Way + Olympic Blvd
- Castlehill Rd + Garland Ct
- Castlehill Rd + Arbol Grande
- Tice Valley Blvd + Tice Valley Ln
- Walnut Creek BART
- Montego + Tampico
- Montego + Tampico
- Ygnacio Valley Rd + Walnut Blvd
- Walnut Blvd + Ygnacio Valley Rd
- Newell Ave + S Main St
- Canyon Rd + De La Cruz Way
- San Miguel Dr + Blackwood Dr
- Parkside Dr + San Juan Ave
- Buena Vista Ave + Parkside Dr
- Buena Vista Ave + San Luis Rd
- Buena Vista Ave + Third Ave
- Buena Vista Ave + Second Ave
- Viking Dr + Odin Dr
- Walnut Blvd + Ygnacio Valley Rd
- Mountain View Blvd + Mynah Ct
- Concord Blvd + Grant St
- Gateway Blvd + Willow Pass Rd
- Clayton Rd + Ellis St
- Clayton Rd + Mitchell Canyon Rd
- Michigan Blvd + Washington Blvd
- Michigan Blvd + Round Tree Way
- Clayton Rd + Silverleaf Ln
- Clayton Rd + Indian Ln
- Clayton Rd + Bailey Rd
- Clayton Rd + Glazier Dr
- Clayton Rd + Denkinger Ct
- Clayton Rd + Mendocino Dr
- Clayton Rd + West St
- Clayton Rd + Maynard St
- Clayton Rd + Barbis Way
- Clayton Rd + Sixth St
- Clayton Rd + Fifth St
- Clayton Rd + Washington Blvd
- Ygnacio Valley Rd + Park Highlands
- Pennsylvania Blvd + Colorado Dr
- Monument Blvd + Mohr Ln
- Crescent Plz + Cleaveland Rd
- Contra Costa Blvd + East Vivian Dr
- Diablo Rd + Green Valley Shopping Center
- Sycamore Valley Rd + Brookside Dr
- Crow Canyon Rd + Shoreline Dr
- Crow Canyon Rd + Alcosta Blvd
- Crow Canyon Rd + Camino Ramon
- Danville Blvd + Alamo Plaza
- Pleasant Hill Rd + Condit Rd
- Alcosta Blvd + Terra Alta Dr
- Alcosta Blvd + Bollinger Canyon Rd
- Mt Diablo Blvd + Carol Ln
- Bishop Ranch 2600
- San Ramon Transit Center
- Concord BART
- Willow Pass Rd + Sixth St
- Willow Pass Rd + Farm Bureau Rd
- Treat Blvd + Lancelot Dr
- Treat Blvd + Cowell Rd
- Treat Blvd + Navaronne Way
- Treat Blvd + Carriage Dr
- Mt Diablo Blvd + Second St
- Walnut Creek BART
- N Civic Dr + Walden Rd
- Happy Valley Rd + Mt Diablo Blvd
- Willow Pass Rd + Ashdale Dr
- Walnut Creek BART
- Alhambra Ave + Roanoke Dr
- St Mary's Rd + Lafayette Community Center
- St Mary's Rd + Rohrer Dr
- Pacheco Blvd + Camino Del Sol
- Pacheco Blvd + Arthur Rd
- Danville Blvd + Hillgrade Ave
- N Main St + Civic Dr
- UFCW and Employers Plaza
- Mt Diablo Blvd + Lafayette Cir
- San Miguel Dr + Mountain View Blvd
- Concord Blvd + Yvonne Dr
- Pleasant Hill Rd + Old Tunnel Rd
- Pleasant Hill Rd + Hwy 24
- Rohrer Dr + Merriewood Dr
- Happy Valley Rd + Upper Happy Valley Rd
- Upper Happy Valley Rd + N Peardale Dr
- Upper Happy Valley Rd + Rahara Dr
- Upper Happy Valley Rd + Los Arabis Dr
- El Nido Ranch Rd + Upper Happy Valley Rd
- Creekside Dr + End
- Locust St + Bonanza St
- Locust St + Peets Coffee
- Mt Diablo Blvd + Locust St
- Broadway Plz + Macys
- Broadway Plz + S Main St
- Bothelho Dr + Locust St
- Locust St + Olympic Blvd
- Locust St + Mt Diablo Blvd
- N Main St + Duncan St
- N Main St + Bonanza St
- N Main St + Arroyo Way
- Pringle Ave + N Main St
- Contra Costa Blvd + Golf Club Rd
- Contra Costa Blvd + Viking Dr
- Sun Valley Blvd + Santa Monica Dr
- Willow Pass Rd + Diamond Blvd
- Willow Pass Rd + Franquette Ave
- Gateway Blvd + Clayton Rd
- Clayton Rd + Galindo St
- Oak St + Galindo St
- Concord BART
- Clayton Rd + San Carlos Ave
- Clayton Rd + Fifth Ave
- Clayton Rd + Coventry Rd
- Clayton Rd + Davis Ave
- Clayton Rd + Grove Way
- Clayton Rd + Babel Ln
- Clayton Rd + Farm Bureau Rd
- Clayton Rd + Loeffler Ln
- Clayton Rd + Cape Cod Way
- Clayton Rd + Bel Air Dr
- Clayton Rd + Wharton Way
- Clayton Rd + Bailey Rd
- Clayton Rd + Indian Ln
- Clayton Rd + Claycord Ave
- Clayton Rd + Ayers Rd
- Clayton Rd + Alberta Way
- Clayton Rd + Hospice Thrift Shoppes
- Clayton Rd + Ygnacio Valley Rd
- Clayton Rd + El Camino Dr
- Center St + Easley Dr
- Marsh Creek Rd + Greystone Rd
- Mountaire Pkwy + Mountaire Cir
- Mountaire Cir + Mountaire Pkwy
- Mountaire Cir + Mt Hamilton Ct
- Mountaire Cir + Mt Washington Way
- Mountaire Cir + Mt Scott Ct
- Mountaire Pkwy + Marsh Creek Rd
- Marsh Creek Rd + El Molino Dr
- Marsh Creek Rd + Bigelow St
- Clayton Rd + Peacock Creek Dr
- Clayton Rd + Clayton Library
- Mt Diablo Blvd + Happy Valley Rd
- Clayton Rd + Kirker Pass Rd
- Clayton Rd + Schenone Ct
- Clayton Rd + Terry Lynn Ln
- Clayton Rd + Ayers Rd
- Clayton Rd + Claycord Ave
- Clayton Rd + Thornwood Dr
- Clayton Rd + Farm Bureau Rd
- Clayton Rd + Grove Way
- Clayton Rd + The Alameda
- Clayton Rd + Denkinger Ct
- Clayton Rd + Newhall Pkwy
- Clayton Rd + Atchison Stage Rd
- Clayton Rd + Mitchell Canyon Rd
- Marsh Creek Rd + High St
- Ayers Rd + Clayton Rd
- Ayers Rd + Sutherland Dr
- Ayers Rd + Olive Dr
- Concord Blvd + Ayers Rd
- Concord Blvd + Meadow Pine Ct
- Concord Blvd + Mariposa Ct
- Concord Blvd + Yvonne Ct
- Concord Blvd + Cantrell Ct
- Kirkwood Dr + Kirker Pass Rd
- Kirkwood Dr + Preston Ct
- Kirkwood Dr + Yardley Ct
- Kirkwood Dr + Jamison Ct
- 1887 Camino Estrada
- Camino Estrada + Sepulveda Ct
- Camino Estrada + Pamplona Ct
- Camino Estrada + Concord Blvd
- Oakhurst Dr + Yolanda Cir
- Oakhurst Dr + Indian Wells Way
- Oakhurst Dr + Indian Wells Way
- Oakhurst Dr + Indianhead Way
- Washington Blvd + Kelrose Ct
- Pennsylvania Blvd + Washington Blvd
- Pennsylvania Blvd + Highlands Park
- Pine Hollow Rd + Pine Hollow School
- Pine Hollow Rd + Redlands Way
- Michigan Blvd + El Camino Dr
- Marchbanks Dr + Crosby Ct
- Michigan Blvd + Maryland Dr
- Michigan Blvd + Pennsylvania Blvd
- Michigan Blvd + Nebraska Ave
- Marsh Creek Rd + Clayton Rd
- Oakhurst Dr + Indianhead Way
- Oakhurst Dr + Eagle Peak Ave
- Oakhurst Dr + Eagle Peak Ave
- Oakhurst Dr + Yolanda Cir
- Concord Blvd + Alicante Ct
- Concord Blvd + Kirker Pass Rd
- Concord Blvd + Lodato Way
- Concord Blvd + Princeton Ct
- Ayers Rd + Clayton Rd
- Kirker Pass Rd + Olive Dr
- Michigan Blvd + New Hampshire Dr
- Michigan Blvd + Kentucky Dr
- Michigan Blvd + Louisiana Dr
- Washington Blvd + Pennsylvania Blvd
- Clayton Rd + Fry Way
- Sun Valley Blvd + Contra Costa Blvd
- Heather Dr + N San Carlos Dr
- Alberta Way + Clayton Rd
- Washington Blvd + Kelrose Ct
- Mt Diablo St + Oakland Ave
- Mt Diablo St + San Carlos Ave
- Mt Diablo St + Fifth St
- Mt Diablo St + Coventry Rd
- Coventry Rd + Cowell Rd
- Cowell Rd + Quail Ct
- Cowell Rd + St Francis Dr
- Cowell Rd + Mcmullin Dr
- Cowell Rd + Kaski Ln
- Treat Blvd + Cowell Rd
- Turtle Creek Rd + Sussex Way
- Turtle Creek Rd + Big Pine Ln
- Turtle Creek Rd + Bent Tree Ln
- N Larwin Ave + Rising Dawn Ln
- N Larwin Ave + N Prairie Willow Ct
- N Larwin Ave + N Red Maple Ct
- S Larwin Ave + Wildberry Ct
- S Larwin Ave + Leatherwood Ct
- S Larwin Ave + Oakbrook Ct
- S Larwin Ave + Deerberry Ct
- S Larwin Ave + Juneberry Ct
- S Larwin Ave + Kenneth Rd
- Concord Blvd + Ayers Rd
- Concord Blvd + Concord Ct
- Concord Blvd + Bailey Rd
- Concord Blvd + Thornwood Dr
- Concord Blvd + Jefferson St
- Concord Blvd + Crestwood Cir
- Concord Blvd + Dave Brubeck Park
- Concord Blvd + Mendocino Dr
- Concord Blvd + Sattler Dr
- Concord Blvd + Margo Dr
- Concord Blvd + Alray Dr
- Concord Blvd + Farm Bureau Rd
- 3425 Concord Blvd
- and 1242 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 | 51.9 | first check |
| 2026-07-30 | 51.9 | no change |
| 2026-07-31 | 51.9 | no change |
| 2026-08-01 | 51.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
13 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 931 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning365 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)
- Warning278 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)
- Warning243 instances
243 of 1492 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)
- Warning75 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)
- Warning5 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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 service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · 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)
- 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)
- 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 Not ready
Resolve this before you certify on the D-10. Service data expired 931 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 931 days ago, so FTA would find the link out of date.
- 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 3254 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. Service data expired 931 days ago. States wheelchair access on 84% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 931 days ago.
- Accessible Not yet
- States wheelchair access on 84% 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.
- 278 of 1492 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 California, 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 84% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 3254 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- 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 0 / 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/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.