GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-02-24T19:37:15Z,
for the dataset file:///shared/nantucket-regional-transit-authority_e991fa1d.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. transfers.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 7
  • Routes: 11
  • Shapes: 11
  • Stops: 246
  • Trips: 120

Specification Compliance report

129 notices reported (0 errors, 129 warnings, 0 infos)

Notice Code Severity Total
missing_recommended_field WARNING 11

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.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 1

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" "DWS DROPOFF ONLY" 175
stop_without_stop_time WARNING 111

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

Only the first 50 of 111 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
50 "TL-54" "Broad Street in front of the Whaling Museum"
51 "TL-55" "Easton Stret/ North Water Street (Outbound Only)"
52 "TL-60" "North Liberty Street/West Chester Street"
53 "TL-61" "West Chester Street/New Lane (Outbound)"
54 "TL-62" "Grove Lane (Outbound)"
55 "TL-63" "Woodbury Lane/Meadow Lane (Outbound)"
56 "TL-64" "New Lane/Madaket Road (Outbound)"
57 "TL-65" "Dukes Road (Outbound)"
58 "TL-66" "Cavalier Stables (Outbound)"
59 "TL-67" "Crooked Lane (Outbound)"
60 "TL-68" "Maxcy Pond Road (Outbound Only)"
61 "TL-69" "Madaket Road (at bike crossing) (Outbound)"
62 "TL-70" "Barrett Farm Road/Swift Rock Road (Outbound)"
63 "TL-71" "Public Works Department (Outbound)"
64 "TL-72" "Warren's Landing Road (Outbound)"
65 "TL-73" "Second Bridge (Outbound)"
66 "TL-74" "Long Pond Drive (Outbound)"
67 "TL-75" "North Cambridge Street (Outbound)"
68 "TL-76" "Oakland Street (Outbound)"
69 "TL-77" "Starbuck Road (Outbound)"
70 "TL-78" "F Street (Outbound only)"
71 "TL-80" "Starbuck Road (Inbound)"
72 "TL-81" "Oakland Street (Inbound)"
73 "TL-82" "South Cambridge Street (Inbound)"
74 "TL-83" "Long Pond Drive (Inbound)"
75 "TL-84" "Second Bridge (Inbound)"
76 "TL-85" "Warren's Landing Road (Inbound)"
77 "TL-86" "Public Works Department (Inbound)"
78 "TL-87" "Barrett Farm Road/Swift Rock Road (Inbound)"
79 "TL-88" "Millbrook Road (Inbound Only)"
80 "TL-89" "Crooked Lane (Inbound)"
81 "TL-90" "Cavalier Stables (Inbound)"
82 "TL-91" "Dukes Road (Inbound)"
83 "TL-92" "New Lane/Madaket Road (Inbound)"
84 "TL-93" "Woodbury Lane/Meadow Lane (Inbound)"
85 "TL-94" "Grove Lane (Inbound)"
86 "TL-95" "West Cheste/New Lane (Inbound)"
87 "TL-96" "North Liberty Street/West Chester Street (Inbound)"
88 "TL-98" "West Chest Street/Centre Street (Inbound Only)"
89 "TL-99" "Chester Street/North Water Street (Inbound Only)"
90 "TL-100" "South Beach Street/Easton Street (Inbound Only)"
91 "TL-102" "North Water Street/Easton Street (Outbound Only)"
92 "TL-103" "South Beach Street/Easton Street (Outbound Only)"
93 "TL-104" "East Lincoln Avenue (Outbound)"
94 "TL-105" "North Beach Street/Charles Street (Outbound)"
95 "TL-106" "North Beach Street/Bathing Beach Road (Outbound)"
96 "TL-107" "Jetties Beach"
97 "TL-108" "North Beach Street/Bathing Beach Road (Inbound)"
98 "TL-109" "North Beach Street/Charles Street (Inbound)"
99 "TL-110" "East Lincoln Avenue (Inbound)"
unused_shape WARNING 5

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"TL-2" 2272
"TL-13" 4289
"TL-8" 4858
"TL-9" 4993
"TL-14" 5924