Feed status · checked 2026-08-01
Roaring Fork Transportation Authority
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in Colorado.
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 39 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
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
211 of 211 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
Remove past service periods the next time you export the feed.Likely your export tool
Some service calendars in the feed have already ended. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
⏱ One setting in most export tools.worth about +6 points in its category
Turn on 'remove unused shapes' (or the like) in your export tool.Likely your export tool
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
⏱ One setting.worth about +4 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
- 211 of 211 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
- Feed evidence
- Some service calendars in the feed have already ended.
- Next action
- Remove past service periods the next time you export the feed.
- 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
- The feed contains route shapes no trip uses.
- Next action
- Turn on 'remove unused shapes' (or the like) in your export tool.
- 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.
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.
Remove past service periods the next time you export the feed. · 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.
Turn on 'remove unused shapes' (or the like) in your export tool. · 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 50 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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
The MobilityData validator flagged 3 kinds of issue across 12 instances (0 error, 12 warning, 0 informational).
Service data covers the next 50 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (CM).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
129 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Forge Rd + Molly Ct", "Railroad Ave + 5th St", "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.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 211 stops.
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.
- BG (gray)
- BRT (yellow)
- CC (teal)
- CL (white)
- CM (teal)
- FL (brown)
- HC (gray)
- HGB (orange)
- JAS (brown)
- L (teal)
- MS (brown)
- MV (gray)
- RG (green)
- SM (blue)
- SMV (green)
- WC (pink)
- XT (white)
| Route | Type | Line color |
|---|---|---|
| BG Burlingame | Bus | gray |
| BRT VelociRFTA | Bus | yellow |
| CC Carbondale Circulator | Bus | teal |
| CL Cemetery Lane | Bus | white |
| CM Castle Maroon | Bus | teal |
| FL Flyer | Bus | brown |
| HC Hunter Creek | Bus | gray |
| HGB Hogback | Bus | orange |
| JAS Jazz Aspen Snowmass | Bus | brown |
| L Local Valley | Bus | teal |
| MS Music School | Bus | brown |
| MV Mountain Valley | Bus | gray |
| RG Ride Glenwood | Bus | green |
| SM Snowmass/Aspen | Bus | blue |
| SMV Snowmass-Valley | Bus | green |
| WC Woody Creek | Bus | pink |
| XT Cross Town | Bus | white |
List every stop
- AABC Airport DV
- Hwy 6 + Lyon Blvd
- New Castle Park & Ride
- Phillips Trailer Park
- River Bend
- Woody Creek Tavern
- W/J Ranch
- Woody Creek Tavern
- Hwy 82 + Service Center Rd DV
- River Bend
- Forge Rd + Molly Ct
- Harmony Rd
- 7th St + Bleeker St
- Main St + 6th St
- Main St + 2nd St
- Rubey Park
- Main St + 2nd St
- Castle Ridge
- Maroon Creek Rd + Hwy 82
- Highlands Villas
- Aspen Highlands
- Parks Department
- Cemetery Ln + Alta Vista Dr
- Hwy 82 + Smith Way
- Cemetery Ln + Snowbunny Ln
- Cemetery Ln + Pitkin Mesa Dr
- Cemetery Ln + Red Butte Dr
- Hwy 82 + McSkimming Rd
- Lupine Dr
- Hyman Ave + Mill St
- Hwy 82 + Twining Flats Rd DV
- Hunter Creek
- Smuggler
- Centennial
- Park Cir + Park Ave
- Chateau Eau Claire
- Music Tent
- Hwy 82 + Crystal Lake Rd
- Hwy 82 + Aspen Village Rd DV
- Harmony Rd
- Highlands Villas
- Aspen High School
- Maroon Creek Rd + Hwy 82
- Cemetery Ln + Pitkin Mesa Dr
- Hwy 82 + Watson Divide Rd DV
- Cemetery Ln + Silver King Dr
- Cemetery Ln + Castle Creek Dr
- Lift 1
- Hwy 6 + Soccer Field Rd
- Old Snowmass DV
- Hwy 6 + Traver Trail
- W 6th St
- Grand Ave + 11th St
- Grand Ave + 11th St
- W 6th St
- Hwy 82 + Lazy Glen Way DV
- Hwy 6 + Traver Trail
- Elks Lodge
- Hwy 6 + Soccer Field Rd
- Snowmass Mall
- Stonebridge Inn
- Base Village
- Brush Creek Rd + Wood Rd
- Brush Creek Rd + Faraway Rd
- Brush Creek Rd + Owl Creek Rd
- Wingo Junction DV
- Brush Creek Rd + Sinclair Rd
- Brush Creek Rd + Meadow Rd
- Town Park Station
- Brush Creek Ranch
- Brush Creek Rd + Medicine Bow Rd
- Brush Creek Ranch
- Town Park Station
- Brush Creek Rd + Meadow Rd
- Paepcke Park
- Holland Hills DV
- Brush Creek Rd + Sinclair Rd
- Brush Creek Rd + Owl Creek Rd
- Brush Creek Rd + Faraway Rd
- Brush Creek Rd + Wood Rd
- Brush Creek Rd + Divide Rd
- Bucksbaum Campus
- Basalt Park & Ride DV
- Downtown Basalt
- Two Rivers Rd + Hillcrest Dr DV
- Hwy 82 + Original Rd DV
- JW Dr + El Jebel Rd
- Brush Creek Rd + Hawk Ridge Ln
- JW Dr + Deer Run
- Willits UV
- Willits DV
- El Jebel Park & Ride DV
- El Jebel Park & Ride UV
- 27th St Station
- Main St + 4th St
- Hwy 82 + Catherine Store Rd DV
- Ranch at Roaring Fork DV
- Truscott UV
- Carbondale Park & Ride
- Carbondale Pool
- Aspen Glen DV
- Hwy 82 + Spring Valley Rd DV
- Grand Ave + 20th St
- Gondola
- Hallam St + 8th St
- Grand Ave + 14th St
- Glenwood Meadows
- Glenwood Rec Center
- Grand Ave + 9th St
- Rio Grande Park
- AABC Airport UV
- Glenwood Meadows
- West Glenwood Park & Ride
- Glenwood Rec Center
- Grand Ave + 9th St
- Hwy 82 + Cemetery Ln
- Grand Ave + 14th St
- Grand Ave + 20th St
- Garmisch St + Hopkins Ave
- Roaring Fork Marketplace
- Hwy 82 + Spring Valley Rd UV
- Aspen Glen UV
- Ranch at Roaring Fork UV
- Main St + Hunter St
- Hwy 82 + Catherine Store Rd UV
- JW Dr + Buckskin Dr
- Main St + Hwy 133
- Main St + Hwy 133
- JW Dr + Deer Run
- JW Dr + El Jebel Rd
- Hunter Creek II
- Hwy 82 + Roundabout DV
- Walking Bridge (Midland Ave + Hopkins)
- Parks Department
- Castle Creek Rd + Marolt Pl
- Original St + Durant Ave
- Cemetery
- Cemetery Ln + Sierra Vista Dr
- Roaring Fork Marketplace
- JW Dr + Buckskin Dr
- Ute Ave
- Chateau Eau Claire
- Hwy 82 + Stillwater Rd
- Hwy 82 + Roaring Fork Dr
- Aspen Library
- Hwy 82 + Original Rd UV
- Burlingame MAA Housing
- Hwy 6 + 135 Rd
- 6th St + Colorado Ave
- 9th St + Colorado Ave
- Aspen Chapel
- Two Rivers Rd + Hillcrest Dr UV
- Downtown Basalt
- Basalt Park & Ride UV
- Holland Hills UV
- Gondola
- Wingo Junction UV
- Maroon Creek Rd + Glenn Gary Dr
- Brush Creek Park & Ride
- Hwy 82 + Lazy Glen Way UV
- Hwy 6 + 135 Rd
- Old Snowmass UV
- 8th St + Pitkin Ave
- 8th St + Colorado Ave
- Cemetery
- Cemetery Ln + Castle Creek Dr
- Truscott DV
- Hwy 82 + Watson Divide Rd UV
- Hwy 82 + Aspen Village Rd UV
- Hwy 82 + Twining Flats Rd UV
- Hwy 82 + Juniper Hill Rd
- Hwy 82 + Service Center Rd UV
- Buttermilk UV
- Aspen Country Inn UV
- Maroon Creek Rd + High School Rd
- Aspen Country Inn DV
- Hwy 82 + Roundabout UV
- Hallam St + 8th St
- Main St + 4th St
- Paepcke Park
- Main St + Galena St
- Carbondale Marketplace
- Main St + Spring St
- Senior Center
- Aspen Rec Center
- Aspen City Market
- Spring St + Durant Ave
- West Glenwood Mall
- Original St + Durant Ave
- Aspen Chapel
- New Castle Park & Ride
- Main St + 6th St
- Main St + 6th St
- Forge Rd
- Forge Rd + Mining Stock Pkwy
- Paepcke Dr
- Paepcke Dr ll
- Paepcke Dr lll
- Buttermilk DV
- Hwy 6 + Lyon Blvd
- Town Park Station (JAS drop-off)
- Town Park Station (JAS pick-up)
- Firehouse
- Cottonwood
- Rifle Park & Ride
- Railroad Ave + 5th St
- Metro Park
- Railroad Ave + 5th St
- Rifle Park & Ride
- Cottonwood
- Firehouse
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 82.5 | first check |
| 2026-07-30 | 80.4 | down 2.1 |
| 2026-07-31 | 80.0 | down 0.4 |
| 2026-08-01 | 79.6 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points 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.
What changed over time
On 2026-07-25 this feed started at grade B. On 2026-07-31 the grade moved from B to C. As of 2026-08-01 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-07-31 Grade went B to C.
Everything we checked
5 findings, ordered by severity.
Show every finding
- Warning211 instances
211 of 211 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 (opens the GTFS Schedule reference on an external site)
- Warning9 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 50 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 Ready
- All 28129 trips have a shape in shapes.txt.
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 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 50 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 50 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 83 / 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 68 / 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.
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/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.