Home
United States Feeds
alameda-county
Source Data Validation Report

alameda-county — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-17T12:22:15Z,
for the dataset file:///shared/alameda-county_2822f923.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: Service Window:
2023-08-31 to 2050-12-30 (?) 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
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
trips.txt

Counts

Agencies: 0
Blocks: 9
Routes: 6
Shapes: 6
Stops: 34
Trips: 75

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

Shapes Frequencies Route Colors Location Types

Specification Compliance report

10 notices reported (9 errors, 1 warnings, 0 infos)

Notice Code Severity Total

invalid_url ERROR 1

invalid_url

A field contains a malformed URL.

Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"agency.txt"	2	"agency_url"	"alco.transloc.com"

start_and_end_range_equal ERROR 1

start_and_end_range_equal

Two date or time fields are equal.

The fields frequencies.start_date and frequencies.end_date have been found equal in frequencies.txt. The GTFS spec is currently unclear how this case should be handled (e.g., is it a trip that circulates once?). It is recommended to use a trip not defined via frequencies.txt for this case.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row number of the faulty record.	startFieldName (?) The start value's field name.	endFieldName (?) The end value's field name.	value (?) The faulty value.
"frequencies.txt"	43	"start_time"	"end_time"	"18:48:00"

stop_time_with_arrival_before_previous_departure_time ERROR 7

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	prevCsvRowNumber (?) The row of the previous stop time.	tripId (?) The trip_id associated to the faulty record.	arrivalTime (?) Arrival time at the faulty record.	departureTime (?) Departure time at the previous stop time.
294	293	"TL-187"	"06:40:00"	"18:37:00"
285	284	"TL-186"	"06:03:00"	"18:00:00"
276	275	"TL-185"	"05:26:00"	"17:23:00"
267	266	"TL-184"	"04:49:00"	"16:46:00"
258	257	"TL-183"	"04:02:00"	"15:59:00"
249	248	"TL-182"	"03:25:00"	"15:22:00"
70	68	"TL-152"	"10:30:00"	"10:33:00"

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"