Call-prep brief · checked 2026-07-11

Orange County Transportation Authority (OCTA)

Grade F · 45.8 / 100

Down 0.3 points since 2026-07-10 (F to F).

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 down 1.6
Rider experience no change
Realtime quality no change

Top three things to fix

Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 28 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Effort: One export setting.
Re-generate shape distances in your export; flag to your vendor if it persists.
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
Effort: Usually an export-tool fix, not hand editing.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Effort: Usually a vendor support ticket.

Ready to send to the agency

Hi Orange County Transportation Authority (OCTA) team, Service data runs out in 28 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. 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/orange-county-transportation-authority-octa-15/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready: Published at a public URL.
Valid Needs attention: 1 validator error to resolve.
Current Ready: Service data covers the next 39 days.

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.octa.net/current/google_transit.zip
Last checked: 2026-07-11
Service window: 28 days of service data remain. Last service date 2026-08-08.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.