Feed status · checked 2026-08-02
Clallam Transit System
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-08-01
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 47 minutes ago; last changed 42 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
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +18 points in its category
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
321 of 332 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 +24 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 +6 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
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
- 321 of 332 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
- 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.
Re-generate shape distances in your export; flag to your vendor if it persists.
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_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.
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 293 days.
- Published accessibility data
- Accessibility information is stated for 3.3% of stops and 74.6% 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 5 kinds of issue across 67 instances (24 error, 16 warning, 27 informational).
Service data covers the next 293 days.
3% of stops state wheelchair accessibility (3% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
3% of stops state accessibility (3% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
182 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Herrick and Hwy 101", "Hwy 112 and Wye Road", "Hwy 101 at Beaver Post Office / Store", 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 332 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.
- 10 (gray)
- 12 (teal)
- 123 (green)
- 15 (yellow)
- 17 (brown)
- 20 (green)
- 22 (teal)
- 24 (brown)
- 26 (red)
- 28 (red)
- 30 (black)
- 40 (black)
- 14 (green)
- 16 (red)
- 50 (red)
- 52 (blue)
- Hurricane (green)
| Route | Type | Line color |
|---|---|---|
| 10 Joyce | Bus | gray |
| 12 Lower Elwha Pilot | Bus | teal |
| 123 Strait Shot | Bus | green |
| 15 La Push | Bus | yellow |
| 17 Forks Pingo | Bus | brown |
| 20 College | Bus | green |
| 22 School Zone | Bus | teal |
| 24 Shane Park | Bus | brown |
| 26 West Side | Bus | red |
| 28 Deer Park Pilot | Bus | red |
| 30 Commuter | Bus | black |
| 40 Pingo | Bus | black |
| 14 Forks | Bus | green |
| 16 Neah Bay | Bus | red |
| 50 Jamestown Campus | Bus | red |
| 52 Diamond Point | Bus | blue |
| Hurricane Ridge | Bus | green |
List every stop
- Ranger Road and Hoppi Road
- N S'Klallam Drive at Ranger Road
- N S'Klallam Drive - pull out
- N S'Klallam Drive
- Ranger and Mike John Road
- Ranger and Place Road
- Place Road and Hwy 112
- Hwy 112 and Peters Road
- Hwy 112 at pullout area
- Hwy 112 and Oxenford
- Hwy 101 and Airport
- Hwy 112 and Freshwater Bay Road
- Hwy 112 and Vert Road
- Hwy 112 and Thompson Road
- Hwy 112 and Johnson Road
- Camp Hayden
- Hwy 112 and Grauel Ramapo Road
- Hwy 112 and Nordstrom Road
- Hwy 112 and Dempsey Road
- Hwy 112 and Miller Road
- Joyce
- Hwy 101 and Reddick
- Hwy 112 and Agate Beach Road by High School
- Hwy 112 and Whiskey Creek Road
- Hwy112 and Farrington Lane
- Hwy 112 and Lyre River Road at D.N.R. Campground
- Hwy 112 and Lyre River Road
- Lyre River
- Hwy 112 and Farrington Road
- Hwy 112 and Gossett Road
- Hwy 112 and Wye Road
- Hwy 112 and Joyce Piedmont Road
- Hwy 101 and Dry Creek Road
- Joyce
- Hwy 112 and Miller Road
- Hwy 112 and Bishop Road
- Hwy 112 and Dempsey Road
- Hwy 112 and Graul Ramapo
- Camp Hayden
- Hwy 112 and Wasankari Road
- Hwy 112 and Vert Road
- Hwy 112 and Gerber Road
- Hwy 112 and Sleepy Hollow
- Hwy 101 at Elwha Clinic
- Hwy 112 and Eden Valley
- Hwy 112 and Dan Kelley Road
- Hwy 112 and Sands Road
- Hwy 112 and Lower Dam Road
- Hwy 112 and Okerman Road
- Laird's Corner
- Hwy 101 and Walkabout
- Hwy 101 and Cameron
- Hwy 101 and Eclipse Industrial Pkwy
- Hwy 101 and Fairmont (Inbound)
- Laird's Corner
- Hwy 101 and Laurel
- Lincoln and 7th
- Lincoln and 4th
- Hwy 112 and Place Road
- Hwy 112 at D.N.R. campground
- Ranger Road and Place Road
- Port Angeles Gateway Transit Center
- Hwy 101 and Lake Aldwell
- Hwy 101 across from Sol Duc Hot Springs Road
- Hwy 101 and E. Snider Road
- Hwy 101 and W. Snider Road
- Hwy 101 across from Hungry Bear Restaurant
- Sappho
- Hwy 101 and Lake Pleasant Road
- Hwy 101 at Beaver Post Office / Store
- Hwy 101 and Salmon Dr
- Hwy 101 and Lucken Road
- Hwy 101 across from Whitcomb Dimmel Road
- Hwy 101 across from Herrick
- Hwy 101 at 110 (across from Ki'tla Center on 101)
- Forks Avenue across from Tillicum Park
- Forks Avenue and A Street
- Forks Transit Center
- Hwy 101 and Olympic Hot Springs Road
- Tillicum Park and Forks Avenue
- Hwy 101 at Grannys
- Ki'tla Business Park at Hwy 101
- Whitcomb Dimmel Road and Hwy 101
- Gaydeski Road and Hwy 101
- Iverson and Hwy 101
- Mansfield and Hwy 101
- Salmon Dr and Hwy 101
- Beaver and Hwy 101
- Lake Pleasant at Hwy 101
- Hungry Bear Restaurant and Hwy 101
- Riverside and Hwy 101
- Shadow Mountain Store on Hwy 101
- Hwy 101 across from E. Snider Road
- Sol Duc Hot Springs Road and Hwy 101
- Fairholm
- Barnes Creek and Hwy 101
- East Beach Road
- Hwy 101 at Shadow Mtn Road (across from the gas station)
- Boundary Ln and Hwy 101
- Herrick and Hwy 101
- Across from Hot Springs Road at Elwha River
- East Beach Road
- Forks Ave @ B St
- Hwy 101 At O.P.I.
- Sappho
- Forks Outfitter
- Hwy 101 at Barnes Creek
- Fairholme
- Hwy 101 at Camp David Jr Road
- 4th and Bogachiel way
- Hwy 110 and Quillayute Road
- LaPush Road at RV Park and Store
- LaPush Road
- La Push
- Ocean Front Dr at Quileute Oceanside Resort
- LaPush Road and Old LaPush Road
- LaPush Road near Hwy 101 across from Ki'tla Center
- LaPush Road near Hwy 101 at Ki'tla Center
- Lower Housing on LaPush Road
- Hwy 110 and Mainline Road
- Hwy 110 and Three Rivers Road
- Hwy 110 and Mora Road
- Hwy 110 and Hermison Road
- Hwy 110 at Third Beach
- LaPush Road at By-Yak-Way
- LaPush Road at Second Beach
- Hwy 113 at Grant Road
- Hwy 112 and Vista Dr
- Hwy 112 at Ray's Store
- Hwy 112 at Ba'adah Heights St
- Hwy 112 and Ba'adah Village Loop Rd
- Hwy 112 at Coast Guard Road in Neah Bay
- Hwy 112 at Warm House
- Hwy 112 at Marina
- Hwy 112 at Mini Mart
- Neah Bay
- Hwy 113 and Hwy 112
- Hwy 112 across from Mini Mart
- Hwy 112 at Washburn Store/Post Office
- Hwy 112 and Hemlock St
- Makah Cultural & Research Center Museum
- Hwy 112 and Backtrack Road
- Hwy 112 and Sekiu River Road
- Hwy 112 and Hoko Ozette Road
- Hwy 112 across from Sekiu Airport Road
- Clallam Bay
- Hwy 112 and Weel Road
- Hwy 112 and Eagle Crest Way
- Clallam Bay Corrections
- Hwy 112 and Hwy 113
- Hwy 112 across from Sekiu River Road
- Clallam Bay
- Sekiu
- Hwy 112 and Sekiu Airport Road
- Hwy 112 and Tveit Dr
- Hwy 112 and Eagle Pt Road
- 3rd Ave at Fort St
- Woodland Ave at Elk St
- Portage St at Bayview Ave
- Forks Avenue at Mocha Motion
- Medical Center
- 5th & Race
- 9th and Race
- Lauridsen near Race
- Lauridsen Boulevard
- Peninsula College
- Melody Lane
- 4th and Lincoln
- Peabody and Ahlvers
- Peabody and Viewcrest
- Port Angeles Highschool
- E Lauridsen Blvd and Albert
- 9th & Lincoln
- Laurel & Hwy 101
- Laurel and Motor
- Laurel and Park
- Laurel and Oakcrest
- Laurel and Ahlvers
- I Street and 16th Street
- I Street and 10th Street
- 8th and I Street
- 8th and G Street
- 8th and E Street
- 8th and B Street
- 8th and S. Cedar
- Cherry Street and 8th
- 16th and E Street
- 16th and H Street
- 8th between South Cedar and South Pine
- Cedar and 8th
- 9th and C Street
- C @ 13th
- C @ 16th
- West 1st and North Cherry Street
- Front St at Oak
- Lower Elwha Road
- Lower Elwha Child Care on Stratton Road
- Lower Elwha Apartments
- Elwha River Casino
- 16th & Butler
- 18th at Serenity house
- 18th near N Street
- 18th at Family Services
- L Street by Fairgrounds Upper Lot
- L Street south of Fairgrounds
- M Street @ 6th
- Edgewood and Lower Elwha
- Lower Elwha and Kacee
- Spokwes Dr
- Lower Elwha and Mapleton Way
- Lincoln Park
- Lauridsen and Bean
- Lauridsen and Fairmont
- Lauridsen and C Street
- 18th Street at Fairchild Heights
- 18th Street at Serenity House
- 18th & Butler
- West 16th at South C Street
- Hwy 101 and Monroe
- Hwy 101 and Mt. Pleasant
- Hwy 101 and Traylors Restaurant
- Kolonels Way
- Hwy 101 at Deer Park Cinema
- Hwy 101 At Bagley Creek
- Hwy 101 and Short Road
- O'Brien Road
- Hwy 101 and Octane Lane
- Hwy 101 and Blue Mountain Road
- 1st and Lincoln
- Hwy 101 and Barr Road
- Hwy 101 and Sherborne Road
- Hwy 101 and Pierson Road
- Hwy 101 and Kirk
- Hwy 101 across Joslin
- Hooker Road
- Hwy 101 and Parkwood Mobile Manor
- Hwy 101 and Taylor Cut-off
- River Road
- Washington Street at Home Depot
- 1st and Vine
- Washington Street at Costco
- Washington Street at Domino's Pizza
- 7th & Washington
- 5th and Washington Street
- 4th and Washington St
- 1st and Eunice
- 1st and Washington
- 1st and Jones
- 1st and Ennis
- 1st and Penn St
- and 82 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 78.2 | first check |
| 2026-07-30 | 78.2 | no change |
| 2026-08-01 | 78.2 | no change |
| 2026-08-02 | 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-08-01.
Same feed file as 2026-08-01; 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
8 findings, ordered by severity.
Show every finding
- Error24 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning330 instances
330 of 1301 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)
- Warning321 instances
321 of 332 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)
- Warning71 instances
71 of 1301 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)
- Warning15 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)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info24 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Ready
- Service data covers the next 293 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 1301 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. 1 validator error to resolve. States wheelchair access on 3% of stops and 75% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 293 days.
- Accessible Not yet
- States wheelchair access on 3% of stops and 75% 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 293 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 24 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 71 / 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 71 / 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/clallam-transit-system/2026-08-02.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-02. 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.