Home
United States Feeds
university-of-az2
Enhanced Validation Report

university-of-az2 — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-11-06T17:03:19Z,
for the dataset file:///shared/university-of-az2_cec4a206.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

University of Arizona
- website: https://arizona.transloc.com
- phone number: (888) 281-2681
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Language:
English: Feed Start Date:
2026-04-13: Feed End Date:
2027-05-17: Service Window:
2026-04-13 to 2027-05-17 (?) 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
feed_info.txt
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 14
Routes: 11
Shapes: 11
Stops: 51
Trips: 196

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

ShapesFrequenciesFeed InformationRoute ColorsHeadsignsStops Wheelchair AccessibilityLocation Types

Specification Compliance report

31 notices reported (28 errors, 3 warnings, 0 infos)

Notice Code Severity Total

block_trips_with_overlapping_stop_times ERROR 2

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.
175	"100400-TL-275"	"100400-TL-1"	176	"100400-TL-276"	"100400-TL-1"	"College of Medicine"	"20260413"
176	"100400-TL-276"	"100400-TL-1"	177	"100400-TL-277"	"100400-TL-1"	"College of Medicine"	"20260413"

stop_time_with_arrival_before_previous_departure_time ERROR 26

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.
1760	1759	"100400-TL-209"	"12:15:00"	"12:23:00"
1643	1642	"100400-TL-200"	"07:20:00"	"07:28:00"
1656	1655	"100400-TL-201"	"07:55:00"	"08:03:00"
1669	1668	"100400-TL-202"	"08:30:00"	"08:38:00"
1682	1681	"100400-TL-203"	"09:05:00"	"09:13:00"
1695	1694	"100400-TL-204"	"09:40:00"	"09:48:00"
1708	1707	"100400-TL-205"	"10:11:00"	"10:19:00"
1721	1720	"100400-TL-206"	"10:42:00"	"10:50:00"
1734	1733	"100400-TL-207"	"11:13:00"	"11:21:00"
1747	1746	"100400-TL-208"	"11:44:00"	"11:52:00"
1773	1772	"100400-TL-210"	"12:46:00"	"12:54:00"
1786	1785	"100400-TL-211"	"13:17:00"	"13:25:00"
1799	1798	"100400-TL-212"	"13:48:00"	"13:56:00"
1812	1811	"100400-TL-213"	"14:19:00"	"14:27:00"
1825	1824	"100400-TL-214"	"14:50:00"	"14:58:00"
1838	1837	"100400-TL-215"	"15:22:00"	"15:30:00"
1851	1850	"100400-TL-216"	"15:54:00"	"16:02:00"
1864	1863	"100400-TL-217"	"16:26:00"	"16:34:00"
1877	1876	"100400-TL-218"	"16:58:00"	"17:06:00"
1890	1889	"100400-TL-219"	"17:30:00"	"17:38:00"
1903	1902	"100400-TL-220"	"18:01:00"	"18:09:00"
1916	1915	"100400-TL-221"	"18:32:00"	"18:40:00"
1929	1928	"100400-TL-222"	"19:03:00"	"19:11:00"
711	710	"100400-TL-63"	"17:23:00"	"17:27:00"
697	696	"100400-TL-62"	"16:55:00"	"16:59:00"
1630	1629	"100400-TL-118"	"06:49:00"	"06:57:00"

fast_travel_between_consecutive_stops WARNING 1

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type	Description	Threshold, km/h
0	Light rail	100
1	Subway	150
2	Rail	500
3	Bus	150
4	Ferry	80
5	Cable tram	30
6	Aerial lift	50
7	Funicular	50
11	Trolleybus	150
12	Monorail	150
-	Unknown	200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip.	tripId (?) `trip_id` of the problematic trip.	routeId (?) `route_id` of the problematic trip.	speedKph (?) Travel speed (km/h).	distanceKm (?) Distance between stops (km).	csvRowNumber1 (?) The row number of the first stop time.	stopSequence1 (?) `stop_sequence` of the first stop.	stopId1 (?) `stop_id` of the first stop.	stopName1 (?) `stop_name` of the first stop.	departureTime1 (?) `departure_time` of the first stop.	csvRowNumber2 (?) The row number of the second stop time.	stopSequence2 (?) `stop_sequence` of the second stop.	stopId2 (?) `stop_id` of the second stop.	stopName2 (?) `stop_name` of the second stop.	arrivalTime2 (?) `arrival_time` of the second stop.
86	"100400-TL-20"	"100400-TL-3"	294.07161184152113	4.9011935306920185	1107	0	"100400-TL-31"	"Bridges Park and Ride"	"04:45:00"	1112	5	"100400-TL-35"	"Optical Sciences"	"04:45:00"

route_long_name_contains_short_name WARNING 1

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`.
"100400-135448"	11	"Commencement"	"Commencement May 2026"

route_short_name_too_long WARNING 1

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`.
"100400-135449"	12	"The Bridges(Comm)"