GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-03T13:53:36Z,
for the dataset file:///shared/tuolumne-county_cc21ad7c.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 0
  • Blocks: 0
  • Routes: 21
  • Shapes: 20
  • Stops: 0
  • Trips: 96

Specification Compliance report

238 notices reported (184 errors, 50 warnings, 4 infos)

Notice Code Severity Total
missing_required_field ERROR 183

missing_required_field

A required field is missing.

The given field has no value in some input row, even though values are required.

You can see more about this notice here.

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

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"stops.txt" 3 "stop_id"
"stops.txt" 4 "stop_id"
"stops.txt" 5 "stop_id"
"stops.txt" 6 "stop_id"
"stops.txt" 7 "stop_id"
"stops.txt" 8 "stop_id"
"stops.txt" 9 "stop_id"
"stops.txt" 38 "stop_id"
"stops.txt" 43 "stop_id"
"stops.txt" 44 "stop_id"
"stops.txt" 45 "stop_id"
"stops.txt" 46 "stop_id"
"stops.txt" 47 "stop_id"
"stops.txt" 56 "stop_id"
"stops.txt" 70 "stop_id"
"stops.txt" 72 "stop_id"
"stops.txt" 73 "stop_id"
"stops.txt" 74 "stop_id"
"stops.txt" 75 "stop_id"
"stops.txt" 76 "stop_id"
"stop_times.txt" 54 "stop_id"
"stop_times.txt" 55 "stop_id"
"stop_times.txt" 57 "stop_id"
"stop_times.txt" 62 "stop_id"
"stop_times.txt" 63 "stop_id"
"stop_times.txt" 65 "stop_id"
"stop_times.txt" 70 "stop_id"
"stop_times.txt" 71 "stop_id"
"stop_times.txt" 73 "stop_id"
"stop_times.txt" 78 "stop_id"
"stop_times.txt" 79 "stop_id"
"stop_times.txt" 81 "stop_id"
"stop_times.txt" 88 "stop_id"
"stop_times.txt" 92 "stop_id"
"stop_times.txt" 93 "stop_id"
"stop_times.txt" 98 "stop_id"
"stop_times.txt" 102 "stop_id"
"stop_times.txt" 103 "stop_id"
"stop_times.txt" 108 "stop_id"
"stop_times.txt" 112 "stop_id"
"stop_times.txt" 113 "stop_id"
"stop_times.txt" 118 "stop_id"
"stop_times.txt" 122 "stop_id"
"stop_times.txt" 123 "stop_id"
"stop_times.txt" 128 "stop_id"
"stop_times.txt" 132 "stop_id"
"stop_times.txt" 133 "stop_id"
"stop_times.txt" 138 "stop_id"
"stop_times.txt" 142 "stop_id"
"stop_times.txt" 143 "stop_id"
stop_time_with_only_arrival_or_departure_time ERROR 1

stop_time_with_only_arrival_or_departure_time

Missing stop_times.arrival_time or stop_times.departure_time.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The trip_id associated to the faulty record. stopSequence (?) The sequence of the faulty stop. specifiedField (?) Either `arrival_time` or `departure_time`
511 "68" 3 "arrival_time"
duplicate_route_name WARNING 5

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
3 "25" 7 "26" "ADV" "Adventure Trolley" 3 ""
3 "25" 8 "19" "ADV" "Adventure Trolley" 3 ""
11 "20" 13 "23" "PINE" "Pinecrest" 3 ""
11 "20" 14 "22" "PINE" "Pinecrest" 3 ""
6 "17" 20 "32" "Rte 2" "Route 2 - To Sierra Village" 3 ""
expired_calendar WARNING 15

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 "25"
4 "29"
5 "9"
6 "17"
7 "26"
8 "19"
9 "7"
10 "13"
11 "20"
12 "18"
13 "23"
14 "22"
17 "11"
18 "30"
21 "12"
missing_recommended_field WARNING 22

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"agency.txt" 2 "agency_id"
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
"routes.txt" 13 "agency_id"
"routes.txt" 14 "agency_id"
"routes.txt" 15 "agency_id"
"routes.txt" 16 "agency_id"
"routes.txt" 17 "agency_id"
"routes.txt" 18 "agency_id"
"routes.txt" 19 "agency_id"
"routes.txt" 20 "agency_id"
"routes.txt" 21 "agency_id"
"routes.txt" 22 "agency_id"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
service_has_no_active_day_of_the_week WARNING 2

service_has_no_active_day_of_the_week

A service is not valid for any day of the week.

You can see more about this notice here.

csvRowNumber (?) The row number in calendar.txt where the error occurs. serviceId (?) The service_id field value.
15 "24"
19 "14"
trip_coverage_not_active_for_next7_days WARNING 1

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.
"20260703" "20140602" "20210121"
unusable_trip WARNING 2

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
62 "60"
97 "95"
unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"23" 4908
unused_trip WARNING 1

unused_trip

Trip is not be used in stop_times.txt

Trips should be referred to at least once in stop_times.txt.

You can see more about this notice here.

tripId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"95" 97
service_extends_far_in_the_future INFO 4

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

serviceId (?) The service_id that ends far in the future. serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"28" "2035-08-31"
"31" "2035-08-23"
"32" "2035-08-23"
"16" "2035-09-28"