Board packet · transit data quality · checked 2026-08-23
Santa Maria Area Transit
Grade D · 64.2 / 100
Down 1.6 points since 2026-08-22 (D to D).
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
Since the previous compatible check, 1 finding was no longer reported:
- 2 of 6 trips scheduled during the sampling window had no live predictions.
This records feed state, not who made a change or why.
What needs attention next
Three improvements, in priority order, each sized so the board can see what it is approving:
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
290 of 290 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.
Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.
11 of 13 sampled vehicle positions were far from their assigned route (worst: 10998 m). A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.
Estimated effort: A vendor support ticket with the trip ids attached.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
528 of 528 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
- 290 of 290 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
- 11 of 13 sampled vehicle positions were far from their assigned route (worst: 10998 m).
- Next action
- Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.
- 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
- 528 of 528 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/santa-maria-area-transit-2272/. Rubric v1.3, validator 8.0.1.