hudson-link — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-08T03:44:47Z,
for the dataset file:///shared/hudson-link_a92759d0.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
LHTL
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-06-01
Feed End Date:
2027-06-28

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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 22
  • Routes: 7
  • Shapes: 18
  • Stops: 33
  • Trips: 2264

Specification Compliance report

3329 notices reported (0 errors, 3328 warnings, 1 infos)

Notice Code Severity Total
expired_calendar WARNING 1

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
5 "4"
leading_or_trailing_whitespaces WARNING 3319

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.

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

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stop_times.txt" 202 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 203 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 204 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 205 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 206 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 207 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 208 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 209 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 210 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 211 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 212 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 213 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 214 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 215 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 216 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 217 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 218 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 219 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 220 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 221 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 222 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 223 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 224 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 225 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 226 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 227 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 228 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 229 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 230 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 231 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 232 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 233 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 234 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 235 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 236 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 237 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 238 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 239 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 240 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 241 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 242 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 243 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 244 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 245 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 246 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 247 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 248 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 249 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 250 "stop_headsign" "H07 EB Tarrytown "
"stop_times.txt" 251 "stop_headsign" "H07 EB Tarrytown "
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
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.
"routes.txt" "route_long_name" "TEST ROUTE" 2
"stops.txt" "stop_name" "NY 59 FORMAN dr. EB" 18
stop_without_stop_time WARNING 4

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.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
28 "36" "81 Tome Valley Road"
29 "37" "6 Park Avenue"
33 "50" "I87 Overpass"
34 "51" "Test Hallet Pl and Chestnut"
unused_shape WARNING 1

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.
"shp-TEST-01" 25617
big_gap_in_service INFO 1

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.
"3" "2026-12-18" "2027-01-08" 20