Feed status · checked 2026-08-01
Rogue Valley Transportation District (RVTD)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Oregon.
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
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 139 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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
524 of 542 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 +24 points in its category
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
654 of 654 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
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
- Service data ended 139 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- 524 of 542 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
- 654 of 654 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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.
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.
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.
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 was 139 days ago.
- Published accessibility data
- Accessibility information is stated for 3.3% 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 9 kinds of issue across 398 instances (0 error, 355 warning, 43 informational).
Service data ended 139 day(s) ago. Trip planners have likely already dropped this feed.
3% of stops state wheelchair accessibility (3% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
3% of stops state accessibility (3% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
371 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Garfield St West of Center Drive (Rogue Credit Union)", "S Central Ave - South of 11th St", "S Central Ave - South of Earhart St", 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 542 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.
- 21 (gray)
- 24 (brown)
- 60 (purple)
- 10 (red)
- 40 (pink)
- 4 (black)
| Route | Type | Line color |
|---|---|---|
| 21 North Medford | Bus | gray |
| 24 RRMC | Bus | brown |
| 60 White City | Bus | purple |
| 10 Ashland | Bus | red |
| 40 Central Point | Bus | pink |
| 4 West Medford | Bus | black |
List every stop
- Front Street Station
- Garfield St West of Center Drive (Rogue Credit Union)
- S Central Ave - South of 11th St
- S Central Ave - South of Earhart St
- S Central Ave - at Bank St
- S. Riverside Ave - South of Barnett Rd
- Stewart Ave - East of S. Pacific Hwy
- Center Dr/ Harry and David Country Village
- South Gateway - Walmart
- S Pacific Hwy - at Charlotte Ann Rd
- S Pacific Hwy - North of Lowery Ln
- Harry & David Corporation
- S Pacific Hwy - South of Matt Lp
- S Pacific Hwy - North of South Stage Rd
- S Pacific Hwy - North of Glenwood Rd
- S Pacific Hwy - North of Motorcycle Ln
- S Pacific Hwy - South of Northridge Terr
- S Pacific Hwy - South of Rose St
- Phoenix - Ray's Food Place
- N Main St - South of 5th St
- S Main St - South of 1st St
- S Main St - South of Oak St
- S Pacific Hwy
- S Pacific Hwy - North of Cabbage Ln
- S Pacific Hwy - South of Rising Sun Farm Road
- S Pacific Hwy - North of Hartley Rd
- Talent Ave - South of Colver Rd
- Talent and Main
- Talent Ave - North of Eva Wy
- Talent Ave - North of Rapp Rd
- Talent Ave - South of Rogue River Pkwy
- Arnos Rd - East of Talent Ave
- Highway 99 - South of Creel Rd
- Higyway 99 - South of Talent Ave
- Jackson Wellsprings
- Highway 99 - South of Valley View Rd
- N Main St - South of Ashland Mine Rd
- N Main St - North of Grant Rd
- North Main and Maple - Ashland Hospital
- N Main St - South of Wimer St
- N Main St - South of Laurel
- Ashland Plaza
- E Main St - North of 1st St
- E Main St - South of Gresham St
- Siskiyou Blvd - South of Sherman St
- Siskiyou Blvd - North of Liberty St
- Siskiyou Blvd - South of Beach St
- Southern Oregon University
- Siskiyou Blvd - South of Avery St
- Ashland St - East of Siskiyou
- Ashland and Walker
- Ashland St - East of Lit Wy
- Ashland St - East of Park St
- Shop'n Kart
- Ashland Bi-Mart
- Tolman Creek Rd - South of Grizzly Dr
- Tolman Creek Rd - South of Dianne St
- Tolman Creek Rd - North of Siskiyou Blvd
- Siskiyou and Bellview
- Siskiyou Blvd - South of Glendale Ave
- Siskiyou Blvd - North of Faith Ave
- Siskiyou Blvd - South of Normal Ave
- Siskiyou Blvd - North of Harmony Ln
- Siskiyou Blvd - South of Ashland St
- Siskiyou Blvd - North of Bridge St
- Siskiyou and Palm
- Siskiyou Blvd - South of Morse St
- Siskiyou Blvd - South of Morton St
- Siskiyou Blvd - South of Sherman St
- Lithia Way - North of 2nd St
- Lithia and Oak
- N Main St - North of Central St
- N Main St - South of Glenn St
- N Main St - North of Maple St
- N Main St - North of Grant St
- N Main St - South of Jackson Rd
- Highway 99 - South of Valley View Rd
- Jackson Wellsprings
- Highway 99 - North of Talent Ave
- Highway 99 - South of Creel Rd
- Arnos Rd - East of Talent Ave
- Talent Ave - North of Rogue River Pkwy
- Talent Ave - North of Rapp Rd
- Talent Ave - South of Gangnes Dr
- Talent and Main
- Talent Ave - South of Colver Rd
- S Pacific Hwy - North of Hartley Rd
- S Pacific Hwy
- S Pacific Hwy - North of Cabbage Ln
- Greenway Village
- S Pacific Hwy
- Hwy 99 - South of Oak St
- Hwy 99 - North of 4th St
- Phoenix - Ray's Food Place
- S Pacific Hwy - South of Rose St
- S Pacific Hwy - South of Northridge Terr
- S Pacific Hwy - at Medford Mobile Estates
- S Pacific Hwy - North of Glenwood Rd
- S Pacific Hwy - South of South Stage Rd
- Harry & David Corporation
- S Pacific Hwy - South of Lowery Ln
- S Pacific Hwy - North of Lowery Ln
- Garfield St - East of S Pacific Hwy
- South Gateway - Walmart
- South Gateway - Fred Meyers
- Stewart Ave - West of Center Dr
- Riverside Ave - North of Barnett Rd
- Riverside Ave - North of Bank St
- Riverside Ave - South of 13th St
- Albertsons
- Tolman and Abbott
- Clay and Birchwood
- Ashland and Shamrock
- Ashland and Lit
- Ashland and Walker
- SOU - Ashland St
- SOU's The Hawk
- Wightman and Iowa
- Wightman South of Railroad
- The Grove - Ashland Police
- Mountain and Clear Creek
- North Mountain Park
- Hersey and Ann
- Hersey and Oak
- Ashland Creek Park
- Hersey and North Main
- Ashland Hospital
- Hersey and North Main
- Ashland Creek Park
- Hersey and Oak
- Hersey and Ann
- North Mountain Park
- Mountain and Clear Creek
- The Grove - Ashland Police
- Wightman South of Railroad
- Wightman and Iowa
- SOU's The Hawk
- Chevron
- Parker House Project
- Ashland Hills Inn
- Food 4 Less
- 10th St - East of Holly St
- Oakdale Ave - South of 11th St
- Oakdale and Dakota
- Oakdale Ave - North of Stewart Ave
- Stewart Ave - East of King St
- Stewart Ave - East of Peach St
- Stewart Ave - West of Hamilton St
- Stewart and Columbus
- Columbus Ave - South of Mt. Pitt
- Dakota Ave - East of Benson St
- Dakota Ave - West of Hamilton St
- Hamilton St - North of 13th St
- Hamilton St - South of 10th St
- Hamilton and West Main - Probation Office
- W Main St - East of Summit Ave
- W 8th St - East of Elm St
- W 8th St - East of Lincoln St
- W 8th St - East of Cannon St
- W 8th St - West of Mistletoe St
- Medford City Hall
- W 8th St - East of Grape St
- Barnett & Riverside
- Barnett & Stewart - Victorico's
- E Barnett Rd - East of Highland Dr
- East Barnett and Ellendale
- E Barnett Rd - East of Hillsdale St
- E Barnett Rd - East of Edgemont Dr
- Black Oak and Siskiyou
- Siskiyou Blvd - East of Sutter Ave
- Siskiyou Blvd - West of Murphy Rd
- Murphy Rd. RRMC
- Murphy and State
- Juanipero and Morrison
- Juanipero and Olympic
- Golf View and Alameda
- Golf View and Creek View
- Golfview/ State Street
- Barnett Road/ Brookdale Senior Living
- East Barnett and Murphy
- E Barnett Rd - West of Medical Center Dr
- E Barnett Rd - West of Black Oak Dr
- E Barnett Rd - West of Crestbrook Rd
- E Barnett Rd - East of Ellendale Dr
- Barnett & Highland
- Barnett Rd. Winco
- 384 W Main St
- 762 W Main St
- West Main and Hamilton - Probation Office
- 16 S Columbus Ave
- 120 S Columbus Ave
- 474 S Columbus Ave
- Columbus and Stewart
- 1672 W Stewart Ave
- 1220 Orchard Home Dr
- Orchard Home and Cunningham
- South Medford High School
- Garfield and Columbus
- 945 Garfield St
- 1597 S Peach St
- 1341 S Peach St
- Stewart and Peach
- 707 W Stewart Ave
- 1125 S Oakdale Ave
- Oakdale Middle School
- 439 S Oakdale Ave
- Black Oak Dr - North of Pembroke Cir
- Hillcrest and Vernada/ Ruhl Park
- Sunrise and Jackson St
- Sunrise and Bianca
- Springbrook and Spring St/ Donahue Frohnmayer Park
- Springbrook and McAndrews - Bonaventure
- Springbrook and Lone Pine/ Roxy Ann Memory
- Springbrook and Brookside - North Medford High School
- Springbrook and Cedar Links
- Springbrook and Northbrook
- Springbrook and Pheasant
- Delta Waters and Blackthorn
- Cardinal Ave/ Ashley Home Store
- Delta Waters Rd - East of Crater Lake Ave
- Delta Waters and Blackthorn
- Springbrook and Pheasant - Kennedy Park
- Springbrook and Bell
- Springbrook and Cedar Links
- Springbrook and Brookside - North Medford High School
- Springbrook and Lone Pine
- Springbrook and McAndrews/ Bonaventure
- Springbrook and Spring - Donahue Frohnmayer Park
- Sunrise and Bianca
- Sunrise and Jackson
- Hillcrest and Modoc - Ruhl Park
- Black Oak Drive - North of Pembroke Circle
- Sage Rd/ Parsons
- Rossanley/ Stowe
- N Ross/ Logos School
- N Ross/ Thorn Oak
- N Ross/ Dahlia
- N Ross/ McAndrews
- N Ross/ W Main (Albertsons)
- Sherm's Thunderbird
- Lozier Ln/ W Prune
- Lozier Ln/ Westdale Pl
- Lozier/ Arlington
- Lozier/ Westdale Pl
- Lozier Ln/ W Prune
- Lozier and West Main - Thunderbird
- N Ross/ W Main (Albertsons)
- N Ross/ McAndrews
- N Ross/ Dahlia
- N Ross/ Stonefield
- and 292 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 47.4 | first check |
| 2026-07-30 | 47.4 | no change |
| 2026-07-31 | 47.4 | no change |
| 2026-08-01 | 47.4 | 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
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 139 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning654 instances
654 of 654 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 (opens the GTFS Schedule reference on an external site)
- Warning524 instances
524 of 542 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)
- Warning249 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 (opens the validator rules on an external site)
- Warning100 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning66 instances
66 of 654 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 (opens GTFS Best Practices on an external site)
- Warning2 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
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 (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- Info1 instance
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 (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.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 139 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 139 days ago, so FTA would find the link out of date.
- 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 654 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. Service data expired 139 days ago. States wheelchair access on 3% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 139 days ago.
- Accessible Not yet
- States wheelchair access on 3% 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.
- 249 of 542 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. This resource supports agencies; it is not a scoring authority.
- Correctness 66 / 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 0 / 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 59 / 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/rogue-valley-transportation-district-rvtd/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.