This data set is created using the township lines from the Snohomish County Assessor's Public Land Survey grid for the north and south boundary. The west boundary is taken from a Washington State county boundaries data set wtih a minor modification at its northerly extent to follow tide land boundries. The eastern boundary is taken from the Snohomish County basins data set.

Snohomish County Land Cover Metrics including City Boundaries

Geospatial data about Snohomish County, WA Schools. Export to CAD, GIS, PDF, CSV and access via API.

This polygon dataset is a compilation of all the townships in Snohomish County derived from the Public Land Survey System (PLSS) grid dataset. The PLSS grid is the master coverage of the PLSS maintained by the Assessor's Office. It contains linework and attribute information for townships and ranges. It is compiled from recorded surveys and plats, coordinates and linework supplied by private surveyors, Snohomish County Public Works Survey, cities, Washington State Department Of Natural Resources (DNR) and the United States Department of the Interior - Bureau of Land Management (BLM). Standard BLM methods are used to construct the aliquot grid. In coastal areas, the aliquot grid may not apply for many of the coastal sections, it has been constructed for the purposes of land title and defining map extents for automated routines.

Elevation isolines created from LiDAR bare-earth DEM. This feature class was derived from LiDAR survey contracted by the US Geological Survey between 2013 -16. More information is available by reading this report: Western_Washington_3DEP_Technical_Data_Report.pdfScale / Resolution: 1:24000Geographic extent: NW quadrant of Snohomish CountyUpdate frequency: As neededLast updated: 5/5/2018Contact: GIS@snoco.org

This polygon dataset is a compilation of all the sections in Snohomish County derived from the Public Land Survey System (PLSS) grid dataset. The PLSS grid is the master coverage of the PLSS maintained by the Assessor's Office. It contains linework and attribute information for townships, ranges, sections, quarter sections and quarter quarter sections. It is compiled from recorded surveys and plats, coordinates and linework supplied by private surveyors, Snohomish County Public Works Survey, cities, Washington State Department Of Natural Resources (DNR) and the United States Department of the Interior - Bureau of Land Management (BLM). Standard BLM methods are used to construct the aliquot grid. In coastal areas, the aliquot grid may not apply for many of the coastal sections, it has been constructed for the purposes of land title and defining map extents for automated routines.

Geospatial data about Snohomish County, WA Voter Precincts. Export to CAD, GIS, PDF, CSV and access via API.

Geospatial data about Snohomish County, WA Police Stations. Export to CAD, GIS, PDF, CSV and access via API.

This imagery service is for viewing only, no downloading of the raster images available.

Related DataThe table stores tax account (parcel) object IDs and related document references. Relationship may be many to many.

Map of Public Utilities Department's current projects

