GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T04:07:06Z,
for the dataset file:///shared/sdm-bogota-co.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Spanish
Feed Start Date:
2013-01-01
Feed End Date:
2020-12-25

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: 6
  • Blocks: 0
  • Routes: 537
  • Shapes: 646
  • Stops: 8724
  • Trips: 118462

Specification Compliance report

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

Notice Code Severity Total
duplicate_route_name WARNING 19

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
94 "100721-2487" 95 "100721-2488" "639" "" 3 "100721-3"
152 "100721-1711" 153 "100721-17112" "T13-2" "" 3 "100721-4"
209 "100721-99422" 210 "100721-99595" "2-7" "" 3 "100721-2"
224 "100721-99574" 225 "100721-99575" "4-3" "" 3 "100721-2"
245 "100721-99448" 246 "100721-99736" "6-5" "" 3 "100721-2"
283 "100721-9998" 284 "100721-99377" "B10" "" 3 "100721-1"
286 "100721-99378" 287 "100721-99147" "B12" "" 3 "100721-1"
289 "100721-99642" 290 "100721-99644" "B14" "" 3 "100721-1"
293 "100721-99846" 294 "100721-99848" "B18" "" 3 "100721-1"
310 "100721-99184" 311 "100721-99724" "B74" "" 3 "100721-1"
348 "100721-2485" 351 "100721-24862" "C53" "" 3 "100721-3"
470 "100721-99316" 471 "100721-99492" "M84" "" 3 "100721-6"
487 "100721-2275" 488 "100721-22752" "Se10" "" 3 "100721-3"
508 "100721-1266" 509 "100721-12662" "C115" "" 3 "100721-3"
510 "100721-2297" 511 "100721-2296" "T31" "" 3 "100721-3"
521 "100721-2243" 522 "100721-2244" "T23" "" 3 "100721-3"
521 "100721-2243" 524 "100721-22442" "T23" "" 3 "100721-3"
526 "100721-2245" 527 "100721-22452" "T37" "" 3 "100721-3"
528 "100721-2348" 529 "100721-23482" "Tc6" "" 3 "100721-3"
expired_calendar WARNING 4

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 "100721-1"
3 "100721-2"
4 "100721-4"
5 "100721-5"
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 "20251213" "20201225" "20251220"
mixed_case_recommended_field WARNING 3666

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.

