GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T13:32:42Z,
for the dataset file:///shared/kauai_00be997b.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:
2025-12-23
Feed End Date:
N/A

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: 54
  • Routes: 11
  • Shapes: 17
  • Stops: 126
  • Trips: 238

Specification Compliance report

93 notices reported (0 errors, 90 warnings, 3 infos)

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 3

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"18488" 1296 4036.456382799699 86 1295 4036.456382799699 85
"29545" 5400 21060.273450114135 657 5399 21060.273450114135 656
"29554" 7938 44457.331710110506 1337 7937 44457.331710110506 1336
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 71

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 71 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" "EIWA (800 850 PARA)" 119
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 34
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 35
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 36
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 37
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 38
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 39
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 40
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 41
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 42
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 43
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 44
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 45
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 46
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 47
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 48
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 96
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 97
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 98
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 99
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 100
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 101
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 102
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 103
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 104
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 105
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 106
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 107
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 108
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 109
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 110
"trips.txt" "trip_headsign" "LIHUE SHUTTLE" 111
"trips.txt" "trip_headsign" "ANAHOLA-WAIMEA" 117
"trips.txt" "trip_headsign" "ANAHOLA-WAIMEA" 118
"trips.txt" "trip_headsign" "ANAHOLA-WAIMEA" 119
"trips.txt" "trip_headsign" "ANAHOLA-WAIMEA" 120
"trips.txt" "trip_headsign" "WAIMEA-ANAHOLA" 121
"trips.txt" "trip_headsign" "WAIMEA-ANAHOLA" 122
"trips.txt" "trip_headsign" "WAIMEA-ANAHOLA" 123
"trips.txt" "trip_headsign" "WAIMEA-ANAHOLA" 124
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 157
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 158
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 159
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 160
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 161
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 162
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 163
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 164
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 165
"trips.txt" "trip_headsign" "KOLOA SHUTTLE" 166
route_color_contrast WARNING 1

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"6936" 11 "#561F94" "#000000"
route_long_name_contains_short_name WARNING 11

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`.
"5194" 2 "70" "70 Lihue Shuttle"
"5195" 3 "800" "800 Wailua to Lihue Mainline"
"5196" 4 "850" "850 Lihue to Wailua Mainline"
"5197" 5 "100" "100 Kekaha to Lihue Mainline"
"5198" 6 "200" "200 Lihue to Kekaha Mainline"
"5199" 7 "30" "30 Koloa Shuttle"
"5200" 8 "400" "400 Hanalei to Lihue Mainline"
"5201" 9 "500" "500 Lihue to Hanalei Mainline"
"5202" 10 "60" "60 Kapahi Shuttle"
"6936" 11 "950" "950 Express"
"6941" 12 "900" "900 Express"
same_name_and_description_for_route WARNING 2

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 "5194" "70 Lihue Shuttle" "route_long_name"
11 "6936" "950 Express" "route_long_name"
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"