Use this web map to link to other geospatial datasets available through county and city sites (Not comprehensive). May need to zoom in to see the participating cities. The county boundaries and city points were published by Washington State agencies and downloaded from geo.wa.gov. Locations are approximate, and no warranties are made regarding this data. The canvas basemap has been compiled by Esri and the ArcGIS user community from a variety of best available sources. Want to have your data site listed? Contact the Geospatial Program Office.

Unincorporated Urban Growth Areas (UGA) as defined by the Growth Management Act (GMA). The annual update is conducted by collecting UGA polygons directly from each of Washington's 39 counties. As of 2025, there are 27 counties with UGAs.All UGA polygons are normalized against the Department of Revenue's (DOR) "City Boundaries" layer (shared to the Washington Geoportal a.k.a. the GIS Open Data site: geo.wa.gov). The City Boundaries layer was processed into this UGA layer such that any overlapping area of UGA polygons (from authoritative individual counties) was erased. Since DOR polygons and county-sourced UGA polygons do not have perfect topology, many slivers resulted after the erase operation. These are attempted to be irradicated by these processing steps. "Multipart To Singlepart" Esri tool; exploded all polygons to be individualSlivers were mathematically identified using a 4 acre area threshold and a 0.3 "thinness ratio" threshold as described by Esri's "Polygon Sliver" tool. These slivers are merged into the neighboring features using Esri's "Eliminate" tool.Polygons that are less than 5,000 sq. ft. and not part of a DOR city (CITY_NM = Null) were also merged via the "Eliminate" tool. (many very small slivers were manually found yet mathematically did not meet the thinness ratio threshold)The final 8 polygons less than 25 sq. ft. were manually deleted (also slivers but were not lined up against another feature and missed by the "Eliminate" tool runs)Dissolved all features back to multipart using all fieldsAll UGAs polygons remaining are unincorporated areas beyond the city limits. Any polygon with CITY_NM populated originated from the DOR "City Boundaries" layer. The DOR's City Boundaries are updated quarterly by DOR. For the purposes of this UGA layer, the city boundaries was downloaded one time (4/24/2025) and will not be updated quarterly. Therefore, if precise city limits are required by any user of UGA boundaries, please refer to the city boundaries layer and conduct any geoprocessing needed. The DOR's "City Boundaries" layer is available here:https://www.arcgis.com/home/item.html?id=69fcb668dc8d49ea8010b6e33e42a13aData is updated in conjunction with the annual statewide parcel layer update. Latest update completed April 2025.

Washington State County Boundaries including Department of Natural Resources (DNR) county codes. This data is created from the WA Public Land Survey source data maintained by the DNR.WA County Boundaries Metadata

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site3/rest/services/Public_Boundaries/WADNR_PUBLIC_Cadastre_OpenData/FeatureServer/10Official Washington State boundary

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not be divided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

Displays outlines depicting the current boundaries of WA State Parks lands. This KML file contains a network link to another KML file that is stored on the WA State Parks website. In this way, using this KML file will always display up-to-date boundaries, eliminating the need to download updated KML files.This data layer depicts the current boundaries for WA State Parks, and properties owned by WSPRC (Washington State Parks and Recreation Commission). Property types include State Park, State Park Conservation Area, State Park Heritage Site, State Park Property, State Park Trail, Historical State Park, and Marine State Park. Data is revised monthly or more frequently; however, errors and inaccuracies may exist in the data. This layer is for informational purposes only and is not intended to be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries.For attribute descriptions, see the metadata for the GIS data layer "ParkBoundaries", available online at http://geo.wa.gov/datasets/wa-stateparks::parks-park-boundaries .To download this and other data from Washington State Parks, go to geo.wa.gov and search for "wsprc" (Washington State Parks and Recreation Commission).

The Washington State Surface Geology Map scale at a scale of 1:24,000 geodatabase was made accessible through the Washington State Department of Natural Resources, Division of Geology and Earth Resources. The data are provided in ESRI ArcGIS 10.0 file geodatabase format (see Read Me file). The projection is in Lambert Conformal Conic, NAD83 HARN datum. Data available for download include:- One ESRI ArcGIS 10.0 geodatabase, consisting of a set of 11 feature classes, 7 relationship classes, and one geodatabase table.- Metadata for each feature class, in both XML and HTML formats (for ease of reading outside of GIS software)- One shapefile depicting the outline of Washington State.- One ArcGIS map document (ending in the .mxd extension), containing specifications for data presentation in ArcMap- One ArcGIS layer file for each feature class (ending in the .lyr extension), containing specifications for data presentation in an ArcGIS viewing application- One Geologic Map Codes document (PDF) defining the symbology used in the map.- The README file These digital data and metadata are provided as is, as available, and with all faults basis. Neither Department of Natural Resources nor any of its officials and employees makes any warranty of any kind for this information, express or implied, including but not limited to any warranties of merchantability or fitness for a particular purpose, nor shall the distribution of this information constitute any warranty. This resource was provided by the Washington State Department of Natural Resources, Division of Geology and Earth Resources and made available for distribution through the National Geothermal Data System.

