County Connection (CCCTA)

What changed since the last check

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

Top three things to fix

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

   Service data ended 908 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.

   Effort: Usually one export setting; export on a schedule so it never lapses again.

   Agencies here usually clear this within about 1 week (based on 18 observed fixes).

2. Add feed_info.txt with feed_start_date and feed_end_date to your export.

   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.

   Effort: Two fields, set once in export settings.

   Agencies here usually clear this within about 1 week (based on 16 observed fixes).

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   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.

   Effort: Often a bulk fix in your scheduling software.

Ready to send to the agency

Hi County Connection (CCCTA) team, Service data ended 908 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. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/county-connection-cccta/

Copy this note from the full scorecard.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. Service data expired 907 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 907 days ago, so FTA would find the link out of date.

agency_id and NTD ID: Not aligned. 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, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90078 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL

https://transitfeeds.com/p/county-connection/222/latest/download

Last checked

2026-07-09

Service window

Feed has expired. Last service date 2024-01-13.

State

California