GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T19:42:36Z,
for the dataset file:///shared/dnk-haywoodtransit.zip. No country code was provided.

Summary

Agencies included

Mountain Projects
- website: https://haywoodtransit.com/route-services/
- phone number: 9195158622
- email: dispatch@mountainprojects.org

Feed Info

Publisher Name:
ITRE: Publisher URL:
https://haywoodtransit.com/route-services/: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
2022-07-01: Feed End Date:
2030-12-31: Service Window:
2023-01-01 to 2029-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
feed_info.txt
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 2
Shapes: 2
Stops: 39
Trips: 3

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

Shapes Frequencies Feed Information Route Colors Location Types

Specification Compliance report

5 notices reported (0 errors, 4 warnings, 1 infos)

Notice Code

Severity

Total

missing_feed_contact_email_and_url

WARNING

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

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"

stops_match_shape_out_of_order

WARNING

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`.	shapeId (?) The id of the shape that is referred to.	tripId (?) The id of the trip that is referred to.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
4	"1.2"	"10053003"	59	"3484710"	"S. Haywood St. @ Church St."	[35.49017483934177,-82.98969731147994]	58	"3484714"	"Transfer Station"	[35.524487546610295,-82.93056556675702]

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.
"trips.txt"	"block_name"	11