Board packet · transit data quality · checked 2026-08-01
Greater Portland Metro Bus
Grade F · 54.6 / 100
Down 1.4 points since 2026-07-31 (F to F).
What this grade measures
The quality of the schedule data this agency publishes 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:
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Estimated effort: Usually a vendor support ticket.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
1314 of 1314 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.
Estimated effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
1345 of 1345 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Estimated effort: A default or per-trip field in your export.
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
- The trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- 1314 of 1314 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
- 1345 of 1345 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
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/greater-portland-metro-bus-2642/. Rubric v1.3, validator 8.0.1.