university-of-houston-downtown — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-28T17:28:53Z,
for the dataset file:///shared/university-of-houston-downtown_1bda91fc.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:
2020-01-06 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: 2
Routes: 2
Shapes: 2
Stops: 8
Trips: 2

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

ShapesFrequenciesRoute ColorsLocation Types

Specification Compliance report

5 notices reported (1 errors, 2 warnings, 2 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"	"UOfHDowntownShuttle.transloc.com"

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"

stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
2	"TL-2"	"TL-2"	8	"TL-9"	"Washington Street"	[29.765401651059946,-95.36058752969547]	7	"TL-5"	"Daly/Trenham Place"	[29.771417429647567,-95.36199228893682]

service_extends_far_in_the_future INFO 2

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).
"TL-2"	"2029-01-05"
"TL-3"	"2050-12-30"