GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T18:30:44Z,
for the dataset file:///shared/schuyler-county-transit-1.zip. No country code was provided.

Summary

Agencies included

Schuyler County Transit
- website: https://www.schuylercountytransit.org
- phone number: (607) 535-3555
- email: schuylercountytransit@arcofcs.org

Feed Info

Publisher Name:
Schuyler County Transit: Publisher URL:
https://schuylercountytransit.org: Feed Email:
schuylercountytransit@arcofcs.org: Feed Language:
English: Feed Start Date:
2023-09-01: Feed End Date:
2025-09-01: Service Window:
2023-09-01 to 2026-12-31 (?) 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
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 4
Shapes: 18
Stops: 43
Trips: 51

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

Shapes Feed Information Fares V1 Route Colors Headsigns Bike Allowed Continuous Stops

Specification Compliance report

8 notices reported (0 errors, 5 warnings, 3 infos)

Notice Code

Severity

Total

feed_expiration_date7_days

WARNING

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20251212"	"20250901"	"20251219"

route_long_name_contains_short_name

WARNING

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`.
"rt2corning"	2	"Corning Cnx"	"Corning Cnx"
"rt7elmira"	3	"Elmira Cnx"	"Elmira Cnx"
"rt6tompkins"	4	"Tompkins Cnx"	"Tompkins Cnx"
"rt1village"	5	"Village Cnx"	"Village Cnx"

unknown_column

INFO

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the unknown column.	index (?) The index of the faulty column.
"agency.txt"	"agency_branding_url"	7
"feed_info.txt"	"feed_id"	2
"routes.txt"	"route_branding_url"	8