← Back to the full scorecard

Board packet · transit data quality · checked 2026-10-08

Berkshire Regional Transit Authority (BRTA)

Grade B · 89.2 / 100

Unchanged since 2026-10-07.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

  1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    194 of 208 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.

    Fixing this covers 194 of 208 stops, about 93% of them.

    Estimated effort: A column in stops.txt; your scheduling software likely has it.

  2. Remove retired stops from the export, or add them back to the trips that should serve them.

    Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Estimated effort: A review pass in your scheduling software.

  3. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

    Some files contain columns that are not part of the GTFS spec. Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Estimated effort: A quick look at the flagged files.

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Massachusetts as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

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
194 of 208 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

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/berkshire-regional-transit-authority-brta/. Rubric v1.4, validator 8.0.1.