GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:55:06Z,
for the dataset file:///shared/waco-transit.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 42
  • Routes: 27
  • Shapes: 21
  • Stops: 188
  • Trips: 253

Specification Compliance report

79 notices reported (2 errors, 77 warnings, 0 infos)

Notice Code Severity Total
number_out_of_range ERROR 2

number_out_of_range

Out of range value.

The values in the given column of the input rows are out of range.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the faulty field. fieldType (?) The type of the faulty field. fieldValue (?) Faulty value.
"frequencies.txt" 2 "headway_secs" "positive integer" 0
"frequencies.txt" 104 "headway_secs" "positive integer" 0
fast_travel_between_far_stops WARNING 8

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
191 "TL-2503" "TL-44" 4077.560520286017 67.95934200476695 1137 1 "TL-120" "8th & Mary" "07:35:00" 1143 13 "TL-109" "Sanderson Farms (Arrive)" "07:35:00"
228 "TL-2558" "TL-44" 4077.560520286017 67.95934200476695 1553 1 "TL-120" "8th & Mary" "07:35:00" 1559 13 "TL-109" "Sanderson Farms (Arrive)" "07:35:00"
193 "TL-2505" "TL-44" 639.2194442783872 10.653657404639786 1158 12 "TL-120" "8th & Mary" "18:30:00" 1160 14 "TL-126" "Sanderson Farms (Depart)" "18:30:00"
230 "TL-2560" "TL-44" 639.2194442783872 10.653657404639786 1574 12 "TL-120" "8th & Mary" "18:30:00" 1576 14 "TL-126" "Sanderson Farms (Depart)" "18:30:00"
192 "TL-2504" "TL-44" 4077.560520286017 67.95934200476695 1145 1 "TL-120" "8th & Mary" "16:50:00" 1151 13 "TL-109" "Sanderson Farms (Arrive)" "16:50:00"
229 "TL-2559" "TL-44" 4077.560520286017 67.95934200476695 1561 1 "TL-120" "8th & Mary" "16:50:00" 1567 13 "TL-109" "Sanderson Farms (Arrive)" "16:50:00"
188 "TL-2500" "TL-44" 4077.560520286017 67.95934200476695 1113 1 "TL-120" "8th & Mary" "13:35:00" 1119 13 "TL-109" "Sanderson Farms (Arrive)" "13:35:00"
225 "TL-2555" "TL-44" 4077.560520286017 67.95934200476695 1529 1 "TL-120" "8th & Mary" "13:35:00" 1535 13 "TL-109" "Sanderson Farms (Arrive)" "13:35:00"
missing_recommended_field WARNING 27

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
"routes.txt" 13 "agency_id"
"routes.txt" 14 "agency_id"
"routes.txt" 15 "agency_id"
"routes.txt" 16 "agency_id"
"routes.txt" 17 "agency_id"
"routes.txt" 18 "agency_id"
"routes.txt" 19 "agency_id"
"routes.txt" 20 "agency_id"
"routes.txt" 21 "agency_id"
"routes.txt" 22 "agency_id"
"routes.txt" 23 "agency_id"
"routes.txt" 24 "agency_id"
"routes.txt" 25 "agency_id"
"routes.txt" 26 "agency_id"
"routes.txt" 27 "agency_id"
"routes.txt" 28 "agency_id"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 27

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_long_name" "MART COMM ROUTE #1" 26
"routes.txt" "route_long_name" "CHINA SPRING/AIRPORT COMM ROUTE #3" 28
"stops.txt" "stop_name" "CEN-TEX HISPANIC CHAMBER" 114
"stops.txt" "stop_name" "8th ST" 143
"stops.txt" "stop_name" "S 5th ST" 145
"stops.txt" "stop_name" "DUTTON AVE" 146
"stops.txt" "stop_name" "S 8th ST" 147
"stops.txt" "stop_name" "BAGBY AVE" 148
"stops.txt" "stop_name" "S 12th ST" 149
"stops.txt" "stop_name" "GURLEY LN" 150
"stops.txt" "stop_name" "S 18th ST" 151
"stops.txt" "stop_name" "LASALLE AVE" 152
"stops.txt" "stop_name" "ROUNDABOUT EXIT 77" 153
"stops.txt" "stop_name" "GARDEN DR" 154
"stops.txt" "stop_name" "I 35 SVC RD" 155
"stops.txt" "stop_name" "MARKETPLACE DR" 156
"stops.txt" "stop_name" "BAGBY AVE" 157
"stops.txt" "stop_name" "S 12th ST" 159
"stops.txt" "stop_name" "JAMES AVE" 160
"stops.txt" "stop_name" "S 10th ST" 161
"stops.txt" "stop_name" "SPEIGHT AVE" 162
"stops.txt" "stop_name" "S 8th ST" 163
"stops.txt" "stop_name" "DUTTON AVE" 164
"stops.txt" "stop_name" "S 4th ST" 165
"stops.txt" "stop_name" "I 35 SVC RD" 166
"stops.txt" "stop_name" "S 8th ST" 167
"stops.txt" "stop_name" "CEFCO (right side)" 170
stop_too_far_from_shape WARNING 1

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.
85 "TL-36" "TL-1043" 32 "TL-146" "Magnolia Market" [31.551881568804514,-97.12797640794093] 126.56439449830448
stop_without_stop_time WARNING 2

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
116 "TL-113" "BU Drop off"
117 "TL-191" "Pick up 3rd & Franklin"
unusable_trip WARNING 10

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
81 "TL-2492"
82 "TL-2493"
83 "TL-502"
166 "TL-2494"
167 "TL-2495"
168 "TL-503"
183 "TL-2496"
184 "TL-2497"
185 "TL-504"
186 "TL-2498"
unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"TL-38" 7242