This map displays the most recent summary streamflow values within the state of Washington from gages maintained by the Washington State Department of Ecology and the United States Geological Survey (USGS). The streamflow symbols reflect the magnitude of the most recent estimated flows relative to historic flows that occurred in past years on the current date at that particular stream gaging station. Generally, streamflows greater than the 75th percentile are considered above normal. Flows between the 25th and 75th percentiles are considered normal, and flow less than the 25th percentile are considered low.Differences exist in Ecology’s and USGS’ presentation of their respective flow information. The flow data displayed for the Ecology gaging stations are calculated overnight from statistics measured from the previous day’s flow so that all streamflow data displayed for the Ecology gaging stations are relative to the previous day’s flow.USGS reports flow in near real-time meaning the reported flow estimates are updated several times a day and are no more than 6 hours old. The flow data displayed for the USGS gaging stations reflects the near real-time flows relative to the historic record of flows on the current date.For more information on the Department of Ecology River and Stream Flow Monitoring program, visit http://www.ecy.wa.gov/programs/eap/flow/index.html.For more information on the USGS Water Watch program, visit http://waterwatch.usgs.gov/.Questions or concerns about the map and data displayed should be directed to gis@ecy.wa.gov.All data displayed are provisional and subject to significant change.

PUBLIC VIEW FOR DOWNLOAD: The Washington State Trails Database provides a comprehensive picture of multi-modal trail systems, which may be used to identify trail gaps, plan trail connections, and prioritize funding to improve access to Washington State trails. This database is compiled from data submitted to RCO by state and local agencies and their partners responsible for building and maintaining trails. RCO makes no guarantees of the accuracy or condition of trails depicted in this dataset. This data should be used for informational purposes only and is not intended to be used for route-finding or navigation. Version 2.0 was published on April 15, 2025.

The Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" “Standard” (http://pubs.usgs.gov/tm/11/a3/). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit (6th level) for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries are being developed where partners and data exist and will be incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).-

The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations

This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site.

The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many.

CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry.

Symbolizing Spatial Features:
Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records.

Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata

Download the entire dataset: https://fortress.wa.gov/dfw/public/PublicDownload/Habitat/HRCD/HRCD.zipThis dataset includes changes in land cover throughout Washington State, specifically areas of tree loss and development. Changes are represented as polygons and include qualitative descriptions and quantitative assessments of changes. Attributes provide details about causes of change (Change Agents), types of changes observed (e.g. canopy loss, impervious surface gain), area of change, and time period for when the change occurred. The change locations were identified from analyzing high resolution (1-meter) NAIP imagery, allowing changes as small as a single tree or new home to be identified.This dataset covers most of Western Washington and several counties in Eastern Washington. Coverage is split along county and/or WRIA boundaries and the time periods for change locations vary by county and/or WRIA. All areas in the dataset were assessed for changes between 2011 and 2017; additionally, some locations include changes as early as 2006 or as recent as 2021.Visit https://hrcd-wdfw.hub.arcgis.com/ or email HRCD@dfw.wa.gov for more information on how the data is created, accuracy information, tutorials, user guides, and current coverage or extent information.This dataset is updated about once a year with more recent years of change, new counties / WRIAs, or both. This copy of the data was updated in January 2024.

WBDHU6: This geospatial dataset represents the 3rd level (6-digit) hydrologic unit boundaries of the Watershed Boundary Dataset (WBD) layer for Washington. It was created by dissolving boundaries from the finer resolution hydrologic units to create these broader boundaries. See metadata for the wbd_wa_poly feature class for a more complete description of the WBD. USGS Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD) located here: http://pubs.usgs.gov/tm/11/a3/pdf/tm11-a3.pdf

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata

The Washington State Parcels Project provides a statewide data set of tax parcels attributes that cover those counties that currently have digital tax parcels. Attribute data has been normalized so that the field names are the same across all counties. The data set contains the tax parcel identification number, situs addresses, the Department of Revenue land use codes, improvement and land values, and a link to the county's assessor's website for parcel information (if it exists).

