Feed status · checked 2026-08-01
Washington State Ferries
Based on the feed this agency publishes
Service mode Ferry
down 0.4 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 16 hours ago; last changed 29 hours 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 terminal. A field survey can start with the busiest terminals.Likely your team
19 of 19 terminals 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
27356 of 27356 trips don't say whether the vehicle is wheelchair accessible. Even with accessible terminals, riders need to know the vessel itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 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
- 19 of 19 terminals don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every terminal. A field survey can start with the busiest terminals.
- 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
- 27356 of 27356 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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 terminal. A field survey can start with the busiest terminals. · 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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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 50 days.
- Published accessibility data
- Accessibility information is stated for 0% of terminals and 0% of trips. This measures published data, not whether terminals or vessels 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 38 routes · 27,356 trips
- Terminal structure
- 19 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- Unknown: none of the 19 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 27,356 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 27,356 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 27,356 ferry trips publish cars_allowed.
- Fares
- Whole feed: applied fare data is published using GTFS Fares v1.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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 5 kinds of issue across 27385 instances (0 error, 27385 warning, 0 informational).
Service data covers the next 50 days.
0% of terminals state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is published.
0% of terminals state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and terminals
Each route is drawn once, using the longest shape its trips follow; terminals are the dots.
This feed has 19 terminals.
The route and terminal data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and terminals: this agency's GTFS feed.
- Friday Harbor - Anacortes (teal)
- Friday Harbor - Lopez Island (teal)
- Friday Harbor - Orcas Island (teal)
- Friday Harbor - Shaw Island (teal)
- Anacortes - Friday Harbor (teal)
- Coupeville - Port Townsend (teal)
- Anacortes - Lopez Island (teal)
- Anacortes - Orcas Island (teal)
- Anacortes - Shaw Island (teal)
- Kingston - Edmonds (teal)
- Lopez Island - Anacortes (teal)
- Lopez Island - Friday Harbor (teal)
- Lopez Island - Orcas Island (teal)
- Lopez Island - Shaw Island (teal)
- Mukilteo - Clinton (teal)
- Orcas Island - Anacortes (teal)
- Orcas Island - Friday Harbor (teal)
- Orcas Island - Lopez Island (teal)
- Orcas Island - Shaw Island (teal)
- Point Defiance - Tahlequah (teal)
- Port Townsend - Coupeville (teal)
- Shaw Island - Anacortes (teal)
- Shaw Island - Friday Harbor (teal)
- Shaw Island - Lopez Island (teal)
- Shaw Island - Orcas Island (teal)
- Southworth - Vashon Island (teal)
- Southworth - Fauntleroy (teal)
- Tahlequah - Point Defiance (teal)
- Vashon Island - Southworth (teal)
- Vashon Island - Fauntleroy (teal)
- Bainbridge Island - Seattle (teal)
- Bremerton - Seattle (teal)
- Clinton - Mukilteo (teal)
- Seattle - Bainbridge Island (teal)
- Seattle - Bremerton (teal)
- Edmonds - Kingston (teal)
- Fauntleroy - Southworth (teal)
- Fauntleroy - Vashon Island (teal)
| Route | Type | Line color |
|---|---|---|
| Friday Harbor - Anacortes | Ferry | teal |
| Friday Harbor - Lopez Island | Ferry | teal |
| Friday Harbor - Orcas Island | Ferry | teal |
| Friday Harbor - Shaw Island | Ferry | teal |
| Anacortes - Friday Harbor | Ferry | teal |
| Coupeville - Port Townsend | Ferry | teal |
| Anacortes - Lopez Island | Ferry | teal |
| Anacortes - Orcas Island | Ferry | teal |
| Anacortes - Shaw Island | Ferry | teal |
| Kingston - Edmonds | Ferry | teal |
| Lopez Island - Anacortes | Ferry | teal |
| Lopez Island - Friday Harbor | Ferry | teal |
| Lopez Island - Orcas Island | Ferry | teal |
| Lopez Island - Shaw Island | Ferry | teal |
| Mukilteo - Clinton | Ferry | teal |
| Orcas Island - Anacortes | Ferry | teal |
| Orcas Island - Friday Harbor | Ferry | teal |
| Orcas Island - Lopez Island | Ferry | teal |
| Orcas Island - Shaw Island | Ferry | teal |
| Point Defiance - Tahlequah | Ferry | teal |
| Port Townsend - Coupeville | Ferry | teal |
| Shaw Island - Anacortes | Ferry | teal |
| Shaw Island - Friday Harbor | Ferry | teal |
| Shaw Island - Lopez Island | Ferry | teal |
| Shaw Island - Orcas Island | Ferry | teal |
| Southworth - Vashon Island | Ferry | teal |
| Southworth - Fauntleroy | Ferry | teal |
| Tahlequah - Point Defiance | Ferry | teal |
| Vashon Island - Southworth | Ferry | teal |
| Vashon Island - Fauntleroy | Ferry | teal |
| Bainbridge Island - Seattle | Ferry | teal |
| Bremerton - Seattle | Ferry | teal |
| Clinton - Mukilteo | Ferry | teal |
| Seattle - Bainbridge Island | Ferry | teal |
| Seattle - Bremerton | Ferry | teal |
| Edmonds - Kingston | Ferry | teal |
| Fauntleroy - Southworth | Ferry | teal |
| Fauntleroy - Vashon Island | Ferry | teal |
List every terminal
- Anacortes
- Friday Harbor
- Coupeville
- Kingston
- Lopez Island
- Mukilteo
- Orcas Island
- Point Defiance
- Port Townsend
- Shaw Island
- Southworth
- Tahlequah
- Vashon Island
- Bainbridge Island
- Bremerton
- Clinton
- Seattle
- Edmonds
- Fauntleroy
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 | 65.0 | first check |
| 2026-07-30 | 65.8 | up 0.8 |
| 2026-07-31 | 65.4 | down 0.4 |
| 2026-08-01 | 65.0 | 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.
The feed file was re-published since 2026-07-31 (-8 KB).
Changed counts
- down Missing bike allowance (flagged by the MobilityData validator). (27896 → 27356) (missing_bike_allowance)
- down 27356 of 27356 trips don't say whether the vehicle is wheelchair accessible. (27896 → 27356) (scorecard_wheelchair_accessible_unknown)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning27356 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning27356 instances
27356 of 27356 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible terminals, riders need to know the vessel 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)
- Warning19 instances
19 of 19 terminals 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 terminal. A field survey can start with the busiest terminals. (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)
- Warning16 instances
Some terminals sit far from the route line they belong to.
Trip planners may draw the vessel route through the wrong path or point riders to the wrong terminal.
Fix: Check the flagged terminals' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged terminal.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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 50 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 27356 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 terminals and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 50 days.
- Accessible Not yet
- States wheelchair access on 0% of terminals 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 terminal and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every terminal and trip. Accessibility here measures what the feed publishes, not whether a terminal is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 50 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 72 / 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 68 / 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/washington-state-ferries/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.