Avon Transit

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

   155 of 155 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

   Effort: Usually one value per route pattern in your scheduling source.

2. 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.

   Effort: Usually an export-tool fix, not hand editing.

3. 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.

   Effort: Usually an export-tool fix, not hand editing.

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 116 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-08-01

Service window

116 days of service data remain. Last service date 2026-11-25.

Feed version

1

Location

Colorado