Call-prep brief · checked 2026-10-07

Roaring Fork Transportation Authority

Grade C · 76.4 / 100

Down 0.4 points since 2026-10-06 (C to C).

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 down 1.6
Rider experience no change

Top three things to fix

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
200 of 200 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.
Fixing this covers all 200 stops in the feed.
Effort: A column in stops.txt; your scheduling software likely has it.
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.
Effort: One setting.
Add feed_contact_email or feed_contact_url to feed_info.txt.
feed_info.txt lists no contact email and no contact URL. Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
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: One field, set once in export settings.

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: 200 of 200 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

Agency: Roaring Fork Transportation Authority
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 200 of 200 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/roaring-fork-transportation-authority-2278/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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 46 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.rfta.com/RFTAGTFSExport.zip
Last checked: 2026-10-07
Service window: 46 days of service data remain. Last service date 2026-11-22.
Feed version: S1000166
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.4, validator 8.0.1.