Home
United States Feeds
hudson-link
Source Data Validation Report

hudson-link — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T06:22:22Z,
for the dataset file:///shared/hudson-link_883451ca.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Lower Hudson Valley Transit
- website: http://www.ridehudsonlink.com
- phone number: (844)822-8920
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2025-10-05 to 2026-06-30 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 52
Routes: 7
Shapes: 14
Stops: 30
Trips: 663

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Headsigns Stops Wheelchair Accessibility Location Types

Specification Compliance report

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

Notice Code Severity Total

missing_recommended_field WARNING 7

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"

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"

route_long_name_contains_short_name WARNING 4

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`.
"H01"	2	"H01"	"H01 (Suffern-Palisades Center)"
"H03"	4	"H03"	"H03 (Monsey-White Plains)"
"H05"	5	"H05"	"H05 (Palisades Center-White Plains)"
"H07"	6	"H07"	"H07 (Palisades Center-Tarrytown)"