Contains data from CARTO.CTYLIMIT.Updated as needed.

Geospatial data about Seattle Zoning Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

This generalized outline of Seattle contains the north and south city limits but extends past the shoreline and contains no internal waterbodies. For the traditional north south city limits, please use this layer, Seattle City Limits - Overview (arcgis.com) .

2020 census geography including tracts for the city of Seattle, King County, Washington. Excludes partial tracts with very small populations within the city limits along the southern border of the city.Includes assignment of Seattle Community Reporting Areas (CRA-53), Community Reporting Area Groups (neighborhood roll up-13), Council Districts (7-assigned to the tract with the majority of the population based on the distribution of the component census blocks), and Urban Village Demographic Areas (UVDA). UVDA assignments subject to change based on future planning areas.

Geospatial data about Seattle Park Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

Speed Limit Map - From Hansen Asset Management System. Includes Speed Limit information for Seattle Streets. This map does not include data for WSDOT maintained roadways, private streets or other entities which maintain streets in Seattle. This map/data has been designed for reference use only. The City of Seattle is not responsible or liable for any inaccuracies contained in the derivative or misuse of this map/data. Speed limit data along city roads was obtained from the city's Hansen Asset Management System.This map is embedder on various SDOT pages like - https://www.seattle.gov/transportation/projects-and-programs/safety-first/vision-zero/speedlimits| Contact: SDOT GIS Team | Contact Email: DOT_IT_GIS@seattle.gov

Known stairways within the City limits, and basic Stairway attributes. Due to the many hills throughout Seattle, there are numerous locations where it becomes too steep for a street or sidewalk. The city built stairways to maintain the connection between adjacent neighborhoods and to provide an interconnected network of sidewalks.

| Attribute Information: 'https://www.seattle.gov/Documents/Departments/SDOT/GIS/Stairways_OD.pdf' rel='nofollow ugc' target='_blank'> https://www.seattle.gov/Documents/Departments/SDOT/GIS/Stairways_OD.pdf

| Data Confidence: Medium-High
| Data Confidence Source: 2015 SDOT Asset Management, Status and Condition Report

| Update Cycle: Weekly
| Contact Email: DOT_IT_GIS@seattle.gov

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.

Peat-settlement-prone areas (sites containing peat and organic soils that may settle when the area is developed or the water table is lowered).Peat settlement-prone areas. Peat settlement-prone areas consist of Category I and Category II peat settlement-prone areas that are delineated on Maps A1 through A26, Peat Settlement-prone Area Boundaries Maps, codified at the end of this Chapter 25.09. This parcel-specific delineation is based on the _location of the relevant bog or bogs identified in City of Seattle Identified Bogs (Troost 2007) plus a buffer of 50 feet for Category I peat settlement-prone areas or a buffer of 25 feet for Category II peat settlement-prone areas. On parcels larger than 50,000 square feet, the Director may consider a parcel-specific delineation, provided by the applicant, of the peat settlement-prone area boundary on a parcel. Where a parcel-specific delineation conflicts with the Peat Settlement-prone Area Boundaries Maps, the parcel-specific delineation shall apply.For more information about the definition of peat settlement prone areas, see Seattle Municipal Code section 25.09.012, Environmentally Critical Areas (ECA) definitions.Updated as needed.

This polygon feature contains geopolitical areas and is used to store geographic and attribute information describing the geographic extent of a political governance area or civil area, referred to in US OMB Circular A-16 as governmental units. The data was compiled from existing data sources and updated as needed by the city of SeaTac using available information.Incorporated in February 1990, the City of SeaTac is located in the Pacific Northwest, approximately midway between the cities of Seattle and Tacoma in the State of Washington. SeaTac is a vibrant community, economically strong, environmentally sensitive, and people-oriented. The City boundaries surround the Seattle-Tacoma International Airport, (approximately 3 square miles in area) which is owned and operated by the Port of Seattle. For additional information regarding the City of SeaTac, its people, or services, please visit https://www.seatacwa.gov. For additional information regarding City GIS data or maps, please visit https://www.seatacwa.gov/our-city/maps-and-gis.

Displays the 20 Large City Clerk neighborhood boundaries, along with their smaller neighborhood boundaries.Disclaimer: The Seattle City Clerk's Office Geographic Indexing Atlas is designed for subject indexing of legislation, photographs, and other records in the City Clerk's Office and Seattle Municipal Archives according to geographic area. Neighborhoods are named and delineated in this collection of maps in order to provide consistency in the way geographic names are used in describing records of the Archives and City Clerk, thus allowing precise retrieval of records. The neighborhood names and boundaries are not intended to represent any "official" City of Seattle neighborhood map.

The Office of the City Clerk makes no claims as to the completeness, accuracy, or content of any data contained in the Geographic Indexing Atlas; nor does it make any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the representations furnished herein. The maps are subject to change for administrative purposes of the Office of the City Clerk. Information contained in the site, if used for any purpose other than as an indexing and search aid for the databases of the Office of the City Clerk, is being used at one's own risk.

The classification of SPU infrastructure in the City of Seattle and the former service area north of the City limits into areas of piped flow where storm water flow is either separated, partially separated, or combined with sanitary flow. An area with separated flow means that drainage flow is in drainage pipes only. A partially separated area means that some pipes are present that have both drainage and sanitary flow. A combined area has all pipes carrying sanitary and drainage flow.Static dataset.

