Current boundaries for King County incorporated places. This is extracted from CITY_ANNEX_AREA.

Zip Code Boundaries for King, Pierce, Snohomish, Kitsap

This data layer describes the boundaries of water districts of King County. These are district boundaries which do not always coincide with service area boundaries. Full metadata: http://www5.kingcounty.gov/sdc/Metadata.aspx?Layer=wtrdst

© King County

Zoning boundaries for unincorporated King County; WA. Created layers using parcels, cities, and legal descriptions. This is the version with the cities clipped out. This is used for GISMO and by KCGIS. We have another version that is presently being maintained as coverage that includes city areas.

Table from the American Community Survey (ACS) 5-year series for King County and City of Seattle median values for a variety of topics including age, gross rent, monthly owner costs, family and nonfamily incomes, earnings. Includes the margin of error for the values.

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

A polygon feature class displaying countywide zip code boundaries.Zip code data supplied by King County, updated quarterly.

This data release contains the GIS data supporting U.S. Geological Survey Open-File Report (OFR) 2005-1252, "The Geologic Map of Seattle—A Progress Report," published in 2005 by Kathy Goetz Troost, Derek B. Booth, Aaron P. Wisher, and Scott A. Shimel (https://doi.org/10.3133/ofr20051252). The OFR was prepared for the 2005 Washington Hydrogeology Symposium and describes the status of geologic mapping for Seattle, Washington, at the time. The map is the result of field mapping and compilation of subsurface geologic data during the years 1999–2004 and was funded by the City of Seattle and the U.S. Geological Survey. Data from more than 36,000 exploration points, geotechnical borings, monitoring wells, excavations, and outcrops were used in making the map. The northern part of the 2005 OFR and the supporting GIS data were subsequently published as two geologic maps: Booth, D.B., Troost, K.G., and Shimel, S.A., 2005, Geologic map of northwestern Seattle (part of the Seattle North 7.5’ X 15’ Quadrangle), King County, Washington: U.S. Geological Survey Scientific Investigations Map 2903, https://doi.org/10.3133/sim2903. Booth, D.B., Troost, K.G., and Shimel, S.A., 2009, Geologic map of northeastern Seattle (part of the Seattle North 7.5' x 15' quadrangle), King County, Washington: U.S. Geological Survey Scientific Investigations Map 3065, https://doi.org/10.3133/sim3065. The southern part of the 2005 OFR and the supporting GIS data were not subsequently published for various reasons. With the original authors' permission, the GIS data used to create the map shown in OFR 2005-1252 are being released here to best meet modern open-data standards and to allow for use in future studies and mapping. The data included in this data release are only those components necessary to create the map shown in OFR 2005-1252. The following map features were not available and are not included in this data release: bedding point data, faults, anticlines, and contact lines. OFR_2005-1252.gdb is an Esri geodatabase containing the following feature classes: ofr_2005_1252_geology_poly (1,068 features); ofr_2005_1252_fill_poly (424 features); ofr_2005_1252_seattle_fault_zone_poly (1 feature); ofr_2005_1252_wastage_landslide_deposits_poly (188 features); ofr_2005_1252_beds_line (6 features); and ofr_2005_1252_scarp_line (351 features). Metadata records associated with each of these elements contain more detailed descriptions of their purposes, constituent entities, and attributes. A shapefile (non-geodatabase) version of the dataset is also included, although due to character limits, some field names and text cells in the attribute tables were truncated relative to the equivalent values in the geodatabase. The authors ask that users of the geologic map data cite both the open-file report and the GIS data release: Open-File Report: Troost, K.G., Booth, D.B., Wisher, A.P., and Shimel, S.A., 2005, The geologic map of Seattle—a progress report: U.S. Geological Survey Open-File Report 2005-1252, https://doi.org/10.3133/ofr20051252. GIS data: Troost, K.G., Booth, D.B., Wisher, A.P., and Shimel, S.A., 2024, GIS data for U.S. Geological Survey OFR 2005-1252, The geologic map of Seattle—a progress report: U.S. Geological Survey data release, https://doi.org/10.5066/P93L6SPS.

No-shooting areas are delineated portions of King County within which the discharge of firearms is prohibited or regulated by King County Code, Title 12, Chapter 12.68. Each no-shooting area on the map is labeled with its corresponding code section number and area descriptor.

A no-shooting area defined by Chapter 12.68 may lie within or extend into an incorporated city, which may have its own laws regulating the discharge of firearms within its boundaries.

In addition, although not depicted on the map, King County Code, Title 7, Chapter 7.12.630 regulates the shooting of guns in King County Parks, which is in general prohibited.

Map created by the King County GIS Center for the Metropolitan King County Council. Revised September 25, 2006.

Data from: American Community Survey, 5-year Series

Data from: American Community Survey, 5-year Series 2006-2010

Table from the American Community Survey (ACS) S1602 limited English speaking households (households where no one age 14 and over speaks English "very well"). These are multiple, nonoverlapping vintages of the 5-year ACS estimates of population and housing attributes starting in 2010 shown by the corresponding census tract vintage. Also includes the most recent release annually.King County, Washington census tracts with nonoverlapping vintages of the 5-year American Community Survey (ACS) estimates starting in 2010. Vintage identified in the "ACS Vintage" field.The census tract boundaries match the vintage of the ACS data (currently 2010 and 2020) so please note the geographic changes between the decades. Tracts have been coded as being within the City of Seattle as well as assigned to neighborhood groups called "Community Reporting Areas". These areas were created after the 2000 census to provide geographically consistent neighborhoods through time for reporting U.S. Census Bureau data. This is not an attempt to identify neighborhood boundaries as defined by neighborhoods themselves.Vintages: 2010, 2015, 2020, 2021, 2022, 2023ACS Table(s): S1602Data downloaded from: Census Bureau's Explore Census Data The United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

This layer contains a unique geographic identifier (GEO_ID_BLK) for each block that is the key field for the data from censuses and surveys such as Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program. Data from many of the Census Bureau’s surveys and censuses, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). All original TIGER/Line shapefiles and geodatabases with demographic data are available atThe TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) Database (MTDB). The shapefiles include information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The shapefiles include polygon boundaries of geographic areas and features, linear features including roads and hydrography, and point features. These shapefiles do not contain any sensitive data or confidential data protected by Title 13 of the U.S.C.Census blocks are statistical areas bounded on all sides by visible features such as streets, roads, streams, and railroad tracks, and by non-visible boundaries including city, town, and county boundaries. Generally, census blocks are small in area as a block in a city. However, Census blocks in suburban and rural areas may be large, irregular and bounded by a variety of features In remote areas, census blocks may encompass hundreds of square miles. Census Block Numbers—Census blocks are numbered uniquely within the boundaries of each state, county, census tract with a 4-character census block number. The first character of the tabulation block number identifies the block group. A block number can only be unique by using the decennial census state (STATEFP20), county (COUNTYFP20), census tract (TRACTCE20), and block (BLOCKCE20). The entire block number is the GEO_ID_BLK. There is no consistency in block numbers from census to census.Full documentation: https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2020/TGRSHP2020_TechDoc.pdf

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Data from: American Community Survey, 5-year Series

