Neighborhood Map Atlas neighborhoods are derived from the Seattle City Clerk's Office Geographic Indexing Atlas. These are the smallest neighborhood areas and have been supplemented with alternate names from other sources in 2020. They roll up to the district areas. The sub-neighborhood field contains the most common name and the alternate name field is a comma delimited list of all the alternate names.

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

Table from the American Community Survey (ACS) 5-year series on education enrollment and attainment related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B14007/B14002 School Enrollment, B15003 Educational Attainment. Data is pulled from block group tables for the most recent ACS vintage and summarized to the neighborhoods based on block group assignment.

Table from the American Community Survey (ACS) 5-year series on age and gender related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B01001 Sex by Age, B01002 Median Age by Sex. 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): B01001, B01002Data 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 estima

Table from the American Community Survey (ACS) 5-year series on poverty and employment status related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B23025 Employment Status for the Population 16 years and over, B23024 Poverty Status by Disability Status by Employment Status for the Population 20 to 64 years, B17010 Poverty Status of Families by Family Type by Presence of Related Children under 18 years, C17002 Ratio of Income to Poverty Level in the Past 12 Months. 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): B23025, B23024, B17010, C17002Data 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.<d

Neighborhood map atlas district areas are derived from the Seattle City Clerk's Office Geographic Indexing Atlas. These are the largest neighborhood areas and have been supplemented with alternate names from other sources in 2020. They are subdivided further into the neighborhood map atlas sub-areas called neighborhoods. The sub-neighborhoods field contains a comma delimited list of all the sub-areas and their alternate names.The original atlas is designed for subject indexing of legislation, photographs, and other documents and is an unofficial delineation of neighborhood boundaries used by the City Clerks Office. Sources for this atlas and the neighborhood names used in it include a 1980 neighborhood map produced by the Department of Community Development, Seattle Public Library indexes, a 1984-1986 Neighborhood Profiles feature series in the Seattle Post-Intelligencer, numerous parks, land use and transportation planning studies, and records in the Seattle Municipal Archives. Many of the neighborhood names are traditional names whose meaning has changed over the years, and others derive from subdivision names or elementary school attendance areas.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.

Table from the American Community Survey (ACS) 5-year series on race and ethnicity related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B03002 Hispanic or Latino Origin by Race, B02008-B02013 Race Alone or in Combination with One or More Other. 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): B03002, B02008, B02009, B02010, B02011, B02012, B02013Data downloaded from: Census Bureau's Explore Census Data The United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACS</

description: Seattle Parks and Recreation GIS Map Layer Shapefile - Play Area Shapefile - This Seattle Parks and Recreation ARCGIS park feature map layer was exported from SPU ARCGIS and converted to a shapefile then manually uploaded to data.seattle.gov via Socrata. OR Web Services - Live "read only" data connection ESRI web services URL: http://gisrevprxy.seattle.gov/arcgis/rest/services/DPR_EXT/ParksExternalWebsite/MapServer/33; abstract: Seattle Parks and Recreation GIS Map Layer Shapefile - Play Area Shapefile - This Seattle Parks and Recreation ARCGIS park feature map layer was exported from SPU ARCGIS and converted to a shapefile then manually uploaded to data.seattle.gov via Socrata. OR Web Services - Live "read only" data connection ESRI web services URL: http://gisrevprxy.seattle.gov/arcgis/rest/services/DPR_EXT/ParksExternalWebsite/MapServer/33

Seattle Parks and Recreation ARCGIS park feature map layer web services are hosted on Seattle Public Utilities' ARCGIS server. This web services URL provides a live read only data connection to the Seattle Parks and Recreations Play Area dataset.

Table from the American Community Survey (ACS) 5-year series on transportation related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B08303 Travel Time to Work, B25044 Tenure by Vehicles Available, B08301 Means of Transportation to Work. 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): B08303, B25044, B08301Data 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 part of USGS Data Series 935 (Cochrane, 2014) presents bathymetry and topography data for the Offshore of Seattle, California, map area, a part of the Southern Salish Sea Habitat Map Series. The data for this map area are a combination of topography extracted from a pre-existing Digital Elevation Model (DEM) merged with bathymetry data that were collected by the National Oceanic and Atmospheric Administration (NOAA) using multibeam sonar systems. The merged data are available for download in a single zip file (BathyTopo_OffshoreSeattle.zip).

This part of USGS Data Series 935 (Cochrane, 2014) presents observations from underwater video collected in the Offshore of Seattle, California, map area, a part of the Southern Salish Sea Habitat Map Series. To validate the interpretations of multibeam sonar data and turn it into geologically and biologically useful information, the U.S. Geological Survey (USGS) towed a camera sled over specific locations throughout the Seattle map area to collect video and photographic data that would “ground truth” the seafloor. The ground-truth survey conducted in the Offshore of Seattle map area occurred in 2011 on the R/V Karluk (USGS field activity K0111PS) and on the Washington State Department of Fish and Game R/V Molluscan (USGS field activity M0111PS). The underwater camera sled was towed 1 to 2 m above the seafloor at speeds of between 1 and 2 nautical miles/hour. The surveys for this map area include approximately 6 hours (9.1 trackline km) of video.

Geological Map of Seattle Creek Map Area, Western Selwyn Basin, Yukon (115P/16)

Geological map (1:50 000 scale) of Seattle Creek area, central Yukon (NTS 115 P/16) including geological cross-sections, mineral occurrences, structural relationships and U-Pb age determinations.

🇨🇦 캐나다

Geological map (1:50 000 scale) of Seattle Creek area, central Yukon (NTS 115 P/16) including geological cross-sections, mineral occurrences, structural relationships and U-Pb age determinations.

This part of USGS Data Series 935 (Cochrane, 2014) presents substrate, geomorphic, and biotope data in the Offshore of Seattle, California, map area, a part of the Southern Salish Sea Habitat Map Series. Given the variable bathymetric resolution, the complex geologic history of the region, and the lack of acoustic backscatter data, automated and semi-automated classification schemes of classifying seafloor substrate and geoform were deemed to have very low accuracy. Instead, classification of these properties was performed manually following the Coastal and Marine Ecological Classification Standard (CMECS; Madden and others, 2009) using observations from underwater video footage. The best overall predictors of biotic assemblage were used to generate the CMECS biotopes. However, the nature of the biological data gathered makes it difficult to define clear biotopes. It was difficult to see or identify many organisms in the underwater video, and with an average of only 3-4 taxa identified per sampling unit, it is hard to characterize biotic assemblages. Some biological clusters of taxa were identified statistically for multiple map areas, and within each area, some of these groupings were found at consistent depths and/or with predictable substrates. The maps are not fine-grained enough to capture the physical variation seen within one-minute video units. Depth zones in the biotope map are based on Dethier (1992).

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.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).-

The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations

This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site.

The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many.

CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry.

Symbolizing Spatial Features:
Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records.

Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata