GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T15:11:34Z,
for the dataset file:///shared/dart-texas.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:
2025-11-08
Feed End Date:
2026-02-01

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: 712
  • Routes: 98
  • Shapes: 273
  • Stops: 7129
  • Trips: 21018

Specification Compliance report

23 notices reported (0 errors, 23 warnings, 0 infos)

Notice Code Severity Total
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-26810" 98 "Silver" "Silver Line"
stop_too_far_from_shape WARNING 21

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.
7380 "371-146246" "371-8687190" 375148 "371-33260" "Cityline/Bush Station" [33.003440000000005,-96.70347000000001] 118.24277718025392
297 "371-146008" "371-8643701" 12407 "371-32923" "Love Field Airport (Baggage Claims)" [32.843829,-96.84915900000001] 130.90041879481302
7164 "371-146236" "371-8686090" 370315 "371-28155" "Bishop @ Binkley - N - Fs" [32.84165081121309,-96.78379124079869] 109.87757586806853
4699 "371-146112" "371-8672519" 250603 "371-28054" "Bruton @ ST Augustine - W - Fs" [32.74879428956689,-96.65689993372779] 113.35401528993975
6960 "371-146226" "371-8685424" 367895 "371-33329" "Baylor Station" [32.786978,-96.776863] 487.0741753540443
6960 "371-146226" "371-8685424" 367896 "371-33549" "Sammons Cancer Center" [32.786978,-96.776863] 173.3150686784289
6981 "371-146227" "371-8685445" 367979 "371-33554" "Roberts Hospital" [32.79074086774551,-96.78067498262432] 156.29717105844097
6981 "371-146227" "371-8685445" 367980 "371-33329" "Baylor Station" [32.788524149597045,-96.78330526115876] 169.52959323871488
6858 "371-146220" "371-8685311" 367502 "371-29214" "Palisades Bldg" [32.98601899999999,-96.71519] 140.9401535478176
6837 "371-146219" "371-8685290" 367350 "371-29214" "Palisades Bldg" [32.985118357047575,-96.71494272838027] 132.8087921299988
5893 "371-146174" "371-8679753" 324261 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5892 "371-146172" "371-8679752" 324190 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5956 "371-146176" "371-8680188" 329388 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5767 "371-146164" "371-8679149" 313664 "371-15093" "Preston @ Alpha - S - Mb" [32.93280000000001,-96.80370900000001] 144.8082186127677
5563 "371-146156" "371-8677778" 301207 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
5300 "371-146141" "371-8676122" 283010 "371-18594" "DFW Remote South Parking" [32.86203,-97.034249] 120.46858940459954
6537 "371-146195" "371-8683364" 360084 "371-32127" "Northwest Plano Park & Ride" [33.069788021059146,-96.8268923384217] 110.64651184967994
6209 "371-146184" "371-8681405" 340864 "371-33260" "Cityline/Bush Station" [33.001858999999996,-96.703049] 175.72992103215114
6147 "371-146182" "371-8681245" 337818 "371-34261" "Synergy Park @ Facilities - E - Ns" [32.99681666481889,-96.74917435623102] 450.84432417813804
6147 "371-146182" "371-8681245" 337819 "371-32769" "Synergy Park @ Point North - N - Mb" [32.997068,-96.748059] 353.87552634342137
2999 "371-146066" "371-8661799" 165636 "371-23624" "Colorado @ Moulin Rouge - E - Ns" [32.759749,-96.872919] 130.03275867952226
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.
5063 "371-146131" "371-8674702" 266100 "371-33335" "Irving Convention Center Station" [32.87768493990388,-96.93956887419387] 266099 "371-34308" "Promenade @ Promenade - N - Ns" [32.87569270520103,-96.93935153216896]