Rail

What changed since the last check

• Correctness down 18.0
• Freshness no change
• Rider experience no change

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 14 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.

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

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

   Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   463 of 463 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Effort: A column in stops.txt; your scheduling software likely has it.

Ready to send to the agency

Hi Rail team, Service data runs out in 14 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/los-angeles-county-metropolitan-transportation-authority-la-metro-30/

Copy this note from the full scorecard.

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 14 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Needs attention

Service data runs out in 14 days; renew before you certify.

agency_id and NTD ID: Not aligned. Your feed's agency_id is LACMTA_Rail; your National Transit Database ID is 90154. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90154 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 agency_id to your NTD ID on your P-50 form.

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://gitlab.com/LACMTA/gtfs_rail/raw/master/gtfs_rail.zip

Last checked

2026-07-09

Service window

14 days of service data remain. Last service date 2026-07-23.

State

California