Parcels, Compiled from Opt-In Open Data Counties, Minnesota

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.<br/><br/>It includes the following 49 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Big Stone, Benton, Carlton, Carver, Cass, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Isanti, Itasca, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright.<br/><br/>If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (, 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.<br/><br/>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:<br/><br/>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.<br/><br/>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.<br/><br/><b>DOWNLOAD NOTES:</b> 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.<br/>

Additional Info

Field Value
dsAccessConst None
dsCurrentRef The authoritative export date for a given record is in the exp_date field of the main table, although not all counties provide this data and, if this is the case, MnGeo does not populate it.

If the exp_date field is not populated, the acquisition date from the metadata is a next best substitute. In very limited cases where the source geometries caused issues in processing, it is possible that the exp_date reflects the date MnGeo repaired the geometry issues.
dsModifiedDate 2024-02-03 00:20:58
dsOriginator Minnesota Geospatial Information Office (MnGeo)
dsPeriodOfContent 2/2/2024
dsPurpose Parcel data has been identified as a foundational data layer for Minnesota and provides benefits for many operational uses. This dataset was developed to enable geospatial professionals to perform statewide geospatial analysis, research, and mapping across the state. The dataset provides parcel data in a common coordinate system and with a common attribute scheme (the GAC parcel standard). The dataset is updated quarterly.
gdrsDsGuid {2825f664-8ea1-400d-b878-d4ffa0f869f0}
spatial {"type":"Polygon","coordinates":[[[-97.23, 43.5],[-97.23, 49.37], [-89.53, 49.37], [-89.53, 43.5], [-97.23, 43.5]]]}

Dataset extent

Tiles © Esri — Esri, DeLorme, NAVTEQ, TomTom, Intermap, iPC, USGS, FAO, NPS, NRCAN, GeoBase, Kadaster NL, Ordnance Survey, Esri Japan, METI, Esri China (Hong Kong), and the GIS User Community