GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-27T01:58:07Z,
for the dataset file:///shared/rts-livingston_0d435fad.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
The Routing Company
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2025-08-25
Feed End Date:
2030-02-05

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 87
  • Stops: 46
  • Trips: 87

Specification Compliance report

153 notices reported (0 errors, 37 warnings, 116 infos)

Notice Code Severity Total
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 2

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.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 31

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.
"trips.txt" "trip_short_name" "CS M-F 8:26AM" 2
"trips.txt" "trip_short_name" "CS M-F 9:38AM" 3
"trips.txt" "trip_short_name" "CS M-F 10:35AM" 4
"trips.txt" "trip_short_name" "CS M-F 6:35PM" 5
"trips.txt" "trip_short_name" "CS M-F 11AM" 6
"trips.txt" "trip_short_name" "CS M-F 8:05PM" 7
"trips.txt" "trip_short_name" "CS M-F 3PM" 8
"trips.txt" "trip_short_name" "CS M-F 1:25PM" 9
"trips.txt" "trip_short_name" "CS M-F 11:25AM" 10
"trips.txt" "trip_short_name" "CS M-F 2:20PM" 12
"trips.txt" "trip_short_name" "CS M-F 11:50AM" 13
"trips.txt" "trip_short_name" "CS M-F 9:20PM" 21
"trips.txt" "trip_short_name" "CS M-F 1PM" 22
"trips.txt" "trip_short_name" "ES 1:00PM" 23
"trips.txt" "trip_short_name" "CS M-F 3:55PM" 26
"trips.txt" "trip_short_name" "CS M-F 1:50PM" 27
"trips.txt" "trip_short_name" "CS M-F 7:25PM" 32
"trips.txt" "trip_short_name" "CS M-F 4:20PM" 34
"trips.txt" "trip_short_name" "CS M-F 5PM" 39
"trips.txt" "trip_short_name" "ES 3:40PM" 41
"trips.txt" "trip_short_name" "ES 3PM" 42
"trips.txt" "trip_short_name" "ES 1:35PM" 43
"trips.txt" "trip_short_name" "ES 11:05AM" 44
"trips.txt" "trip_short_name" "CS M-F 8AM" 46
"trips.txt" "trip_short_name" "CS M-F 5:45PM" 48
"trips.txt" "trip_short_name" "ES 2:25PM" 49
"trips.txt" "trip_short_name" "ES 11:40AM" 50
"trips.txt" "trip_short_name" "ES 10:30AM" 51
"trips.txt" "trip_short_name" "CS M-F 3:25PM" 64
"trips.txt" "trip_short_name" "243 AM" 79
"trips.txt" "trip_short_name" "243 PM" 80
route_short_name_too_long WARNING 3

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

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`.
"1046" 2 "Knight Express"
"1039" 4 "Rochester Shuttle"
"1042" 6 "Campus Shuttle"
big_gap_in_service INFO 25

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"service-2205" "2027-12-18" "2028-01-08" 20
"service-2204" "2027-12-18" "2028-01-08" 20
"service-2206" "2027-12-18" "2028-01-08" 20
"service-2203" "2026-12-18" "2027-01-08" 20
"service-2202" "2026-12-18" "2027-01-08" 20
"service-2207" "2027-12-18" "2028-01-08" 20
"service-2208" "2027-12-18" "2028-01-08" 20
"service-3031" "2027-12-18" "2028-01-08" 20
"service-2239" "2026-12-18" "2027-01-08" 20
"service-2209" "2027-12-18" "2028-01-08" 20
"service-2210" "2027-12-18" "2028-01-08" 20
"service-2253" "2027-12-18" "2028-01-08" 20
"service-2211" "2027-12-18" "2028-01-08" 20
"service-2256" "2027-12-18" "2028-01-08" 20
"service-2255" "2027-12-18" "2028-01-08" 20
"service-2240" "2026-12-18" "2027-01-08" 20
"service-2212" "2027-12-18" "2028-01-08" 20
"service-2257" "2027-12-18" "2028-01-08" 20
"service-2241" "2026-12-18" "2027-01-08" 20
"service-3032" "2027-12-18" "2028-01-08" 20
"service-3033" "2027-12-18" "2028-01-08" 20
"service-3034" "2027-12-18" "2028-01-08" 20
"service-2258" "2027-12-18" "2028-01-08" 20
"service-3030" "2027-12-18" "2028-01-08" 20
"service-3035" "2027-12-18" "2028-01-08" 20
service_extends_far_in_the_future INFO 87

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

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

serviceId (?) The service_id that ends far in the future. serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"service-2273" "2030-02-03"
"service-2264" "2030-02-02"
"service-2274" "2030-02-03"
"service-2272" "2030-02-03"
"service-2259" "2030-02-02"
"service-2265" "2030-02-02"
"service-2271" "2030-02-03"
"service-2266" "2030-02-02"
"service-2269" "2030-02-03"
"service-2267" "2030-02-02"
"service-2268" "2030-02-03"
"service-2270" "2030-02-03"
"service-2102" "2030-02-05"
"service-2103" "2030-02-05"
"service-2104" "2030-02-05"
"service-2200" "2030-02-03"
"service-2205" "2030-02-02"
"service-2204" "2030-02-02"
"service-2206" "2030-02-02"
"service-2203" "2030-02-01"
"service-2195" "2030-02-03"
"service-2201" "2030-02-03"
"service-2202" "2030-02-01"
"service-2101" "2030-02-05"
"service-2214" "2030-02-05"
"service-2215" "2030-02-05"
"service-2216" "2030-02-05"
"service-2230" "2030-02-05"
"service-2217" "2030-02-05"
"service-2232" "2030-02-05"
"service-2224" "2030-02-05"
"service-2221" "2030-02-05"
"service-2218" "2030-02-05"
"service-2234" "2030-02-03"
"service-2223" "2030-02-05"
"service-2219" "2030-02-05"
"service-2207" "2030-02-02"
"service-2235" "2030-02-03"
"service-2208" "2030-02-02"
"service-3031" "2030-02-02"
"service-3037" "2030-02-03"
"service-3042" "2030-02-03"
"service-2239" "2030-02-01"
"service-2233" "2030-02-05"
"service-2220" "2030-02-05"
"service-2323" "2030-02-04"
"service-2236" "2030-02-03"
"service-2209" "2030-02-02"
"service-2226" "2030-02-05"
"service-2222" "2030-02-05"
service_window_outside_feed_period INFO 4

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"service-2103" "2025-06-02" "2030-02-05" 84 0
"service-2104" "2025-06-02" "2030-02-05" 84 0
"service-2101" "2025-06-02" "2030-02-05" 84 0
"service-2102" "2025-06-02" "2030-02-05" 84 0