GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-02-03T21:02:22Z,
for the dataset file:///shared/metro-sabanas2_756ddb94.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
CRISTIAN GUTIERREZ y DAVID MONROY
Publisher URL:
http://www.google.com
Feed Email:
cdsgg1@gmail.com
Feed Language:
Spanish
Feed Start Date:
2025-01-01
Feed End Date:
2025-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 4
  • Shapes: 4
  • Stops: 135
  • Trips: 132

Specification Compliance report

13 notices reported (0 errors, 13 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"
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 "20260203" "20251231" "20260210"
stop_without_stop_time WARNING 6

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
4 "3" "04E003"
6 "5" "05I061"
33 "32" "07A024"
40 "39" "01A006"
41 "40" "01A007"
73 "72" "03A011"
stops_match_shape_out_of_order WARNING 4

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
2 "1" "1-1" 3 "2" "04A002" [9.302085507024179,-75.39621683316219] 2 "1" "04A001" [9.300922761026998,-75.39576860643587]
101 "2" "2-1" 3931 "35" "01A020" [9.298125456826465,-75.41184981569316] 3930 "34" "01A019" [9.297077416681523,-75.41115060636068]
35 "3" "3-1" 1259 "14" "09I003" [9.304159678742245,-75.37177038645528] 1258 "13" "09J002" [9.307630431900014,-75.36717779908868]
68 "4" "4-1" 2544 "8" "07A013" [9.31041750214292,-75.38199497591138] 2543 "6" "04A065" [9.305233601531933,-75.39654851331254]
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.
"20260203" "20240101" "20251231"