Parcels, Compiled from Opt-In Open Data Counties, Minnesota
Go to Section:- Overview
- Data Quality
- Data Organization
- Coordinate System
- Attributes
- Distribution - Get Data
- Metadata Reference
Section 1: Overview
Originator:Minnesota Geospatial Information Office (MnGeo)
Title:
Parcels, Compiled from Opt-In Open Data Counties, Minnesota
Abstract:
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.
Purpose:
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.
Time Period of Content Date:
04/30/2026
Currentness Reference:
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.
Progress:
Complete
Maintenance and Update Frequency:
Quarterly
Spatial Extent of Data:
Minnesota
Bounding Coordinates:
-97.23
-89.53
49.37
43.5
Place Keywords:
Minnesota, MN, 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, Yellow Medicine County
Theme Keywords:
planningCadastre, parcels, tax parcels, property, land ownership, land records
Theme Keyword Thesaurus:
ISO 19115 Topic Category
Access Constraints:
None
Use Constraints:
None
Contact Person Information:
Norman Anderson,
GIS Technical Lead ITS4
Minnesota Geospatial Information Office (MnGeo)
600 Robert St N
St. Paul,
MN
55146
Phone: 651-201-2483
Email: gisinfo.mngeo@state.mn.us
Section 2: Data Quality
Attribute Accuracy:
Unknown and varies by county.
MnGeo assembles this dataset from individual county parcel datasets. This dataset uses the GAC parcel data standard. If a county's parcel data is not shared with MnGeo already in the standard, then MnGeo maps the attributes provided to the standard.
The dataset 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 include attributes that are not mapped to the GAC standard. Additionally, some county attribute fields are 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 requests 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.
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.
Additional Notes:
1- Data provided by counties are often limited to a subset of fields and may not be the same fields across all counties. The fields provided by a given county may change by quarter.
2- The USECLASS and XUSECLASS fields, while typically consistent within a county, are not standardized between counties.
3- The OWN_ADDR_# and TAX_ADDR_# fields are sometimes populated in ways not consistent with the standard. An address number/street address may not be in Line 1, and city/state/zip cannot be relied on to be in Line 3.
4- Some unusual addresses cause issues for the address parser when parsing is needed for aggregation and may be missing some or all of the address data or have address data in incorrect fields.
5- Objectid field is not stable quarter-to-quarter
Logical Consistency:
This dataset does not strictly conform to the GAC standard for parcel data. Certain fields mandated by the standard (or required under certain conditions) may not be present in the source data and may not be safely inferred through the compilation processing. Specifically, conformance in CTU_NAME, CTU_ID_TXT, EXP_DATE, NSTANDARD, and ACRES_POLY are known to be deficient.
Parcels have geometries validated with "Repair Geometry" functionality. All geometries are forced to 2D. No edge matching, rubber-sheeting or duplicate detection was performed on this dataset.
One of the data quality checks is for small (under 0.1 square meter) parcels. Hennepin County has >3000 such parcels of about 3300 statewide. These are real MnDOT parcels, at least in Hennepin County.
Users should consult county websites for original county data if there is concern over the degree or accuracy of processing.
Both the underlying data quality and the processing program are under active development. If errors are noticed, please contact us so we can improve our data processing.
Completeness:
All parcels from counties are included except those with invalid geometries.
Contents of attribute columns are inconsistent and depend on the data provided by county sources. Therefore, the dataset is not strictly compliant with the current (1.1.2, 2019-11-20) parcel data standard. Where counties do not provide mandatory fields and MnGeo cannot infer their contents with high confidence, those fields are left empty. For instance, compliance with the non-standard parcel codes and Parcel ID numbers varies. Similarly, few counties provide the export date and edit date for each row.
Since counties may provide different parcel data attributes to MnGeo each quarter, attribute fields that are mapped in the current compilation may not be mapped in the next iteration.
Horizontal Positional Accuracy:
Unknown and varies by county.
Vertical Positional Accuracy:
Not applicable.
Lineage:
DATA SOURCES
Source parcel data is provided by counties and is included in this dataset if the county opted-in for their data to be included.
Some datasets are downloaded from publicly available sources such as the Minnesota Geospatial Commons or county open data sites and the remaining data is obtained through manual methods by county staff sharing data directly with MnGeo staff.
DATA PROCESSING
The data compilation process is performed using Python code developed and maintained by MnGeo staff, with initial code development from the Minnesota Department of Natural Resources and others. The code contains methods for compiling data, along with attribute field maps that associate county source file attribute fields to attribute fields in the destination standardized layer.
If a county requests 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.
The code applies significant amounts of processing. Both the underlying data quality and the processing program are under active development. If errors are noticed in the dataset, please contact us so we can improve our data processing.
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.
Users should consult county websites for original county data for the most up-to-date and accurate parcel data.
Section 3: Spatial Data Organization (not used in this metadata)
Section 4: Coordinate System
Horizontal Coordinate Scheme:
Universal Transverse Mercator
UTM Zone Number:
15
Horizontal Datum:
NAD83
Horizontal Units:
meters
Vertical Datum:
Vertical Units:
Depth Datum:
Depth Units:
Section 5: Attributes
Overview:
Overview
A standard set of attribute fields is included for each county. Not all attribute fields are populated by each county. Information about the attributes can be found in the Minnesota Geospatial Advisory Council's (GAC) parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html
Identification Elements
COUNTY_PIN: County PIN (Text 22)
STATE_PIN: State PIN (Text 28)
Address Elements
ANUMBERPRE: Address Number Prefix (Text 15)
ANUMBER: Address Number (Long Integer 10)
ANUMBERSUF: Address Number Suffix (Text 15)
ST_PRE_MOD: Street Name Pre Modifier (Text 15)
ST_PRE_DIR: Street Name Pre Directional (Text 9)
ST_PRE_TYP: Street Name Pre Type (Text 35)
ST_PRE_SEP: Street Name Pre Separator (Text 20)
ST_NAME: Street Name (Text 60)
ST_POS_TYP: Street Name Post Type (Text 15)
ST_POS_DIR: Street Name Post Directional (Text 9)
ST_POST_MOD: Street Name Post Modifier (Text 15)
SUB_TYPE1: Subaddress Type 1 (Text 12)
SUB_ID1: Subaddress Identifier 1 (Text 30)
SUB_TYPE2: Subaddress Type 2 (Text 12)
SUB_ID2: Subaddress Identifier 2 (Text 30)
ZIP: ZIP Code (Text 5)
ZIP4: ZIP Plus 4 (Text 4)
Area Elements
CTU_NAME: CTU Name (Text 100)
CTU_ID_TXT: CTU Code (Text 8)
POSTCOMM: Postal Community Name (Text 40)
CO_CODE: County Code (Text 5)
CO_NAME: County Name (Text 40)
STATE_CODE: State Code (Text 2)
Tax and Survey Elements
LOT: Lot (Text 30)
BLOCK: Block (Text 30)
PLAT_NAME: Plat Name (Text 150)
OWNER_NAME: Owner Name (Text 100)
OWNER_MORE: Owner More Information (Text 100)
OWN_ADD_L1: Owner Address Line 1 (Text 100)
OWN_ADD_L2: Owner Address Line 2 (Text 100)
OWN_ADD_L3: Owner Address Line 3 (Text 100)
OWN_ADD_L4: Owner Address Line 4 (Text 100)
TAX_NAME: Tax Name (Text 100)
TAX_ADD_L1: Tax Payer Address Line 1 (Text 100)
TAX_ADD_L2: Tax Payer Address Line 2 (Text 100)
TAX_ADD_L3: Tax Payer Address Line 3 (Text 100)
TAX_ADD_L4: Tax Payer Address Line 4 (Text 100)
LANDMARK: Landmark (Text 150)
HOMESTEAD: Homestead Exemption (Text 10)
ACRES_POLY: Acres (Polygon) (Double 11 (2 decimal places))
ACRES_DEED: Acres (Deed) (Double 11 (2 decimal places))
EMV_LAND: Estimated Value of Land (Integer Long)
EMV_BLDG: Estimated Value of Building (Integer Long)
EMV_TOTAL: Estimated Value Total (Integer Long)
TAX_YEAR: Tax Year (Integer Short)
MKT_YEAR: Market Year (Integer Short)
TAX_CAPAC: Tax Capacity (Integer Long)
TOTAL_TAX: Total Tax (Integer Long)
SPEC_ASSES: Special Assessment (Integer Long)
USECLASS1: Use Classification 1 (Text 100)
USECLASS2: Use Classification 2 (Text 100)
USECLASS3: Use Classification 3 (Text 100)
USECLASS4: Use Classification 4 (Text 100)
MULTI_USES: Multiple Uses (Text 10)
TAX_EXEMPT: Tax Exempt (Text 3)
XUSECLASS1: Exempt Use Classification 1 (Text 100)
XUSECLASS2: Exempt Use Classification 2 (Text 100)
XUSECLASS3: Exempt Use Classification 3 (Text 100)
XUSECLASS4: Exempt Use Classification 4 (Text 100)
DWELL_TYPE: Dwelling Type (Text 30)
HOME_STYLE: Home Style (Text 30)
FIN_SQ_FT: Finished Square Footage (Integer Long)
GARAGE: Presence of Garage (Text 10)
GARAGESQFT: Square Footage of Garage (Integer Long)
BASEMENT: Presence of Basement (Text 10)
HEATING: Type of Heating (Text 30)
COOLING: Type of Cooling (Text 30)
YEAR_BUILT: Year Built (Integer Short)
NUM_UNITS: Number of Residential Units (Integer Long)
SALE_DATE: Date of Last Sale (Date 8)
SALE_VALUE: Value at Last Sale (Integer Long)
GREEN_ACRE: Green Acres Program (Text 10)
OPEN_SPACE: Open Space (Text 10)
AG_PRESERV: Agricultural Preserve (Text 10)
AGPRE_ENRD: Agricultural Preserve Enroll Date (Date 8)
AGPRE_EXPD: Agricultural Preserve Expiration Date (Date 8)
ABB_LEGAL: Abbreviated Legal Description (Integer Short)
EDIT_DATE: Edit Date (Date 8)
EXP_DATE: Export Date (Date 8)
POLYPTREL: Polygon to Point Relationship (Integer Short)
N_STANDARD: Non-Standard Parcel Status (Integer Short)
Ownership and Administration Elements
OWNERSHIP: Ownership Category (Text 30)
SCHOOL_DST: School District (Text 10)
WSHD_DST: Watershed District (Text 50)
Public Land Survey System (PLSS) Elements
SECTION: Section (Integer Short (3))
TOWNSHIP: Township (Integer Short (3))
RANGE: Range (Integer Short (3))
RANGE_DIR: Range Direction (Integer Short (1))
PRIN_MER: Principal Meridian (Integer Short (1))
Detailed Citation:
Table Detail:
Section 6: Distribution
Publisher:
Minnesota Geospatial Information Office (MnGeo)
Publication Date:
04/30/2026
Contact Person Information:
Norman Anderson,
GIS Technical Lead ITS4
Minnesota Geospatial Information Office (MnGeo)
600 Robert St N
St. Paul,
MN
55146
Phone: 651-201-2483
Email: gisinfo.mngeo@state.mn.us
Distributor's Data Set Identifier:
plan_parcels_open
Ordering Instructions:
This data set is distributed via the Minnesota Geospatial Commons. Online Linkage: I AGREE
to the notice in "Distribution Liability" above. Clicking to agree will either begin the download process, link to a service, or provide more instructions. See "Ordering Instructions" above for details.
Section 7: Metadata Reference
Metadata Date:
04/30/2026
Contact Person Information:
Norman Anderson,
GIS Technical Lead ITS4
Minnesota Geospatial Information Office (MnGeo)
600 Robert St N
St. Paul,
MN
55146
Phone: 651-201-2483
Email: gisinfo.mngeo@state.mn.us
Metadata Standard Name:
Minnesota Geographic Metadata Guidelines
Metadata Standard Version:
1.2