Search
  1. Home
  2. United States Feeds
  3. dart-texas
  4. Enhanced Validation Report

dart-texas — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T15:13:44Z,
for the dataset file:///shared/dart-texas_c9b36010.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Dallas Area Rapid Transit

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2026-03-13
Feed End Date:
2026-05-24

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 569
  • Routes: 92
  • Shapes: 253
  • Stops: 6992
  • Trips: 19460

Specification Compliance report

38 notices reported (17 errors, 21 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 17

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
17345 "371-8895962" "371-merged_b0652e6d9065c9f8b994" 17717 "371-8880781" "371-19" "60389" "20260321"
17717 "371-8880781" "371-19" 17416 "371-8896034" "371-merged_b0652e6d9065c9f8b994" "60389" "20260321"
17683 "371-8880739" "371-19" 17493 "371-8896109" "371-merged_b0652e6d9065c9f8b994" "60387" "20260321"
17493 "371-8896109" "371-merged_b0652e6d9065c9f8b994" 17644 "371-8880677" "371-19" "60387" "20260321"
17644 "371-8880677" "371-19" 17376 "371-8895994" "371-merged_b0652e6d9065c9f8b994" "60387" "20260321"
17376 "371-8895994" "371-merged_b0652e6d9065c9f8b994" 17685 "371-8880749" "371-19" "60387" "20260321"
17358 "371-8895975" "371-merged_b0652e6d9065c9f8b994" 17681 "371-8880727" "371-19" "60387" "20260321"
17353 "371-8895970" "371-merged_b0652e6d9065c9f8b994" 17679 "371-8880723" "371-19" "60386" "20260321"
17679 "371-8880723" "371-19" 17423 "371-8896042" "371-merged_b0652e6d9065c9f8b994" "60386" "20260321"
17362 "371-8895979" "371-merged_b0652e6d9065c9f8b994" 17682 "371-8880732" "371-19" "60386" "20260321"
17645 "371-8880678" "371-19" 17379 "371-8895997" "371-merged_b0652e6d9065c9f8b994" "60385" "20260321"
17379 "371-8895997" "371-merged_b0652e6d9065c9f8b994" 17686 "371-8880750" "371-19" "60385" "20260321"
17307 "371-8895924" "371-merged_b0652e6d9065c9f8b994" 17643 "371-8880676" "371-19" "60384" "20260321"
17643 "371-8880676" "371-19" 17378 "371-8895996" "371-merged_b0652e6d9065c9f8b994" "60384" "20260321"
17678 "371-8880711" "371-19" 17346 "371-8895963" "371-merged_b0652e6d9065c9f8b994" "60381" "20260321"
17346 "371-8895963" "371-merged_b0652e6d9065c9f8b994" 17719 "371-8880783" "371-19" "60381" "20260321"
17719 "371-8880783" "371-19" 17417 "371-8896035" "371-merged_b0652e6d9065c9f8b994" "60381" "20260321"
route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"371-26986" 92 "Silver" "Silver Line"
stop_too_far_from_shape WARNING 19

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
2570 "371-146951" "371-8853692" 143361 "371-23624" "Colorado @ Moulin Rouge - E - Ns" [32.759749,-96.872919] 130.03275867952226
6379 "371-147121" "371-8848989" 340032 "371-28155" "Bishop @ Binkley - N - Fs" [32.84165081121309,-96.78379124079869] 109.87757586806853
6196 "371-147112" "371-8848344" 337696 "371-33554" "Roberts Hospital" [32.79074086774551,-96.78067498262432] 156.29717105844097
6196 "371-147112" "371-8848344" 337697 "371-33329" "Baylor Station" [32.788524149597045,-96.78330526115876] 169.52959323871488
6175 "371-147111" "371-8848323" 337612 "371-33329" "Baylor Station" [32.786978,-96.776863] 487.0741753540443
6175 "371-147111" "371-8848323" 337613 "371-33549" "Sammons Cancer Center" [32.786978,-96.776863] 173.3150686784289
6073 "371-147105" "371-8848221" 337219 "371-29214" "Palisades Bldg" [32.98601899999999,-96.71519] 140.9401535478176
6052 "371-147104" "371-8848200" 337067 "371-29214" "Palisades Bldg" [32.985118357047575,-96.71494272838027] 132.8087921299988
5411 "371-147063" "371-8843826" 305291 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5602 "371-147069" "371-8844883" 313723 "371-34160" "Waterview @ Frankford - S - Mb" [32.998599000000006,-96.750989] 397.05233768176686
5602 "371-147069" "371-8844883" 313724 "371-26025" "Waterview @ Frankford - S - Fs" [32.99314781695754,-96.75555433269882] 395.2094166573452
5348 "371-147061" "371-8843391" 300167 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5347 "371-147059" "371-8843390" 300095 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5213 "371-147051" "371-8855674" 288778 "371-15093" "Preston @ Alpha - S - Mb" [32.93280000000001,-96.80370900000001] 144.8082186127677
4217 "371-146999" "371-8858557" 227881 "371-28054" "Bruton @ ST Augustine - W - Fs" [32.74879428956689,-96.65689993372779] 113.35401528993975
5018 "371-147043" "371-8841476" 277112 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
4755 "371-147028" "371-8839820" 258916 "371-18594" "DFW Remote South Parking" [32.86203,-97.034249] 120.46858940459954
5664 "371-147071" "371-8845043" 316767 "371-33260" "Cityline/Bush Station" [33.001858999999996,-96.703049] 175.72992103215114
297 "371-146895" "371-8807474" 12482 "371-32923" "Love Field Airport (Baggage Claims)" [32.843829,-96.84915900000001] 130.90041879481302
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
4518 "371-147018" "371-8838400" 241681 "371-33335" "Irving Convention Center Station" [32.87768493990388,-96.93956887419387] 241680 "371-34308" "Promenade @ Promenade - N - Ns" [32.87569270520103,-96.93935153216896]