Feed status · checked 2026-08-01
Dallas Area Rapid Transit (DART)
Based on the feed this agency publishes
Service mode Tram + Rail + 2 more
down 0.4 since 2026-07-31
Catalogued in Texas.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 79 minutes ago; last changed 15 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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.
⏱ Varies.worth about +24 points in its category
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show transit vehicles jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +24 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
22230 of 22230 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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
- 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
- Feed evidence
- 22230 of 22230 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
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.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Re-generate shape distances in your export; flag to your vendor if it persists.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 43 days.
- Published accessibility data
- Accessibility information is stated for 41.8% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 16 kinds of issue across 31001 instances (1039 error, 29954 warning, 8 informational).
Service data covers the next 43 days.
42% of stops state wheelchair accessibility (42% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
42% of stops state accessibility (42% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
75 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (001, 003, 005, 009, 013, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
6834 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("FOREST @ SHEPHERD - E - NS", "WALNUT HILL @ RAMBLER - W - MB", "WALNUT HILL @ GREENVILLE - E - MB", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 6974 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 001 (yellow)
- 003 (yellow)
- 005 (yellow)
- 009 (yellow)
- 013 (yellow)
- 015 (yellow)
- 016 (yellow)
- 017 (yellow)
- 018 (yellow)
- 020 (yellow)
- 022 (yellow)
- 023 (yellow)
- 025 (yellow)
- 027 (yellow)
- 030 (yellow)
- 038 (yellow)
- 057 (yellow)
- 101 (purple)
- 102 (purple)
- 103 (purple)
- 104 (purple)
- 106 (purple)
- 108 (purple)
- 109 (purple)
- 114 (purple)
- 122 (purple)
- 128 (purple)
- 141 (purple)
- 145 (purple)
- 147 (purple)
- 200 (teal)
- 202 (teal)
- 203 (teal)
- 204 (teal)
- 205 (teal)
- 207 (teal)
- 212 (teal)
- 213 (teal)
- 214 (teal)
- 215 (teal)
- 216 (teal)
- 217 (teal)
- 218 (teal)
- 219 (teal)
- 220 (teal)
- 221 (teal)
- 223 (teal)
- 224 (teal)
- 226 (teal)
- 227 (teal)
- 228 (teal)
- 229 (teal)
- 230 (teal)
- 231 (teal)
- 232 (teal)
- 233 (teal)
- 234 (teal)
- 235 (teal)
- 236 (teal)
- 237 (teal)
- 238 (teal)
- 239 (teal)
- 241 (teal)
- 242 (teal)
- 243 (teal)
- 244 (teal)
- 245 (teal)
- 247 (teal)
- 249 (teal)
- 250 (teal)
- 251 (teal)
- 306 (pink)
- 308 (pink)
- 408 (gray)
- 413 (gray)
- 417 (gray)
- 419 (gray)
- 421 (gray)
- 422 (gray)
- 423 (gray)
- 425 (brown)
- 440 (gray)
- 442 (gray)
- 883E (gray)
- 883W (gray)
- 620 (black)
- BLUE (teal)
- GREEN (green)
- ORANGE (orange)
- RED (red)
- SILVER (white)
- TRE (black)
| Route | Type | Line color |
|---|---|---|
| 001 MALCOLM X/MAPLE | Bus | yellow |
| 003 ROSS | Bus | yellow |
| 005 LOVE FIELD SHUTTLE | Bus | yellow |
| 009 JEFFERSON GASTON | Bus | yellow |
| 013 ERVAY | Bus | yellow |
| 015 BUCKNER | Bus | yellow |
| 016 FERGUSON | Bus | yellow |
| 017 SKILLMAN | Bus | yellow |
| 018 SAMUELL | Bus | yellow |
| 020 NORTHWEST HWY | Bus | yellow |
| 022 FOREST LANE | Bus | yellow |
| 023 HASKELL | Bus | yellow |
| 025 COCKRELL HILL NORTH | Bus | yellow |
| 027 RIDGECREST | Bus | yellow |
| 030 LAKE JUNE | Bus | yellow |
| 038 LEDBETTER | Bus | yellow |
| 057 WESTMORELAND | Bus | yellow |
| 101 HAMPTON | Bus | purple |
| 102 FORT WORTH | Bus | purple |
| 103 CEDAR SPRINGS | Bus | purple |
| 104 ILLINOIS | Bus | purple |
| 106 BICKERS | Bus | purple |
| 108 CAMP WISDOM | Bus | purple |
| 109 BECKLEY | Bus | purple |
| 114 EAST OAK CLIFF | Bus | purple |
| 122 RECORD CROSSING | Bus | purple |
| 128 SINGLETON | Bus | purple |
| 141 BONNIE VIEW | Bus | purple |
| 145 MARSALIS | Bus | purple |
| 147 POLK | Bus | purple |
| 200 SPRING VALLEY | Bus | teal |
| 202 BUCKINGHAM | Bus | teal |
| 203 CENTERVILLE | Bus | teal |
| 204 MILLER | Bus | teal |
| 205 HENDERSON | Bus | teal |
| 207 LEMMON | Bus | teal |
| 212 LA PRADA | Bus | teal |
| 213 HARRY HINES | Bus | teal |
| 214 LINDSLEY | Bus | teal |
| 215 KIEST | Bus | teal |
| 216 EVERGLADE | Bus | teal |
| 217 LANCASTER/RAMONA | Bus | teal |
| 218 MILITARY | Bus | teal |
| 219 SYLVAN | Bus | teal |
| 220 SCYENE | Bus | teal |
| 221 MERRIFIELD | Bus | teal |
| 223 CLARK | Bus | teal |
| 224 I-30 BROADWAY | Bus | teal |
| 226 CLARENDON | Bus | teal |
| 227 O-CONNOR - LUNA - VALLEY VIEW | Bus | teal |
| 228 SIMPSON STUART | Bus | teal |
| 229 MACARTHUR - BELTLINE | Bus | teal |
| 230 IRVING BLVD | Bus | teal |
| 231 S BELTLINE | Bus | teal |
| 232 FRANKFORD | Bus | teal |
| 233 JOSEY | Bus | teal |
| 234 PARKER | Bus | teal |
| 235 TIMBERGLEN/MIDWAY | Bus | teal |
| 236 W 15 | Bus | teal |
| 237 PRESTON | Bus | teal |
| 238 NAAMAN FOREST/BELTLINE | Bus | teal |
| 239 DALLAS - ADDISON - LEGACY | Bus | teal |
| 241 COIT | Bus | teal |
| 242 WALNUT HILL | Bus | teal |
| 243 PLANO RD | Bus | teal |
| 244 UTD RICHARDSON | Bus | teal |
| 245 SHILOH | Bus | teal |
| 247 JUPITER | Bus | teal |
| 249 COLUMBIA | Bus | teal |
| 250 E BELTLINE | Bus | teal |
| 251 SATURN | Bus | teal |
| 306 GLENN HEIGHTS EXPRESS | Bus | pink |
| 308 NORTHWEST PLANO EXPRESS | Bus | pink |
| 408 PALISADES E-SHUTTLE | Bus | gray |
| 413 TI SHUTTLE - FOREST LANE CAMPUS | Bus | gray |
| 417 TI SHUTTLE- MAIN CAMPUS NORTH ROUTE | Bus | gray |
| 419 TI SHUTTLE- MAIN CAMPUS SOUTH ROUTE | Bus | gray |
| 421 BAYLOR BRYAN TOWER | Bus | gray |
| 422 UT SOUTHWESTERN SOUTH | Bus | gray |
| 423 UT SOUTHWESTERN NORTH | Bus | gray |
| 425 MCKINNEY AVENUE TROLLEY | Cable tram | brown |
| 440 MUSTANG EXPRESS | Bus | gray |
| 442 BUSH/ MEADOWS-MOCKINGBIRD STA. | Bus | gray |
| 883E UT DALLAS EAST | Bus | gray |
| 883W UT DALLAS WEST | Bus | gray |
| 620 DALLAS STREETCAR | Cable tram | black |
| BLUE DART LIGHT RAIL - BLUE LINE | Tram / light rail | teal |
| GREEN DART LIGHT RAIL - GREEN LINE | Tram / light rail | green |
| ORANGE DART LIGHT RAIL - ORANGE LINE | Tram / light rail | orange |
| RED DART LIGHT RAIL - RED LINE | Tram / light rail | red |
| SILVER SILVER LINE | Rail | white |
| TRE TRINITY RAILWAY | Rail | black |
List every stop
- FOREST @ SHEPHERD - E - NS
- WALNUT HILL @ RAMBLER - W - MB
- WALNUT HILL @ GREENVILLE - E - MB
- MATILDA @ PENROSE - S - NS
- MATILDA @ MCCOMMAS - S - NS
- MATILDA @ MONTICELLO - S - NS
- MATILDA @ VANDERBILT - S - NS
- MATILDA @ VICKERY - S - NS
- MATILDA @ VELASCO - S - NS
- MATILDA @ GOLIAD - S - NS
- MATILDA @ RICHMOND - S - NS
- MATILDA @ ORAM - S - NS
- MATILDA @ LEWIS - S - NS
- ROSS @ HOPE - W - NS
- LIVE OAK @ WASHINGTON - W - NS
- LIVE OAK @ HALL - W - NS
- LIVE OAK @ LIBERTY - W - NS
- LIVE OAK @ CANTEGRAL - W - NS
- LIVE OAK @ CANTEGRAL - E - MB
- LIVE OAK @ TEXAS - E - NS
- LIVE OAK @ SKILES - E - MB
- LIVE OAK @ HASKELL - E - NS
- ROSS @ HOPE - E - FS
- MATILDA @ LEWIS - N - FS
- MATILDA @ ORAM - N - NS
- MATILDA @ RICHMOND - N - NS
- MATILDA @ GOLIAD - N - NS
- MATILDA @ VELASCO - N - NS
- MATILDA @ VICKERY - N - NS
- MATILDA @ VANDERBILT - N - FS
- MATILDA @ MONTICELLO - N - NS
- MATILDA @ MCCOMMAS - N - NS
- MATILDA @ PENROSE - N - NS
- MATILDA @ ANITA - N - FS
- GREENVILLE @ SOUTHWESTERN - N - MB1
- WALNUT HILL @ RAMBLER - W - NS
- GREENVILLE @ UNIVERSITY - N - NS
- GREENVILLE @ UNIVERSITY - S - NS
- GREENVILLE @ SOUTHWESTERN - N - NS
- ERVAY @ SOUTH - N - NS
- ERVAY @ AL LIPSCOMB WAY - N - NS
- ERVAY @ SANGER - N - FS
- ERVAY @ BEAUMONT - N - FS
- ERVAY @ MARILLA - N - NS
- ERVAY @ YOUNG - N - NS
- ST PAUL @ CADIZ - S - NS
- ST PAUL @ GRIFFIN - S - MB
- ERVAY @ BEAUMONT - S - NS
- ERVAY @ SANGER - S - NS
- ERVAY @ AL LIPSCOMB WAY - S - FS
- ERVAY @ SOUTH - S - NS
- ABRAMS @ RICHMOND - S - MB
- ABRAMS @ WORTH - S - NS
- ABRAMS @ GASTON - N - FS
- ABRAMS @ BEACON - S - NS
- COLUMBIA @ ORIENT - S - NS
- COLUMBIA @ MUNGER - S - NS
- COLUMBIA @ FITZHUGH - S - NS
- COLUMBIA @ PRAIRIE - S - NS
- COLUMBIA @ COLSON - S - NS
- COLUMBIA @ CARROLL - S - FS
- MAIN @ PEAK - S - FS
- MAIN @ HASKELL - S - NS
- ELM @ HALL - W - NS
- ELM @ MALCOLM X - W - NS
- ELM @ GOOD-LATIMER - W - FS
- MAIN @ HASKELL - N - NS
- MAIN @ PEAK - N - NS
- MAIN @ CARROLL - N - NS
- COLUMBIA @ COLSON - N - NS
- COLUMBIA @ PRAIRIE - N - NS
- COLUMBIA @ FITZHUGH - N - NS
- COLUMBIA @ MUNGER - N - NS
- COLUMBIA @ ST MARY - N - NS
- COLUMBIA @ ORIENT - N - NS
- ABRAMS @ FULTON - N - NS
- ABRAMS @ VICTOR - N - FS
- ABRAMS @ GLASGOW - N - NS
- ABRAMS @ WORTH - N - NS
- ABRAMS @ LA VISTA - N - NS
- ABRAMS @ RICHMOND - N - NS
- ADAMS @ GRIFFITH - S - NS
- LLEWELLYN @ BROOKLYN - N - FS
- LLEWELLYN @ 12TH - N - NS
- LLEWELLYN @ JEFFERSON - N - NS
- LLEWELLYN @ 10TH - N - FS
- LLEWELLYN @ DAVIS - N - NS
- MARKET @ JACKSON - N - FS
- LLEWELLYN @ 7TH - S - NS
- LLEWELLYN @ MELBA - S - NS
- LLEWELLYN @ JEFFERSON - S - NS
- LLEWELLYN @ 12TH - S - NS
- LLEWELLYN @ BROOKLYN - S - NS
- ADAMS @ YARMOUTH - S - FS
- VERNON @ ILLINOIS - S - FS
- VERNON @ LUDLOW - N - NS
- VERNON @ FERNDALE - N - NS
- VERNON @ PIONEER - N - FS
- VERNON @ MONSSEN - N - NS
- TYLER @ CLARENDON - N - NS
- TYLER @ PEMBROKE - N - NS
- TYLER @ PAGE - N - NS
- TYLER @ 12TH - N - NS
- TYLER @ JEFFERSON - N - NS
- TYLER @ 10TH - N - NS
- TYLER @ 9TH - N - NS
- TYLER @ 8TH - N - NS
- TYLER @ DAVIS - N - NS
- TYLER @ WINSTON - N - NS
- TYLER @ CANTY - N - FS
- TYLER @ STEWART - N - NS
- TYLER @ SALMON - N - NS
- SYLVAN @ RAINBOW - N - FS
- SYLVAN @ EVERGREEN HILLS - N - NS
- SYLVAN @ KESSLER - N - NS
- COMMERCE @ LANGFORD - E - NS
- COMMERCE @ LEW STERRETT CROSSWALK - W - NS
- SYLVAN @ FT WORTH - S - FS
- SYLVAN @ EVERGREEN HILLS - S - NS
- SYLVAN @ RAINBOW - S - NS
- TYLER @ COLORADO - S - FS
- TYLER @ SALMON - S - NS
- TYLER @ STEWART - S - NS
- TYLER @ EVERTS - S - NS
- POLK @ DAVIS - S - NS
- POLK @ 8TH - S - NS
- POLK @ 9TH - S - MB
- POLK @ 10TH - S - NS
- POLK @ JEFFERSON - S - NS
- POLK @ 12TH - S - NS
- POLK CUTOFF @ PAGE - S - NS
- TYLER @ PEMBROKE - S - NS
- TYLER @ BURLINGTON - S - NS
- TYLER @ CLARENDON - S - NS
- VERNON @ ELMDALE - S - NS
- VERNON @ PIONEER - S - NS
- VERNON @ FERNDALE - S - NS
- VERNON @ WILBUR - S - NS
- PINELAND @ FAIR OAKS - E - MB
- FAIR OAKS @ PHOENIX - S - NS
- RIDGECREST @ HEMLOCK- E - MB
- RIDGECREST @ EASTRIDGE - E - MB1
- RIDGECREST @ EASTRIDGE - E - MB3
- RIDGECREST @ EASTRIDGE - E - NS
- MELODY @ HEMLOCK - W - MB1
- MELODY @ HEMLOCK - W - MB2
- MELODY @ HEMLOCK - W - MB3
- MELODY @ HEMLOCK - W - MB4
- MELODY @ HEMLOCK - W - MB5
- MELODY @ HEMLOCK - W - MB6
- MELODY @ HEMLOCK - W - NS
- MELODY @ SHADYBROOK - W - MB
- SOUTHWESTERN @ CARUTH HAVEN - S - NS
- MELODY @ HEMLOCK - E - NS
- MELODY @ EASTRIDGE - E - MB1
- MELODY @ EASTRIDGE - E - MB2
- MELODY @ EASTRIDGE - E - MB3
- MELODY @ EASTRIDGE - E - MB4
- MELODY @ EASTRIDGE - E - MB5
- MELODY @ EASTRIDGE - E - MB6
- MELODY @ EASTRIDGE - E - MB7
- EASTRIDGE @ MELODY - N - FS
- RIDGECREST @ EASTRIDGE - W - FS
- RIDGECREST @ HEMLOCK - W - MB3
- RIDGECREST @ HEMLOCK - W - NS
- RIDGECREST @ PARK - W - NS
- FAIR OAKS @ PHOENIX - N - NS
- ELSIE FAYE HEGGINS@ LELAND - W - NS
- MLK @ EDGEWOOD - N - NS
- MLK @ HARWOOD - S - NS
- OAK LAWN @ LEMMON - S - FS
- MAPLE @ HOOD - S - NS
- MAPLE @ TURTLE CREEK - S - FS
- ERVAY @ ELM - N - MB
- MAPLE @ HOOD - N - FS
- OAK LAWN @ HALL - N - NS
- OAK LAWN @ LEMMON - N - NS
- NORTHWEST @ AMES - E - NS
- MALCOLM X @ MLK - N - NS
- MLK @ MEADOW - N - NS
- ROBERT B CULLUM @ GRAND - N - FS
- PEAK @ MAIN - W - NS
- PEAK @ ELM - W - FS
- PEAK @ VICTOR - W - NS
- PEAK @ GASTON - W - NS
- PEAK @ LIVE OAK - W - NS
- PEAK @ MUNGER - W - NS
- BLACKBURN @ TURTLE CREEK - W - MB
- OAK LAWN @ HOLLAND - S - MB
- MAPLE @ HONDO - N - FS
- MAPLE @ LUCAS - S - NS
- MEDICAL DISTRICT @ MAPLE - S - FS
- MEDICAL DISTRICT @ HARRY HINES - S - MB
- MEDICAL DISTRICT @ HARRY HINES - N - FS
- MEDICAL DISTRICT @ MAPLE - N - MB
- MAPLE @ KINGS - S - NS
- MAPLE @ LUCAS - N - NS
- MAPLE @ OAK LAWN - N - NS
- OAK LAWN @ HOLLAND - N - NS
- BLACKBURN @ OAK LAWN - E - FS
- BLACKBURN @ TRAVIS - E - MB
- BLACKBURN @ MCKINNEY - E - FS
- HASKELL @ LAFAYETTE - E - FS
- HASKELL @ ROSS - E - NS
- HASKELL @ LIVE OAK - E - NS
- HASKELL @ GASTON - E - NS
- HASKELL @ JUNIUS - E - NS
- HASKELL @ CRUTCHER - E - NS
- HASKELL @ ELM - E - NS
- HASKELL @ ASH - E - FS
- HASKELL @ PARRY - E - NS
- HAMPTON @ WADDY - N - NS
- HAMPTON @ MARVIN - N - NS
- JEFFERSON @ MARLBOROUGH - E - NS
- JEFFERSON @ EDGEFIELD - E - NS
- JEFFERSON @ TYLER - E - NS
- JEFFERSON @ VAN BUREN - E - FS
- JEFFERSON @ LLEWELLYN - E - NS
- JEFFERSON @ BISHOP - E - NS
- JEFFERSON @ ZANG - E - NS
- JEFFERSON @ BECKLEY - E - NS
- JEFFERSON @ CRAWFORD - E - NS
- JEFFERSON @ MARSALIS - E - NS
- JEFFERSON @ 10TH - E - NS
- HOUSTON @ COMMERCE - S - NS
- MARSALIS @ COLORADO - S - NS
- COLORADO @ LANCASTER - E - NS
- JEFFERSON @ 10TH - W - NS
- JEFFERSON @ HAMPTON - W - NS
- HAMPTON @ WENTWORTH - S - NS
- HAMPTON @ BENTLEY - N - NS
- HAMPTON @ BRANDON - N - NS
- HAMPTON @ SEARCY - S - NS
- HAMPTON @ ENGLE - S - MB
- HAMPTON @ ILLINOIS - S - NS
- ILLINOIS @ CHALMERS - W - NS
- SCYENE @ HANCOCK - W - MB
- DIXON @ BARBER - S - NS
- DIXON @ BOURQUIN - S - NS
- DIXON @ WULLSCHELGER - S - FS
- DIXON @ WULLSCHLEGER - N - NS
- 2ND @ REESE - N - FS
- ELSIE FAYE HEGGINS@ VERDUN - E - NS
- 2ND @ KENILWORTH - N - NS
- 2ND @ PINE - N - NS
- 2ND @ HERRLING - N - NS
- 2ND @ JAMAICA - N - NS
- 2ND @ PENELOPE - N - NS
- 2ND @ CARL - N - NS
- 2ND @ HAMILTON - S - NS
- and 6724 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 38.2 | first check |
| 2026-07-30 | 36.1 | down 2.1 |
| 2026-07-31 | 35.7 | down 0.4 |
| 2026-08-01 | 35.3 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
20 findings, ordered by severity.
Show every finding
- Error931 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: 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. (Varies.)
Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error108 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show transit vehicles jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning29211 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning22230 instances
22230 of 22230 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning4056 instances
4056 of 6974 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning450 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning182 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning54 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
3 of 22230 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6938 instances
About 6938 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info5 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 2 validator errors to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Ready
- Service data covers the next 43 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 22230 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 2 validator errors to resolve. States wheelchair access on 42% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 43 days.
- Accessible Not yet
- States wheelchair access on 42% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 43 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1039 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 0 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 72 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 56 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/dallas-area-rapid-transit-dart/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.