Feed status · checked 2026-08-01
Lincoln County Transit (LCT)
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 20 hours ago; last changed 37 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
149 of 149 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
60 of 60 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
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
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.
⏱ A review pass in your scheduling software.worth about +4 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
- 149 of 149 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
- 60 of 60 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
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
Remove retired stops from the export, or add them back to the trips that should serve them. · 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 61 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
- 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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 49 instances (0 error, 5 warning, 44 informational).
Service data covers the next 61 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Coast to Valley Express).
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.
68 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("SE 10th & Sturdevant (Olalla Store)", "SE 2nd & Main St", "NE 1st & Main 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.
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 149 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.
- Coast to Valley Express (teal)
- Blueline (teal)
- Newport City Loop (teal)
- Lincoln City Loop (teal)
- East County (teal)
- North County (teal)
- South County (teal)
| Route | Type | Line color |
|---|---|---|
| Coast to Valley Express | Bus | teal |
| Blueline | Bus | teal |
| Newport City Loop | Bus | teal |
| Lincoln City Loop | Bus | teal |
| East County | Bus | teal |
| North County | Bus | teal |
| South County | Bus | teal |
List every stop
- SE 10th & Sturdevant (Olalla Store)
- Toledo JC Thriftway
- SE 2nd & Main St
- NE 1st & Main St
- Food Fair
- Hospital SPCH SW 9th St
- Newport City Hall
- Fred Meyer
- Across from Food Fair
- SE Sturdevant Rd & 10th (Olalla Store)
- South Beach Market - Mailboxes
- Waldport Post Office
- Rays Market
- Holiday Motel
- Waukeetum St & 101
- Lakeside Market
- Bayshore Dr & Hwy 101
- SE 123rd & Hwy 101
- Driftwood Mobile Park & Hwy 101
- Espresso 101
- Seal Rock Store
- NE 73rd & Avery St
- Pacific Shores RV Park
- Bloch Wayside
- Waves Motel - 8th & Coast
- Hwy 101 & 8th Street - Grocery Outlet
- Courthouse
- Post Office
- 2nd & Coast
- Whaler
- Elizabeth St Inn & Shilo
- Hallmark Resort
- SW 8th & Bayley St
- Newport Business Plaza
- OCCC
- Aquarium Village
- Aquarium
- NOAA
- Port RV Park
- Rogue
- 9th & Alder
- Bay Blvd
- Clearwater
- Yacht Club
- Newport Elks
- NE 1st & Avery
- Human Bean at 6th & 101
- Oscars at 12th & 101
- Safeway - west end
- Little Creek Apts
- Salmon Run & Oceanview
- LC Community Center
- NE 28th & Yacht Ave
- US Market
- DMV
- Chinook Winds Casino
- Safeway
- Grocery Outlet
- NW 17th St & Hwy 101
- City Hall - McKays
- Surfwood Manor
- Taft IGA on Hwy 101
- SW 62nd & Hwy 101
- Ace Hardware - Taft
- SE Fleet & 32nd St
- Lincoln City Outlets
- The Palace
- Bijou Theatre
- Otis PO
- Across from Neotsu PO
- SW 32nd St @ SW Coast Hwy
- Willow & Hwy 101
- Gleneden Beach PO
- Salishan & Hwy 101
- Otter Rock Fire Department
- Depoe Bay Fire Department
- Olive & Nye St
- Gleneden Beach Post Office
- NE 36th & Hwy 101
- Depoe Bay Shell
- Beverly Beach/Eastside 101
- Depoe Bay Union 76
- Lincoln Beach Thriftway
- Street Car Village
- Neotsu PO
- Depoe Bay Mall 101
- Starbucks & Hwy 101
- Panther Creek & Hillside
- Rose Lodge
- NE 1st & Main St
- Hwy 20 at East Exit
- Logsden & Gwee-Shut
- Siletz Community Clinic
- Gwee Shut & Judd Rd
- Hi-School Pharmacy
- NW 10th & Spring
- Dorchester House
- NW 25th - Walmart
- 3rd Street & Pontiac Street - Yachats Log Church
- Waldport Clinic
- Dollar General
- Hwy 101 & NE 17th Street
- 22nd Street at Beach Club
- Walmart - Loop Route Only
- Applegate Street and 11th Street
- Main Street and 14th Street
- 26th Street and SW Western Boulevard (Hilton Garden Inn)
- Corvallis Transit Center
- Amtrak Station, Albany
- Corvallis Samaritan Hospital
- Toledo Park N' Ride
- South Beach Hatfield MSC
- NE 3rd & Fogarty St (NHS)
- Ferry Slip & 35th
- Surf View Village
- NW Nye St & 5th
- Hwy 101 & NE 3rd (Lee's Wok)
- Community Center
- SW 32nd & SW Coast
- HWY 101 & SW 62nd St
- Beverly Beach Pk/Westside HWY 101
- Rec. Center
- Siletz Fire Station
- SW Bay Blvd & SW Fall St
- PCH (Hospital) SW 9th St
- NW 20th St & Hwy 101
- Hwy 101 & 32nd St
- North Albany Park & Ride
- Eddyville Junction - Flag Stop
- Ellmaker State Park
- Blodgett
- Bi-Mart 53rd St.
- Oregon State University (McNary Hall)
- 53rd & Philomath Blvd
- NE 25th St @ Hwy 101
- NE 29th St @ Hwy 101
- Taco Bell @ Hwy 101
- SE 1st St & Hwy 101
- Rainbow Villas
- Orsborn Saw
- OCC College & Taft Schools
- Lighthouse Square
- City Hall & Library
- Bi-Mart Lincoln City
- SE 9th & Hwy 101
- NE 52nd St & Hwy 101
- Hwy 101 & SE 31st St
- California St
- Seal Rock Park & Hwy 101 - Across from Yuzen Restaurant
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 84.8 | first check |
| 2026-07-30 | 84.8 | no change |
| 2026-07-31 | 84.8 | no change |
| 2026-08-01 | 84.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning149 instances
149 of 149 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)
- Warning60 instances
60 of 60 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)
- Warning5 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)
- 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)
- 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 · 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 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 61 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 60 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. 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 Met
- Service data covers the next 61 days.
- 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.
- 5 of 149 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 60 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 94 / 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 100 / 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 60 / 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.
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/lincoln-county-transit-lct/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.