busmaps.com

Search

Home
United States Feeds
uc-san-diego-transportation-services-triton
Source Data Validation Report

uc-san-diego-transportation-services-triton — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-17T12:26:55Z,
for the dataset file:///shared/uc-san-diego-transportation-services-triton_df208d79.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

UC San Diego Transportation Services - Triton Transit
- website: https://transportation.ucsd.edu/campus/shuttles/index.html
- phone number: 858-534-7422
- email: tritontransit@ucsd.edu

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2026-03-29 to 2026-06-13 (?) 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: 1
Blocks: 19
Routes: 7
Shapes: 6
Stops: 71
Trips: 395

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

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

Notice Code Severity Total

block_trips_with_overlapping_stop_times ERROR 1

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip.	tripIdA (?) The id of first faulty trip.	serviceIdA (?) The service id of the first faulty trip.	csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip.	tripIdB (?) The id of the other faulty trip.	serviceIdB (?) The service id of the other faulty trip.	blockId (?) The `trips.block_id` of the overlapping trip.	intersection (?) The overlapping period.
364	"TL-13659"	"TL-82"	381	"TL-13755"	"TL-82"	"IL1_W/E (Fall 24)"	"20260329"

missing_recommended_field WARNING 7

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

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"

stop_too_far_from_shape WARNING 2

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`.	shapeId (?) The id of the shape that is referred to.	tripId (?) The id of the trip that is referred to.	stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`.	stopId (?) The id of the stop that is referred to.	stopName (?) The name of the stop that is referred to.	match (?) Latitude and longitude pair of the location.	geoDistanceToShape (?) Distance from stop to shape.
2	"TL-1"	"TL-13500"	2781	"TL-84"	"P785 Parking Lot"	[32.879949999999994,-117.21991000000001]	143.18868427553016
2	"TL-1"	"TL-13500"	2782	"TL-71"	"Athena Parking Structure"	[32.879949999999994,-117.21991000000001]	232.74781524180747

unusable_trip WARNING 3

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.
83	"TL-13785"
84	"TL-13786"
85	"TL-13787"

unused_trip WARNING 3

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.
"TL-13785"	83
"TL-13786"	84
"TL-13787"	85