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) System (MTS). The MTS 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 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 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, 2024, 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.

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

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.

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

Political county boundaries for Washington state. Also as KINGCO for King County only.

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) System (MTS). The MTS 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 are clusters of blocks within the same census tract. Each census tract contains at least one block group, and are uniquely numbered within census tracts. Block groups have a valid code range of 0 through 9. They also 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 block group 3 within that census tract. Block groups 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 block group 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 block group 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. 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.

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.

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

This layer contains data concerning the location and characteristics of bedrock, mappable geologic units, within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

The WA CSZ Tsunami Loss Estimate Study feature class data package includes comprehensive geospatial datasets and supporting information used to conduct building loss and casualty estimates for a Magnitude 9.0 Cascadia Subduction Zone (CSZ) earthquake and tsunami. This data supported Hazus analysis and includes building and demographic inventories (such as Hazus-compatible user-defined facilities, population estimates, and age-based demographic layers); tsunami inundation and hazard layers (including tsunami hazard boundaries and wave arrival times); tsunami evacuation data; tsunami casualty and economic impact data; and other supporting geospatial layers.Metadata can be attained through URL links below for feature class package, raster files, tables, and scripts.Feature class package includes:Feature Class: CBG_2010_ACS2019_Age65Plus_RatioName: American Community Survey 2015-2019 Age Estimates per 2010 Census Block Group for WA CSZ Tsunami Loss Estimate StudyURL: https://waseocgis.maps.arcgis.com/home/item.html?id=9b59baf3244141b2b5643e0a80446a2aRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Age_Estimates_per_2010_CBGs_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: CBG_2020_Pop_and_Housing_AllName: US Census 2020 Census Block Group Population and Housing for WA CSZ Tsunami Loss Estimate StudyURL: https://waseocgis.maps.arcgis.com/home/item.html?id=c39de520ee6d4643999a6494f33e8384Rest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/US_Census_2020_Population_and_Housing_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: CensusBlock_2020_Pop_and_HousingName: US Census 2020 Census Block Population and Housing for WA CSZ Tsunami Loss Estimate StudyURL: US Census 2020 Census Block Population and Housing for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/US_Census_2020_Census_Block_Population_and_Housing_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: Barriers_AssumedName: Assumed Evacuation Barriers for WA CSZ Tsunami Loss Estimate StudyURL: Assumed Evacuation Barriers for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Barriers_to_CSZ_Tsunami_Evacuation/FeatureServerFeature Class: BridgeFailures_WRRAPName: Assumed Bridge Failures from RRAP for WA CSZ Tsunami Loss Estimate StudyURL: Assumed Bridge Failures from RRAP for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Assumed_Bridge_Failures_for_CSZ_Tsunami_Loss_and_Casualty_Estimates_from_RRAP/FeatureServerFeature Class: NonBldg_LodgingName: WA Non Building Lodging Facilities for WA CSZ Tsunami Loss Estimate StudyURL: WA Non Building Lodging Facilities for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/WA_Non_Building_Lodging_Facilities_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: User_Defined_FacilitiesName: User Designed Facilities for WA CSZ Tsunami Loss Estimate StudyURL: User Designed Facilities for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/User_Designed_Facilities_for_WA_EMD_M9_CSZ_Tsunami_Casualty_and_Building_Loss_Estimate/FeatureServerFeature Class: County_WaterInclusive_LinesName: Water Inclusive County Line Boundaries for WA CSZ Tsunami Loss Estimate StudyURL: Water Inclusive County Line Boundaries for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Water_Inclusive_County_Line_Boundaries_for_WA_EMD_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: County_Tsunami_HazusName: Terrestrial WA County Boundaries for WA CSZ Tsunami Loss Estimate StudyURL: Terrestrial WA County Boundaries for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Washington_County_Terrestrial_Boundaries_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: County_WaterInclusiveName: Water Inclusive County Polygon Boundaries for WA CSZ Tsunami Loss Estimate StudyURL: Water Inclusive County Polygon Boundaries for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Water_Inclusive_Washington_County_Boundaries_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: County_WaterInclusive_SubdivisionsName: Subdivided Water Inclusive WA County Boundaries for WA CSZ Tsunami Loss Estimate StudyURL: Subdivided Water Inclusive WA County Boundaries for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Water_Inclusive_WA_County_Boundaries_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: CSZ_Earthquake_Tsunami_Study_ZoneName: WA Study Zone for WA CSZ Tsunami Loss Estimate StudyURL: WA Study Zone for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Washington_Study_Zone_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: Evacuation_Boundary_Compilation Name: Compiled WA County Tsunami Evacuation Boundaries for WA CSZ Tsunami Loss Estimate StudyURL: Compiled WA County Tsunami Evacuation Boundaries for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Compiled_WA_County_Tsunami_Evacuation_Boundaries_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: Evacuation_Constrained_Areas Name: WA Evacuation Constrained Areas for WA CSZ Tsunami Loss Estimate StudyURL: WA Evacuation Constrained Areas for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/WA_Evacuation_Constrained_Areas_for_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: PathDistance_2_PartialSafety_ftName: Path Distance to Partial Tsunami Safety for WA CSZ Tsunami Loss Estimate StudyURL: Path Distance to Partial Tsunami Safety for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Path_Distance_to_Partial_Tsunami_Safety_for_WA_CSZ_Tsunami_Loss_and_Casualty_Estimates/FeatureServerFeature Class: PathDistance_2_Safety_ftName: Path Distance to Tsunami Safety for WA CSZ Tsunami Loss Estimate StudyURL: Path Distance to Tsunami Safety for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Path_Distance_to_Tsunami_Safety_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: Wave_Arrival_TimeName: Wave Arrival Time for WA CSZ Tsunami Loss Estimate StudyURL: Wave Arrival Time for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Wave_Arrival_Time_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: Roads_WA StateName: WA Tsunami Road and Trail Evacuation for WA CSZ Tsunami Loss Estimate StudyURL: WA Tsunami Road and Trail Evacuation for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/WA_Tsunami_Road_and_Trail_Evacuation_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: FatalityBoundary_WA StateName: Tsunami Fatality Boundary for WA CSZ Tsunami Loss Estimate StudyURL: Tsunami Fatality Boundary for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Tsunami_fatality_boundary_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: HazardBoundary_WA_StateName: Tsunami Hazard Boundary for WA CSZ Tsunami Loss Estimate StudyURL: Tsunami Hazard Boundary for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Tsunami_Hazard_Boundary_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerFeature Class: StudyArea_WA_StateName: Study Area for Pedestrian Evacuation Analysis Tool for WA CSZ Tsunami Loss Estimate StudyURL: Study Area for Pedestrian Evacuation Analysis Tool for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/Study_Area_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServer Raster Files, Tables, and Scripts not included in the feature class package:Table: All_eqtsEcon_50 Name: 50 Percent Ground Motion Scenario Economic Loss for WA CSZ Tsunami Loss Estimate Study URL: 50 Percent Ground Motion Scenario Economic Loss for WA CSZ Tsunami Loss Estimate StudyRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/50_Percent_Ground_Motion_Scenario_Economic_Loss_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerTable: All_eqtsEcon_84 Name: 84 Percent Ground Motion Scenario Economic Loss for WA CSZ Tsunami Loss Estimate Study URL: 84 Percent Ground Motion Scenario Economic Loss for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service: https://services7.arcgis.com/vUVXhXafpruJFs3l/arcgis/rest/services/84_Percent_Ground_Motion_Scenario_Economic_Loss_for_WA_CSZ_Tsunami_Loss_Estimate_Study/FeatureServerTable: All_eqtsPDS_50 Name: 50 Percent Ground Motion Scenario Combined Earthquake and Tsunami Probability of Damage States and Debris for WA CSZ Tsunami Loss Estimate StudyURL: 50 Percent Ground Motion Scenario Combined Earthquake and Tsunami Probability of Damage States and Debris for WA CSZ Tsunami Loss Estimate Study - OverviewRest Service:

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:24,000.

