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 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.
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.
A County Geologic Atlas (CGA) project is a study of a county's geology, and its mineral and ground-water resources. The information collected during the project is used to develop maps, data-base files, and reports. This same information is also produced as digital files. The map information is formatted as geographic information system (GIS) files with associated data bases. The maps and reports are also reproduced as portable document files (PDFs) that can be opened on virtually any computer using the free Acrobat Reader from Adobe.com. All of the digital files for the CGA's can be downloaded from the University of Minnesota Digital Conservancy. The majority of the files can also be viewed and queried through the use of this Story Map.Atlas information is commonly used in planning and environmental protection programs, as an educational resource, and by industries involved in water and mineral resources. It represents a comprehensive, detailed compilation of geologic data and interpretations within a county. The distribution and character of geologic materials determine how and where water enters the earth, and where it is stored in aquifers that can supply our needs. Geologic maps are a key element in delineating those flow paths and in relating land use to water quality. The atlas also provides a framework and terminology to support more detailed, site-specific studies. The records of water wells drilled in the area are an important source of data for constructing the maps and for understanding the distribution and use of ground water in the county. A data base of the information from those wells is one of the atlas products, and it can be queried with the GIS files to yield valuable insights for managing the ground-water resource.The atlas is also useful to non-professionals who simply wish to learn more about the geology of the county. It is a one-stop, comprehensive collection of information in a variety of forms and styles that should be useful to anyone with an interest in earth science or the county.The geologic data and maps are produced and distributed by the Minnesota Geological Survey (MGS) as Part A of an Atlas. The Minnesota Department of Natural Resources follows with an investigation of the quantity, quality, and pollution sensitivity of ground water. Their products are distributed as Part B of the atlas, at a later date. If necessary, a report with additional information that was not possible to include on the limited space of the printed maps is produced by MGS as Part C of, or included as a supplement to, an atlas. The Atlas CD or DVD, which is available online at the Digital Conservancy, includes all the atlas products developed by the Minnesota Geological Survey.
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, Stearns, Steele, Stevens, St. Louis, Traverse, 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
This map portrays our current geologic understanding of the temporal and geographic distribution of units within major Precambrian terranes and of the Phanerozoic strata. The state wide data is mapped at a scale of 1:500,000 and the county bedrock datasets (Becker, Brown, Meeker, Isanti, Cass) are mapped at a 1:100,000 scale. A Story Map displaying this data can be found at Minnesota's Bedrock Geology story map.The western part of the mapped Precambrian terrane in the state wide dataset is inferred largely from geophysical maps, anchored locally by drilling. In many places, contacts are drawn between units of the same or similar apparent rock type (and same unit label); these are recognized as geometrically distinct, though geophysically or lithologically similar. Digital files for the state wide bedrock (http://hdl.handle.net/11299/101466) corresponding to this map allow removal of Cretaceous, Paleozoic, and some parts of Mesoproterozoic strata to reveal an interpretation of the underlying Precambrian bedrock.
For additional state wide data see: (http://hdl.handle.net/11299/98043) which contains files associated with Bedrock Topography, Depth to Bedrock, and locations of Outcrop and Geochronologic analyses. Individual county bedrock can be found and downloaded at the University of Minnesota's Digital Conservancy.
This map portrays our current geologic understanding of the temporal and geographic distribution of units within major Precambrian terranes and of the Phanerozoic strata. The state wide data is mapped at a scale of 1:500,000 and the county bedrock datasets (Becker, Brown, Meeker, Isanti, Cass) are mapped at a 1:100,000 scale. A Story Map displaying this data can be found at Minnesota's Bedrock Geology story map.The western part of the mapped Precambrian terrane in the state wide dataset is inferred largely from geophysical maps, anchored locally by drilling. In many places, contacts are drawn between units of the same or similar apparent rock type (and same unit label); these are recognized as geometrically distinct, though geophysically or lithologically similar. Digital files for the state wide bedrock (http://hdl.handle.net/11299/101466) corresponding to this map allow removal of Cretaceous, Paleozoic, and some parts of Mesoproterozoic strata to reveal an interpretation of the underlying Precambrian bedrock.
For additional state wide data see: (http://hdl.handle.net/11299/98043) which contains files associated with Bedrock Topography, Depth to Bedrock, and locations of Outcrop and Geochronologic analyses. Individual county bedrock can be found and downloaded at the University of Minnesota's Digital Conservancy.
This map portrays our current geologic understanding of the temporal and geographic distribution of units within major Precambrian terranes and of the Phanerozoic strata. The state wide data is mapped at a scale of 1:500,000 and the county bedrock datasets (Becker, Brown, Meeker, Isanti, Cass) are mapped at a 1:100,000 scale. A Story Map displaying this data can be found at Minnesota's Bedrock Geology story map.The western part of the mapped Precambrian terrane in the state wide dataset is inferred largely from geophysical maps, anchored locally by drilling. In many places, contacts are drawn between units of the same or similar apparent rock type (and same unit label); these are recognized as geometrically distinct, though geophysically or lithologically similar. Digital files for the state wide bedrock (http://hdl.handle.net/11299/101466) corresponding to this map allow removal of Cretaceous, Paleozoic, and some parts of Mesoproterozoic strata to reveal an interpretation of the underlying Precambrian bedrock.
For additional state wide data see: (http://hdl.handle.net/11299/98043) which contains files associated with Bedrock Topography, Depth to Bedrock, and locations of Outcrop and Geochronologic analyses. Individual county bedrock can be found and downloaded at the University of Minnesota's Digital Conservancy.
This dataset contains lidar-derived elevation products for the Minnesota portion of the Red River of the North Basin. The Minnesota Department of Natural Resources (DNR) processed the data to make it consistent with other lidar data available in Minnesota, including converting it to UTM Zone 15 coordinates and tiling to 3.25 square mile blocks based on 1/16 of a standard USGS 1:24,000 quadrangle.
Data covers the following Minnesota counties: Becker, Beltrami, Big Stone, Clay, Clearwater, Grant, Kittson, Koochiching (northern portion), Lake of the Woods, Mahnomen, Marshall, Norman, Otter Tail, Pennington, Polk, Red Lake, Roseau, Stevens, Traverse, Wilkin. Products included are: One- and three-meter DEMs, one- and three-meter hillshades, and two-foot contours, plus a tile index map for each county. Since breaklines were not available for all of the Minnesota portion of the basin, the data has not been hydro-flattened.
The original data was provided by the International Water Institute (IWI) and the United States Geological Survey. IWI's Red River Basin Mapping Initiative acquired a highly accurate digital elevation model (DEM) for the Red River of the North Basin south of the U.S./Canada border in UTM Zone 14 coordinates.
This metadata record was created at the Minnesota Geospatial Information Office by combining information from the IWI and DNR.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
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 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.
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.