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

Generally the smallest level of geography established for purposes of conducting elections along with polling places.

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.

Mobile ready land records, maps and data integrated with tax, CAMA and permitting information.

Polygon and polyline features representing waterbodies and waterlines.

The published representation of real property areas, combined with assessing and tax information from CAMA and Tax systems, and organized for consumption in desktop and web applications. Last updated 4/4/24.

This dataset includes the main MNDNR Scientific and Natural Areas (SNA) feature class, along with ancillary feature classes such as annotation and parking lots. These feature classes support MNNR's SNA Work Planning application.

scientific_and_natural_area_boundaries: A polygon feature class delineated on and digitized from 1:24,000 U.S.G.S. quad maps of Minnesota Scientific and Natural Areas (SNAs).

Scientific and natural areas are established to protect and perpetuate in an undisturbed natural state those lands and waters embracing natural features of exceptional scientific and educational value. The SNA Program's goal is to ensure that no single rare feature is lost from any region of the state. This requires protection and management of each feature in sufficient quantity and distribution across the landscape. The Programs' Long Range Plan is to protect at least five locations of plant communities known to occur in each landscape region, and three locations per region of each rare species, plant or animal, and geologic feature. It is estimated that 500 natural areas are needed throughout the state to adequately protect significant features. Because over 40 percent of these rare features occur in prairies, 200 SNAs would be in the prairie area of the state. Of the remainder, approximately 135 are estimated to be needed in the deciduous and 165 in coniferous forest landscape communities in the next 100 years. Protection of multiple sites in each landscape region is a vital means of capturing the genetic diversity and preventing the loss of important species, communities, and features. This strategy observes the wisdom of not putting all our eggs in one basket.

In addition to SNA, Itasca and Crow Wing Counties have established county natural areas. Itasca County's natural areas were established in 1966. Sites are set aside as SNAs because of their natural attributes and rare resources, which warrant protection for their inherent values and as places for scientific and educational use. Protection guards against developments such as trails, campgrounds, picnic sites, logging, mineral exploration and development, cultivation, and other uses of land, public or private, that interfere with the preservation of its natural features

Polygons that represent the extent of soil classifications or types.

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network.

District boundaries for wild, scenic, and recreational rivers designated under the Minnesota State Wild and Scenic Rivers Act. Includes portions of the Minnesota River, Mississippi River, Rum River, Kettle River, North Fork of the Crow River and the Cannon River.