When a recent state law (RCW 47.04.380) referenced “legacy state transportation facilities” WSDOT quickly realized that we did not have a geospatial dataset that documented the location, dates, and former names of our legacy State Highways. Using old county and state maps, right-of-way maps, data from our internal bridge information system, and articles from old department newsletters, we have mapped about 2500 miles of former state highways. This dataset does not include information for roads that are no longer open to traffic. This dataset presents current roadways within Washington State that were formerly designated by the State of Washington as State Roads, Primary State Highways, Secondary State Highways, State Routes, or US Highways and is authored by the Washington State Department of Transportation GIS and Roadway Data Office. Updates will occur as needed.

These GIS files represent geographic boundaries for lands that are under the protection of NYS Agricultural District Law, administered by the New York State Department of Agriculture and Markets. The boundaries are derived from New York State Agricultural District, 1:24,000-scale, maps produced at county agencies. The district boundaries correspond to tax parcel data. District boundaries are joined into a file representing all of the Agricultural Districts within an entire county. Note that 2003 legislation allows lands to be added to districts on an annual basis. Electronic data provided here may predate those additions. Tax parcel detail and secondary rights-of-way are not included in this dataset. Rights-of-way for state and federal highways, railroads and utilities are only included when they are delineated on the original 1:24,000 scale maps. The data files are in ArcGIS shapefile format.

DOL registration data was downloaded and processed to summarize the total number of registered certain electric vehicles by year and county. Transactions Counts were summed by year and county, for all Transaction Types. Data were filtered to only include plug-in hybrid electric vehicle (PHEV) and batter electric vehicles (BEV). Source data transaction types include: 1) Registration Renewal - continuation of vehicle driving privileges. Commonly referred to as "getting new tabs". 2) Registration at time of Transfer - renewals that occur when the ownership of a vehicle changes. 3) Original Registration - first ever issuance of vehicle driving privileges in Washington. Processed registration data were joined by county with spatial data to create a feature class for the last full calendar year of registration data.Data includes transactions completed from January 2017 through December 2024. DOL updates data monthly, this dataset will be updated quarterly.Department of Licensing Vehicle Registration attribute data downloaded from geodata.wa.gov (Vehicle Registration Summary | Data.WA | State of Washington)County Boundaries obtained from Washington Department of Natural Resources (WA County Boundaries - Overview)REST URL: https://services.arcgis.com/IYrj3otxNjPsrTRD/ArcGIS/rest/services/DOL/FeatureServerPlease direct questions about this layer to partnerships@wsdot. If you are having trouble viewing this item, please email OnlineMapSupport@wsdot.wa.gov.

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. Some GNIS names in this data are offensive so the word “Negro” has been replaced with the hydrologic unit code while the process of reviewing and changing the names is ongoing through official channels.

This layer contains data concerning the location and characteristics of unconsolidated Quaternary deposits within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022