GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T20:11:21Z,
for the dataset file:///shared/beaver-county-transit-authority.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar_dates.txt
  3. routes.txt
  4. shapes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 1
  • Blocks: 25
  • Routes: 4
  • Shapes: 25
  • Stops: 234
  • Trips: 231

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 4

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.
2 "d3181ce2-9075-4cbb-86c9-a51fe7f17696"
3 "80ec048e-6c18-4ee8-8319-67ba9639bf23"
10 "e2fcd6c1-634f-4cb1-9456-8ed5fd5eaf48"
38 "1402e848-e680-45ab-87fd-be18fb54e361"
leading_or_trailing_whitespaces WARNING 117

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 117 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.
"stops.txt" 3 "stop_name" "9th St at Indiana Ave "
"stops.txt" 4 "stop_name" "Pennsylvania Ave at 6th St "
"stops.txt" 13 "stop_name" "Brodhead Rd at Bonanni Dr "
"stops.txt" 16 "stop_name" "Brodhead Rd opp. Village Shops "
"stops.txt" 17 "stop_name" "Brodhead Rd at Center Grange Rd "
"stops.txt" 18 "stop_name" "Brodhead Rd at Main St "
"stops.txt" 19 "stop_name" "Brodhead Rd at Charity St "
"stops.txt" 21 "stop_name" "Brodhead Rd opp. Ridgeview Dr "
"stops.txt" 23 "stop_name" "Brodhead Rd at Hospital Dr "
"stops.txt" 25 "stop_name" "Mill St at Golf Course Rd "
"stops.txt" 28 "stop_name" "Mill St at Guy St "
"stops.txt" 30 "stop_name" "Brodhead Rd at Sheffield Rd "
"stops.txt" 31 "stop_name" "Main St at Brodhead Rd "
"stops.txt" 32 "stop_name" "Main St at 21st St "
"stops.txt" 35 "stop_name" "Tyler St at Warnock St "
"stops.txt" 36 "stop_name" "Tyler St at Upland St "
"stops.txt" 37 "stop_name" "Tyler St at Waugaman St "
"stops.txt" 44 "stop_name" "Franklin Ave at Engle St "
"stops.txt" 51 "stop_name" "Liberty Ave at 6th St "
"stops.txt" 53 "stop_name" "Ohio River Blvd at Riverview Ave "
"stops.txt" 54 "stop_name" "Ohio River Blvd at Elizabeth St "
"stops.txt" 56 "stop_name" "Ohio River Blvd at Camp Horne Rd "
"stops.txt" 57 "stop_name" "Ohio River Blvd at Walnut St "
"stops.txt" 58 "stop_name" "Ohio River Blvd at Hazel Ln "
"stops.txt" 61 "stop_name" "4th St at Park Rd "
"stops.txt" 62 "stop_name" "4th St at Merchant St "
"stops.txt" 63 "stop_name" "Merchant St at 6th St "
"stops.txt" 65 "stop_name" "Merchant St at 11th St "
"stops.txt" 67 "stop_name" "Duss Ave at 16th St "
"stops.txt" 68 "stop_name" "Duss Ave at 19th St "
"stops.txt" 69 "stop_name" "Duss Ave at 23rd St "
"stops.txt" 72 "stop_name" "Duss Ave at Keystone Rd "
"stops.txt" 74 "stop_name" "Duss Ave at Dearborn St "
"stops.txt" 75 "stop_name" "State St at Johnson Ave "
"stops.txt" 82 "stop_name" "3rd Ave at 8th St "
"stops.txt" 83 "stop_name" "3rd Ave at 5th St "
"stops.txt" 84 "stop_name" "Ohio River Blvd at East Rochester Plaza "
"stops.txt" 86 "stop_name" "Brighton Ave at Jefferson St "
"stops.txt" 89 "stop_name" "3rd Ave at Brightwood Manor "
"stops.txt" 90 "stop_name" "3rd Ave at 16th St "
"stops.txt" 91 "stop_name" "3rd Ave at 12th St "
"stops.txt" 92 "stop_name" "3rd Ave at 9th St "
"stops.txt" 93 "stop_name" "3rd Ave at 6th St "
"stops.txt" 94 "stop_name" "7th Ave at 6th St "
"stops.txt" 96 "stop_name" "7th Ave at 13th St "
"stops.txt" 97 "stop_name" "7th Ave at 17th St "
"stops.txt" 98 "stop_name" "7th Ave at 22nd St "
"stops.txt" 99 "stop_name" "7th Ave at 25th St "
"stops.txt" 101 "stop_name" "4th Ave at 36th St "
"stops.txt" 105 "stop_name" "Wallace Run Rd at Shenango Rd "
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"
same_name_and_description_for_route WARNING 1

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The id of the faulty record. routeDesc (?) The `routes.routes_desc` of the faulty record. specifiedField (?) Either `route_short_name` or `route_long_name`.
3 "0c2cf8b1-9b0c-41c2-b51d-3d8ebfd0ceb3" "Beaver/BVM" "route_long_name"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20251212" "20210219" "20211230"