County tax parcels include land record information. Data is typically refreshed on a weekly basis.Tax Parcel data is an approximation of property only, not suitable for legal, engineering, or surveying purposes.For more information, access the Metadata

Boundary of St Louis County. Maintained and updated daily with parcel fabric.Metadata

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 59 counties that have opted-in as of the publication date of this dataset: Aitkin County, Anoka County, Becker County, Benton County, Big Stone County, Carlton County, Carver County, Cass County, Chippewa County, Chisago County, Clay County, Clearwater County, Cook County, Crow Wing County, Dakota County, Douglas County, Fillmore County, Grant County, Hennepin County, Houston County, Isanti County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Lyon County, Marshall County, McLeod County, Mille Lacs County, Morrison County, Mower County, Murray County, Norman County, Olmsted County, Otter Tail County, Pennington County, Pipestone County, Polk County, Pope County, Ramsey County, Red Lake County, Renville County, Rice County, Scott County, Sherburne County, St. Louis County, Stearns County, Steele County, Stevens County, Traverse County, Wabasha County, Waseca County, Washington County, Wilkin County, Winona County, Wright County, and Yellow Medicine County.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

School District boundaries for St. Louis County.For more information, access the Metadata

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 42 suppliers (51 counties) that have opted-in to share their data openly as of the publication date of this dataset: Metropolitan Emergency Services Board (10 county), Aitkin County, Becker County, Benton County, Big Stone County, Carlton County, Cass County, Chippewa County, Clay County, Clearwater County, Cook County, Crow Wing County, Douglas County, Fillmore County, Houston County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County , Otter Tail County, Pipestone County, Polk County, Pope County, Renville County, Rock County, Saint Louis County, Stearns County, Stevens County, Wabasha County, Waseca County, Winona County, Wright County, 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 countiesMetadata PDFDownloadGeopackageDownloadData DownloadDownload

County tax parcels include land record information. Data is typically refreshed on a weekly basis.Tax Parcel data is an approximation of property only, not suitable for legal, engineering, or surveying purposes.For more information, access the Metadata

Quarter-section boundaries for St. Louis County. Edited and maintained in the parcel fabric and exported to this feature class weekly. For more information, access the Metadata

This dataset is a compilation of address point data from Minnesota suppliers that have opted-in for their address point data to be included in this dataset.

It includes the following 43 suppliers (52 counties) that have opted-in to share their data openly as of the publication date of this dataset: Metropolitan Emergency Services Board (10 county), Aitkin County, Becker County, Benton County, Big Stone County, Carlton County, Cass County, Chippewa County, Clay County, Clearwater County, Cook County, Crow Wing County, Douglas County, Fillmore County, Grant County, Houston County, Itasca County, Jackson County, Koochiching County, Lac qui Parle County, Lake County, Lake of the Woods County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County , Otter Tail County, Pipestone County, Polk County, Pope County, Renville County, Rock County, Saint Louis County, Stearns County, Stevens County, Wabasha County, Waseca County, Winona County, Wright County, Yellow Medicine County

Metropolitan Emergency Services Board counties: Anoka County, Carver County, Chisago County, Dakota County, Hennepin County, Isanti County, Ramsey County, Scott County, Sherburne County, Washington County

The two sources of address point data are the Minnesota Next Generation 9-1-1 (NG9-1-1) Program, in collaboration with local data suppliers, and the MetroGIS Metro Address Points Dataset 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 Address Point attribute schema: https://www.mngeo.state.mn.us/committee/address/address_standard.html.

The MetroGIS Metro Address Points Dataset was created by a joint collaborative project involving the technical and managerial GIS staff from the ten 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 in from the Minnesota Geospatial Commons: https://gisdata.mn.gov/dataset/us-mn-state-metrogis-loc-address-points

‘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 loc_addresses_open_metadata feature layer will contain the geometry/shape of the supplier boundaries, supplier name, supplier type, and feature count.

Aggregation Process: 1. Download address location data from the NG9-1-1 Enterprise database. 2. Download the latest data from the Geospatial Commons for MetroGIS. 3. Extract, Translate, and Load (ETL) the data to the GAC Address Point Standard schema. 4. Combine NG9-1-1 data with MetroGIS data. 5. Filter the data for the Opt-In suppliersMetadata PDFDownloadGeopackageDownloadData DownloadDownload

