Feed status · checked 2026-08-01
Beaver County Transit Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Pennsylvania.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 81 minutes ago; last changed 21 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
241 of 241 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
257 of 257 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 241 of 241 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 257 of 257 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 152 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 9 instances (0 error, 7 warning, 2 informational).
Service data covers the next 152 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
211 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Wallace Run Rd + Shenango Rd", "Shenango Rd + Wallace Run Rd", "4th Ave opp 47th St", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 241 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (teal)
- 2 (orange)
- 3 (yellow)
- 4 (green)
- 5 (gray)
| Route | Type | Line color |
|---|---|---|
| 1 1 Ambridge/Beaver Falls | Bus | teal |
| 2 2 Rochester/Ambridge | Bus | orange |
| 3 3 Rochester/Vanport/Monaca | Bus | yellow |
| 4 4 Center/Pittsburgh | Bus | green |
| 5 5 Ambridge/Pittsburgh | Bus | gray |
List every stop
- Rochester Transportation Center
- Walmart Supercenter
- Chippewa Central Square (Giant Eagle)
- Chippewa Center (Dunham's)
- Wallace Run Rd + Shenango Rd
- Shenango Rd + Wallace Run Rd
- 4th Ave opp 47th St
- 4th Ave + 47th St
- 4th Ave opp 45th St
- 4th Ave + 45th St
- 4th Ave opp 43rd St
- 4th Ave + 43rd St
- 4th Ave + 36th St
- 4th Ave + 36th St
- 4th Ave opp 33rd St
- 4th Ave + 33rd St
- 7th Ave + 25th St
- 7th Ave + 25th St
- 7th Ave + 22nd St
- 7th Ave + 22nd St
- 7th Ave + 17th St
- 7th Ave + 17th St
- 7th Ave + 13th St
- 7th Ave + 13th St
- 7th Ave + 10th St
- 7th Ave + 10th St
- 7th Ave + 6th St
- 7th Ave + 6th St
- 3rd Ave + 6th St
- 3rd Ave + 6th St
- 3rd Ave + 9th St
- 3rd Ave + 9th St
- 3rd Ave + 12th St
- 3rd Ave + 12th St
- 3rd Ave + 16th St
- 3rd Ave + 16th St
- 3rd Ave + Brightwood Manor
- 3rd Ave + Brightwood Manor
- YMCA Dr + 3rd Ave
- 2230 3rd Ave (YMCA)
- 437 Delaware Ave
- 438 Delaware Ave
- Brighton Ave + Jefferson St
- Brighton Ave + Jefferson St
- Brighton Ave + New York Ave
- Brighton Ave + Pleasant St
- Ohio River Blvd + East Rochester Plaza
- 3rd Ave + 5th St
- 3rd Ave opp 5th St
- 3rd Ave + 8th St
- 3rd Ave opp 8th St
- 3rd Ave + Harvey Run Rd
- 3rd Ave opp Harvey Run Rd
- 1st Ave + 9th St
- 1st Ave + 9th St
- Northern Lights Shopping Center
- Northern Lights Shopping Center
- Ohio River Blvd + Virginia Ave
- State St opp. Phillips St
- State St + Phillip St
- State St + Holmes Ave
- State St + Holmes Ave
- State St + Johnson Ave
- State St + Johnson Ave
- Duss Ave + Dearborn St
- Duss Ave opp Dearborn St
- Duss Ave opp Legionville Hollow Rd
- 2950 Duss Ave
- 2973 Duss Ave
- Duss Ave + Keystone Rd
- Duss Ave opp Keystone Rd
- Duss Ave + Harmony Ave
- Duss Ave opp Harmony Rd
- Duss Ave + 25th St
- Duss Ave opp 25th St
- Duss Ave + 23rd St
- Duss Ave + 23rd St
- Duss Ave + 21st Street North
- Duss Ave + 21st Street South
- Duss Ave + 19th St
- Duss Ave + 19th St
- Duss Ave + 16th St
- Duss Ave + 16th St
- Duss Ave + 14th St
- Duss Ave + 14th St
- 11th St opp. Ambridge Police Dept
- 719 Merchant St
- Merchant St + 4th St
- 4th St + Park Rd
- 4th St + Park Rd
- Ohio River Blvd + Broad St
- Ohio River Blvd + Broad St
- Ohio River Blvd + Quaker VSC
- Ohio River Blvd opp Quaker VSC
- Ohio River Blvd + Hazel Ln
- Ohio River Blvd + Hazel Ln
- Ohio River Blvd + Walnut St
- Ohio River Blvd + Walnut St
- Merchant St + 8th St
- Merchant St + 6th St
- East Busway (Regional Bus Stop)
- Ohio River Blvd + Willow St
- Ohio River Blvd + Monitor Ave
- Ohio River Blvd + Elizabeth St
- Ohio River Blvd + Riverview Ave
- Liberty Ave + Smithfield St
- Liberty Ave + Smithfield St
- Ohio River Blvd + Fisk St
- Merchant St + 4th St
- 810 Merchant St
- Merchant St + 11th St
- Liberty Ave + William Penn
- Grant St + Liberty Ave (Federal Bldg)
- Ambridge + Park & Ride
- Grant St at Oliver Ave
- Merchant St + 11th St
- Ohio River Blvd + McKees Rocks Bridge
- Ohio River Blvd opp McKees Rocks Bridge
- Ohio River Blvd + Riverview Ave
- Ohio River Blvd + Elizabeth St
- Ohio River Blvd + Camp Horne Rd
- Richard J. Ober Expressway Travel Center
- 9th St + Indiana Ave
- 9th St + Indiana Ave
- Pennsylvania Ave + 6th St
- Pennsylvania Ave + 6th St
- Walmart Plaza
- Walmart Plaza 2
- Township Market Place (Vision Works)
- Township Market Place (Lowe’s Plaza)
- Township Market Place (Texas Roadhouse)
- Township Market Place (opp Texas RH)
- Liberty Ave + Gateway #4
- Wagner Road (Target)
- Wagner Road (First Commonwealth Bank)
- 79 Wagner Rd (opp HV Rehab)
- 79 Wagner Rd (HV Rehab)
- Beaver Valley Mall (El Paso)
- Brodhead Rd + North Branch Rd
- Brodhead Rd + Oak Ln
- Brodhead Rd + Lincoln Dr
- Brodhead Rd opp Lincoln Dr
- Brodhead Rd opp Bonanni Dr
- Brodhead Rd + Bonanni Dr
- Brodhead Rd + Mulberry Ln
- 3531 Brodhead Rd
- CCBC (Middle Lot)
- Brodhead Rd + College Rd
- Brodhead Rd opp College Rd
- Brodhead Rd + Sherwood Dr
- Brodhead Rd opp Village Shops
- Brodhead Rd + Center Grange Rd
- Brodhead Rd + Center Grange Rd
- Brodhead Rd opp Main St
- Brodhead Rd + Main St
- Brodhead Rd opp Charity St
- Brodhead Rd + Charity St
- Brodhead Rd + Ridgeview Dr
- Brodhead Rd opp Ridgeview Dr
- Brodhead Rd + Orchard St
- Brodhead Rd + Mt Carmel Drive
- Brodhead + Smith Ave North
- Bordhead + Smith Ave South
- Brodhead Rd + Caler St
- Brodhead Rd + Hospital Dr
- AdmiralStr
- AdmiralStr
- Mill St opp Golf Course Rd
- Mill St + Golf Course Rd
- Mill St + Guy St
- Mill St + Spring St
- Green Garden Plaza (Giant Eagle)
- Brodhead Rd + Sheffield Rd
- Brodhead Rd + Sheffield Rd
- Main St + Brodhead Rd
- Main St + Brodhead Rd
- Main St + 21st St
- Main St + 21st St
- 21st Str Aldi
- 21st Str opp Aldi
- Tyler St + Grand Ave
- Grand Ave + Tyler Ave
- Tyler St + Warnock St
- Tyler St + Warnock St
- Tyler St + Upland St
- Tyler St + Upland St
- Waugaman St + Tyler St
- Tyler St + Waugaman St
- Wykes Street
- Monaca Rd opp 6th Ave
- Monaca Rd + Sheffield
- Monaca Rd opp Sheffield
- Franklin Ave + Orchard St
- Franklin Ave opp Pine St
- 746 Franklin Ave
- Franklin Ave (Klenovich's)
- Franklin Ave + Engle St
- Franklin Ave + Engle St
- 434 Franklin Ave
- 427 Franklin Ave
- Franklin Ave
- Franklin Ave (Municipal Parking Lot)
- 11th St + Maplewood Ave
- 319 Station St
- 11th St + Church St
- Duss Ave + 9th St
- Duss Ave + 8th St
- Duss Ave + Beaver Rd
- Merchant St + 6th St
- Liberty Ave + 6th St
- Liberty Ave + Market St
- Liberty Ave + Wood St
- 3rd St + Lincoln Ave
- 3rd St + Lincoln Ave
- 3rd St + Beaver St
- 3rd St + Beaver St
- 3rd St + Insurance St
- 3rd St + Insurance St
- 376 Market St
- Market St + 5th St (Stop 1)
- Medical Center
- Friendship Circle (East)
- Friendship Circle (Entrance)
- Friendship Ridge
- Francis Farmer Apartments
- Market St + 5th St (Stop 2)
- Market Courthouse Parking Lot Entrance
- 3rd St + Buffalo St
- 3rd St + Buffalo St
- 3rd St + Walnut St
- StateAve@Chestnut
- 212 St Ave
- State Ave + Tamaqui Dr
- State Ave + Toy St
- State Ave + Locust St
- State Ave + Dravo St
- State Ave + Dravo St
- 697 State at Cornerstone
- 690 State Opp Cornstone
- Grant St + Strawberry Way
- Bus Layover at state st
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 74.8 | first check |
| 2026-07-30 | 74.8 | no change |
| 2026-07-31 | 74.8 | no change |
| 2026-08-01 | 74.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning257 instances
257 of 257 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning241 instances
241 of 241 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 152 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 257 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 152 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 87 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/beaver-county-transit-authority-2262/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.