GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T20:49:35Z,
for the dataset file:///shared/mcallen-tx-us.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Metro Mcallen
- website: http://mcallen.net/metro
- phone number: (956)681-3510
- email: metromcallen@mcallen.net

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Email:
alex@busmaps.com: Feed Language:
English: Feed Start Date:
2023-07-03: Feed End Date:
2026-12-31: Service Window:
2023-07-03 to 2026-12-31 (?) 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: 40
Routes: 20
Shapes: 20
Stops: 360
Trips: 306

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

Shapes Frequencies Feed Information Route Colors Headsigns Stops Wheelchair Accessibility Location Types

Specification Compliance report

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

Notice Code Severity Total

stop_time_with_arrival_before_previous_departure_time ERROR 5

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.
9021	9020	"104923-TL-3492"	"14:44:00"	"15:43:00"
8965	8964	"104923-TL-3491"	"12:44:00"	"13:43:00"
8909	8908	"104923-TL-3490"	"10:44:00"	"11:43:00"
9077	9076	"104923-TL-3493"	"16:44:00"	"17:43:00"
8853	8852	"104923-TL-3489"	"08:44:00"	"09:43:00"

mixed_case_recommended_field WARNING 1

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
`Field Text`	`Dataset`
"Schwerin, Hauptbahnhof"	Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin"	NYC Ferry
"Campo Grande Norte"	Carris

Bad examples:
`Field Text`
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"stops.txt"	"stop_name"	"23rd and 107"	330