GTFS Scorecard
← All agencies

Feed status · checked 2026-10-07

Linn Shuttle

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

Service mode Bus

63.0 / 100

down 0.4 since 2026-10-06

Cataloged in Oregon.

Expires in 25 daysAccessibility gapsFlexible serviceRealtime access needed

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 39 minutes ago; last changed 4 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

Linn Shuttle’s published feed lists 3 bus routes, 22 scheduled trips and 70 stops. Its service dates run from 2026-10-02 through 2026-11-01. The published file last changed on 2026-10-06.

Top things to fix

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

Service data runs out in 25 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

This one is about the feed as a whole, so there is no share of it to count.

⏱ One export setting.worth about +55 points in its category

Fix 02

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

70 of 70 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 70 stops in the feed.

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

Fix 03

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

22 of 22 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 22 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 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.
  • Oregon 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.

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.

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_feed_expiring_soon

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

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown

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

  3. Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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. 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 25 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.

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

Correctness88.0 / 100

The MobilityData validator flagged 5 kinds of issue across 87 instances (0 error, 43 warning, 44 informational).

Freshness41.7 / 100

Service data runs out in 25 day(s). Publish an updated feed soon or riders will lose trip planning.

Rider experience45.0 / 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 not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 29 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Sweet Home Public Library - 13th Ave & Kalmia St", "Lebanon Walmart (3290 S Santiam Hwy)", "Lebanon Park & E Oak 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.

Realtime qualityNot yet measured

This agency publishes realtime, but the feed needs an access key we don't have 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 70 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.

  • LBCC Express (green)
  • In-Town Transit (teal)
  • Linn Shuttle (purple)
Routes in Linn Shuttle's feed
RouteTypeLine color
LBCC ExpressBusgreen
In-Town TransitBusteal
Linn ShuttleBuspurple
List every stop
  • Sweet Home Senior Center
  • Sweet Home Public Library - 13th Ave & Kalmia St
  • Lebanon Walmart (3290 S Santiam Hwy)
  • Lebanon Park & E Oak St
  • Linn-Benton Community College - Lebanon Center
  • Linn-Benton Community College - Albany Main Campus
  • Albany Second & Broadalbin
  • Albany Amtrak Station
  • Albany Clay St at Heritage Mall
  • Foster Mall
  • Hoy's Ace Hardware
  • Shea Viewpoint
  • 12th Ave & Elm St
  • 3rd Ave & Holley Rd
  • Sweet Home High School (Eastbound)
  • Sweet Home City Hall
  • 49th St to Airport Rd
  • Long St
  • 22nd St to Jr High
  • Sweet Home High School (Westbound)
  • Hwy 20 at Short Bridge
  • Washington St SW & 1st Ave W
  • Hwy 20 & Fairview Rd (Westbound)
  • Hwy 20 & Liberty Rd (Eastbound)
  • Hwy 20 & Santiam Terrace Rd
  • Hwy 20 & Sodaville Waterloo Rd
  • Hwy 20 at Green Thumb Garden Supply
  • WinCo & Kohl's (Killdeer Ave Se)
  • Lebanon A.T.T.C.
  • 18th & Elm
  • 10th & Elm
  • 5th & Elm
  • Hwy 228 & Evergreen Ln
  • Evergreen & Nandina
  • Thriftway & Clinic
  • 12th & Nandina
  • Tamarack Ridge Estates
  • 18th Ave & Tamarack St
  • Bi-Mart (1980 Main St)
  • Safeway (1540 Main St)
  • Post Office
  • Cedar Shack
  • Foster RV
  • Wiley Creek Lodge
  • Fair Share
  • Stonebrooke Apartments
  • Linn Haven Apartments
  • 44th Ave & Hwy 20
  • Lakeside Market
  • Sunnyside County Park
  • Lewis Creek Park
  • Edgewater RV Park
  • Hilltop Market
  • City Hall
  • Riverbend Campground
  • Cascadia County Park
  • Trout Creek Trailhead
  • Trout Creek Trailhead
  • Mountain House
  • Mountain House
  • Tombstone Pass
  • Tombstone Pass
  • Lost Prairie Campground
  • Lost Prairie Campground
  • Lava Lake Sno-Park
  • Fish Lake McKenzie River Trail
  • Sahalie Falls
  • Clear Lake Resort
  • US Forest Service Office
  • Lebanon Medical College

Over time

Overall score across the last 2 checks — down 0.4 since 2026-10-06.

2026-10-06: 63.42026-10-07: 63.0
Show the numbers
CheckScoreChange
2026-10-0663.4 first check
2026-10-0763.0 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)c4cae9f362ef2026-11-01Current rubric: see the trend above
2026-08-06 to 2026-08-07 (2 checks)91edd18350b82026-11-01C, 77.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-10 (21 checks)91edd18350b82026-11-01C, 79.3 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

10 findings, ordered by severity.

Show every finding
  • Warning70 instances

    70 of 70 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

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

  • Warning22 instances

    22 of 22 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning1 instance

    This feed's service calendar runs out within the next 30 days.

    If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

    Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

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

  • Warning1 instance

    Service data runs out in 25 day(s).

    When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

    Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

    Finding code: scorecard_feed_expiring_soon · Read the fix guide for scorecard_feed_expiring_soon · See GTFS Best Practices

  • 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 for scorecard_no_fare_data · See GTFS Best Practices

  • Warning1 instance

    This feed offers flexible service that riders book ahead, but it has no booking_rules.txt.

    Riders can see the service area but not how or when to book a trip. Without that, they can't 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 for scorecard_flex_no_booking_rules · See GTFS Schedule reference

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

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

  • Info2 instances

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

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 Needs attention

This feed is close to NTD-ready. Service data runs out in 25 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 25 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 22 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

Two requirements remain for this feed to earn the conformance mark. Service data runs out in 25 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 25 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.

Can riders use it?

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

  • 42 of 70 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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 25 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.

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 88 / 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 42 / 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 45 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Access needed to measure
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Oregon 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 Linn Shuttle 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 Linn Shuttle uses the same numbers as this page: grade D (63.0 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 Oregon

Other scorecards in Oregon, 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.

Linn Shuttle: GTFS feed quality grade D, 63.0 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/linn-shuttle/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.