Capitol Corridor Joint Powers Authority (Capitol Corridor)

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

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

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

   Estimated effort: Two fields, set once in export settings.

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

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

   Estimated effort: A field at a time; not urgent.

   Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).

Where this agency stands

Ahead of 51% of all tracked agencies, and ahead of 50% of small agencies nationwide.