Board packet · transit data quality · checked 2026-10-07
Dallas Area Rapid Transit (DART)
Grade F · 21.9 / 100
Down 0.5 points since 2026-10-06 (F to F).
What this grade measures
The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.
Progress this period
No newly cleared items this period. The score and trend above reflect where the feed stands today.
What needs attention next
Three improvements, in priority order, each sized so the board can see what it is approving:
Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 11 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
This one is about the feed as a whole, so there is no share of it to count.
Estimated 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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Estimated 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 transit vehicles jumping backwards or mis-order stops.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Estimated effort: Usually an export-tool fix, not hand editing.
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Texas as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data runs out in 11 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Trip distance exceeds shape distance (flagged by the MobilityData validator).
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/dallas-area-rapid-transit-dart/. Rubric v1.4, validator 8.0.1.