Only the first 50 of 3666 affected records are displayed below.

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" "AC 63 - KR 22" 2
"stops.txt" "stop_name" "KR 19 - CL 70" 3
"stops.txt" "stop_name" "AC 34 - KR 16" 5
"stops.txt" "stop_name" "AK 13 - CL 31" 7
"stops.txt" "stop_name" "AC 32 - KR 13a" 8
"stops.txt" "stop_name" "AC 34 - KR 24" 10
"stops.txt" "stop_name" "AK 28 - CL 37" 11
"stops.txt" "stop_name" "CL 39A - AK 24" 12
"stops.txt" "stop_name" "AK 24 - CL 40" 13
"stops.txt" "stop_name" "AC 53 - AK 24" 14
"stops.txt" "stop_name" "AC 53 - KR 28" 15
"stops.txt" "stop_name" "AC 53 - KR 37a" 16
"stops.txt" "stop_name" "AC 53 - KR 46" 17
"stops.txt" "stop_name" "AK 68 - CL 67g" 18
"stops.txt" "stop_name" "AC 72 - KR 68g" 20
"stops.txt" "stop_name" "AC 72 - KR 70f" 21
"stops.txt" "stop_name" "AC 72 - KR 75" 22
"stops.txt" "stop_name" "AC 72 - KR 80" 23
"stops.txt" "stop_name" "AC 90 - KR 87b" 29
"stops.txt" "stop_name" "AC 90 - KR 91" 30
"stops.txt" "stop_name" "TV 94L - CL 82" 32
"stops.txt" "stop_name" "CL 82 - KR 92" 33
"stops.txt" "stop_name" "KR 90 - CL 83" 34
"stops.txt" "stop_name" "KR 95A - CL 129d" 41
"stops.txt" "stop_name" "AC 26 - KR 82" 43
"stops.txt" "stop_name" "CL 97 - KR 60" 46
"stops.txt" "stop_name" "CL 106 - TV 59" 47
"stops.txt" "stop_name" "CL 106 - KR 54" 48
"stops.txt" "stop_name" "CL 106 - KR 53" 49
"stops.txt" "stop_name" "KR 53 - CL 115" 50
"stops.txt" "stop_name" "AC 134 - KR 58c" 54
"stops.txt" "stop_name" "CL 137 - KR 90a" 60
"stops.txt" "stop_name" "CL 130c - KR 93" 61
"stops.txt" "stop_name" "CL 129b - KR 94b" 62
"stops.txt" "stop_name" "KR 95A - CL 129c" 63
"stops.txt" "stop_name" "CL 129c - KR 97a" 64
"stops.txt" "stop_name" "KR 100a - CL 130" 65
"stops.txt" "stop_name" "AC 132 - AK 104" 67
"stops.txt" "stop_name" "AC 132 - KR 110a" 68
"stops.txt" "stop_name" "AK 68 - AC 63" 69
"stops.txt" "stop_name" "CL 139 - KR 129b" 70
"stops.txt" "stop_name" "AC 26 - KR 103" 71
"stops.txt" "stop_name" "KR 149b - CL 138" 72
"stops.txt" "stop_name" "KR 17 - CL 66" 77
"stops.txt" "stop_name" "AC 90 - KR 87" 88
"stops.txt" "stop_name" "AC 19 - KR 4" 90
"stops.txt" "stop_name" "CL 1F - KR 35b" 92
"stops.txt" "stop_name" "CL 1F - KR 32b" 93
"stops.txt" "stop_name" "CL 1F - KR 31" 94
"stops.txt" "stop_name" "CL 1F - KR 29b" 95
stop_too_far_from_shape WARNING 7

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
81720 "100721-SP_502" "100721-TR_502_1" 3680109 "100721-1673" "KR 100 - CL L 20" [4.675999660738318,-74.14366607700359] 103.41664672904093
73508 "100721-SP_404" "100721-TR_404_1" 3394283 "100721-40072" "AK 11 - CL 123" [4.700625505335906,-74.0330662046809] 149.9391218179647
73508 "100721-SP_404" "100721-TR_404_1" 3394285 "100721-33166" "AK 9 - CL 110" [4.69084172616935,-74.03807008937144] 143.94672753046902
112304 "100721-SP_2296" "100721-TR_2296_1" 5045302 "100721-31876" "AC 26 - KR 68B Bis" [4.656444,-74.105706] 126.09401564814692
23234 "100721-SP_141" "100721-TR_141_1" 1315168 "100721-3267" "KR 99 - CL 20c" [4.675662500861339,-74.14120795364843] 130.23213645246005
95819 "100721-SP_79" "100721-TR_79_1" 4425374 "100721-28324" "CL 66 - KR 17" [4.655650409492936,-74.06641696761237] 133.98834701844928
114550 "100721-SP_22442" "100721-TR_22442_1" 5106585 "100721-36852" "AK 7 - CL 36" [4.625698000000001,-74.065958] 152.6210294527326
stops_match_shape_out_of_order WARNING 8

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.
116731 "100721-SP_2134" "100721-TR_2134_1" 5209263 "100721-47481" "DG 32B Sur - KR 12B 533a12" [4.56926699219159,-74.11074140357694] 5209262 "100721-4860" "DG 32C BIS A Sur - TV 12d" [4.569067999999999,-74.110748]
96332 "100721-SP_806" "100721-TR_806_1" 4450099 "100721-43322" "AV Caracas - CL 74 C Sur" [4.514839639441121,-74.11639144728309] 4450098 "100721-3140" "AV. Caracas - CL 74C Sur" [4.514827681872184,-74.11638533105769]
35364 "100721-SP_2486" "100721-TR_2486_1" 1961618 "100721-1944" "AC 100 - KR 45" [4.6872802730531395,-74.05962773981354] 1961617 "100721-3745" "211a00" [4.687277059054277,-74.05961509810709]
35174 "100721-SP_2485" "100721-TR_2485_1" 1930888 "100721-1944" "AC 100 - KR 45" [4.6872802730531395,-74.05962773981354] 1930887 "100721-3745" "211a00" [4.687277059054277,-74.05961509810709]
18313 "100721-SP_1370" "100721-TR_1370_1" 980624 "100721-1807" "CL 42 Sur - KR 78D Bis" [4.614750948302931,-74.15918061793464] 980623 "100721-1806" "CL 41B Sur - KR 74" [4.612731863545149,-74.15600496611997]
740 "100721-SP_1008" "100721-TR_1008_100_2" 51408 "100721-43322" "AV Caracas - CL 74 C Sur" [4.514839639441121,-74.11639144728309] 51407 "100721-3140" "AV. Caracas - CL 74C Sur" [4.514827681872184,-74.11638533105769]
38317 "100721-SP_1563" "100721-TR_1563_1" 2183626 "100721-1807" "CL 42 Sur - KR 78D Bis" [4.614750948302931,-74.15918061793464] 2183625 "100721-1806" "CL 41B Sur - KR 74" [4.612353049110456,-74.15579248048344]
78958 "100721-SP_468" "100721-TR_468_1" 3576179 "100721-1807" "CL 42 Sur - KR 78D Bis" [4.614750948302931,-74.15918061793464] 3576178 "100721-1806" "CL 41B Sur - KR 74" [4.612731863545149,-74.15600496611997]
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.
"20251213" "20130101" "20200101"