GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T18:23:09Z,
for the dataset file:///shared/bcta.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • BCTA
    • website: https://bcta.com/
    • phone number: (724) 728-4255
    • email: support@availtec.com

Feed Info

Publisher Name:
Beaver County Transit Authority
Publisher URL:
https://bcta.com/
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-01-08
Feed End Date:
2026-12-31

Files included

  1. agency.txt
  2. calendar_dates.txt
  3. fare_attributes.txt
  4. feed_info.txt
  5. frequencies.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 19
  • Routes: 5
  • Shapes: 18
  • Stops: 241
  • Trips: 257

Specification Compliance report

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

Notice Code Severity Total
missing_feed_contact_email_and_url WARNING 1

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
route_long_name_contains_short_name WARNING 5

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`.
"1" 2 "1" "1 Ambridge/Beaver Falls"
"2" 3 "2" "2 Rochester/Ambridge"
"3" 4 "3" "3 Rochester/Vanport/Monaca"
"4" 5 "4" "4 Center/Pittsburgh"
"5" 6 "5" "5 Ambridge/Pittsburgh"