Search
  1. Home
  2. Mexico Feeds
  3. dt-mx
  4. Source Data Validation Report

dt-mx — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T04:13:21Z,
for the dataset file:///shared/dt-mx_953f0304.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Daytrip
Feed Email:
daytrip@daytrip.com
Feed Language:
English
Feed Start Date:
2025-12-01

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. routes.txt
  8. stop_times.txt
  9. stops.txt
  10. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 13
  • Shapes: 0
  • Stops: 10
  • Trips: 80

Specification Compliance report

30 notices reported (0 errors, 30 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 1

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "1"
missing_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
missing_recommended_field WARNING 14

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_end_date"
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
"routes.txt" 13 "agency_id"
"routes.txt" 14 "agency_id"
route_short_name_too_long WARNING 13

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"CAN_TUL" 2 "Daytrip Shuttle"
"TUL_CAN" 3 "Daytrip Shuttle"
"CAN_AKM" 4 "Daytrip Shuttle"
"AKM_CAN" 5 "Daytrip Shuttle"
"CAN_PTA" 6 "Daytrip Shuttle"
"PTA_CAN" 7 "Daytrip Shuttle"
"CAN_XCA" 8 "Daytrip Shuttle"
"XCA_CAN" 9 "Daytrip Shuttle"
"CAN_COZ" 10 "Daytrip Shuttle"
"COZ_CAN" 11 "Daytrip Shuttle"
"CAN_PDC" 12 "Daytrip Shuttle"
"PDC_CAN" 13 "Daytrip Shuttle"
"TUL_PDC" 14 "Daytrip Shuttle"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260505" "20251201" "20260430"