GTFS Scorecard
← All agencies

Feed status · checked 2026-10-07

Roaring Fork Transportation Authority

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

76.4 / 100

down 0.4 since 2026-10-06

Cataloged in Colorado.

Covers 46 daysAccessibility gapsRealtime 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.4, validator 8.0.1.

Checked for changes 32 minutes ago; last changed 19 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

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

About this feed

Roaring Fork Transportation Authority’s published feed lists 13 bus routes, 10,094 scheduled trips and 200 stops. Its service dates run from 2026-09-21 through 2026-11-22. The published file last changed on 2026-10-06.

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

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.

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

Fix 02

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.

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.

⏱ One setting.worth about +4 points in its category

Fix 03

Add feed_contact_email or feed_contact_url to feed_info.txt.Likely your export tool

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.

⏱ One field, set once in export settings.worth about +4 points in its category

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for unused_shape

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  3. Fix 03 · Read the fix guide for missing_feed_contact_email_and_url

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

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 46 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 your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness82.5 / 100

The MobilityData validator flagged 7 kinds of issue across 8 instances (0 error, 5 warning, 3 informational).

Freshness76.7 / 100

Service data covers the next 46 days.

Rider experience67.5 / 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.

Accessibility37.5 / 100

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.

  • 127 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Main St + 4th St", "Hallam St + 8th St", "Hwy 82 + Cemetery Ln", 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

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 200 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.

  • BG (gray)
  • BRT (yellow)
  • CC (teal)
  • CL (white)
  • CM (teal)
  • FL (brown)
  • HC (gray)
  • HGB (orange)
  • L (teal)
  • MV (gray)
  • RG (purple)
  • SM (blue)
  • SMV (blue)
Routes in Roaring Fork Transportation Authority's feed
RouteTypeLine color
BG BurlingameBusgray
BRT VelociRFTABusyellow
CC Carbondale CirculatorBusteal
CL Cemetery LaneBuswhite
CM Castle MaroonBusteal
FL FlyerBusbrown
HC Hunter CreekBusgray
HGB HogbackBusorange
L Local ValleyBusteal
MV Mountain ValleyBusgray
RG Ride GlenwoodBuspurple
SM Snowmass/AspenBusblue
SMV Snowmass-ValleyBusblue
List every stop
  • AABC Airport DV
  • Hwy 6 + Lyon Blvd
  • New Castle Park & Ride
  • Hwy 82 + Service Center Rd DV
  • 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
  • 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
  • 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
  • Chateau Eau Claire
  • Hwy 82 + Stillwater Rd
  • Hwy 82 + Roaring Fork Dr
  • Aspen Library
  • Hwy 82 + Original Rd UV
  • 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
  • Glenwood Springs Middle School
  • 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
  • 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 2 checks — down 0.4 since 2026-10-06.

2026-10-06: 76.82026-10-07: 76.4
Show the numbers
CheckScoreChange
2026-10-0676.8 first check
2026-10-0776.4 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.6
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

CheckedPublished fileService dates throughGrade at the time
2026-10-06 to 2026-10-07 (2 checks)19556f98e4fd2026-11-22Current rubric: see the trend above
2026-08-06 to 2026-09-13 (4 checks)315e298283f22026-09-20D, 61.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-10 (21 checks)315e298283f22026-09-20B, 84.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall score fell 0.4 points since 2026-10-06.

Same feed file as 2026-10-06; the published zip did not change.

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

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Warning200 instances

    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.

    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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • 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 for unused_shape · See MobilityData GTFS Validator rules

  • 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules

  • Warning1 instance

    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 for stop_without_stop_time · See MobilityData GTFS Validator rules

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

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

  • Info1 instance

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

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

  • Info1 instance

    Future calendar (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_calendar · See MobilityData GTFS Validator rules

  • Info1 instance

    Future feed (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_feed · See MobilityData GTFS Validator rules

  • 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. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

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

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 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 10094 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

One requirement remains for this feed to earn 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 46 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.

Can riders use it?

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

  • 1 of 200 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 46 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 82 / 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 77 / 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.

Part of the Colorado portfolio: the same scorecards for every feed we track in that group, on one free page.

For programs that support several agencies

This scorecard and the board one-pager for Roaring Fork Transportation Authority are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.

The report for Roaring Fork Transportation Authority uses the same numbers as this page: grade C (76.4 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.

One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.

See the program report bundle

See a sample bundle report: a real agency's current grade, with placeholder branding.

A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.

Similar feeds in Colorado

Other scorecards in Colorado, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Roaring Fork Transportation Authority: GTFS feed quality grade C, 76.4 of 100, checked 2026-10-07. GTFS 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-2278/2026-10-07.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-10-07. 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.