Feed status · checked 2026-08-01
Link Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Washington.
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 74 minutes ago; last changed 33 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
621 of 621 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
2293 of 2293 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
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
⏱ Usually an export-tool fix, not hand editing.worth about +8 points in its category
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
- 621 of 621 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
- 2293 of 2293 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 sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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 156 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 your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 3 kinds of issue across 1348 instances (0 error, 1348 warning, 0 informational).
Service data covers the next 156 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
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (6, 20, 21, 23, 122).
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.
484 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Wenatchee Ave and Chehalis", "Eastmont Ave and 3rd", "3rd St and Valley Mall", 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 621 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.
- 12 (red)
- 122 (red)
- 15 (black)
- 18 (yellow)
- 19 (blue)
- 2 (purple)
- 20 (red)
- 21 (green)
- 22 (orange)
- 23 (green)
- 24 (black)
- 25 (orange)
- 28 (red)
- 3 (teal)
- 32 (green)
- 4 (green)
- 5 (yellow)
- 6 (orange)
- 7 (red)
- 8 (black)
- 9 (green)
| Route | Type | Line color |
|---|---|---|
| 12 Fred Meyer | Bus | red |
| 122 Express | Bus | red |
| 15 Airport | Bus | black |
| 18 E Wen/WVC | Bus | yellow |
| 19 Eastmont | Bus | blue |
| 2 E Wen/Walmart | Bus | purple |
| 20 Chelan/Orondo | Bus | red |
| 21 Manson | Bus | green |
| 22 Leavenworth | Bus | orange |
| 23 Rock Island | Bus | green |
| 24 Malaga | Bus | black |
| 25 Waterville | Bus | orange |
| 28 Cashmere | Bus | red |
| 3 Hospital | Bus | teal |
| 32 Leavenworth Local | Bus | green |
| 4 Riverside Dr | Bus | green |
| 5 Western Ave | Bus | yellow |
| 6 S Wen Ave | Bus | orange |
| 7 Target | Bus | red |
| 8 Miller St | Bus | black |
| 9 Lincoln Park | Bus | green |
List every stop
- Wenatchee Ave and Chehalis
- Eastmont Ave and 3rd
- Columbia Station
- Mission at Lincoln Park
- 3rd St and Valley Mall
- Baker Ave and 5th
- 5th St and Colorado
- Valley North Center at JC Penney
- Eastmont Ave and 4th
- Eastmont Ave and 3rd
- Grant Rd and Mandolin
- 3rd St and Highline
- Baker Ave and 23rd
- Grant Rd and Kentucky
- Grant Rd and Mary
- Okanogan Ave and Orondo at PSJ
- Okanogan Ave and Kittitas
- Okanogan at Colonial Vista
- Okanogan Ave and Ferry
- Okanogan Ave and Park
- Red Apple Rd and Highland
- Grant Rd and Nevada
- Grant Rd and Nile
- Miller St and Russell at Pioneer MS
- Miller St and Coolidge
- Miller St and Plum
- Miller St and Washington
- Miller St and Orchard
- Miller St and Fifth
- Miller St and 9th
- Springwater at Target
- Maple at Foothills Community Center
- Riverside Dr and 9th
- Methow St and Ridgeview
- Riverside Dr and 9th
- Western Ave and Maple
- Grant Rd and Nile
- Grant Rd and Nevada
- Grant Rd and Mary
- 1 Pangborn Drive
- Wenatchee Ave and Maiden
- Grant Rd and Kentucky
- Olds Station Park-and-Ride (southside)
- Olds Station Park-and-Ride (northside)
- Methow St and Parkway
- Rock Island Rd and Nevada
- Kentucky Ave and Grant
- Kentucky Ave and 1st
- Euclid Ave and Gunn
- Euclid Ave and Gunn
- Cascade Ave and 35th
- 33rd St and Sunset
- Cascade Ave and 31st
- Cascade Ave and 33rd
- Cascade Ave and 33rd
- Ferry St and Cascade
- Cascade Ave and 31st
- Cascade Ave and 29th
- Kentucky Ave and 3rd
- Cascade Ave and 27th
- Cascade Ave and 25th
- Cascade Ave and Lloyd
- Cascade Ave and Broadmoor
- Cascade Ave and Bellevue
- Cascade Ave at Bello Rio Apts
- Cascade Ave at Bello Rio Apts
- Pangborn Dr and Airport
- 19th St and Cascade
- 19th St and Cascade
- Baker Ave and 19th
- Baker Ave and 17th
- Baker Ave and 17th
- Palouse St and Chelan
- Buchanan Ave and Washington
- Washington St and Delaware
- Washington Park
- Washington St and Cove
- Elliott Ave and Castlerock
- Castlerock Ave and Dogwood
- 11th St and Eastmont
- 11th St and Devon
- Castlerock Ave and Brandi
- 11th St and Colorado
- Crawford Ave and Miller
- 3rd St and Georgia
- Walmart
- Red Apple Rd and Linwood
- Maiden Ln and Western
- Western Ave and Story
- Western Ave and Maple
- Maple St and Poplar
- Ferry St and Mission
- Cascade Ave and 29th
- Ferry St and Walker Ave
- Miller and Stevens at Wenatchee HS
- Miller St and Springwater
- Springwater Ave and Miller
- Miller St and 9th
- Miller St and 5th
- Miller St and Orchard
- Miller St and Madison
- Miller St and Washington
- Miller St and Castlerock
- Miller St and Columbine
- Miller St and Montana
- Wenatchee Ave and Peachy
- Red Apple Rd and Rosewood
- Red Apple Rd and Linwood
- Okanogan Ave and Red Apple
- Okanogan Ave and Ferry
- Okanogan Ave at Colonial Vista
- Okanogan Ave and Peachy
- Okanogan Ave and Kittitas
- Okanogan Ave and Orondo at PSJ
- Wenatchee Ave and Crawford at Rescue Mis
- Malaga-Alcoa Hwy and Stemilt Creek
- Miller and Stevens at Wenatchee HS
- Malaga-Alcoa Hwy and Stemilt Creek
- 2900 Malaga-Alcoa Hwy
- Malaga Market
- Malaga-Alcoa Hwy and Main
- Saturday Ave and Dixie
- Dixie Ln and Marlette
- Dixie Ln and Bainard
- Dixie Ln and W. Malaga
- W. Malaga Rd and Wallace
- W. Malaga Rd and Conarty
- Miller St and Crawford at Hospital
- W. Malaga Rd at Three Lakes
- W. Malaga Rd and Golf Dr
- Wenatchee Ave and Crawford
- Crawford Ave and Cashmere
- Crawford Ave and Okanogan
- Crawford Ave and Fuller
- Miller St and Crawford at Hospital
- Baker Ave and 12th
- Baker Ave and 12th
- Baker Ave and 14th
- Crawford Ave and Pearview
- Baker Ave and 9th
- Baker Ave and 19th
- Baker Ave and 21st
- Baker Ave and 23rd
- Baker Ave and Stull
- Entiat Park-and-Ride
- Crawford Ave and Fuller
- Orondo Store
- Central Ave and Walnut
- Locust St and Central
- Locust St and Baker
- Locust St and Adams
- Douglas County Courthouse
- 5th St and Colorado
- Central Ave and Birch
- US 2/97 at BJ's Shell Station
- Crawford Ave and Okanogan
- US 2/97 at Lincoln Rock
- 3rd St and James
- 3rd St at Eastmont High School
- 3rd St and June
- 3rd St and Kansas
- Mission St and Fifth
- Mission St and 9th
- Mission St and Miller
- Crawford Ave and Cashmere St
- Taco Bell
- Chelan Ave and Springwater
- Chelan and 9th
- Chelan Ave and 7th
- Lakeside Park-and-Ride
- US 97A and Water
- US 97A at Lady of the Lake
- US 97A and Park St
- Webster Ave at Chelan HS
- Sanders St and Trow
- Sanders St and Wapato
- Johnson at Chelan City Hall
- SR 150 and Nixon at Don Morse Park
- SR 150 at Darnell's
- SR 150 and Eldorado
- SR 150 and Eldorado
- SR 150 and Boyd
- Ohme Garden Road and US 97A
- Ohme Garden Road and US 97A
- Valley Mall Pkwy and 5th
- US 97A and Lakeshore
- SR 150 and Winesap
- SR 150 and Bennett
- SR 150 and Bennett
- SR 150 at Lakeview
- SR 150 at Lakeview
- SR 150 and Madeline
- SR 150 and Madeline
- Eastmont Ave and 6th
- SR 150 and Sunrise
- 9th St and Ramona
- Eastmont Ave and 8th
- SR 150 and Totem Pole
- Manson Bay Park
- SR 150 and Harris
- US 97A and Lakeshore at Pat & Mike's
- SR 150 and Wapato Lake
- SR 150 and Wapato Lake
- US 2 at Rivers Edge Lodge
- Manson Bay Market
- Wenatchee Ave and Bridge
- 330 SR 150
- Entiat Way and Auvil Ave
- Entiat Way and Auvil Ave
- Western and Academy
- Western Ave and Academy
- Western Ave and Heritage Dr
- SR 150 and Boyd
- Western Ave and Heritage
- SR 150 at Don Morse Park
- Wenatchee Ave and Bridge
- Johnson Ave and Columbia
- Sanders St and Woodin
- Webster Ave and 2nd at Chelan HS
- Sanders St and Trow
- US 97A and Park
- US 97A and Water
- Lakeside Park-and-Ride
- US 97A and Bear Mountain
- US 97A and Bear Mountain
- Wenatchee Ave and Peachy
- US 97A at Stayman Flats
- US 97A and Stayman Flats
- US 97A and Navarre Coulee
- US 97A and Navarre Coulee
- US 97A and Pine Meadows
- US 97A and Wisdom
- US 97A and Howe
- US 97A and Risk
- Entiat Park-and-Ride
- US 97A and Risk
- Wenatchee Ave and Chehalis
- US 97A and Howe
- US 97A and Wisdom
- US 97A and Pine Meadows
- Entiat Way and Hagen at Entiat School
- Entiat Way and Hagen at Entiat School
- Entiat River Road Park-and-Ride
- Entiat River Road Park-and-Ride
- US 97A at Turtle Rock
- US 97A at Turtle Rock
- Orondo Ave and Wenatchee
- US 97A at Wenatchee Valley Truck Stop
- US 97A at Wenatchee Valley Truck Stop
- US 97A at Stemilt
- and 371 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 | 78.2 | first check |
| 2026-07-30 | 78.2 | no change |
| 2026-07-31 | 78.2 | no change |
| 2026-08-01 | 78.2 | 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
6 findings, ordered by severity.
Show every finding
- Warning2293 instances
2293 of 2293 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)
- Warning1343 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning621 instances
621 of 621 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)
- Warning4 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
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 156 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) Different (allowed)
- Your feed's agency_id is 0; your National Transit Database ID is 40252. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 0 to NTD ID 40252, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 2293 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 156 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 156 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 WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies. This resource supports agencies; it is not a scoring authority.
- Correctness 84 / 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 52 / 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/link-transit/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.