Board packet · transit data quality · checked 2026-10-07
Avon Transit
Grade B · 88.4 / 100
Down 0.4 points since 2026-10-06 (B to B).
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:
Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.
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: Usually an export-tool fix, not hand editing.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
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: Usually an export-tool fix, not hand editing.
Turn on 'remove unused shapes' (or the like) in your export tool.
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
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: One setting.
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Colorado 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.
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
- On some trips the stop distances run a little past the end of the route line.
- Next action
- Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
- 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
- Some stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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 route shapes no trip uses.
- Next action
- Turn on 'remove unused shapes' (or the like) in your export tool.
- 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/avon-transit-2433/. Rubric v1.4, validator 8.0.1.