Search
  1. Home
  2. United States Feeds
  3. piercecountyferries-wa
  4. Source Data Validation Report

piercecountyferries-wa — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-10T02:52:43Z,
for the dataset file:///shared/piercecountyferries-wa_20ae591d.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:
Trillium Solutions, Inc.
Feed Email:
support+test+piercecountyferries-wa-us@trilliumtransit.com
Feed Language:
English
Feed Start Date:
2025-12-19
Feed End Date:
2026-05-21

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: 2
  • Routes: 2
  • Shapes: 6
  • Stops: 3
  • Trips: 100

Specification Compliance report

149 notices reported (0 errors, 107 warnings, 42 infos)

Notice Code Severity Total
expired_calendar WARNING 4

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
3 "c_70148_b_86127_d_2"
4 "c_70148_b_86126_d_2"
5 "c_70148_b_86125_d_2"
6 "c_70148_b_86124_d_2"
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 "20260510" "20260521" "20260609"
missing_bike_allowance WARNING 100

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

Only the first 50 of 100 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
2 "18987" "t_1366430_b_81997_tn_0"
3 "18987" "t_1366431_b_81997_tn_0"
4 "18987" "t_1366432_b_81997_tn_0"
5 "18987" "t_1366433_b_81997_tn_0"
6 "18987" "t_1366434_b_81997_tn_0"
7 "18987" "t_1366435_b_81997_tn_0"
8 "18987" "t_1366436_b_81997_tn_0"
9 "18987" "t_1366437_b_81997_tn_0"
10 "18987" "t_1373176_b_81997_tn_0"
11 "18987" "t_1366438_b_81997_tn_0"
12 "18987" "t_1366439_b_81997_tn_0"
13 "18987" "t_1366440_b_81997_tn_0"
14 "18987" "t_1366441_b_81997_tn_0"
15 "18987" "t_6043981_b_81997_tn_0"
16 "18987" "t_1366446_b_81997_tn_0"
17 "18987" "t_1366447_b_81997_tn_0"
18 "18987" "t_1366448_b_81997_tn_0"
19 "18987" "t_1366450_b_81997_tn_0"
20 "18987" "t_1366451_b_81997_tn_0"
21 "18987" "t_1366452_b_81997_tn_0"
22 "18987" "t_1366453_b_81997_tn_0"
23 "18987" "t_1366454_b_81997_tn_0"
24 "18987" "t_1373177_b_81997_tn_0"
25 "18987" "t_1373178_b_81997_tn_0"
26 "18987" "t_6043980_b_81997_tn_0"
27 "18987" "t_6043982_b_81997_tn_0"
28 "18987" "t_1373179_b_81997_tn_0"
29 "18987" "t_1373180_b_81997_tn_0"
30 "18987" "t_1366467_b_none_tn_0"
31 "18987" "t_5297727_b_none_tn_0"
32 "18987" "t_1366578_b_none_tn_0"
33 "18987" "t_1366468_b_none_tn_0"
34 "18987" "t_1366466_b_none_tn_0"
35 "18987" "t_1366465_b_none_tn_0"
36 "18987" "t_1366464_b_none_tn_0"
37 "18987" "t_1366463_b_none_tn_0"
38 "18987" "t_1366462_b_none_tn_0"
39 "18987" "t_1366461_b_none_tn_0"
40 "18987" "t_1366460_b_none_tn_0"
41 "18987" "t_1366459_b_none_tn_0"
42 "18987" "t_1366458_b_none_tn_0"
43 "18987" "t_1366586_b_none_tn_0"
44 "18987" "t_1366585_b_none_tn_0"
45 "18987" "t_1366583_b_none_tn_0"
46 "18987" "t_1366581_b_none_tn_0"
47 "18987" "t_1366580_b_none_tn_0"
48 "18987" "t_6044043_b_none_tn_0"
49 "18987" "t_6044042_b_none_tn_0"
50 "18987" "t_6044041_b_none_tn_0"
51 "18987" "t_5297728_b_none_tn_0"
route_long_name_contains_short_name WARNING 2

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`.
"18987" 2 "Anderson" "Anderson Island Daily"
"18988" 3 "Ketron" "Ketron Island Daily"
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"