Call-prep brief · checked 2026-11-21
Avon Transit
Grade B · 85.3 / 100
Unchanged since 2026-11-20.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
Top three things to fix
Check the flagged stop times for transposed minutes.
Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.
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.
Effort: A few minutes per flagged trip.
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.
Effort: Usually an export-tool fix, not hand editing.
Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing.
Between two distant stops, the times imply a speed no bus reaches. A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.
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.
Effort: Minutes per flagged trip once you open it.
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-11-02.
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
- Some scheduled trips move faster between stops than a bus can.
- Next action
- Check the flagged stop times for transposed minutes.
- 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
- Between two distant stops, the times imply a speed no bus reaches.
- Next action
- Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing.
- 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
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 141 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 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.
The bar this score answers to
A local transit-data support resource is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers.
Key facts
- Feed URL
- https://www.avon.org/DocumentCenter/View/25051/TownOfAvon_gtfs
- Last checked
- 2026-11-21
- Service window
- 141 days of service data remain. Last service date 2027-04-11.
- Feed version
- 1
- Location
- Colorado
Part of the Colorado portfolio: see where this agency sits among the other feeds in that group before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.5, validator 8.0.1.