GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T22:42:21Z,
for the dataset file:///shared/lax-flyaway.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: 37
  • Routes: 5
  • Shapes: 5
  • Stops: 21
  • Trips: 37

Specification Compliance report

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

Notice Code Severity Total
missing_recommended_field WARNING 5

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"
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"
stop_too_far_from_shape WARNING 5

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.
21 "TL-4" "TL-229" 200 "TL-11" "Lot E" [33.94404,-118.39523000000003] 2026.1572183079334
17 "TL-3" "TL-225" 160 "TL-11" "Lot E" [33.94396,-118.39752999999999] 2207.699719026878
17 "TL-3" "TL-225" 161 "TL-13" "LAXit" [33.94553,-118.39949000000003] 178.24210200806831
12 "TL-2" "TL-220" 110 "TL-11" "Lot E" [33.9440202085,-118.39731349929998] 2193.0989088123556
12 "TL-2" "TL-220" 111 "TL-19" "LAXit" [33.945509459397606,-118.39929392177156] 280.5631101034763
stop_without_stop_time WARNING 5

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.
15 "TL-1" "Aviation/111th"
16 "TL-2" "Aviation/LAX Station"
17 "TL-12" "Re Rental Car Depot"
18 "TL-20" "Century West"
19 "TL-21" "Century East"
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-6" 1332