GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T17:18:58Z,
for the dataset file:///shared/yuba-sutter-transit_2f574f87.zip. No country code was provided.

Summary

Agencies included

Yuba-Sutter Transit
- website: http://www.yubasuttertransit.com/
- phone number: (530) 742-2877
- email: Not provided

Feed Info

Publisher Name:
Trillium Solutions, Inc.: Publisher URL:
http://www.trilliumtransit.com: Feed Email:
support+test+yubasutter-ca-us@trilliumtransit.com: Feed Language:
English: Feed Start Date:
2025-01-23: Feed End Date:
2026-12-31: Service Window:
2022-11-01 to 2026-12-31 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
areas.txt
booking_rules.txt
calendar.txt
calendar_attributes.txt
calendar_dates.txt
directions.txt
fare_attributes.txt
fare_leg_rules.txt
fare_media.txt
fare_products.txt
fare_rules.txt
farezone_attributes.txt
feed_info.txt
frequencies.txt
linked_datasets.txt
location_groups.txt
routes.txt
runcut.txt
shapes.txt
stop_attributes.txt
stop_times.txt
stops.txt
timetable_stop_order.txt
timetables.txt
transfers.txt
trips.txt

Counts

Agencies: 1
Blocks: 4
Routes: 14
Shapes: 50
Stops: 289
Trips: 374

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Transfers Shapes Feed Information Fares V1 Fare Products Fare Media Route Colors Headsigns Stops Wheelchair Accessibility Location Types Route-Based Fares Continuous Stops

Specification Compliance report

54 notices reported (0 errors, 10 warnings, 44 infos)

Notice Code

Severity

Total

expired_calendar

WARNING

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.
2	"c_71030_b_84151_d_32"
3	"c_71030_b_84151_d_31"
4	"c_71030_b_84151_d_14"

same_stop_and_route_url

WARNING

same_stop_and_route_url

Same stops.stop_url and routes.route_url.

A stop should not have the same stop.stop_url as a record from routes.txt.

You can see more about this notice here.

stopCsvRowNumber (?) The row number of the faulty record from `stops.txt`.	stopId (?) The faulty record's id.	stopUrl (?) The duplicate URL value.	routeId (?) The faulty record's id from `routes.txt.	routeCsvRowNumber (?) The row number of the faulty record from `routes.txt`.
278	"2371244"	"https://www.yubasuttertransit.com/live-oak"	"6463"	7
279	"2371245"	"https://www.yubasuttertransit.com/live-oak"	"6463"	7
280	"2371246"	"https://www.yubasuttertransit.com/live-oak"	"6463"	7
281	"2371247"	"https://www.yubasuttertransit.com/live-oak"	"6463"	7

stop_without_stop_time

WARNING

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.
259	"12413"	"Oregon House Post Office"
283	"2577933"	"Yuba College Sutter Center"

trip_coverage_not_active_for_next7_days

WARNING

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20260423"	"20250121"	"20260130"

unknown_column

INFO

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.
"fare_leg_rules.txt"	"from_timeframe_id"	5
"fare_leg_rules.txt"	"to_timeframe_id"	6
"location_groups.txt"	"location_id"	2
"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
"agency.txt"	"tts_agency_name"	8
"areas.txt"	"wkt"	2
"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"	12
"routes.txt"	"eligibility_restricted"	13
"routes.txt"	"tts_route_short_name"	16
"routes.txt"	"tts_route_long_name"	17
"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

unknown_file

INFO

unknown_file

A file is unknown.

You can see more about this notice here.

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