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.

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.

Point file of all incorporated cities in the state of Washington. Points were taken from the main polygon for each incorporated entity shown in the City Limits of Washington State data set.

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

This dataset contains FIPS (Federal Information Processing Standard), GNIS (Geographic Name Information System common) codes for identifying Washington state counties cities and towns. This is an official list from OFM (Office of Financial Management).

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. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2022 BAS as well.

Mapping of Visible Surface Water (VSW), or water features not concealed by other objects (i.e., tree canopy, bridges, etc.), is an important component of landcover models. VSW is not intended to represent a full hydrography or show connectivity, like other available water datasets – like NHD – whose boundaries may include other landcover types (i.e., shrubs, trees, etc.). Each feature has been visually verified and given attributes by an analyst. This dataset is also unique in that it reflects surface water for a single year - 2017. A variety of funding sources acquired between 2019 and 2023 aided the completion of the dataset for the entire state of Washington. More information on the dataset, current data coverage, and applications can be found on our website: https://hrcd-wdfw.hub.arcgis.com/.

Tip: Try using the filter options on the data tab to limit your download to a single County or WRIA. The filtered download can take a substantial amount of time to initiate, so it may be necessary to download the full dataset if the filter option does not work.

Access Washington's 206 data folders with 2,104 services and 5,824 layers of parcel boundaries, property tax records, and GIS mapping data.

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. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The Geographic Names Information System (GNIS) is the Federal standard for geographic nomenclature. The U.S. Geological Survey developed the GNIS for the U.S. Board on Geographic Names, a Federal inter-agency body chartered by public law to maintain uniform feature name usage throughout the Government and to promulgate standard names to the public. The GNIS is the official repository of domestic geographic names data; the official vehicle for geographic names use by all departments of the Federal Government; and the source for applying geographic names to Federal electronic and printed products of all types. See http://geonames.usgs.gov for additional information.

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. Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

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. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2017, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

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. State Legislative Districts (SLDs) are the areas from which members are elected to State legislatures. The SLDs embody the upper (senate) and lower (house) chambers of the state legislature. Nebraska has a unicameral legislature and the District of Columbia has a single council, both of which the Census Bureau treats as upper-chamber legislative areas for the purpose of data presentation; there are no data by SLDL for either Nebraska or the District of Columbia. A unique three-character census code, identified by state participants, is assigned to each SLD within a state. In Connecticut, Illinois, Louisiana, New Hampshire, Wisconsin, and Puerto Rico, the Redistricting Data Program (RDP) participant did not define the SLDs to cover all of the state or state equivalent area. In these areas with no SLDs defined, the code "ZZZ" has been assigned, which is treated as a single SLD for purposes of data presentation. The most recent state legislative district boundaries collected by the Census Bureau are for the 2022 election year and were provided by state-level participants through the RDP.

Water Resource Inventory Areas (WRIA) for Washington State at 1:24,000 scale. WRIAs were formalized under WAC 173-500-040 and authorized under the Water Resources Act of 1971, RCW 90.54. Ecology was given the responsibility for the development and management of these administrative and planning boundaries. These boundaries represent the administrative under pinning of this agency's business activities. The original WRIA boundary agreements and judgments were reached jointly by Washington's natural resource agencies (Ecology, Natural Resources, Fish and Wildlife) in 1970.

This web map contains datasets representing the National Hydrography Dataset (NHD) of Washington State, labels for NHD features, and the Watershed Boundary Dataset (WBD) basins for Hydrologic Unit Code (HUC) levels 4, 8, and 12. The NHD dataset has been adopted as the Washington State hydrography standard. The NHD is a national framework for assigning reach addresses to water-related entities, such as industrial discharges, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network, much like addresses on streets. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities--and any associated information about them--can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, land use and population, to help understand and display their respective effects upon one another. Furthermore, because the NHD provides a nationally consistent framework for addressing and analysis, water-related information linked to reach addresses by one organization (national, state, local) can be shared with other organizations and easily integrated into many different types of applications to the benefit of all.This high-resolution NHD, generally developed at 1:24,000/1:4,800 scale. Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.This map contains a BETA version of WaterType attached to the Skagit River Basin NHDflowlines. This Beta version of the Watertype is the result of a pilot project and will be refined over the next six months. The field is for users of NHD who want access to Water Type and who are not under Forest Practices rules. The WaterType uses Shorelines Master Program type S streams and Fish Presence Data from both WA Dept Natural Resources and WA Dept Fish and Wildlife.

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

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).

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

In 2007, Washington State legislators requested a trails database, but funding to complete that statewide project was not made available at the time.

In 2009, the Federal Government outlined the need for trails database schema in their Data Standards Review Committee, stressing the efficiency in management decisions that a streamlined database can provide.

“The collection, storage and management of trail related data are important components of everyday business activities in many federal and state land-managing agencies, trail organizations and businesses. From a management perspective, trails data must often mesh closely with other types of infrastructure, resource and facility enterprise data.”

In 2014, the Washington State Office of the Chief Information Officer's (OCIO) Geospatial Program Office acquired a Nonhighway and Off-Road Vehicle Activities (NOVA) Program grant through the Washington State Recreation and Conservation Office (RCO) giving the OCIO initial funding to develop a statewide trails database based on Federal Geographic Data Committee standards. Using the same standard for all trails data will allow land managers and recreational users throughout the state to access and use the data regardless of administrative boundary.

"Data standards will make it easier for trail information to be accessed and exchanged and used by more than one individual agency or group…Ease in sharing data increases the capability for enhanced and consistent mapping, inventory, monitoring, conditions assessment, maintenance, costing, budgeting, information retrieval, and summary reporting for internal and external needs.”

Along with streamlining data and facilitating efficiency in management practices across agencies, the database will provide a source of trails information that is open and free to the public.The 2016 State Legislature provided additional funding from the Nonhighway and Off-road Vehicle Activities Account to the Office of the Chief Information Officer to continue work on the database.

Additional details about the project can be found here:

Washington State Trails Map

Please note that this map and its component services have been designed to work together as part of the web application.

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.