GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-06-11T12:59:24Z,
for the dataset file:///shared/universal-studios-hollywood_2e58d6ef.zip. No country code was provided.

Summary

Agencies included

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2021-11-23 to 2042-11-23 (?) 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: 4
Routes: 2
Shapes: 2
Stops: 5
Trips: 8

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

6 notices reported (5 errors, 1 warnings, 0 infos)

Notice Code

Severity

Total

block_trips_with_overlapping_stop_times

ERROR

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.
3	"TL-2"	"TL-1"	5	"TL-7"	"TL-1"	"MTA_02"	"20211123"
2	"TL-1"	"TL-1"	4	"TL-6"	"TL-1"	"MTA_01"	"20211123"
7	"TL-13"	"TL-3"	8	"TL-4"	"TL-3"	"Hotel_01"	"20221224"
6	"TL-12"	"TL-3"	9	"TL-5"	"TL-3"	"Hotel_02"	"20221224"

invalid_url

ERROR

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"	"universalstudioshollywood.transloc.com"

missing_recommended_file

WARNING

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"