GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-16T00:44:05Z,
for the dataset file:///shared/port-of-seattle-seatac-employee-parking_333a457f.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

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: 0
  • Blocks: 1
  • Routes: 9
  • Shapes: 6
  • Stops: 37
  • Trips: 6

Specification Compliance report

21 notices reported (16 errors, 5 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 15

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.
2 "TL-4" "TL-1" 3 "TL-5" "TL-1" "Active Times" "20240501"
2 "TL-4" "TL-1" 4 "TL-6" "TL-1" "Active Times" "20240501"
2 "TL-4" "TL-1" 6 "TL-2" "TL-1" "Active Times" "20240501"
2 "TL-4" "TL-1" 5 "TL-7" "TL-1" "Active Times" "20240501"
2 "TL-4" "TL-1" 7 "TL-1" "TL-1" "Active Times" "20240501"
3 "TL-5" "TL-1" 4 "TL-6" "TL-1" "Active Times" "20240501"
3 "TL-5" "TL-1" 6 "TL-2" "TL-1" "Active Times" "20240501"
3 "TL-5" "TL-1" 5 "TL-7" "TL-1" "Active Times" "20240501"
3 "TL-5" "TL-1" 7 "TL-1" "TL-1" "Active Times" "20240501"
4 "TL-6" "TL-1" 6 "TL-2" "TL-1" "Active Times" "20240501"
4 "TL-6" "TL-1" 5 "TL-7" "TL-1" "Active Times" "20240501"
4 "TL-6" "TL-1" 7 "TL-1" "TL-1" "Active Times" "20240501"
6 "TL-2" "TL-1" 5 "TL-7" "TL-1" "Active Times" "20240501"
6 "TL-2" "TL-1" 7 "TL-1" "TL-1" "Active Times" "20240501"
5 "TL-7" "TL-1" 7 "TL-1" "TL-1" "Active Times" "20240501"
invalid_url ERROR 1

invalid_url

A field contains a malformed URL.

Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"agency.txt" 2 "agency_url" "seatac-ep.transloc.com"
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 2

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" "518 to NEGTL" 7
"routes.txt" "route_long_name" "NEGTL to 518" 8
stop_without_stop_time WARNING 1

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.
12 "TL-12" "Shelter 1"
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.
7 "TL-4" "TL-1" 4 "TL-15" "Shelter 2" [47.4705700397292,-122.30518000057579] 3 "TL-14" "Handi Hut" [47.47162000097245,-122.30762400466902]