Feed status · checked 2026-08-01
Basin Transit Service (BTS)
Based on the feed this agency publishes
Service mode Bus
down 0.4 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 81 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
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
228 of 228 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
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
95 of 95 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
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.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
- 228 of 228 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
- 95 of 95 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
- Feed evidence
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- 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.
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.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · 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 30 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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 2 kinds of issue across 3 instances (0 error, 3 warning, 0 informational).
Service data covers the next 30 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 not 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 (4).
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.
199 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Downtown Transit Center (Pine St & 7th St)", "Fairgrounds Transit Center/Altamont Station", "Klamath Falls Amtrak Station (Spring St & Oak Ave)", 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.
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 228 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.
- 1 (blue)
- 2 (green)
- 3 (red)
- 5 (brown)
- 4 (yellow)
- 6 (purple)
- Basin Connect (green)
- Basin Connect North (green)
| Route | Type | Line color |
|---|---|---|
| 1 Mainline | Bus | blue |
| 2 Mainline | Bus | green |
| 3 Stewart Lennox | Bus | red |
| 5 Pelican City | Bus | brown |
| 4 Moyina Heights | Bus | yellow |
| 6 South Suburbs | Bus | purple |
| Basin Connect | Bus | green |
| Basin Connect North | Bus | green |
List every stop
- Beaver Marsh Bus Stop
- Montelius Street and Hwy 97
- South 6th Street and Open Door
- Maywood Drive at Food Bank
- North Senior Center
- Dagget Avenue and Urhmann Road
- Keller Rd & Bellm Dr
- Harlan Dr & Rio Vista Way
- Harlan Dr & Grenada Way
- Madison St & Estate Dr
- Madison St & Independence Ave
- S 6th St (Albertson's)
- S 6th St & Ward St
- S 6th St & Gary St
- Fairgrounds Transit Center/Altamont Station
- S 6th St & Executive Plaza
- S 6th St & Austin St (Dollar Tree)
- Washburn Way (Fred Meyer)
- Avalon St (Sherm's, Town Center Mall)
- Eberlein Ave & Division St
- E Main St & Wantland Ave
- E Main St & Darrow Ave
- E Main St & Garden Ave
- E Main St & Oak Ave
- E Main St & S Eldorado Ave (Gino's Cafe)
- Main St & Spring St (Klamath County Museums)
- Main St & 11th St (Winema Inn)
- Main St & 9th St (Oregon Bank Building)
- Klamath Ave & 8th St (State Offices)
- 11th St & Washington St
- 11th St & Grant St
- Oregon Ave & Fulton St
- Oregon Ave & Addison St
- Biehn St & Lytton St
- Biehn St & Hawthorne St
- Biehn St (Pelican Cinema)
- Dahlia St & Almond St (Burger King)
- Almond St & Daggett Ave
- Sky Lakes Medical Center
- Oregon Institute of Technology
- Dahlia St (McDonald's)
- Almond St (Dr Benson's)
- Klamath Eye Center (Biehn St)
- Biehn St & Iowa St
- Biehn St & Oregon Ave
- Oregon Ave & Addison St
- Oregon Ave & Fulton St
- 9th St & Lincoln St
- 9th St & Pine St
- Klamath Ave & Commercial St
- Broad St & Main St
- E Main St & S Eldorado Ave
- E Main St & Oak Ave
- E Main St (Mills Elementary School)
- E Main St & Garden Ave
- E Main St & Darrow Ave
- E Main St & Wantland Ave
- Washburn Way & Radcliffe Ave (Fred Meyer)
- Avalon St (McDonald's)
- S 6th St (Ross Dress For Less)
- Arthur St (Klamath Basin Senior Center)
- S 6th St (Big Lots)
- S 6th St & Gary St (Eastbound)
- S 6th St & Hope St (Casey's Restaurant)
- S 6th St & Madison St
- S 6th St (Furniture Warehouse - American Marine)
- S 6th St (Wiseman's RV Park)
- S 6th St & Hilyard Ave
- S 6th St (Klamath Community College)
- Daggett Ave & Shallock Ave
- Daggett Avenue and Bryant Williams
- Eldorado Ave (Klamath Basin Behavioral Health KBBH)
- Eldorado Ave & Peach St
- Eldorado Ave & Birch St
- Eldorado Ave & Del Moro St
- Eldorado Ave & Fremont St
- Eldorado Ave & Earle St
- Esplanade Ave & Spring St
- Main St & Mortimer St
- Main St & Bike Path Canal (Eastbound)
- Washburn Way & Garden Ave
- Washburn Way & Applegate Ave (Southbound)
- Eberlein Ave & Washburn Way
- S 6th St & Homedale Rd (Hope Lutheran Church)
- Homedale Rd & Harlan Dr (Southbound)
- Homedale Rd & Maryland Ave
- Homedale Rd & Bristol Ave
- Homedale Rd & Barry Ave
- Homedale Rd & American Ave
- Glenwood Dr & Ankeny St
- Glenwood Dr & Laurelwood Dr
- Laurelwood Dr & Gatewood Dr
- Gatewood Dr & Golden Ct
- Homedale Rd & Sturdivant Ave
- Homedale Rd & Sylvia Ave
- Homedale Rd & Harlan Dr (Northbound)
- Homedale Rd & Leland Dr
- Homedale Rd & Delaware Ave
- Washburn Way & Eberlein Ave (Northbound)
- Washburn Way & Garden Ave
- Main St & Bike Path Canal (Westbound)
- Esplanade Ave & Spring St
- Eldorado Ave & Earle St
- Eldorado Ave & Fremont St
- Eldoardo Ave & Lawrence St
- Eldorado Ave & Lexington Ave
- Eldorado Ave (Klamath Retirement Center)
- Daggett Ave & Clairmont Dr
- Daggett Ave & Mountain View Blvd
- Main St (Klamath County Building)
- Main St (Baldwin Hotel Museum)
- Main St & 1st St (Waffle Hut)
- Riverside Dr (Klamath Advocacy Center)
- Riverside Dr & Greensprings Dr
- Riverside Dr & Frontage Rd
- Riverside Dr & Abilene Ave
- Riverside Dr & Greensprings Dr (Green Springs Market)
- Greensprings Dr (Villa West Estates)
- Greensprings Dr (Turtle Cove)
- Balsam Dr & Emerald St
- Orindale Rd & Balsam Dr
- Orindale Rd & Sunnyside Ln
- Weyerhauser Rd & Peggy Ave
- Weyerhauser Rd & Mahan Ave
- Weyerhauser Rd & Rae St
- Hwy 66 across from Riy’s Market
- Greensprings Dr (Coast Truck Center)
- Greensprings Dr (Greensprings RV Park)
- Greensprings Dr & Mallard Ln
- Riverside Dr (American Gas)
- Riverside Dr (Klamath Visitor's Center)
- Klamath Ave & 3rd St
- 4th St & Pine St
- Arthur St & Shasta Way
- Shasta Way (Bike Path/Canal)
- Vandenberg Rd & Foothills Blvd
- Vandenberg Rd (Klamath County Jail)
- Foothills Blvd (Steen Sports Park)
- Foothills Blvd & Homedale Rd
- Patterson St & Springcrest Way
- Eberlein Ave & Carlson Dr
- McClellan Dr & Eberlein Ave
- McClellan Dr & Shasta Way
- Alva Ave & Chinchalla Way
- Patterson St & Winema Way
- Shasta Way & Madison St
- Shasta Way & Homedale Rd
- Shasta Way & Kane St
- Shasta Way & Ivory St
- Shasta Way & Gary St
- Shasta Way & Derby St
- Washburn Way & Crosby Ave (Northbound)
- Washburn Way & Hilyard Ave (Pacific Crest Federal Credit Union)
- Washburn Way (Walmart)
- Laverne Ave (Epicenter Bowling Complex)
- Laverne Ave & Altamont Dr
- Altamont Dr & Bristol Ave
- Altamont Dr & Anderson Ave (Southbound)
- Summers Lane & Anderson Ave
- Summers Lane & Sturdivant Ave
- Summers Lane & Bristol Ave
- Summers Lane (Mia & Pia's Pizzeria)
- Summers Lane (Mazama High School)
- Hilyard Ave & Crest St
- Hilyard Ave & Altamont Dr
- Hilyard Ave & Washburn Way
- Crosby Ave & Washburn Way (Westbound)
- Washburn Way & 6th St (Planet Fitness/Natural Grocers)
- Keller Rd & Alt Way
- Hwy 39 & OC & E Rail Trail
- 5651 Delaware Ave
- Homedale Rd & 6th St (Lutheran Square)
- N 3rd St & Jefferson St (Southbound)
- California Ave & Upham St (Southbound)
- Siskiyou St & Delta St
- Montelius St & Lakeport Blvd
- Harvard St & McLean St
- Torrey St & Corvallis St
- Nosler St & California Ave
- California Ave & Front St
- Nevada St & Kiln St
- Bartlett Ave & Homedale Rd
- Daggett Ave & Mountain View Blvd (Southbound)
- Klamath Works/Sky Lakes (S 6th St & Owens St)
- Shasta Way & Washburn Way
- 8th St & Commercial St (EagleRidge High School)
- Elm Ave & Market St
- Klamath Falls Amtrak Station (Spring St & Oak Ave)
- Alameda Ave (YMCA)
- Avalon St (Klamath Housing Authority)
- Veterans Memorial Park
- California Ave & Oregon Ave
- Shasta Way & Lark St
- Oak Ave & Broad St
- S 5th Ave & Plum Ave
- S 6th St & Plum Ave
- S 6th St & E Main St
- S 6th St & Washburn Way
- S 6th Ave (Holiday Inn Express)
- Crescent @ USPS Stop
- Gilchrist @ Old Movie Theatre
- Keno (Library)
- Worden (Worden Café)
- Midland (Post Office)
- Falcon Heights
- Running Y Resort
- Rocky Point Fire Station
- Lake of the Woods
- Malin (Post Office)
- Merrill (City Hall)
- Dairy
- Bonanza (City Hall)
- Beatty (Community Center)
- Bly
- Pine St & 3rd St
- Cortez St & Balsam Dr
- 4690 Weyerhauser Road
- Washburn Way & Darrow Avenue
- Madison St & Mack Ave
- Homedale Rd & Russet Dr
- Homedale Rd at Albertsons (Northbound)
- Washburn Way & Eberlein Ave (Southbound)
- Main St (Ella Redkey Pool)
- LaPine @ CET Bus Stop #30
- Hawthorne Main Transfer Station
- Chemult Post Office
- Downtown Transit Center (Pine St & 7th St)
- Crescent Lake Junction USPS and Sportmans Park
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 | 69.2 | first check |
| 2026-07-30 | 67.1 | down 2.1 |
| 2026-07-31 | 66.7 | down 0.4 |
| 2026-08-01 | 66.3 | 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 D. On 2026-08-01 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-08-01 Feed entered the expiry window (30 days of service left).
Everything we checked
6 findings, ordered by severity.
Show every finding
- Warning228 instances
228 of 228 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)
- Warning95 instances
95 of 95 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)
- Warning10 instances
10 of 95 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
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- 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 95 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 runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 30 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 30 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 Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. This resource supports agencies; it is not a scoring authority.
- Correctness 92 / 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 50 / 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 43 / 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/basin-transit-service-bts/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.