Santa Clarita Transit

What changed since the last check

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

Top three things to fix

1. Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.

   Neither feed_info.txt nor the calendars state when service ends. Nobody can tell when this feed will go stale.

   Effort: Likely a one-time export setting.

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

   Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

   Invalid input files in subfolder (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. 3 validator errors to resolve. No service end date could be read, so currency is unknown.

Published Ready

Published at a public URL.

Valid Needs attention

3 validator errors to resolve.

Current Not ready

No service end date could be read, so currency is unknown.

agency_id and NTD ID: Not aligned. Your agency.txt sets no agency_id, so this feed can't be lined up automatically with your National Transit Database record (NTD ID 90171). Optionally set agency_id to 90171 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 the two on your P-50 form.

Key facts

Feed URL

https://gitlab.com/LACMTA/gtfs_lax/-/archive/master/gtfs_lax-master.zip?path=santa_clarita

Last checked

2026-06-27

Service window

Expiry date not stated in the feed.