Home
Mexico Feeds
mex-mich-zamora
Enhanced Validation Report

mex-mich-zamora — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-10-02T20:27:37Z,
for the dataset file:///shared/mex-mich-zamora_3507ebf6.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Dirección Movilidad del Ayuntamiento de Zamora
- website: https://rutaton.zamora.gob.mx/direccion-movilidad
- phone number: +52 351 136 4540
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Language:
Spanish: Feed Start Date:
2026-01-01: Feed End Date:
2027-12-31: Service Window:
2026-01-01 to 2027-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
fare_attributes.txt
fare_rules.txt
feed_info.txt
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 43
Shapes: 84
Stops: 1516
Trips: 86

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

ShapesFrequenciesFeed InformationFares V1Route ColorsHeadsignsStops Wheelchair AccessibilityTrips Wheelchair AccessibilityBike AllowedLocation Types

Specification Compliance report

4 notices reported (0 errors, 2 warnings, 2 infos)

Notice Code Severity Total

fast_travel_between_consecutive_stops WARNING 2

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.
17	"4571-pattern-16_0"	"4571-az2"	170.21803658940672	0.2836967276490112	478	9	"4571-S_RO7Q"	"Avenida del Bosque"	"00:12:34"	479	10	"4571-S_LID6"	"Virrey de Mendoza Oriente"	"00:12:40"
16	"4571-pattern-15_0"	"4571-az1"	170.21803658940672	0.2836967276490112	457	9	"4571-S_RO7Q"	"Avenida del Bosque"	"00:12:36"	458	10	"4571-S_LID6"	"Virrey de Mendoza Oriente"	"00:12:42"

trip_headsign_matches_intermediate_stop INFO 2

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`.	tripId (?) The id of the trip with the problematic headsign.	tripHeadsign (?) The headsign value that matches an intermediate stop name.	stopId1 (?) The id of the intermediate stop whose name matches the headsign.	stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign.	stopId2 (?) The id of the actual last stop of the trip.
9	"4571-pattern-8_0"	"La Ladera"	"4571-S_ZWJA"	49	"4571-S_N0RA"
40	"4571-pattern-39_0"	"El Tepehuaje"	"4571-S_LVSL"	77	"4571-S_DFY0"