Mountain Line

What changed since the last check

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

Top three things to fix

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

   Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

   Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. 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.

NTD certification readiness: Not ready

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

Published Ready

Published at a public URL.

Valid Needs attention

6 validator errors to resolve.

Current Not ready

Service data expired 192 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://transitfeeds.com/p/mountain-line/243/latest/download

Last checked

2026-07-09

Service window

Feed has expired. Last service date 2025-12-28.

State

Arizona