BAS Submissions Read Me

This shapefile includes the annexation polygons that the Office of Financial Management (OFM) has sent to the Census Bureau since March 2020 as part of the Boundary and Annexation Survey (BAS). The Census Bureau uses these polygons to update Washington State’s city limits. Field names follow Census BAS guidelines, and an outline of relevant field names is below. More information about BAS can be found here: https://www.census.gov/programs-surveys/bas.html

The polygons include the quarterly annexations and other boundary corrections that effect the Census city boundaries, as well as several county boundary adjustments for King, Kittitas, Pierce, Spokane, and Stevens County. The annexation polygons were originally created by Washington’s Department of Transportation, and then edited by OFM to align with the latest BAS city boundary file available. These polygons to not follow the strict legal description of the annexation, as their intent is to make clear delineations between jurisdictions for population allocation. The following are the main differences between BAS annexation polygons and the originals:

<!--· The edges and vertices of polygons are snapped first to contiguous Census city limits and then to county parcels

<!--·
Where an annexation moves a city boundary to be either adjacent or across a right of way, the polygon is drawn to the centerline of the right of way

<!--· Annexations that are only include a right of way are often omitted, as they will not change the Census Bureau boundary

This file is updated quarterly. For questions or for data from earlier years, please contact Nate Chase nate.chase@ofm.wa.gov.

Relevant Field Names:

<!--·
CHNG_TYPE- Type of area update. A is annexation, D is deannexation, and B is a boundary correction which is a newly discovered boundary discrepancy

<!--· Eff_date- the local effective date

<!--· AUTHYPE- O is ordinance or resolution; X is for boundary correction; L signifies a county boundary correction

<!--· DOCU- the legal ordinance or resolution for the annexation. If there is a blank, then the entry is a correction polygon.

<!--· RELATE- Changing from in or out of jurisdiction

<!--· JUSTIFY- OFM’s reason for submitting the change polygon

<!--· A_Date- this is the date that OFM approves the annexation. OFM cannot legally approve annexations until all state requirements are met. The approval date cannot be earlier than the effective date, but it can be on the same day. OFM’s population determinations use the approval date of annexations. BAS submissions are only submitted after this date.

<!--· Source- The file in which the change polygon was originally submitted. Examples:

o
2022_Q1 submitted in December 2021

o 2022_Q2 submitted in March 2022

o
2022_Q3 submitted in June 2022

o
2022_Q4 submitted in September 2022

Public parks within King County. City parks and other agency parks may not be complete.