The BSST was created for the Washington State Transportation RRAP which analyzed state highway and roads and their impacts from a Cascadia 9.0M earthquake. The RRAP report is available here: https://mil.wa.gov/asset/5d8ba2a03a1b7. The state bridge results in GIS format are available here: https://www.wsdot.wa.gov/mapsdata/geodatacatalog/default.htm . Technical and user manuals for the BSST tool are available here: https://www.osti.gov/biblio/1581518-washington-state-highway-bridge-seismic-screening-tool-bsst-technical-report In addition to the state bridges that were analyzed above, local bridges were obtained from WSDOT and analyzed in the BSST which is the data that is presented here. The data was provided from WSDOT to CISA Region 10. Much of the data for local (city/county) bridges were taken from the national bridge inventory and additional data that WSDOT had available. The local data used in the BSST is not complete and should be updated at the local level by bridge engineers and GIS specialist and analyzed in the BSST to ensure the latest bridge information is included in the tool. The data provided here is an initial analysis using data from WSDOT but it is recommend that local jurisdictions update their information and re-run the tool to ensure the most accurate data is used. The data provided here only includes bridges in western/central WA and only for a Cascadia 9.0M event. The 4,306 local highway bridges incorporated into this study from the WSDOT bridge inventory database were assessed using the BSST analysis methodology detailed previously in this report. Results consist of three types of outcomes: Bridge Damage Levels and Types, Bridge Repair Types, and Bridge Reopening Times. All output is a part of this feature class. Bridge damage types are projected on the basis of both damage level (None, Moderate, Significant), whether a bridge is a special bridge type, and also the types of damage that the bridge will experience (including both direct seismic and secondary earthquake-induced impacts); The projected repair types and reopening times necessary to bring bridges back to a minimum level of functionality that enables their use for emergency response were computed using the methodology specified in the Bridge Reopening Times section. Refer to the BSST Technical Report. The BSST was developed to assess the potential impacts of a CSZ earthquake to highway bridges in Washington State at a system-level as part of the Washington State Transportation Systems RRAP project. The results provided identify the Damage Levels, Damage Types, Repair Types and Reopening Times associated with 4,306 bridges located in Western and Central Washington that were evaluated for this RRAP project. Understanding that this analysis likely constitutes a “worst-case scenario” with respect to bridge damage, the results nonetheless project that the majority of bridges in Washington State will experience moderate to significant damage resulting from a CSZ earthquake. While the majority of bridges that experience damage could be reopened within one year of the earthquake, a substantial number of those bridges are projected to take more than a year to reopen—in many cases 2 or more years. The results also project that while many bridges may be reopened after either minor repairs/inspections or the construction of a temporary bypass road, a substantial number of more significantly damaged bridges span bodies of water and will require complete replacement prior to reopening. This suggests that significant gains in roadway corridor reopening times could be gained by focusing on retrofits or upgrades to these more vulnerable bridges that span rivers and other bodies of water. This tool is primarily intended to inform regional highway prioritization for emergency response activities; however, the BSST provides a useful evaluation methodology that could be applied to other regional emergency preparedness and infrastructure assessment studies. This could include studies of bridge infrastructure to other potential seismic events within the region, or at varying jurisdictional levels (i.e., county, local). The BSST also uses currently available seismic, seismically-induced secondary hazard and infrastructure information. As new seismic information becomes available, or as secondary-hazards (e.g., landslides, avalanches) become characterized more comprehensively, such information could be integrated into the current BSST methodology. Similarly, as seismic retrofit activities or other infrastructure improvement projects continue throughout Washington State, or as new infrastructure are built, it will be important that the infrastructure data integrated in the BSST also be updated periodically. Doing so will ensure that planners and infrastructure managers maintain the most current and complete understanding of the network-level seismic risks of a CSZ event to bridges in Washington. Please note that all results from the BSST are based on a model and information received from WSDOT. Damages from an earthquake may be different than what is provided here. Liquefaction data was used within the BSST tool. WADNR is the source for liquefaction data and is available here: https://www.dnr.wa.gov/programs-and-services/geology/geologic-hazards/geologic-hazard-maps#nehrp-site-class-and-liquefaction-susceptibilityUSGS ShakeMap was also used in the BSST tool for a M9.0 Cascadia earthquake and is available here: https://earthquake.usgs.gov/scenarios/eventpage/gllegacycasc9p0expanded_se/shakemap/pga. Data Assumptions/MethodologyData was provided by WSDOT for all local bridges. Data was transferred into BSST format. Bridges that were not included in the Cascadia 9.0M ShakeMap were removed from the tool. This mainly encompasses bridges in the far eastern side of the state. Removed all bridges that were designated as a pedestrian, trail or dam. Removed all bridges that had null or 0 structure length. Those bridges that had no main span quantity, all were changed to 1, meaning a single span bridge. For the bridges missing the federal functional class a value of 9 was assigned. For the bridges with a null in waterway adequacy these values were changed to N. For those bridges that had a null value for scour code these were change to N. Some points had low accuracy coordinates (lat/longs), so these locations were removed from the database since they could not be found. For those bridges that had a BMS elements ID related to a Pier Wall a W code was added to the Pier Type in the road bridges spreadsheet of the BSST tool. This would ensure these bridges were counted as having a pier wall. This information should be updated and verified by local jurisdictions. Snohomish County used the tool for their local bridges. A few of the bridges output in this tool was updated to reflect their results since better data was provided by the county. The tool uses AASHTO curves from various years. These curves were digitized in GIS from a pdf map. The accuracy of these maps could be up to +/- 10 miles due to digitizing the data at the state level. Most of the offset occurred in eastern WA, so impacts should be minimal.

The Public Land Survey System (PLSS) Grid - Line is linework derived from the master coverage of the PLSS maintained by the Assessor's Office. This dataset only contains linework and attribute information for townships, ranges, sections, quarter sections and quarter quarter sections and government lot lines. It is compiled from recorded surveys and plats, coordinates and linework supplied by private surveyors, Snohomish County Public Works Survey, cities, Washington State Department Of Natural Resources (DNR) and the United States Department of the Interior - Bureau of Land Management (BLM). Standard BLM methods are used to construct the aliquot grid. In coastal areas, the aliquot grid may not apply for many of the coastal sections, it has been constructed for the purposes of land title and defining map extents for automated routines.

