Call-prep brief · checked 2026-07-09
Capitol Corridor Joint Powers Authority (Capitol Corridor)
Grade D · 61.1 / 100
Unchanged since 2026-07-08.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
Top three 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.
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.
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).
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).
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.
Effort: A field at a time; not urgent.
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Ready to send to the agency
Hi Capitol Corridor Joint Powers Authority (Capitol Corridor) team, 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. 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/capitol-corridor-joint-powers-authority-capitol-corridor/
NTD certification readiness: Not ready
Resolve this before you certify on the D-10. Service data expired 1100 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 1100 days ago, so FTA would find the link out of date.
agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
Key facts
- Feed URL
- https://www.capitolcorridor.org/googletransit/GTFS.zip
- Last checked
- 2026-07-09
- Service window
- Feed has expired. Last service date 2023-06-30.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.