U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
County assessor's online applications for searching and rviewing data about parcels and proprties.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This dataset shows the general location of shrubsteppe and eastside steppe as defined by WDFW’s Priority Habitats and Species (PHS) program. It shows where WDFW recommends counties and cities require site-specific information be gathered to inform site-scale land use decisions. It is not designed to directly inform parcel-scale land use decisions, rather it is designed to be used as a flagging tool. As such, if this dataset errs, it is more likely to over-identify shrubsteppe and eastside steppe than under-identify. It is “best available science” regarding the general location of shrubsteppe and eastside steppe in Washington.
This dataset is a compilation of road centerline data from Minnesota suppliers that have opted-in for their road centerline data to be included in this dataset.
It includes the following 43 suppliers that have opted-in to share their data openly as of the publication date of this dataset: Aitkin County, Anoka County, Benton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Cook County, Dakota County, Douglas County, Fillmore County, Hennepin County, Houston County, Isanti County, Itasca County, Koochinching County, Lac qui Parle County, Lake County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County, Otter Tail County, Pipestone County, Pope County, Polk County, Ramsey County, Renville County, Rock County, Saint Louis County, Scott County, Sherburne County, Stearns, Stevens County, Waseca County, Washington County, Wright County, and Yellow Medicine County.
The two sources of road centerline data are the Minnesota Next Generation 9-1-1 (NG9-1-1) Program, in collaboration with local data suppliers, and the MetroGIS Road Centerlines (Geospatial Advisory Council Schema) which is on the Minnesota Geospatial Commons:
The Minnesota NG9-1-1 Program enterprise database provides the data outside of the Metro Region which is provide by the suppliers. The data have been aggregated into a single dataset which implements the MN NG9-1-1 GIS Data Model (https://ng911gis-minnesota.hub.arcgis.com/documents/79beb1f9bde84e84a0fa9b74950f7589/about ).
Only data which have meet the requirements for supporting NG9-1-1 are in the statewide aggregate GIS data. MnGeo extracts the available data, applies domain translations, and transforms it to UTM Zone 15 to comply with the GAC road centerline attribute schema: https://www.mngeo.state.mn.us/committee/standards/roadcenterline/index.html.
The MetroGIS Road Centerlines data was created by a joint collaborative project involving the technical and managerial GIS staff from the the Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne, and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. The data are pulled from the Minnesota Geospatial Commons: https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-road-centerlines-gac
‘Supplier’ is a term used throughout this document. A supplier will typically be a county, but it could also be a public safety answering point (PSAP), region, or tribal nation. The supplier is the agency which provides the individual datasets for the aggregated dataset. The trans_road_centerlines_open_metadata feature layer will contain the geometry/shape of the supplier boundaries, supplier name, supplier type, and feature count.
Aggregation Process:
1. Extract NG9-1-1 data from the Department of Public Safety (DPS) Enterprise database.
2. Download the latest MetroGIS data from the Geospatial Commons.
3. Extract, Translate, and Load (ETL) the DPS data to the GAC schema.
4. Combine NG9-1-1 data with MetroGIS data.
5. Filter the data for the Opt-In Open data counties
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
Lake Stevens Sewer District map used for CityWorks intergration. This map includes parcel data and base layers for use by the Lake Stevens Sewer District. The District is located in Snohomish county, Washington. In 2005, the District entered into the Unified Sewer Agreement with the City to operate and maintain all sewer collection and treatment facilities within the entire Lake Stevens Urban Growth Area ("UGA"), both unincorporated area and the City.
The District currently operates 120 miles of collection system, 12 miles of interceptor and 29 lift stations and the treatment plant is located adjacent to 9th Street SE and Sunnyside Boulevard above the Snohomish River floodplain. The Sunnyside Treatment Plant facility provides adequate waste water treatment and disposal to the District's service area through 2028, with provisions for upgrades to serve build-out conditions.
Lidar DBO from Snohomish county for Lake Stevens, WA and surrounding area.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
County assessor's online applications for searching and rviewing data about parcels and proprties.