GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T18:45:52Z,
for the dataset file:///shared/syncromatics-vailgov_cfcf02bd.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2026-06-07
Feed End Date:
2026-12-06

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_attributes.txt
  4. directions.txt
  5. feed_info.txt
  6. realtime_routes.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 31
  • Routes: 8
  • Shapes: 13
  • Stops: 100
  • Trips: 524

Specification Compliance report

11 notices reported (0 errors, 8 warnings, 3 infos)

Notice Code Severity Total
leading_or_trailing_whitespaces WARNING 2

leading_or_trailing_whitespaces

The 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.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 51 "stop_name" "1610 Sunburst Drive - Westbound "
"stops.txt" 58 "stop_name" "Simba Run "
same_name_and_description_for_route WARNING 5

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The id of the faulty record. routeDesc (?) The `routes.routes_desc` of the faulty record. specifiedField (?) Either `route_short_name` or `route_long_name`.
2 "5306" "West Vail Green" "route_long_name"
3 "5307" "East Vail" "route_long_name"
4 "5308" "Golf Course" "route_long_name"
5 "5309" "Sandstone" "route_long_name"
6 "5310" "West Vail Red" "route_long_name"
trip_distance_exceeds_shape_distance_below_threshold WARNING 1

trip_distance_exceeds_shape_distance_below_threshold

The distance between the last shape point and last stop point is greater than 0 but less than the 11.1m threshold.

You can see more about this notice here.

tripId (?) The faulty record's trip id. shapeId (?) The faulty record's shape id. maxTripDistanceTraveled (?) The faulty record's trip max distance traveled. maxShapeDistanceTraveled (?) The faulty record's shape max distance traveled. geoDistanceToShape (?) The distance in meters between the shape and the stop.
"6151642" "16652" 9549.796899243205 9549.78880848495 0.0
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"calendar_attributes.txt"
"realtime_routes.txt"
"directions.txt"