GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-06T02:33:34Z,
for the dataset file:///shared/de30-ati.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Autoridad de Transporte Integrado

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Spanish
Feed Start Date:
2023-01-01
Feed End Date:
2024-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 37
  • Shapes: 75
  • Stops: 1369
  • Trips: 3695

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 3

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 "102404-1"
3 "102404-2"
4 "102404-3"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20251206" "20241231" "20251213"
mixed_case_recommended_field WARNING 39

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" "PR-165 lado opuesto calle 2" 17
"stops.txt" "stop_name" "PR-165 despues calle 2" 90
"stops.txt" "stop_name" "PR-2 despues lado opuesto PR-6" 152
"stops.txt" "stop_name" "PR-2 despues calle B" 160
"stops.txt" "stop_name" "PR-2 antes PR-6" 184
"stops.txt" "stop_name" "PR-2 antes calle A" 187
"stops.txt" "stop_name" "PR-174 despues calle A" 321
"stops.txt" "stop_name" "PR-174 despues calle F" 322
"stops.txt" "stop_name" "calle 27 antes calle 16" 454
"stops.txt" "stop_name" "calle 25 despues calle 27" 455
"stops.txt" "stop_name" "calle 25 antes calle 17" 456
"stops.txt" "stop_name" "calle 8 antes calle 11" 457
"stops.txt" "stop_name" "calle 2 antes lado opuesto calle 7" 458
"stops.txt" "stop_name" "PR-846 lado opuesto calle 21" 554
"stops.txt" "stop_name" "PR-187 despues PR-951" 787
"stops.txt" "stop_name" "PR-187 esquina PR-951" 789
"stops.txt" "stop_name" "PR-187 lado opuesto residencia" 796
"stops.txt" "stop_name" "PR-5 lado opuesto calle B" 822
"stops.txt" "stop_name" "PR-174 antes calle A" 825
"stops.txt" "stop_name" "calle 10 esquina calle 19" 839
"stops.txt" "stop_name" "calle 10 esquina calle 21" 840
"stops.txt" "stop_name" "PR-5 despues calle B" 859
"stops.txt" "stop_name" "calle 419 esquina calle 420" 1062
"stops.txt" "stop_name" "calle 419 ante calle 425" 1063
"stops.txt" "stop_name" "calle 419 ante calle 435" 1064
"stops.txt" "stop_name" "calle 435 despues calle 419" 1065
"stops.txt" "stop_name" "calle 435 esquina calle 517" 1066
"stops.txt" "stop_name" "calle 435 esquina antes calle 525" 1067
"stops.txt" "stop_name" "calle A antes lado opuesto calle D" 1115
"stops.txt" "stop_name" "calle B despues calle A" 1117
"stops.txt" "stop_name" "calle B despues calle 11" 1118
"stops.txt" "stop_name" "calle E antes calle D" 1119
"stops.txt" "stop_name" "calle D antes PR-169" 1120
"stops.txt" "stop_name" "PR-169 despues calle D" 1121
"stops.txt" "stop_name" "calle D esquina calle E" 1132
"stops.txt" "stop_name" "calle E antes calle B" 1133
"stops.txt" "stop_name" "calle B lado opuesto calle 11" 1134
"stops.txt" "stop_name" "calle A despues calle B" 1135
"stops.txt" "stop_name" "calle A esquina calle D" 1136
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.
"20251206" "20230102" "20241231"