GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:57:13Z,
for the dataset file:///shared/santa-cruz.zip. No country code was provided.

Summary

Agencies included

UCSC Transportation and Parking Services
- website: https://transportation.ucsc.edu/buses-shuttles/campus-shuttles/
- phone number: 831-459-4543
- email: taps@ucsc.edu

Feed Info

Publisher Name:
UCSC Transportation and Parking Services: Publisher URL:
https://taps.ucsc.edu/: Feed Email:
rtuli@ucsc.edu: Feed Language:
English: Feed Start Date:
2025-09-01: Feed End Date:
2025-12-12: Service Window:
2025-09-25 to 2025-12-12 (?) 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
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
trips.txt

Counts

Agencies: 1
Blocks: 58
Routes: 5
Shapes: 10
Stops: 37
Trips: 727

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

Shapes Feed Information Route Colors Headsigns Stops Wheelchair Accessibility Continuous Stops

Specification Compliance report

6 notices reported (0 errors, 6 warnings, 0 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	"2"
3	"3"
5	"6"

feed_expiration_date7_days

WARNING

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

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"	"20251212"	"20251219"

route_long_name_contains_short_name

WARNING

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`.
"LOOP"	2	"LOOP"	"Loop"

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.
"20251212"	"20250925"	"20251212"