← All agencies

Feed status · checked 2026-08-01

County Connection (CCCTA)

Based on the feed this agency publishes

Service mode Bus

53.7 / 100

unchanged since 2026-07-31

Catalogued in Tennessee.

Expires in 7 daysRealtime not yet published

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 79 minutes ago; last changed 34 days ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

Service data runs out in 7 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

⏱ One export setting.worth about +73 points in its category

Fix 02

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

Fix 03

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool

Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

⏱ Usually one export setting.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
Service data runs out in 7 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
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.

  1. Re-export with a validity window that reaches at least 60 days out. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 7 days.
Published accessibility data
Accessibility information is stated for 84.6% 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.

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

Correctness59.5 / 100

The MobilityData validator flagged 7 kinds of issue across 68088 instances (0 error, 68086 warning, 2 informational).

Freshness0.0 / 100

Service data runs out in 7 day(s). Publish an updated feed soon or riders will lose trip planning.

Rider experience88.6 / 100

85% of stops state wheelchair accessibility (84% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility90.4 / 100

85% of stops state accessibility (84% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (11, 14, 16, 311, 314, 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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 948 stops.

Skip to route and stop data

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)
  • 7 (gray)
  • 9 (teal)
  • 91X (orange)
  • 92X (orange)
  • 93X (orange)
  • 95X (orange)
  • 96X (orange)
  • 97X (orange)
  • 98X (orange)
  • 99X (gray)
Routes in County Connection (CCCTA)'s feed
RouteTypeLine color
1 Rossmoor/ShadelandsBusteal
10 Concord BART/Clayton RdBusteal
11 Concord BART/Pleasant Hill BARTBusgray
14 Concord BART/Walnut Creek BARTBusgray
15 Concord BART/Pleasant Hill BARTBusteal
16 Martinez Amtrak/Concord BARTBusgray
17 Concord BART/North Concord BARTBusteal
18 Martinez Amtrak/Pleasant Hill BARTBusteal
19 Martinez Amtrak/Concord BARTBusteal
20 DVC/Concord BARTBusteal
21 Walnut Creek BART/San RamonBusteal
28 Concord BART/AmtrakBusteal
301 Walnut Creek BART/N Via MonteBuspurple
310 Concord BART/Clayton RdBuspurple
311 Concord BART/Walnut Creek BARTBusgray
314 Concord BART/DVCBusgray
315 Concord BART/Bel Air DrBuspurple
316 Martinez Amtrak/Pleasant Hill BARTBusgray
320 DVC/Concord BARTBuspurple
321 Walnut Creek BART/San RamonBuspurple
335 Dublin BART/San RamonBuspurple
35 Dublin/Pleasanton BART/San RamonBusteal
4 Walnut Creek BART/Broadway PlazaBusgray
5 Walnut Creek BART/Creekside DrBusgray
6 Lafayette BART/Orinda BARTBusteal
7 Pleasant Hill BART/ShadelandsBusgray
9 DVC/Walnut Creek BARTBusteal
91X Concord Commuter ExpressBusorange
92X Pleasanton ACE/Mitchell DrBusorange
93X Walnut Creek BART/Antioch BARTBusorange
95X San Ramon/BART Walnut CreekBusorange
96X BART Walnut Creek/Bishop RanchBusorange
97X Dublin BART/Bishop RanchBusorange
98X Martinez Amtrak/Walnut Creek BARTBusorange
99X Martinez Amtrak/North Concord BARTBusgray
List every stop
  • 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
  • Solano Way and Imhoff Rd
  • S Main St and Crest Ave
  • S Main St and Rudgear Rd
  • Tice Valley Blvd and Byron Park
  • Tice Valley Blvd and Westborough Ln
  • Tice Valley Blvd and Olympic Blvd
  • Pleasant Hill BART
  • Pleasant Hill BART
  • Pleasant Hill BART
  • Pleasant Hill BART
  • Pleasant Hill BART
  • Danville Park and Ride
  • 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
  • Railroad Ave and Love Ln and Linda 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 and Country 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
  • Dublin Pleasanton BART
  • Lafayette BART
  • 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 Moraga Rd
  • Mt Diablo Blvd and Moraga Rd
  • 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 and C 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 Pacheco Blvd
  • 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
  • Moraga Rd and Kendall Cir
  • Moraga Rd and Ascot Dr
  • Moraga Rd and Devin Dr
  • Moraga Rd and Corliss Dr
  • Moraga Rd and Alta Mesa Dr
  • Moraga Rd and Moraga Way
  • Moraga Way and School St
  • Moraga Way and Camino Ricardo
  • Moraga Way and Hardie Dr
  • Moraga Way and Miramonte Dr
  • Moraga Way and St Andrews Dr
  • Moraga Way and Viader Dr
  • St Mary'S Rd and Moraga Library
  • St Mary'S Rd and Carter Dr
  • St Mary'S Rd and Carter Dr
  • St Mary'S Rd and Moraga Library
  • Orinda BART
  • Camino Pablo and Brookwood Rd
  • Camino Pablo and Moraga Way
  • Moraga Way and Orchard Rd
  • Moraga Way and Mcdonnell Nursery
  • Moraga Way and Casa Vieja
  • Moraga Way and Los Cerros
  • Moraga Way and Oak Dr
  • Moraga Way and Valley View Dr
  • Moraga Way and Woodland Rd
  • Moraga Way and Ivy Dr
  • Moraga Way and Southwaite Ct
  • Moraga Way and El Camino Moraga
  • Moraga Way and El Corte
  • Moraga Way and Estabueno
  • Moraga Way and Coral Dr
  • Moraga Way and Whitehall Dr
  • Moraga Way and Southwaite Ct
  • Moraga Way and Ivy Dr
  • Moraga Way and Hall Dr
  • Moraga Way and Ardor Dr
  • Moraga Way and Holy Shepherd Lutheran Church
  • Moraga Way and Glorietta Blvd
  • Moraga Way and Brookside Dr
  • Moraga Way and Orchard Rd
  • Moraga Way and Eastwood Dr
  • Orinda Way and Orinda Library
  • Orinda Way and Orinda Community Center
  • Orinda Way and Irwin Way
  • Orinda Way and Avenida De Orinda
  • Ellinwood Way and Contra Costa Employment Human Services
  • Alhambra Ave and Rockridge Dr
  • Alhambra Ave and Shetland Dr
  • Alhambra Ave and Elderwood Dr
  • Alhambra Ave and Heritage Oaks Dr
  • Boyd Rd and Patterson Rd
  • Boyd Rd and Campbell Ln
  • Boyd Rd and Cleaveland Rd
  • Boyd Rd and Sequoia Elementary School
  • Buskirk Ave and Mayhew Way
  • Buskirk Ave and Lamkin Ln
  • Buskirk Ave and The Crossroads
  • Buskirk Ave and Mayhew Way
  • Chilpancingo Pkwy and Contra Costa Blvd
  • Chilpancingo Pkwy and Contra Costa Blvd
  • Cleaveland Rd and Boyd Rd
  • Cleaveland Rd and Crescent Plz
  • Cleaveland Rd and Trelany Rd
  • Cleaveland Rd and Crescent Plz
  • Coggins Dr and Villa Montanaro
  • Coggins Dr and Park Vista Apartments
  • Contra Costa Blvd and Golf Club Rd
  • Contra Costa Blvd and S and G Carpet and More
  • Contra Costa Blvd and Chipotle Mexican Grill
  • Contra Costa Blvd and Cottonwood Dr
  • Contra Costa Blvd and Viking Dr
  • Contra Costa Blvd and East Vivian Dr
  • Contra Costa Blvd and Beth Dr
  • Contra Costa Blvd and Dexter Dr
  • Contra Costa Blvd and Harriet Dr
  • Contra Costa Blvd and Safeway
  • Contra Costa Blvd and Harriet Dr
  • Contra Costa Blvd and Ellinwood Dr
  • Contra Costa Blvd and Doray Dr
  • Contra Costa Blvd and Doris Dr
  • Contra Costa Blvd and Vivian Dr
  • Contra Costa Blvd and Woodsworth Ln
  • Crescent Plz and Crescent Dr
  • Crescent Plz and Cleaveland Rd
  • Crescent Plz and Cleaveland Rd
  • Crescent Plz and Crescent Dr
  • Ellinwood Dr and Longbrook Way
  • Golf Club Rd and College Dr
  • Monument Blvd and Contra Costa Blvd
  • Gregory Ln and Contra Costa Blvd
  • Gregory Ln and Cleaveland Rd
  • Gregory Ln and Moiso Ln
  • Gregory Ln and Kahrs Ave
  • Gregory Ln and Helen Rd and Brandon Rd
  • Gregory Ln and Brandon Rd
  • Gregory Ln and Pleasant Hill Rd
  • Gregory Ln and Brandon Rd
  • Gregory Ln and Rolling Green Cir
  • Gregory Ln and Kahrs Ave
  • Gregory Ln and Price Ln
  • Gregory Ln and Moiso Ln
  • Gregory Ln and Cleaveland Rd
  • Gregory Ln and Contra Costa Blvd
  • Morello Ave and Taylor Blvd
  • and 698 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.

2026-07-25: 55.82026-07-30: 53.72026-07-31: 53.72026-08-01: 53.7
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2555.8 first check
2026-07-3053.7 down 2.1
2026-07-3153.7 no change
2026-08-0153.7 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-31.

Same feed file as 2026-07-31; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

12 findings, ordered by severity.

Show every finding
  • Warning60889 instances

    Some route lines list the same point twice in a row.

    Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning6996 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning146 instances

    146 of 948 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)

  • Warning134 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)

  • Warning37 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)

  • Warning29 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)

  • 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

    Service data runs out in 7 day(s).

    When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

    Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

    Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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)

  • 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

    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 Needs attention

This feed is close to NTD-ready. Service data runs out in 7 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Needs attention
Service data runs out in 7 days; renew before you certify.
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 1498 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 runs out in 7 days; renew to qualify. States wheelchair access on 85% of stops and 100% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Not yet
Service data runs out in 7 days; renew to qualify.
Accessible Not yet
States wheelchair access on 85% 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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 7 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.

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 60 / 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 89 / 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.

County Connection (CCCTA) GTFS data quality grade: F

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-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.