Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Roaring Fork Transportation Authority
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 90% of all tracked agencies and 90% of mid-size agencies. Operates 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.1, validator 8.0.1.
Checked for changes 10 hours ago; last changed 8 days ago.
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
Remove past service periods the next time you export the feed.Likely your export tool
Some service calendars in the feed have already expired. 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
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Enable 'remove unused shapes' (or similar) 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
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.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Enable 'remove unused shapes' (or similar) 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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 73 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.
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.
Skip to route and stop dataBasemap: 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 |
This feed has 211 stops.
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 9 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 83.7 | first check |
| 2026-07-01 | 83.7 | no change |
| 2026-07-02 | 83.7 | no change |
| 2026-07-04 | 83.7 | no change |
| 2026-07-05 | 83.7 | no change |
| 2026-07-06 | 83.7 | no change |
| 2026-07-07 | 83.7 | no change |
| 2026-07-08 | 83.7 | no change |
| 2026-07-09 | 83.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-08.
Same feed file as 2026-07-08; 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
- 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.)
Validator rule: 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 expired.
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: 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: Enable 'remove unused shapes' (or similar) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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).
App makers and state data programs 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.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
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.
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 73 days.
- agency_id matches your 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.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 73 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 73 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
Your state runs a transit-data program that can help: CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 86 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 68 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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-162/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.