GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T19:25:20Z,
for the dataset file:///shared/tulaliptransit.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Trillium Solutions, Inc.
Feed Email:
support+test+tulaliptransit-wa-us@trilliumtransit.com
Feed Language:
English
Feed Start Date:
2024-12-27
Feed End Date:
2026-01-01

Files included

  1. agency.txt
  2. areas.txt
  3. booking_rules.txt
  4. calendar.txt
  5. calendar_attributes.txt
  6. calendar_dates.txt
  7. directions.txt
  8. fare_attributes.txt
  9. fare_rules.txt
  10. farezone_attributes.txt
  11. feed_info.txt
  12. frequencies.txt
  13. linked_datasets.txt
  14. location_groups.txt
  15. routes.txt
  16. runcut.txt
  17. shapes.txt
  18. stop_attributes.txt
  19. stop_times.txt
  20. stops.txt
  21. timetable_stop_order.txt
  22. timetables.txt
  23. transfers.txt
  24. trips.txt

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 1
  • Shapes: 2
  • Stops: 21
  • Trips: 12

Specification Compliance report

45 notices reported (0 errors, 3 warnings, 42 infos)

Notice Code Severity Total
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20251212" "20260101" "20260111"
mixed_case_recommended_field WARNING 1

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.
"stops.txt" "stop_name" "beda?chelh" 16
same_route_and_agency_url WARNING 1

same_route_and_agency_url

Same routes.route_url and agency.agency_url.

A route should not have the same routes.route_url as a record from agency.txt.

You can see more about this notice here.

routeCsvRowNumber (?) The row number of the faulty record from `routes.txt`. routeId (?) The faulty record's id. agencyName (?) The faulty record's referenced agency name. routeUrl (?) The duplicate URL value agencyCsvRowNumber (?) The row number of the faulty record from `agency.txt`.
2 "74496" "Tulalip Transit" "https://www.tulaliptribes-nsn.gov/Dept/TulalipTransit" 2
unknown_column INFO 34

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"areas.txt" "wkt" 2
"agency.txt" "tts_agency_name" 8
"calendar.txt" "service_name" 2
"calendar_dates.txt" "holiday_name" 3
"feed_info.txt" "feed_license" 5
"feed_info.txt" "feed_id" 10
"routes.txt" "min_headway_minutes" 11
"routes.txt" "eligibility_restricted" 12
"routes.txt" "tts_route_short_name" 15
"routes.txt" "tts_route_long_name" 16
"stop_times.txt" "start_service_area_id" 11
"stop_times.txt" "end_service_area_id" 12
"stop_times.txt" "start_service_area_radius" 13
"stop_times.txt" "end_service_area_radius" 14
"stop_times.txt" "mean_duration_factor" 21
"stop_times.txt" "mean_duration_offset" 22
"stop_times.txt" "safe_duration_factor" 23
"stop_times.txt" "safe_duration_offset" 24
"stop_times.txt" "tts_stop_headsign" 25
"stop_times.txt" "min_arrival_time" 26
"stop_times.txt" "max_departure_time" 27
"stops.txt" "position" 13
"stops.txt" "direction" 14
"trips.txt" "trip_type" 11
"trips.txt" "drt_max_travel_time" 12
"trips.txt" "drt_avg_travel_time" 13
"trips.txt" "drt_advance_book_min" 14
"trips.txt" "drt_pickup_message" 15
"trips.txt" "drt_drop_off_message" 16
"trips.txt" "continuous_pickup_message" 17
"trips.txt" "continuous_drop_off_message" 18
"trips.txt" "tts_trip_headsign" 19
"trips.txt" "tts_trip_short_name" 20
"location_groups.txt" "location_id" 2
unknown_file INFO 8

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"calendar_attributes.txt"
"directions.txt"
"farezone_attributes.txt"
"runcut.txt"
"stop_attributes.txt"
"timetable_stop_order.txt"
"timetables.txt"
"linked_datasets.txt"