GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T18:36:43Z,
for the dataset file:///shared/maui.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-09-12
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: 16
  • Routes: 12
  • Shapes: 18
  • Stops: 210
  • Trips: 240

Specification Compliance report

126 notices reported (0 errors, 123 warnings, 3 infos)

Notice Code Severity Total
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 115

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 115 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.
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 2
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 3
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 4
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 5
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 6
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 7
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 8
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 9
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 10
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 11
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 12
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 13
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 14
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 15
"trips.txt" "trip_headsign" "1 WAILUKU LOOP" 16
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 17
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 18
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 19
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 20
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 21
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 22
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 23
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 24
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 25
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 26
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 27
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 28
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 29
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 30
"trips.txt" "trip_headsign" "2 WAILUKU LOOP REVERSE" 31
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 32
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 33
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 34
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 35
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 36
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 37
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 38
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 39
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 40
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 41
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 42
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 43
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 44
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 45
"trips.txt" "trip_headsign" "5 KAHULUI LOOP" 46
"trips.txt" "trip_headsign" "6 KAHULUI LOOP REVERSE" 47
"trips.txt" "trip_headsign" "6 KAHULUI LOOP REVERSE" 48
"trips.txt" "trip_headsign" "6 KAHULUI LOOP REVERSE" 49
"trips.txt" "trip_headsign" "6 KAHULUI LOOP REVERSE" 50
"trips.txt" "trip_headsign" "6 KAHULUI LOOP REVERSE" 51
route_long_name_contains_short_name WARNING 6

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`.
"2570" 4 "15" "15 - Kihei Villager"
"2572" 5 "40" "40 - Upcountry Islander"
"2573" 6 "23" "23 - Lahaina Villager"
"2574" 7 "35" "35 - Haiku Islander"
"2576" 9 "10" "10 - Kihei Islander"
"6220" 13 "29" "29 - West Maui Express"
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"