Washington State’s Growth Management Act (GMA) (chapter 36.70A RCW) requires the development of a comprehensive plan. Comprehensive Plan {https://www.snohomishcountywa.gov/2139/Comprehensive-Plan} changes are voted on once per year by the Snohomish County Council, with recommendations given by the Planning Commission, Public comments, and the Department of Planning and Development Services (PDS).The Comprehensive Plan serves as the document that guides County decisions and services on a wide range of topics, including: land use, transportation, parks, housing, capital facilities and the natural environment. The Comprehensive Plan consists of five components:The General Policy Plan consists of goals, objectives and policies that serve as a guide to the county’s growth and development.The Future Land Use Map (PDF) expresses graphically the 20-year vision of the preferred land use pattern. It identifies the urban growth areas around cities and towns, as well as urban, rural, and resource lands. The map is implemented through numerous zoning classifications and development regulations.The Transportation Element presents a plan for transportation facilities and services to support the needs of the projected populations.The Capital Facilities Plan (PDF) contains an inventory of the county’s public facilities and utilities, establishes level of service standards necessary to support development, and prioritizes facilities needed to support the needs of the projected populations.The Park and Recreation Element presents a plan for park and recreation facilities and services to support the needs of the projected populations.Outside of the periodic update cycle, less extensive revisions are allowed through the docketing process and County-initiated amendment proposals. Information on current and past proposals, and to find out about submitting an amendment to the Comprehensive Plan can be obtained from the Docket and County-Initiated Amendments web page.

Features in this layer represent the end points of linear features such as culverts, ditches and pipes or the center points of features such as access roads, detention ponds, and vaults. They are used to help create these features during the Drainage Inventory process.

Digital Ground Model Data Sources for King County and surrounding Kitsap, Island, Pierce, and Snohomish Counties.

This map shows the locations of boil water notices and water outages in Collier County.You may search by clicking on the map or using an address on the search bar.

Map showing garbage, recycling and yard waste collection days

A spatial tiling index designed for storage of file-based image and other raster (i.e., LiDAR elevation, landcover) data sets. A regular grid with origin at 0,0 of the Washington North State Plane Coordinate System, with grid cells defined by orthogonal bounds 7500 feet long in easting and in northing. Only those cells currently involved in one of several image/raster data projects for King County and southwestern Snohomish County are labelled, though the labeling scheme can be extended. The name of the spatial index is derived from the acronym (I)n(D)e(X) (P)olygons at the (7500) foot tile level, or idxp7500. Cell label is a row-id cocantenated with a column-id generating a four-character identifier that uniquely identifies every cell. The row portion of the identifier is a two-character alpha code of the format aa, ab, ac.... ba, bb, etc. and the column portion is a two-digit integer value such as 01, 02, 03.... 11,12,13, etc. A composite cell identifier would be then, for example, aa01, aa02, .....ba11,ba12, etc. Not all image and raster data is stored at the tiling level represented by this index. Data is stored at this level if full-resolution, uncompressed data would generate larger than manageable file sizes at a larger tile size.

A spatial tiling index designed for storage of file-based image and other raster (i.e., LiDAR elevation, landcover) data sets. An irregular grid of overlapping polygons, each enclosing its respective Public Land Survey System (PLSS) township in an orthogonal polygon minimally encompassing all portions of that township, i.e., minimum bounding rectangle. The amount of overlap between adjacent tiles varies depending on the geometry of the underlying township. Currently extended to include all townships within or partially within King County as well as those townships in the southwestern portion of Snohomish County included within King County's ESA/SAO project area. The name of the spatial index is derived from the acronym (I)n(D)e(X) (P)olygons for (T)ownship-(R)ange, (M)inimum (B)ounding (R)ectangle, or idxptrmbr. Tile label is the t(township number)r(range number)as in t24r02. The meridian zone identifiers, N for townships and E for range is inferred as this index is intended as a local index for ease of use by the majority of users of GIS data. Lowercase identifiers are used for consistency between Unix and Windows OS storage. This index or tile level is the primary user-access level for most LiDAR elevation, orthoimagery and high-resolution raster landcover data. However, not all image and raster data is stored at the tiling level if a given data's resolution does not justify storing the data as multiple tiles.