Altamont Corridor Express

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 578 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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.

2. Add the required column named in the finding to the flagged file.

   A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

   Effort: Often an export setting; ask your vendor if it recurs.

3. Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

Ready to send to the agency

Hi Altamont Corridor Express team, Service data ended 578 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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/altamont-corridor-express/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 578 days ago, so FTA would find the link out of date.

Published Ready

Published at a public URL.

Valid Needs attention

2 validator errors to resolve.

Current Not ready

Service data expired 578 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 NTD ID (optional): Different (allowed). Your feed's agency_id is CE; your National Transit Database ID is 90182. 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 CE to NTD ID 90182, and keep the feed value stable. Do not change it solely to make the two values equal.

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/altamont-corridor-express/823/latest/download

Last checked

2026-08-01

Service window

Feed has expired. Last service date 2024-12-31.

Feed version

20231226

Location

California