GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-13T19:31:07Z,
for the dataset file:/tmp/gtfs-validator-temp16435514768907404319/e82b6157-9116-4085-9499-fe8590719ec410577774475867466327.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-01-26
Feed End Date:
N/A

Files included


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

Counts


  • Agencies: 1
  • Blocks: 43
  • Routes: 15
  • Shapes: 43
  • Stops: 363
  • Trips: 566

Specification Compliance report

64 notices reported (0 errors, 61 warnings, 3 infos)

Notice Code Severity Total
leading_or_trailing_whitespaces WARNING 8

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" 10 "stop_name" "Loughborough Dr @ M St "
"stops.txt" 41 "stop_name" "Mansionette @ Redwing/St Patricks "
"stops.txt" 209 "stop_name" "Atwater Target "
"stops.txt" 211 "stop_name" "Atwater Target "
"stops.txt" 342 "stop_name" "University Transit Center "
"stops.txt" 345 "stop_name" "Mains St at C St Southbound "
"stops.txt" 361 "stop_name" "Merced Rescue Mission "
"routes.txt" 2 "route_long_name" "UC-UC Merced "
missing_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
missing_recommended_field WARNING 1

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_end_date"
mixed_case_recommended_field WARNING 2

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" "DMV (eastbound)" 20
"stops.txt" "stop_name" "21st @ G ST (westbound)" 328
route_long_name_contains_short_name WARNING 15

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"1225" 2 "UC" "UC-UC Merced"
"18" 3 "L" "L - Livingston Commuter"
"19" 4 "LB" "LB - Los Banos Commuter"
"20" 5 "M1" "M1 - Merced West Archived 2/17/2026"
"21" 6 "M2" "M2 - R Street Route"
"22" 7 "M3" "M3 - M Street Route"
"23" 8 "M4" "M4 - G Street Route"
"24" 9 "M5" "M5 - Merced South-East"
"25" 10 "M6" "M6 - Olive Loops"
"5889" 11 "M7" "M7 - South G Street Route"
"953" 12 "A2" "A2 - Winton Way"
"957" 13 "A1" "A1 - Atwater Loop"
"958" 14 "P" "P - Planada Commuter"
"972" 15 "T" "T - Turlock Commuter"
"973" 16 "W1" "W1 - Winton Commuter"
trip_distance_exceeds_shape_distance_below_threshold WARNING 34

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.
"6374448" "29020" 66519.17601434224 66519.17601434221 0.0
"A2A-11" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-13" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-15" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-17" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-19" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-21" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-23" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-25" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-3" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-5" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-7" "28993" 9054.484139240953 9054.405449641474 0.0
"A2A-9" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-1" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-11" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-13" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-15" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-17" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-3" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-5" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-7" "28993" 9054.484139240953 9054.405449641474 0.0
"A2AWKND-9" "28993" 9054.484139240953 9054.405449641474 0.0
"LAWKN D-1" "29028" 38614.318734340275 38613.93051842586 0.0
"LAWKN D-3" "29028" 38614.318734340275 38613.93051842586 0.0
"LAWKN D-5" "29028" 38614.318734340275 38613.93051842586 0.0
"LAWKN D-7" "29028" 38614.318734340275 38613.93051842586 0.0
"LAWKN D-9" "29028" 38614.318734340275 38613.93051842586 0.0
"LBA-1" "29020" 66519.17601434224 66519.17601434221 0.0
"LBA-3" "29020" 66519.17601434224 66519.17601434221 0.0
"LBA-5" "29020" 66519.17601434224 66519.17601434221 0.0
"LBA-7" "29020" 66519.17601434224 66519.17601434221 0.0
"LBB-2" "29020" 66519.17601434224 66519.17601434221 0.0
"LBB-6" "29020" 66519.17601434224 66519.17601434221 0.0
"LBB-8" "29020" 66519.17601434224 66519.17601434221 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"