gtfs-ibague — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T15:11:36Z,
for the dataset file:///shared/gtfs-ibague_8a3d4d31.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
- Sistema Estratégico de Transporte Público de Ibagué
- website: https://transmusical.gov.co
- phone number:
- email: Not provided
Feed Info
- Publisher Name:
- Observatorio de Movilidad y Transporte - Universidad de Ibague - SETP
- Feed Email:
- omtu@unibague.edu.co
- Feed Language:
- Spanish
- Feed Start Date:
- 2024-01-01
- Feed End Date:
- 2030-12-31
- Service Window:
- 2024-01-01 to 2030-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
- feed_info.txt
- frequencies.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 0
- Routes: 30
- Shapes: 62
- Stops: 1153
- Trips: 62
Specification Compliance report
65 notices reported (0 errors, 2 warnings, 63 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| leading_or_trailing_whitespaces | WARNING | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
leading_or_trailing_whitespacesThe value in CSV file has leading or trailing whitespaces. This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser. The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces. You can see more about this notice here.
stop_too_far_from_shape | WARNING | 1 | stop_too_far_from_shapeStop too far from trip shape. Per GTFS Best Practices, route alignments (in You can see more about this notice here.
service_extends_far_in_the_future | INFO | 1 | service_extends_far_in_the_futureA service end date is more than 2 years in the future. You can see more about this notice here.
trip_with_shape_dist_traveled_but_no_shape_distances | INFO | 62 | trip_with_shape_dist_traveled_but_no_shape_distancesA trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt. When stop times define distance values but the shape does not carry matching distances on every point, consumers cannot use those distances to align stops to the shape geometry reliably. This inconsistency may cause incorrect routing or display behaviour. Note: Only the first stop time carrying a shape_dist_traveled value is referenced in the notice; this is a representative row rather than an exhaustive list. You can see more about this notice here. Only the first 50 of 62 affected records are displayed below.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||