Call-prep brief · checked 2026-07-09
Clark County Public Transportation Benefit Area
Grade B · 84.1 / 100
Unchanged since 2026-07-08.
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
- Realtime quality no change
Top three things to fix
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Effort: Usually a vendor support ticket.
Agencies here usually clear this within about 1 week (based on 9 observed fixes).
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
Effort: Usually a vendor support ticket.
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
911 of 915 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.
Effort: A column in stops.txt; your scheduling software likely has it.
NTD certification readiness: Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 72 days.
agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
The bar this score answers to
The state transit-data program is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies.
Key facts
- Feed URL
- https://www.c-tran.com/images/Google/GoogleTransitUpload.zip
- Last checked
- 2026-07-09
- Service window
- 65 days of service data remain. Last service date 2026-09-12.
- Feed version
- 20260510-20260912
- State
- Washington
Part of the Washington portfolio: see where this agency sits among the state's feeds before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.