GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Roaring Fork Transportation Authority (RFTA) Flex

Based on the feed this agency publishes

Service mode Bus

76.7 / 100

unchanged since 2026-07-31

Catalogued in Colorado.

Covers 61 daysAccessibility gapsFlexible serviceRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 70 minutes ago; last changed 41 days ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

218 of 218 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.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

7 of 7 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

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

⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

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
218 of 218 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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. 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. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 61 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send Trillium a fix request

This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.

Score by category

Correctness86.0 / 100

The MobilityData validator flagged 5 kinds of issue across 250 instances (0 error, 219 warning, 31 informational).

Freshness100.0 / 100

Service data covers the next 61 days.

Rider experience44.9 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 128 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Railroad Ave + 5th St", "Rifle Park & Ride", "Rifle Park & Ride", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

This feed has no route shapes, so the map shows its stops only.

This feed has 218 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

Routes in Roaring Fork Transportation Authority (RFTA) Flex's feed
RouteTypeLine color
DowntownerBusgreen (no shape in feed)
ADA Complementary ParatransitBusgreen (no shape in feed)
Garfield County TravelerBusgreen (no shape in feed)
Pitkin County Senior VanBusgreen (no shape in feed)
List every stop
  • Burlingame
  • Railroad Ave + 5th St
  • Rifle Park & Ride
  • Rifle Park & Ride
  • Cottonwood
  • Cottonwood
  • Firehouse
  • Firehouse
  • Main St + 6th St
  • New Castle Park & Ride
  • Hwy 82 + Spring Valley Rd DV
  • Aspen Glen UV
  • Aspen Glen DV
  • Ranch at Roaring Fork UV
  • Ranch at Roaring Fork DV
  • Hwy 82 + Catherine Store Rd UV
  • Hwy 82 + Catherine Store Rd DV
  • JW Dr + Buckskin Dr
  • JW Dr + Buckskin Dr
  • JW Dr + El Jebel Rd
  • JW Dr + El Jebel Rd
  • Holland Hills UV
  • Holland Hills DV
  • Basalt Park & Ride UV
  • Basalt Park & Ride DV
  • Downtown Basalt
  • Two Rivers Rd + Hillcrest Dr UV
  • Two Rivers Rd + Hillcrest Dr DV
  • Hwy 82 + Original Rd UV
  • Hwy 82 + Original Rd DV
  • Wingo Junction UV
  • Wingo Junction DV
  • Hwy 82 + Lazy Glen Way DV
  • Old Snowmass DV
  • Hwy 82 + Smith Way
  • Hwy 82 + Juniper Hill Rd
  • Hwy 82 + Aspen Village Rd UV
  • Hallam St + 8th St
  • Hallam St + 8th St
  • Aspen High School
  • River Bend
  • Woody Creek Tavern
  • Truscott DV
  • Cemetery Ln + Pitkin Mesa Dr
  • Cemetery Ln + Silver King Dr
  • Cemetery Ln + Alta Vista Dr
  • Hwy 82 + Cemetery Ln
  • Main St + 2nd St
  • Main St + Galena St
  • Brush Creek Rd + Meadow Rd Downhill
  • W/J Ranch
  • Brush Creek Rd + Medicine Bow Rd Uphill
  • Grand Ave + 20th St
  • Grand Ave + 20th St
  • Grand Ave + 14th St
  • Grand Ave + 14th St
  • Grand Ave + 9th St
  • Grand Ave + 9th St
  • West Glenwood Mall
  • AABC Airport DV
  • Hwy 82 + Service Center Rd DV
  • Hwy 82 + Service Center Rd UV
  • Brush Creek Ranch Uphill
  • West Glenwood Park & Ride
  • Rubey Park Transit Center
  • Castle Ridge
  • Aspen Chapel
  • Main St + 4th St
  • Hunter Creek II
  • Centennial
  • Park Cir + Park Ave
  • Walking Bridge
  • Hwy 82 + Crystal Lake Rd
  • 7th St + Bleeker St
  • Aspen Highlands
  • Maroon Creek Rd + Glenn Gary Dr
  • Parks Department
  • Spring St + Durant Ave
  • Glenwood Rec Center
  • Rio Grande Park
  • Smuggler
  • Chateau Eau Claire
  • Hwy 82 + Aspen Village Rd DV
  • Hwy 82 + Twining Flats Rd UV
  • Hwy 82 + Twining Flats Rd DV
  • Brush Creek Park & Ride
  • Maroon Creek Rd + Hwy 82
  • Paepcke Park
  • Paepcke Park
  • Main St + 2nd St
  • Highlands Villas
  • Highlands Villas
  • Cemetery Ln + Red Butte Dr
  • Main St + Spring St
  • Town Park Station Uphill
  • Town Park Station Downhill
  • Brush Creek Rd + Sinclair Rd Uphill
  • Brush Creek Rd + Sinclair Rd Downhill
  • Brush Creek Rd + Meadow Rd Uphill
  • Brush Creek Rd + Wood Rd Downhill
  • Castle Creek Rd + Marolt Pl
  • Maroon Creek Rd + Hwy 82
  • Aspen Country Inn DV
  • Aspen Country Inn UV
  • Buttermilk UV
  • Buttermilk DV
  • Truscott UV
  • Brush Creek Rd + Faraway Rd Downhill
  • Brush Creek Rd + Faraway Rd Uphill
  • Snowmass Mall
  • Stonebridge Inn Downhill
  • Metro Park
  • Railroad Ave + 5th St
  • Original St + Durant Ave
  • Main St + Hunter St
  • Gondola
  • Harmony Rd
  • Harmony Rd
  • Hwy 82 + Roundabout DV
  • Hwy 82 + Roundabout UV
  • Hunter Creek
  • Hyman Ave + Mill St
  • Main St + 6th St
  • Cemetery Ln + Pitkin Mesa Dr
  • Glenwood Meadows
  • Hwy 6 + Lyon Blvd
  • Cemetery
  • Aspen Rec Center
  • Cemetery Ln + Snowbunny Ln
  • Aspen City Market
  • Hwy 6 + Lyon Blvd
  • Main St + 6th St
  • New Castle Park & Ride
  • Grand Ave + 11th St
  • Parks Department
  • W 6th St
  • Hwy 6 + Traver Trail
  • Elks Lodge
  • Hwy 6 + 135 Rd
  • Cemetery Ln + Castle Creek Dr
  • Cemetery Ln + Sierra Vista Dr
  • Hwy 6 + Traver Trail
  • W 6th St
  • Grand Ave + 11th St
  • 27th St Station
  • LUPINE DR
  • Carbondale Park & Ride
  • Main St + Hwy 133
  • Downtown Basalt
  • JW Dr + Deer Run
  • Carbondale Pool
  • Roaring Fork Marketplace
  • Hwy 82 + Spring Valley Rd UV
  • JW Dr + Deer Run
  • Hwy 82 + Lazy Glen Way UV
  • Old Snowmass UV
  • AABC Airport UV
  • Glenwood Meadows
  • Glenwood Rec Center
  • Base Village
  • Brush Creek Rd + Owl Creek Rd Downhill
  • Brush Creek Rd + Owl Creek Rd Uphill
  • Brush Creek Rd + Wood Rd Uphill
  • Brush Creek Rd + Hawk Ridge Ln Uphill
  • Brush Creek Rd + Divide Rd Uphill
  • 8th St + Colorado Ave
  • Brush Creek Ranch Downhill
  • Hwy 82 + Watson Divide Rd DV
  • Main St + 4th St
  • Hwy 82 + Watson Divide Rd UV
  • Main St + Hwy 133
  • Phillips Trailer Park
  • Benedict Music Tent
  • Ute Ave
  • Buttermilk Base Area
  • Aspen St + Cooper Ave
  • Main St + 1st St
  • Main St + 1st St
  • Chateau Eau Claire
  • Hwy 82 + Stillwater Rd
  • Hwy 82 + Roaring Fork Dr
  • Hwy 82 + McSkimming Rd
  • Aspen Library
  • Original St + Durant Ave
  • Garmisch St + Hopkins Ave
  • Lift 1
  • Rio Grande Parking Garage
  • Gondola
  • Rio Grande Park
  • Hwy 6 + 135 Rd
  • Woody Creek Tavern
  • River Bend
  • El Jebel Park & Ride DV
  • El Jebel Park & Ride UV
  • Willits DV
  • Willits UV
  • Hwy 6 + Soccer Field Rd
  • Hwy 6 + Soccer Field Rd
  • 6th St + Colorado Ave
  • 9th St + Colorado Ave
  • Gilstrap Court
  • Kids Plex
  • Valley View Hospital
  • Maroon Bells
  • Bucksbaum Campus
  • Roaring Fork Marketplace
  • Burlingame MAA Housing
  • Cemetery
  • Maroon Creek Rd + High School Rd
  • Carbondale Marketplace
  • Senior Center
  • Aspen Chapel
  • Glenwood Springs Middle School
  • Highline Rd + Brush Creek Rd
  • Highline Rd + Brush Creek Rd
  • Highline Rd + Snowmass Club Cir
  • Owl Creek Rd + Brush Creek Rd
  • Owl Creek Rd + Brush Creek Rd

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 76.72026-07-30: 76.72026-07-31: 76.72026-08-01: 76.7
Show the numbers
CheckScoreChange
2026-07-2576.7 first check
2026-07-3076.7 no change
2026-07-3176.7 no change
2026-08-0176.7 no change

What changed since your last check

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

What changed in this feed

Overall grade and score held steady since 2026-07-31.

Same feed file as 2026-07-31; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Warning218 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning218 instances

    218 of 218 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.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning7 instances

    7 of 7 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning7 instances

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

    Fix: 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. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning1 instance

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Info21 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Info8 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

  • Info2 instances

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    This feed includes flexible (demand-responsive) service, and riders are told how to book it.

    Dial-a-ride and zone service are described for trip planners, not just fixed routes.

    Fix: No action needed. (None.)

    Finding code: scorecard_flex_service

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 61 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 your 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.
shapes.txt covers your trips Not ready
No trips in this feed have a shape_id linked to a row in shapes.txt. Add shapes.txt with a shape_id for each trip's path, and set trips.shape_id to match. Reduced, Rural, and Tribal NTD reporters need this in their published GTFS starting Report Year 2026; Full Reporters needed it in Report Year 2025.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 61 days.
Accessible Not yet
States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 218 of 218 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 61 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

A local transit-data support resource is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers. This resource supports agencies; it is not a scoring authority.

Correctness 86 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 100 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 45 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Roaring Fork Transportation Authority (RFTA) Flex GTFS data quality grade: C

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/roaring-fork-transportation-authority-rfta/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.