Road Centerlines, Compiled from Opt-In Open Data Counties, Minnesota

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. <br/><br/>It includes the following 33 counties that have opted-in as of the publication date of this dataset release: Aitkin County, Anoka County, Benton County, Carver County, Chisago County, Clay County, Cook County, Dakota County, Douglas County, Fillmore County, Hennepin County, Houston County, Itasca County, Isanti County, Koochinching County, Lac qui Parle County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Otter Tail County, Pipestone County, Pope County, Ramsey County, Renville County, Saint Louis County, Scott County, Sherburne County, Stevens County, and Washington County.<br/><br/>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:<br/><br/>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 ). <br/><br/>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. <br/><br/>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<br/><br/>‘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. <br/><br/>Aggregation Process:<br/>1. Extract NG9-1-1 data from the Department of Public Safety (DPS) Enterprise database.<br/>2. Download the latest MetroGIS data from the Geospatial Commons.<br/>3. Extract, Translate, and Load (ETL) the DPS data to the GAC schema.<br/>4. Combine NG9-1-1 data with MetroGIS data.<br/>5. Filter the data for the Opt-In Open data counties<br/><br/>