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

This resource is a member of a series. 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. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

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.

This data set depicts the county boundaries of the State of Washington. This data set was created by the Washington State Department of Natural Resources to meet that agency's need for land surveying, land title, and land management GIS data. It is part of the Washington State Cadastral Framework Data set. The Washington Cadastral Framework data represents an integrated set of geographic-referencing data covering the State of Washington. It is derived from Land Surveys, DNR Orthophotos, USGS 7-1/2 minute quadrangles, DNR Ownership Tract Book, and various public organizations. The initial data population includes Public Land Survey System information, state boundary, county boundaries, and Department of Natural Resource parcel information.If you have any questions about this data, please contact Thomas A. Blake, GIS Data Products Supervisor - blaket@wsdot.wa.gov - (360) 570-2363. If you're having trouble viewing these services, please contact our Online Map Support.Attribute Definitions:Jurisdiction Name – Provides the name of the county.County Number – Provides the counties number.County FIPS Code - The unique code that identifies the counties of Washington State.

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 2023 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. In MCD states where no MCD exists or no MCD is defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The generalized boundaries of legal MCDs are based on those as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CCDs, delineated in 21 states, are based on those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth?s surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

A dataset listing Washington counties by population for 2024.

Scoggins Dam in northwest Oregon lies within the Gales Creek fault zone (GCF), a northwest-striking system of active faults forming the boundary between the Coast Range and the Tualatin Valley about 25 km east of Portland, Oregon. Geologic mapping published in 2020 shows the dam to lie within a block-faulted releasing stepover between the right-lateral, NW-striking Scoggins Creek and Parsons Creek strands of the GCF. The Scoggins Creek strand is presently mapped beneath the existing dam about 200 m north of the south abutment. Preliminary results from paleoseismic trenching by the U.S. Bureau of Reclamation, Portland State University, and the U.S. Geological Survey indicate that these two major fault strands have had multiple surface rupturing earthquakes in the Holocene. To confirm the accuracy of the 2020 geologic map and the geometry of the GCF in the releasing stepover region, we completed additional geologic mapping of the dam, reservoir, and an alternative dam site downstream between July 2018 and May 2020. Using high-resolution lidar topographic data and satellite imagery on handheld digital tablets, we collected data at ~500 field sites in the heavily forested terrain. We used these detailed field observations to locate and digitally map the main Scoggins Creek and Parsons Creek fault strands, as well as the cross faults linking the two main strands, to produce an improved and more detailed geologic map and cross sections of Scoggins Valley and its existing and proposed dam sites.

The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.

© Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project

This layer is a component of Feature classes representing locality (county, city, and town) boundaries in the Commonwealth of Virginia..

The 2022 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. 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 and beyond, 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.

Historic rail line locations throughout Pierce County sourced from Washington State Archive and Bureau of Land Management historic maps dated from 1850's to 2010. Please read metadata for additional information (https://matterhorn.co.pierce.wa.us/GISmetadata/pdbplan_historic_railroads.html). Any data download constitutes acceptance of the Terms of Use (https://matterhorn.co.pierce.wa.us/Disclaimer/PierceCountyGISDataTermsofUse.pdf).

Historic road arcs throughout Pierce County sourced from Washington State Archive and Bureau of Land Management historic maps dated from 1850's to 2010. Please read metadata for additional information (https://matterhorn.co.pierce.wa.us/GISmetadata/pdbplan_historic_roads.html). Any data download constitutes acceptance of the Terms of Use (https://matterhorn.co.pierce.wa.us/Disclaimer/PierceCountyGISDataTermsofUse.pdf).

Washington state county boundaries.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth?s surface using the State Plane coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

Broadband Federal Funding layer for the WA State Broadband Office Digital Equity Dashboard. Federal Funding Awards by County (feature layer) contains an overview of grant award programs in each county. Additional layers in the Public Federal Awards group reference other federal programs.The Availability of Service (Funding Awards) Experience Builder used in the WA State Broadband Office Digital Equity Dashboard references the following data in this web map:Federal Funding Awards by County (feature layer)Federal Funding Awards (table)The layers in the Public Federal Awards refer to specific federal grant programs. The tables other than Federal Funding Awards refer to projects that span multiple counties or have a region other than a county specified as the boundary.

This map shows specific water-quality items and hydrologic data site information which come from QWDATA (Water Quality) and GWSI (Ground Water Information System). Both QWDATA and GWSI are subsystems of NWIS (National Water Inventory System)of the USGS (United States Geologic Survey). This map is for Washington County, Utah. The scope and purpose of NWIS is defined on the web site: http://water.usgs.gov/public/pubs/FS/FS-027-98/

Washington State Department of Children, Youth, and Families (DCYF) Administrative Regions are geographically discrete areas within which DCYF administers its programs and services. The DCYF Administrative Regions data set provides time-enabled current and past administrative region boundaries. DCYF was formally established with an effective date of July 1, 2018.Important Notes:DCYF administrative region boundaries are composed of entire Washington State County boundaries.Current administrative region feaures have a "DateEnd" field value of

The Washington State Department of Social and Health Services, Behavioral Health Administration, Office of Forensic Mental Health Services Trueblood et al v. Washington State DSHS page links the Trueblood Implementation Plan, in which phased implementation regions are identified. The plan notes that the implementation regions are based on the Washington State Managed Care Organizations (MCO) and Administrative Service Organizations (ASO) regions. Further investigation reveals that both of these types of regions are based on Washington State Health Care Authority Integrated Managed Care Regions, which are in turn composed of Washington State County boundaries.“Trueblood” is an alias that refers to Cassie Cordell Trueblood, next friend of A.B., an incapacitated person, et al., v. The Washington State Department Of Social And Health Services, et al., Cause No. 2:14-cv-01178-MJP (https://www.clearinghouse.net/chDocs/public/JC-WA-0011-0002.pdf).Accuracy note - The Trueblood Implementation Regions boundaries are derived from 2010 US Census County boundaries. These boundaries are known to have significant discrepancies with survey-quality county boundary data available from Washington State Department of Natural Resources. Therefore, care should be taken to avoid making any final determinations regarding the Trueblood Implementation Region in which is located a high-accuracy feature such as a physical address when it is near a region boundary.Important: DSHS reserves the right to alter, suspend, re-host, or retire this service at any time and without notice. This is a map service that you can use in custom web applications and software products. Your use of this map service in these types of tools forms a dependency on the service definition (available fields, layers, etc.). If you form any dependency on this service, be aware of this significant risk to your purposes. You might consider mitigating your risk by extracting the source data and using it to host your own service in an environment under your control. Typically, DSHS Enterprise GIS staff will provide notification of changes via the Comments RSS capability in ArcGIS Online. You should subscribe to this RSS feed to monitor change notifications: https://www.arcgis.com/sharing/rest/content/items/585bca49c0614b75a2dbc28f8d4f5079/comments?f=rss