This polygon feature contains geographic and attribute information for the purpose of depicting Zoning Areas within the City of SeaTac, Washington. Last updated December 5, 2018.

Description

This polygon feature contains geographic and attribute information for the purpose of depicting Zoning Areas within the City of SeaTac, Washington. The data was compiled from existing zoning information and King County parcel data.To implement the SeaTac Comprehensive Plan's policies and objectives and the goals of the State Growth Management Act (GMA); To protect health, safety, and general welfare; To provide for the economic, social, and aesthetic advantages of orderly development and redevelopment through harmonious groupings of compatible and complementary land uses and the application of appropriate development standards; To provide for adequate public facilities and services in conjunction with development; To ensure public safety by restricting development of lands containing physical hazards and to minimize the adverse environmental impacts of development; and To ensure that land use decisions are made in accordance with the public interest and applicable laws of the State of Washington, including the Growth Management Act and subsequent amendments (Ord. 92-1041 --1)Updates to Zoning were made per Ordinance 18-1005, data was updated 3/28/2018.Updates to the Zoning were made per ORD17-1022, data was updated December 2017.Last amended in December 2015.The change to Angle Lake District Area Boundary was adopted on July 9th, 2015 (Ord. 15-1010).UL-5000 was changed to High Density Single Family Overlay Zone (HDS-OZ) on Nov 10, 2015.Segale properties were rezoned to UH-900 on Dec 8, 2015.Pursuant to Article XI, Section 11 of Washington State Constitution (Ord. 92-1041 -- 1). Zoning boundaries have been adjusted to line up with King County Assessor parcel lines that were improved in 2006 and 2007. Slivers and gaps will appear if this zoning layer is overlaid with historical zoning layers. The geometry of this data derives from KC parcel data which is updated quarterly. Then it was intersected with the existing zoning data to trasfer the attribute.Incorporated in February 1990, the City of SeaTac is located in the Pacific Northwest, approximately midway between the cities of Seattle and Tacoma in the State of Washington. SeaTac is a vibrant community, economically strong, environmentally sensitive, and people-oriented. The City boundaries surround the Seattle-Tacoma International Airport, (approximately 3 square miles in area) which is owned and operated by the Port of Seattle. For additional information regarding the City of SeaTac, its people, or services, please visit https://www.seatacwa.gov. For additional information regarding City GIS data or maps, please visit https://www.seatacwa.gov/our-city/maps-and-gis.

This polygon feature contains geographic and attribute information for the purpose of depicting Comprehensive Plan Areas within the City of SeaTac, Washington. The data was compiled from existing comprehensive plan information and King County parcel data.This data layer is a reflection of the comprehensive plan that indicates how the City wants to grow and function in the future. The source document contains broad statements of community goals and policies, as well as specific steps for achieving them. The City of SeaTac Comprehensive Plan serves as a "blueprint" for how SeaTac can achieve its vision for itself over the next 20 to 26 years. The Comprehensive Plan will provide the legal basis for future zoning and other implementation measures.City of SeaTac Comprehensive Plan as prepared and adopted by the SeaTac City Council.Last amended in June 23, 2015 (Ord. 15-1009).The change to Angle Lake District Area Boundary was adopted on July 9th, 2015 (Ord. 15-1010).The Washington Growth management Act (GMA) mandates that cities in high growth areas, like Puget Sound region, prepare and adopt comprehensive plans that are consistent with the GMA. The content was last modified in Dec 2013. Boundaries were updated based on parcel data from 02/13/2015, to reflect changes in ROWs and Parcel line, etc. Comprehensive plan boundaries have been adjusted to line up with King County Assessor parcel lines that were improved in 2006 and 2007. Slivers and gaps will appear if this comprehensive plan layer is overlaid with historical parcel, zoning, or comprehensive plan layers. The geometry of this data derives from KC parcel data which is updated quarterly. Then it was intersected with the existing Comprehensive Plan data to transfer the attribute.Incorporated in February 1990, the City of SeaTac is located in the Pacific Northwest, approximately midway between the cities of Seattle and Tacoma in the State of Washington. SeaTac is a vibrant community, economically strong, environmentally sensitive, and people-oriented. The City boundaries surround the Seattle-Tacoma International Airport, (approximately 3 square miles in area) which is owned and operated by the Port of Seattle. For additional information regarding the City of SeaTac, its people, or services, please visit https://www.seatacwa.gov. For additional information regarding City GIS data or maps, please visit https://www.seatacwa.gov/our-city/maps-and-gis.

Table from the American Community Survey (ACS) 5-year series on languages spoken and English ability related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B16004 Age by Language Spoken at Home by Ability to Speak English, C16002 Household Language by Household Limited English-Speaking Status. Data is pulled from block group tables for the most recent ACS vintage and summarized to the neighborhoods based on block group assignment.Table created for and used in the Neighborhood Profiles application.Vintages: 2023ACS Table(s): B16004, C16002Data 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.

2023 Parks and Open Space Walking Analysis. These area the 5 and 10 Walking Service Area Gaps based on Park Access Points outside of Urban Village boundaries.Created by taking the clipped 5 and 10 minute walk service areas and erasing them them from the "land" of the Shoreline boundary. This final version removes the Service Area Gaps that are within Urban Village boundaries.

Table from the American Community Survey (ACS) B17004 of poverty status in the past 12 months of individuals by sex by work experience. 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): B17004Data 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.