GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-29T20:39:32Z,
for the dataset file:///shared/new-river-transit-authority-1_a4bc37da.zip. No country code was provided.

Summary

Agencies included

City of Beckley (New River Transit)
- website: https://newrivertransitauthority.org/
- phone number: (304)-894-8917
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Email:
alex@busmaps.com: Feed Language:
English: Feed Start Date:
2025-01-01: Feed End Date:
2027-12-31: Service Window:
2025-01-01 to 2027-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
calendar_dates.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 7
Routes: 6
Shapes: 11
Stops: 55
Trips: 70

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

Shapes Feed Information Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

4 notices reported (0 errors, 2 warnings, 2 infos)

Notice Code

Severity

Total

stop_too_far_from_shape

WARNING

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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.	stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`.	stopId (?) The id of the stop that is referred to.	stopName (?) The name of the stop that is referred to.	match (?) Latitude and longitude pair of the location.	geoDistanceToShape (?) Distance from stop to shape.
18	"103169-73517"	"103169-1127255"	171	"103169-134631"	"Crossroads Mall Ob"	[37.84593000000001,-81.19559]	108.69491676819817

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.
46	"103169-73524"	"103169-1127283"	464	"103169-134611"	"Cvs"	[37.78992579114193,-81.20869162936118]	463	"103169-221462"	"Greenbrier Estates apartment complex"	[37.79065027762401,-81.20102467591231]

trip_headsign_matches_intermediate_stop

INFO

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`.	tripId (?) The id of the trip with the problematic headsign.	tripHeadsign (?) The headsign value that matches an intermediate stop name.	stopId1 (?) The id of the intermediate stop whose name matches the headsign.	stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign.	stopId2 (?) The id of the actual last stop of the trip.
28	"103169-1127265"	"BIG Transfer Ib"	"103169-135256"	8	"103169-135256"
29	"103169-1127266"	"BIG Transfer Ib"	"103169-135256"	8	"103169-135256"