GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T19:38:49Z,
for the dataset file:///shared/life-university_85ec7998.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:
2024-11-25 to 2030-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: 6
Routes: 6
Shapes: 6
Stops: 50
Trips: 6

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

3 notices reported (1 errors, 2 warnings, 0 infos)

Notice Code

Severity

Total

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

stop_too_far_from_shape

WARNING

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.
6	"TL-5"	"TL-6"	41	"TL-41"	"MSSP"	[33.9327,-84.51265]	100.35078764509747