The Washington State Department of Transportation (WSDOT) developed this data set in fulfillment of a grant from the Federal Highway Administration (FHWA) to test a conceptual climate risk assessment model developed for transportation infrastructure. WSDOT applied the model using scenario planning in a series of statewide workshops, using local experts, to create qualitative assessment of climate vulnerability on its assets in each region and mode across Washington. For the purposes of this statewide effort, managed assets were defined as sections of highway or railroad, and whole facilities (Ferry Terminal or Airport). Fourteen workshops engaged experts across all WSDOT regions, state ferries, rail, and aviation. The outcome of each workshop was a subjective evaluation of asset vulnerability agreed upon by participants. This feature class contains the results for railroads. This study assumed 100% probability of climate change impacts previously identified in the University of Washington Climate Impacts Group's 2009 assessment. Types of impacts discussed in the workshops with local experts included: temperature changes, increase in extreme weather events, precipitation changes, sea level rise, fire risk, and high winds. The scientific community's understanding of climate impacts continues to evolve as the models and collective understanding of feedback systems improve. We do not have perfect information about exactly how, when, where, and to what magnitude climate changes will unfold in Washington State. After reviewing the extreme weather events and other impacts projected for their area, workshop participants defined sections of highway, rail, or specific facilities with consideration of the local geology, natural and constructed drainage and hydrology, elevation, slope, land use and operational maintenance issues. Once defined, each corridor or facility was then ranked for two variables: asset criticality and potential impact. Asset criticality (which was defined by the workshop participants) should not be confused with other measures such as highway functional class. 1) How critical is that site or corridor to overall transportation operations and public safety? The following scale guided the qualitative assessment of criticality: a. 1-3 = Low - facility/corridor with low daily traffic, available alternate routes, not part of the National Highway System b. 4-6 = Medium - facility/corridor has low to medium daily traffic, serves as an alternate route of other state corridors or facilities c. 7-10 = High - facility/corridor is an Interstate or other major highway, is considered a lifeline route or is the sole access to a population center or critical facility. 2) How might potential climate changes impact site or corridor operations? The following scale guided the assessment of climate impacts: a. 1-3 = Low - Reduced Capacity: facility/corridor partially open to use and full operations can be restored within 10 days b. 4-6 = Medium - Temporary Operational Failure: Facility/corridor closed for hours or days. Reopening or repair could be completed within 60 days. c. 7-10 = High - Complete Failure: facility/corridor likely to require major repair or rebuild with closures lasting more than 60 days These qualitative rankings for impacts and asset criticality and some general descriptions were captured in spreadsheets that were later used to create GIS layers. This data is intended for use in statewide or regional planning and to assist in adapting maintenance and engineering policies and practices to protect our transportation infrastructure over the coming decades. The rankings here were based on our knowledge and understanding at the time of the study, and should only be taken as a best professional estimate for considering potential conditions that might put people or infrastructure at risk. Current information about projected climate changes and asset use and condition should always be taken into account, especially as time progresses.

This GIS data shows the locations of WSDOT road crossings, including culverts, dams, bridges, and fishways.The GIS data contains attributes identifying location information in latitude and longitude, as well as state plane coordinates and state route and milepost. Additional attributes include indicators for fish use, barrier status, and fish species. It is a subset of data compiled and extracted from the Washington Department of Fish and Wildlife's (WDFW) Fish Passage and Diversion Screening Inventory (FPDSI) database. It includes data compiled from several WDFW and non-WDFW fish passage barrier inventory efforts.

Presents the locations of DSHS-licensed Long Term Care Adult Family Homes, Assisted Living Facilities, and Enhanced Services Facilities. Also presents the business locations of Certified Residential Service and Supports Providers and their Group Training Homes when available. The data is extracted nightly from the Washington State Department of Social and Health Services (DSHS) Aging and Long Term Support Administration's (ALTSA), Facilities Management System (FMS) and geocoded using the the Washington Master Address Services (WAMAS) address correction and geocoding tool. This is the same data that is available in the lookup tools in the Residential Care Services web site with the addition of location data columns.Current and archived records since the initial load on 3/9/2020 are provided in this dataset. Filter on GDLArchiveDate is NULL to work with only the current records.

Washington Legislative Districts 2024, also known as Remedial Map 3B, created in CASE NO. 3:22-cv-05035-RSL at the United States District Court for the Western District of Washinton at Seattle, presided over by judge Robert. S Lasnik.https://www.documentcloud.org/documents/24483664-redistricting-orderThese districts replace the 2022 Legislative districts and will be used in the 2024 elections pending US Supreme Court action.Please note that there are four split Census Blocks due to annexations in Yakima County. Portions of blocks 530770018013012, 530770018012077, 530770020042004, and 530770018011075 transferred from LD 15 to LD 14. This feature layer contains 49 features representing each of Washington State's 49 legislative districts and is projected to NAD 1983 HARN Washington State Plane South US Feet.For questions, please contact Nicholas Pharris at the Secretary of State. nicholas.pharris@sos.wa.gov

This imagery service is for viewing only, no downloading of the raster images available.