This dataset contains polygons representing individual taxed parcels or individual tax-exempt parcels tracked for taxing purposes. It also contains polygons representing the locations of multiple tax properties. In the case of multiple tax properties, several parcel polygons may be stacked on top of one another. These are multiple tax parcels that cannot be delineated on a two-dimensional map, including both taxed and tax-exempt parcels. The parcels are represented with identical geometries but have different parcel IDs and associated tax attributes. The PID field contains the property ID number for each parcel.Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/County%20Tax%20Parcels.pdf

© This dataset is compiled monthly by the Hennepin County GIS Office from parcel geometry that is created and maintained by the Hennepin County Resident and Real Estate Services Survey Division and tax attributes extracted from the Hennepin County Real Estate Services property tax information system.

The County parcels dataset contains polygons representing individual taxed parcels or individual tax-exempt parcels tracked for taxing purposes. It also contains polygons representing the locations of multiple tax properties (multi-PID parcels). It is the combination of the parcel base dataset and the multiple parcel base dataset with attributes from a monthly extract of the property tax information system. The PID field contains the property ID number for each parcel.In the case of multiple tax properties, several parcel polygons may be stacked on top of one another. These are multiple tax parcels that cannot be delineated on a two-dimensional map, including both taxed and tax-exempt parcels. The parcels are represented with identical geometries but have different parcel IDs and associated tax attributes.For more information about this dataset, please view metadata.

The Hennepin GIS Hub is a public portal into the county map gallery, open data site and other useful resources.

2-foot and 10-foot elevation contours derived from the Spring 2012 Minnesota Department of Natural Resources (MN DNR) LiDAR dataset.

Geospatial data about Hennepin County, Minnesota FEMA Floodplains - 100 Year. Export to CAD, GIS, PDF, CSV and access via API.

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.

This layer contains address point features which are used for geocoding addresses and property identification numbers. Data attributes include property addresses and property identification numbers. Addresses are stored in both parsed and concatenated fields.Link to Attribute Table Information: https://gis.hennepin.us/OpenData/Metadata/Address%20Points.pdfData updated: daily

Field DefinitionsPIN13 digit tax ID for parcelANUMBERAddress numberANUMBERSUFAddress number suffixST_PRE_DIRStreet direction that comes before street nameST_NAMEStreet nameST_TYPEType of street (Ave, St, Ln etc.)ST_POST_DIRStreet direction that comes after the street nameAUNITUnit number of addressZIPCODEPostal codeFORMATTED_ADDRESSFull mailing addressOWNERNAMEName of property ownerTAXPAYER1Taxpayer nameTAXPAYER2Taxpayer name and addressTAXPAYER3Taxpayer name and address continuedTAXPAYER4Taxpayer name and address continuedASSESSMENT_YEARYear for which the property value is assessedTAX_YEARYear for which the property taxes are duePLATPlat numberPROPERTY_TYPEType of propertyMAIN_PTProperty type on primary use of parcelSUB_PT1Property type of secondary use of parcelSUB_PT2Property type of tertiary use of parcelSUB_PT3Property type of quaternary use of parcelMULTIPLE_USESIndicates whether parcel has multiple uses or notTAX_EXEMPTIndicates whether parcel is tax exemptEXEMPTCD1Exempt code for first tax exempt portionEXEMPTCD2Exempt code for second tax exempt portionEXEMPTCD3Exempt code for third tax exempt portionEXEMPTCD4Exempt code for fourth tax exempt portionPARCEL_AREA_SQFTLand area of parcel in square feetXX coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)YY coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)NEIGHBORHOODName of neighborhood the property is inCOMMUNITYName of community the property is inWARDName of ward the property is inZONINGName of zoning district the property is inLANDUSEProperty's land use designationLANDVALUEProperty's assessed land value as of January 2 of its assessment yearBUILDINGVALUEProperty's assessed building value as of January 2 of its assessment yearTOTALVALUEProperty's total assessed value as of January 2 of its assessment yearEXEMPTSTATUSIndicates the status of property (if exempt)HOMESTEADIndicates whether property is homesteadedBLDG_IDUnique identifier for buildingsBUILDINGUSEUse classification of buildingYEARBUILTYear that the building was constructedBELOWGROUNDAREATotal square footage below gradeABOVEGROUNDAREATotal square footage above gradeNUM_STORIESNumber of stories in buildingGARAGE_PRESENTIndicates whether property has a garagePRIMARYHEATINGPrimary type of heating in buildingCONSTRUCTIONTYPEStyle of constructionEXTERIORTYPEExterior finish of buildingROOFStyle of roofTOTAL_UNITSTotal number of unitsFIREPLACESNumber of fireplacesBATHROOMSNumber of bathroomsBEDROOMSNumber of bedrooms

This data was compiled by the Mapping Prejudice Project and shows the location of racial covenants recorded in Hennepin County between 1910 and 1955. Racial covenants were legal clauses embedded in property records that restricted ownership and occupancy of land parcels based on race. These covenants dramatically reshaped the demographic landscape of Hennepin County in the first half of the twentieth century. In 1948, the United States Supreme Court ruled racial covenants to be legally unenforceable in the Shelly v. Kraemer decision. Racial covenants continued to be inserted into property records, however, prompting the Minnesota state legislature to outlaw the recording of new racial covenants in 1953. The same legislative body made covenants illegal in 1962. The practice was formally ended nationally with the passage of the Fair Housing Act in 1968. If you need to perform analysis, change symbology, or filter the data, use Hennepin_County_Racial_Covenants. The data underlying this web service and documentation about the variables can be accessed from the Data Repository for the University of Minnesota.