Route

Washington Coast Trail

Route by Lauren Lake (PacificCoastalTrail blog), 2022

What is a route?

A route is a trail that a hiker worked out and published. No agency or association looks after it as one trail, and there may be no signs for it. Every route.

Download the GPXOfficial site

Length
180 mi290 km
Time
12 days
Where
WA

The map needs JavaScript. Download the GPX or GeoJSON file from this page.

  • Main track
  • Alternates and connectors

Track: Lauren Lake (the author's GPX file), read 2026-11-17, drawn simplified to 30 m.

At a glance

Length
180 mi290 km
Season
May to September, because of the tides and creeks on the Olympic Wilderness Coast
High point
584 ft178 mComputed from the track.
Low point
0 ft0 mSea level. Computed from the track.
Climb
9,829 ft2,996 mComputed from the track, walking south to north.
Shape
End to end. Cape Disappointment, Washington to Cape Flattery, Washington
Terrain
Coast
Permits
A permit is required for the Olympic Wilderness Coast in those months, May to September.

Know before you go. The route is not on foot all the way. Its author rounded the two major bays in the south with a shuttle driver and says it could be done by bus, and used a bus again at Taholah and Queets and to Forks. The author says the bays and the tribal lands that cannot be hiked all have bus options to bypass them. At a couple of tide pinch points the author stopped just short and crossed on an early morning tide, and some days are scrambles over rocks and ladders. At least a few nights of wilderness camping are needed.

Walking is not on file for this trail yet.

Map credit

Track credit: Lauren Lake, PacificCoastalTrail blog (https://pacificcoastaltrail.wordpress.com), CC BY 4.0.

Base map: OpenFreeMap, © OpenMapTiles, data © OpenStreetMap contributors. Relief and contours: Terrain Tiles, accessed from https://registry.opendata.aws/terrain-tiles. United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey. Canada terrain data contains information licensed under the Open Government Licence - Canada. ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736. Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration. Mexico terrain data source: INEGI, Continental relief, 2016.

In brief

The Washington Coast Trail is a route along the Washington coast from Cape Disappointment to Cape Flattery, about 180 miles. Its author walked it northbound in 12 days and left the hardest part, the Wilderness Coast, for the end. The two big bays in the south are rounded by shuttle or bus, and the north has tide pinch points and scrambles over rocks and ladders.

In brief. The Washington Coast Trail is a 180-mile (290 km) route through coastal country in Washington, United States. It runs from Cape Disappointment, Washington, to Cape Flattery, Washington, and walking all of it usually takes 12 days. Its highest point is 584 ft (178 m), and the track climbs 9,829 ft (2,996 m) in total, computed from the track. This page has a GPX of the track to download.

Last checked

Elevation profile

0200400600050100150Elevation (ft)Distance along the track (mi)0501001500100200Elevation (m)Distance along the track (km)

Computed from the track, walking south to north, the trail climbs 9,829 ft (2,996 m) in total over 179 mi (288.1 km) of track, between a low point of sea level and a high point of 584 ft (178 m). The line breaks where the track does: it has 6 parts, and no climb is counted across a gap.

Not for navigation: check the trail’s own maps and current conditions before you go. Something wrong on this page? Report a problem.

About this data

Where the track and the facts come from, licence, checks, the logo, corrections, and every field of the record

The route

Author
Lauren Lake (PacificCoastalTrail blog)Who worked the route out (route.creator)
First published
2022
Track policy
OpenThe author publishes the track freely

CC BY 4.0 is fine for this as well.

Lauren Lake (PacificCoastalTrail blog) The author’s words

Read on https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983.

  1. Track policy: OpenThe author publishes the track freely. A track is included only where the author's terms allow passing it on, or where OpenStreetMap carries the route as a route relation. Otherwise get it from the author.This route
  2. Track policy: SoldThe route is got by buying a guide or map set. No track is included from any source, OpenStreetMap included.
  3. Track policy: WithheldThe author chooses not to publish a track. No track is included from any source, OpenStreetMap included.
  4. Track policy: UnclearWhether the author shares the track is not settled. No track is included until it is settled.

About the route

The author calls the Washington, Oregon and California coast routes together the Pacific Coastal Trail, and is working on a further 245 miles from Cape Flattery to Bellingham, which this record does not include. The route passes Cape Alava, the western end of the Pacific Northwest Trail, and the author's track file marks a junction with that trail on the Olympic coast.

The record

Kind
RouteA trail that a hiker worked out and published. No agency or association looks after it as one trail, and there may be no signs for it
Designation
Person-defined route (Lauren Lake, 2022); no agency or association
Tier
RegionalA long trail of 50 miles (80 km) or more
Listing
First setIn the first set of trails
Where
WA (Washington), United States
Length
180 mi290 kmAbout 180 mi (290 km), the author's figure, given on this dataset's issue tracker: "The length is approximately 180 miles, though very dependent on how you hike/boat/bus the bay crossings.". The published length of walking the whole trail from end to end (for a loop reached by a stem, with the stem both ways), a check value, not measured from the track.
Record ID
washington-coast-trailStable: the directory name, never changed

Where the hiking facts come from

Checked 2026-11-17.

The season comes from the page of the body that manages the trail or the trail's own association or, for a route, its author.

Verification Checked 2026-11-17

Measured
YesThe track was downloaded and measured
Published
180 mi290 km
Measured
179 mi287.9 kmgeodesic, from the track
Difference
−0.7%measured minus published
Parts
6pieces left after joining ends within 100 m
Within 15% of the published length Beyond 15%: the record must say why

The author's GPX file, 12 daily tracks: 287.9 km in 6 parts (3,100 points), 0.7% under the author's 180 mi (290 km). The bay crossings and bus rides are gaps between parts, not part of the track.

Elevation

These figures were computed from the trail’s track and Terrain Tiles (Mapzen terrarium), open data on AWS, not read from a page about the trail. A point was taken every 30 m along each part of the track, and its elevation was read from the model. Smoothing and counting: moving average over 90 m of track; ascent and descent counted with a 5 m reversal threshold.

Highest point on the track
584 ft178 mAt 48.36267, -124.70117 (latitude, longitude)
Lowest point on the track
0 ft0 mSea level. At 46.38711, -124.06339 (latitude, longitude)
Total climb
9,829 ft2,996 mComputed from the track, walking south to north. Walking the other way swaps climb and descent.
Total descent
10,135 ft3,089 mComputed from the track, walking south to north. Walking the other way swaps climb and descent.
Length sampled
179 mi288.1 kmThe length of the track, not the published length
Published length
180 mi290 km
Coverage
0.994 (about 99% of the published length)Length sampled divided by the published length
Parts
6Pieces left after joining track ends within 100 m, counted for the elevation sampling. It can differ from the count under Verification, which was made with another joining rule. No climb is counted across a gap.
Part starts
34.4, 50.5, 75.5, 84.6, 101.6 mi55.4, 81.2, 121.5, 136.1, 163.5 kmThe distance along the profile where each part after the first begins
Elevation model
Terrain Tiles (Mapzen terrarium), open data on AWS
Model credit
Terrain Tiles, accessed from https://registry.opendata.aws/terrain-tiles. United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey. Canada terrain data contains information licensed under the Open Government Licence - Canada. ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736. Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration.The credit to show, as the model gives it
Tiles
Zoom 12, about 29.2 m per cell at 40 degrees north
Sampling
Every 30 m along the track
Smoothing
Moving average over 90 m of track; ascent and descent counted with a 5 m reversal threshold
Computed
2026-11-17
Method version
1

Limits

Computed from a public elevation model, not measured on the ground. Highest and lowest are the model's values at the sample points, with anything below sea level shown as 0. Ascent and descent depend on the smoothing and the threshold, and published figures for the same trail can differ from them by 15 percent or more. Parts of the track are never joined, so a gap is not counted.

Source and licence

Track in this dataset
line.geojsonThe main track file of the record
Source status
VerifiedThe track was downloaded from the source and measured
Publisher
Lauren Lake, PacificCoastalTrail blog (publishes the route)
Source
https://pacificcoastaltrail.wordpress.com/2022/03/23/itinerary-washington-coast/Where to ask for the track: a layer or relation page
Track source
Lauren Lake (the author's GPX file)
Format
GPX 1.1 exported from CalTopo: 20 tracks of one segment each (12 daily tracks, 3 bus tracks, 3 alternates and 2 tracks not used), 110 waypoints, no routes
Main track
The main track is the file's 12 daily tracks, Day 1 to Day 12, in the order of the days from Cape Disappointment to Cape Flattery. The file lists them out of order, and Day 5 is stored from Taholah to Moclips and is reversed. Nothing is drawn between days, so the bay crossings and bus rides are gaps: 12.7 km from the Stackpole Road parking lot (where a waypoint reads "Meet shuttle for ride to Tokeland") to Tokeland, around Willapa Bay; 3.8 km from Westport across the mouth of Grays Harbor; 0.4 km inside Moclips, between the end of Day 4 and the bus stop where Day 5 starts; 19.2 km from Taholah to the restart point south of Queets, where the itinerary page has a bus; and 13.3 km from the Cedar Creek bus stop to the turnoff for Oil City, where the file has a bus track by way of Forks. The track is in 12 pieces and 6 parts. The file's three bus tracks, its tracks Quinault North and Quinault South (which the itinerary page does not describe as walked) and its waypoints are not used. The three alternates (the La Push alternate and two overland routes round tide points) are in alternates.geojson.How the main track is told apart from alternates, connectors and side trails
Coordinates
EPSG:4326What the source stores; published files are longitude/latitude (EPSG:4326)
Licence
CC BY 4.0
Credit
Lauren Lake, PacificCoastalTrail blog (https://pacificcoastaltrail.wordpress.com), CC BY 4.0The credit line to show, as the source asks
May be passed on
YesThe source's terms allow its track to be passed on
OpenStreetMap only
No
Source checked
2026-11-17
Newer release?
page-link: the itinerary page links the route's CalTopo map (https://caltopo.com/m/BHDR0). The track came as a GPX file the author attached to the dataset's issue 1 on 2026-11-17; read the page again, and ask the author for a new file, when the page changes.How to tell whether the source has a newer release

What the source says

Creative Commons Attribution 4.0 International (CC BY 4.0). The route's author wrote on this dataset's public issue tracker on 2026-11-17: "CC BY 4.0 is fine for this as well." (https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983). The author had agreed earlier in the same issue, for the California track, to be credited as the source with a link to the blog (https://github.com/swaits/longhikes/issues/1#issuecomment-6928214012). The itinerary page itself (read 2026-11-17) states no terms.

With the page it was read on. Not legal advice.

OpenStreetMap

Relation
None recordedNo relation found, or not searched
Note
Not searched: the author publishes the track and has shared it.

Logo

No emblem of its own. No emblem of the route was found. The author's itinerary page, home page and About page were read on 2026-11-17: the images they carry are photographs and the blog's own header text, with no crest, badge or mark for the route.

Corrections

If you made this route

The author of a route can ask for its record to be corrected or removed, and the record will be corrected or removed. Say which route: washington-coast-trail. See About.

This record is a text file anyone can correct. Please say where a correction can be checked: a source page, a map, or a measured track.

Every field of the record, with its exact value

As stored in trail.toml. The record schema says what each field means.

id
washington-coast-trail
name
Washington Coast Trail
country
US
regions[0]
WA
length_km
290
length_note
About 180 mi (290 km), the author's figure, given on this dataset's issue tracker: "The length is approximately 180 miles, though very dependent on how you hike/boat/bus the bay crossings."
kind
route
tier
regional
designation
Person-defined route (Lauren Lake, 2022); no agency or association
wave
1
places_checked
2026-11-20
places_track
d534dd0b7f82825d
source.status
verified
source.publisher
Lauren Lake, PacificCoastalTrail blog (publishes the route)
source.publisher_url
https://pacificcoastaltrail.wordpress.com/
source.url
https://pacificcoastaltrail.wordpress.com/2022/03/23/itinerary-washington-coast/
source.discovery
page-link: the itinerary page links the route's CalTopo map (https://caltopo.com/m/BHDR0). The track came as a GPX file the author attached to the dataset's issue 1 on 2026-11-17; read the page again, and ask the author for a new file, when the page changes.
source.format
GPX 1.1 exported from CalTopo: 20 tracks of one segment each (12 daily tracks, 3 bus tracks, 3 alternates and 2 tracks not used), 110 waypoints, no routes
source.crs
EPSG:4326
source.licence
CC-BY-4.0
source.licence_text
Creative Commons Attribution 4.0 International (CC BY 4.0). The route's author wrote on this dataset's public issue tracker on 2026-11-17: "CC BY 4.0 is fine for this as well." (https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983). The author had agreed earlier in the same issue, for the California track, to be credited as the source with a link to the blog (https://github.com/swaits/longhikes/issues/1#issuecomment-6928214012). The itinerary page itself (read 2026-11-17) states no terms.
source.attribution
Lauren Lake, PacificCoastalTrail blog (https://pacificcoastaltrail.wordpress.com), CC BY 4.0
source.osm_only
false
source.mainline
The main track is the file's 12 daily tracks, Day 1 to Day 12, in the order of the days from Cape Disappointment to Cape Flattery. The file lists them out of order, and Day 5 is stored from Taholah to Moclips and is reversed. Nothing is drawn between days, so the bay crossings and bus rides are gaps: 12.7 km from the Stackpole Road parking lot (where a waypoint reads "Meet shuttle for ride to Tokeland") to Tokeland, around Willapa Bay; 3.8 km from Westport across the mouth of Grays Harbor; 0.4 km inside Moclips, between the end of Day 4 and the bus stop where Day 5 starts; 19.2 km from Taholah to the restart point south of Queets, where the itinerary page has a bus; and 13.3 km from the Cedar Creek bus stop to the turnoff for Oil City, where the file has a bus track by way of Forks. The track is in 12 pieces and 6 parts. The file's three bus tracks, its tracks Quinault North and Quinault South (which the itinerary page does not describe as walked) and its waypoints are not used. The three alternates (the La Push alternate and two overland routes round tide points) are in alternates.geojson.
source.source_checked
2026-11-17
source.redistributable
true
source.line_source
Lauren Lake (the author's GPX file)
source.line_file
line.geojson
osm.relation
0
osm.note
Not searched: the author publishes the track and has shared it.
shield.status
no-logo-exists
shield.logo_source
""
shield.contact
Lauren Lake, PacificCoastalTrail blog
shield.note
No emblem of the route was found. The author's itinerary page, home page and About page were read on 2026-11-17: the images they carry are photographs and the blog's own header text, with no crest, badge or mark for the route.
shield.logo_file
""
shield.logo_owner
Lauren Lake, PacificCoastalTrail blog
verification.verified
true
verification.date
2026-11-17
verification.measured_km
287.9
verification.difference_percent
-0.7
verification.parts
6
verification.note
The author's GPX file, 12 daily tracks: 287.9 km in 6 parts (3,100 points), 0.7% under the author's 180 mi (290 km). The bay crossings and bus rides are gaps between parts, not part of the track.
route.creator
Lauren Lake (PacificCoastalTrail blog)
route.year
2022
route.line_policy
open
route.creator_words
CC BY 4.0 is fine for this as well.
route.creator_words_url
https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983
route.note
The author calls the Washington, Oregon and California coast routes together the Pacific Coastal Trail, and is working on a further 245 miles from Cape Flattery to Bellingham, which this record does not include. The route passes Cape Alava, the western end of the Pacific Northwest Trail, and the author's track file marks a junction with that trail on the Olympic coast.
guide[0].title
Itinerary: Washington Coast
guide[0].author
Lauren Lake (PacificCoastalTrail blog)
guide[0].access
free
guide[0].url
https://pacificcoastaltrail.wordpress.com/2022/03/23/itinerary-washington-coast/
guide[0].format
web page with a 12-day table of stopping points, and a link to a CalTopo map; the GPX file is shared on the dataset's issue tracker
hike.summary
The Washington Coast Trail is a route along the Washington coast from Cape Disappointment to Cape Flattery, about 180 miles. Its author walked it northbound in 12 days and left the hardest part, the Wilderness Coast, for the end. The two big bays in the south are rounded by shuttle or bus, and the north has tide pinch points and scrambles over rocks and ladders.
hike.official_url
https://pacificcoastaltrail.wordpress.com/2022/03/23/itinerary-washington-coast/
hike.start
Cape Disappointment, Washington
hike.end
Cape Flattery, Washington
hike.shape
point-to-point
hike.days[0]
12
hike.days[1]
12
hike.terrain[0]
coast
hike.caution
The route is not on foot all the way. Its author rounded the two major bays in the south with a shuttle driver and says it could be done by bus, and used a bus again at Taholah and Queets and to Forks. The author says the bays and the tribal lands that cannot be hiked all have bus options to bypass them. At a couple of tide pinch points the author stopped just short and crossed on an early morning tide, and some days are scrambles over rocks and ladders. At least a few nights of wilderness camping are needed.
hike.season
May to September, because of the tides and creeks on the Olympic Wilderness Coast
hike.months[0]
5
hike.months[1]
6
hike.months[2]
7
hike.months[3]
8
hike.months[4]
9
hike.permit
A permit is required for the Olympic Wilderness Coast in those months, May to September.
hike.start_lonlat[0]
-124.076
hike.start_lonlat[1]
46.271
hike.end_lonlat[0]
-124.718
hike.end_lonlat[1]
48.388
hike.checked
2026-11-17
hike.season_basis
primary
hike.source[0].url
https://pacificcoastaltrail.wordpress.com/2022/03/23/itinerary-washington-coast/
hike.source[0].publisher
Lauren Lake, PacificCoastalTrail blog
hike.source[0].facts[0]
official_url
hike.source[0].facts[1]
summary
hike.source[0].facts[2]
days
hike.source[0].facts[3]
terrain
hike.source[0].facts[4]
caution
hike.source[1].url
https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983
hike.source[1].publisher
Lauren Lake, PacificCoastalTrail blog (said by the route's author on the dataset's issue tracker, 2026-11-17)
hike.source[1].facts[0]
summary
hike.source[1].facts[1]
start
hike.source[1].facts[2]
end
hike.source[1].facts[3]
shape
hike.source[1].facts[4]
caution
hike.source[2].url
https://github.com/swaits/longhikes/issues/1#issuecomment-6958673541
hike.source[2].publisher
Lauren Lake, PacificCoastalTrail blog (said by the route's author on the dataset's issue tracker, 2026-11-17)
hike.source[2].facts[0]
season
hike.source[2].facts[1]
months
hike.source[2].facts[2]
permit
hike.source[2].facts[3]
caution
hike.source[3].url
https://github.com/swaits/longhikes/issues/1#issuecomment-6935845788
hike.source[3].publisher
Lauren Lake, PacificCoastalTrail blog (the author's GPX file, attached to the dataset's issue tracker)
hike.source[3].facts[0]
start_lonlat
hike.source[3].facts[1]
end_lonlat
place[0].kind
park
place[0].slug
olympic-national-park
place[0].basis
track
place[0].km
98.5
place[1].kind
wilderness
place[1].slug
daniel-j-evans-wilderness
place[1].basis
track
place[1].km
71.9
history[0].date
2026-11-17
history[0].change
The record was added at the request of the route's author, as a person-defined route of about 180 miles (290 km) in WA, with the author's own track and alternates.
history[0].fields[0]
record
history[0].basis
The route's author sent the track on the dataset's public issue tracker, named the route the Washington Coast Trail, gave its ends, Cape Disappointment and Cape Flattery, and its length, and named the itinerary page as the best page for it.
history[0].basis_url
https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983
history[0].asked_by
the route's author
history[0].outcome
applied
history[1].date
2026-11-17
history[1].change
The season, months and permit were added, and the caution now says that every bay and closed stretch has a bus option, all as the route's author said.
history[1].fields[0]
hike.season
history[1].fields[1]
hike.months
history[1].fields[2]
hike.permit
history[1].fields[3]
hike.caution
history[1].basis
The route's author replied on the dataset's public issue tracker that the hiking season is May to September, because of tides and creeks on the Olympic Wilderness Coast, that a permit is required for the Olympic Wilderness Coast in those months, and that the bays and the tribal lands that cannot be hiked all have bus options to bypass.
history[1].basis_url
https://github.com/swaits/longhikes/issues/1#issuecomment-6958673541
history[1].asked_by
the route's author
history[1].outcome
applied
history[2].date
2026-11-20
history[2].change
The season is recorded as coming from the page of the body that manages the trail or, for a route, its author.
history[2].fields[0]
hike.season_basis
history[2].basis
The season is stated by Lauren Lake, PacificCoastalTrail blog (said by the route's author on the dataset's issue tracker, 2026-11-17) as: May to September, because of the tides and creeks on the Olympic Wilderness Coast.
history[2].basis_url
https://github.com/swaits/longhikes/issues/1#issuecomment-6958673541
history[2].asked_by
the dataset's own check
history[2].outcome
applied
history[3].date
2026-11-20
history[3].change
The trail was placed in Olympic National Park, Daniel J. Evans Wilderness.
history[3].fields[0]
place
history[3].basis
Measured from the trail's main track against the GMBA Mountain Inventory v2 (Snethlage et al. 2022), via EarthEnv outlines (gmba-v2, 2026-11-20), the National Park Service, Land Resources Division outlines (nps, 2026-11-20), the Wilderness Connect, University of Montana (wilderness.net) outlines (wilderness-connect, 2026-11-20) by tools/place_trails.py.
history[3].basis_url
https://www.earthenv.org/mountains
history[3].asked_by
the dataset's own check
history[3].outcome
applied

History of this record

What was changed or asked for, on what evidence, and who asked, oldest first (4 entries)
  1. The record was added at the request of the route's author, as a person-defined route of about 180 miles (290 km) in WA, with the author's own track and alternates.

    Basis: The route's author sent the track on the dataset's public issue tracker, named the route the Washington Coast Trail, gave its ends, Cape Disappointment and Cape Flattery, and its length, and named the itinerary page as the best page for it. https://github.com/swaits/longhikes/issues/1#issuecomment-6935950983

    Asked by: the route's author

    • record
  2. The season, months and permit were added, and the caution now says that every bay and closed stretch has a bus option, all as the route's author said.

    Basis: The route's author replied on the dataset's public issue tracker that the hiking season is May to September, because of tides and creeks on the Olympic Wilderness Coast, that a permit is required for the Olympic Wilderness Coast in those months, and that the bays and the tribal lands that cannot be hiked all have bus options to bypass. https://github.com/swaits/longhikes/issues/1#issuecomment-6958673541

    Asked by: the route's author

    • hike.season
    • hike.months
    • hike.permit
    • hike.caution
  3. The season is recorded as coming from the page of the body that manages the trail or, for a route, its author.

    Basis: The season is stated by Lauren Lake, PacificCoastalTrail blog (said by the route's author on the dataset's issue tracker, 2026-11-17) as: May to September, because of the tides and creeks on the Olympic Wilderness Coast. https://github.com/swaits/longhikes/issues/1#issuecomment-6958673541

    Asked by: the dataset's own check

    • hike.season_basis
  4. The trail was placed in Olympic National Park, Daniel J. Evans Wilderness.

    Basis: Measured from the trail's main track against the GMBA Mountain Inventory v2 (Snethlage et al. 2022), via EarthEnv outlines (gmba-v2, 2026-11-20), the National Park Service, Land Resources Division outlines (nps, 2026-11-20), the Wilderness Connect, University of Montana (wilderness.net) outlines (wilderness-connect, 2026-11-20) by tools/place_trails.py. https://www.earthenv.org/mountains

    Asked by: the dataset's own check

    • place