GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-06T01:45:55Z,
for the dataset file:///shared/govcbus.zip. No country code was provided.

Summary

Agencies included

Gold Coast Transit District
- website: http://www.goldcoasttransit.org/
- phone number: (805) 487-4222
- email: Not provided
Thousand Oaks Transit
- website: https://www.toaks.org/departments/public-works/transit
- phone number: (805) 375-5473
- email: TOTransit@toaks.org
Vctc Intercity
- website: https://www.goventura.org/
- phone number: 800.438.1112
- email: ridercomments@goventura.org
Kanan Shuttle
- website: https://www.toaks.org/departments/public-works/transit/kanan-shuttle
- phone number:
- email: Not provided
Ojai Trolley
- website: https://ojaitrolley.com/
- phone number:
- email: Not provided
Valley Express Transit Service
- website: http://www.valleyexpressbus.org/
- phone number: 805-933-2267
- email: Not provided
Simi Valley Transit
- website: https://www.simivalley.org/departments/community-services/simi-valley-transit
- phone number: (805) 583-6456
- email: Not provided
Camarillo Area Transit
- website: https://www.cityofcamarillo.org/residents/public_transportation/camarillo_area_transit.php
- phone number:
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Email:
alex@busmaps.com: Feed Language:
English: Feed Start Date:
2020-07-07: Feed End Date:
2026-12-31: Service Window:
2020-07-07 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
calendar.txt
calendar_dates.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 8
Blocks: 220
Routes: 54
Shapes: 129
Stops: 1209
Trips: 1957

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 Trips Wheelchair Accessibility Location Types

Specification Compliance report

17 notices reported (0 errors, 17 warnings, 0 infos)

Notice Code

Severity

Total

mixed_case_recommended_field

WARNING

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"	"3rd & B"	37
"stops.txt"	"stop_name"	"3rd & A"	59
"stops.txt"	"stop_name"	"5th & F"	62
"stops.txt"	"stop_name"	"HWY 150 & HWY 33"	96
"stops.txt"	"stop_name"	"HWY 150 & HWY 33"	99
"stops.txt"	"stop_name"	"5th & H"	444
"stops.txt"	"stop_name"	"5th & K"	445
"stops.txt"	"stop_name"	"4th & D"	522
"stops.txt"	"stop_name"	"4th & F"	523

route_color_contrast

WARNING

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"101925-4720"	36	"#EE0000"	"#000000"

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`.
"101925-3580"	20	"Fixed Route"	"Fixed Route Service"
"101925-3638"	21	"Fillmore"	"Fillmore Loop"

route_short_name_too_long

WARNING

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

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`.
"101925-4249"	30	"A.M. Rio Vista"
"101925-4251"	32	"Santa Paula A"
"101925-4252"	33	"Santa Paula B"
"101925-4253"	34	"P.M. Rio Vista Tripper"
"101925-6466"	45	"Fillmore-Moorpark Route"