Depicts roadways and other addressed line types (i.e. water access shorelines, etc.) within St. Louis County. Address left/right attributes depict theoretical address ranges (low-high) along segments. Road names (spelling and abbreviations), address ranges, and community left/right attributes are intended to reflect accurate synchronization with the county's 9-1-1 Master Street Address Guide (MSAG).Metadata

Township boundaries for St. Louis County. Edited and maintained in the parcel fabric and exported to this feature class weekly. For more information, access the Metadata

Minor Civil Divisions in St. Louis County. A minor civil division (MCD) is a term used by the United States Census Bureau for primary governmental and/or administrative divisions of a county, such as a civil township, precinct, or magisterial district.Metadata

This dataset contains 4 Band red, green, blue, infrared (RGBI) digital orthophoto imagery of Cook, Lake, St. Louis and Carlton counties in northern Minnesota.

The orthophotos are 0.5 meter ground sample distance (GSD) and are in UTM Zone 15, NAD83 (meters). The tiling format of the imagery is based on a 3.75' x 3.75' quarter quadrangle with a 150 meter buffer on all four sides. This dataset includes 969 digital orthophoto quarter quadrangles (DOQQs) in GeoTiff format with an associated world file, and this metadata file. The data is available online as a web mapping service (WMS).

All imagery was collected by Keystone Aerial Surveys Inc with a Vexcel UltraCamX camera from an altitude of approximately 24,000 feet. All imagery was processed by Keystone using the camera manufacturer's software, Inpho's photogrammetry suite and Keystone-created software.

Funding for this data was provided by the Minnesota Natural Heritage Fund, the Minnesota Clean Water Legacy Act, The Environmental and Natural Resources Trust Fund, St. Louis County, the Coastal Zone Management Program, and the National Geospatial Intelligence Agency.Metadata PDFDownloadData DownloadDownloadMnGeo WMS service (aerial photography) URLView

Depicts addressed structures within St. Louis County. Address points are generally placed near the rooftop centroid or, in the case of larger buildings, near the addressed doorway/structure access. Most addressed structures in this feature class are convential buildings, but addresses are also sometimes assigned to: Recreational vehicles, construction trailers, and mobile homes. Permanent campsites or outdoor facilities, Outdoor sports areas, Trailhead parking lots, Gravel pits, and Telematics Communications towers. Limitations: Addresses within cities, Greenwood Township, and on reservations. The custodians of this feature class (St. Louis County 9-1-1 Communications) administer addressing in rural areas of St. Louis County, not within incorporated municipalities, American Indian Resrvations, or Greenwood Township. Therefore addresses depicted within cities (including Duluth), on reservations, and in Greenwood Township are based on secondhand information and are less likely to be current or accurate. Sub-Addresses: Although it is a future goal, this feature class does not yet contain accurate sub-addresses (i.e. 1234 Spruce Ave, Unit C).Metadata

This map shows the free and open data status of county public geospatial (GIS) data across Minnesota. The accompanying data set can be used to make similar maps using GIS software.

Counties shown in this dataset as having free and open public geospatial data (with or without a policy) are: Aitkin, Anoka, Becker, Beltrami, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Grant, Hennepin, Hubbard, Isanti, Itasca, Kittson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Meeker, Mille Lacs, Morrison, Mower, Norman, Olmsted, Otter Tail, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Scott, Sherburne, St. Louis, Stearns, Steele, Stevens, Traverse, Wabasha, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.

To see if a county's data is distributed via the Minnesota Geospatial Commons, check the Commons organizations page: https://gisdata.mn.gov/organization

To see if a county distributes data via its website, check the link(s) on the Minnesota County GIS Contacts webpage: https://www.mngeo.state.mn.us/county_contacts.html

The bulk of the thin sections in the database are poorly located or not located at all, as they temporally span the entire history of the Minnesota Geological Survey. However many of the thin sections constructed since the 1970's can be fairly easily located via old field maps and notebooks on file at the Minnesota Geological Survey. Due to the overwhelming number of sections they have been located on an 'as-needed' basis, meaning that as we progress through different mapping project areas, every attempt was made to properly locate where the sample for the thin section was taken. Several hundred thin sections have been located, mainly in northeastern Minnesota in Cook and Lake Counties, in central St. Louis County, and Itasca County. All thin sections that were made since the advent of GIS and GPS are already located, having been stored with the data for individual mapping projects.