Call-prep brief · checked 2026-07-11
Dallas Area Rapid Transit (DART)
Grade F · 20.7 / 100
Down 0.4 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.7
- Rider experience 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 8 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.
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.
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.
Ready to send to the agency
Hi Dallas Area Rapid Transit (DART) team, Service data runs out in 8 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/dallas-area-rapid-transit-dart-152/
NTD GTFS readiness: Needs attention
This feed is close to NTD-ready. 2 validator errors to resolve. Service data runs out in 19 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Needs attention
- Service data runs out in 19 days; renew before you certify.
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
- http://www.dart.org/transitdata/latest/google_transit.zip
- Last checked
- 2026-07-11
- Service window
- 8 days of service data remain. Last service date 2026-07-19.
- Feed version
- V702-215-214-20260608
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.