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.

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.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

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.

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

The Minneapolis Assessor's Office tracks and records every real property transaction in the city. This is public information. Attributes included in the dataset: CRV - Certificate of Real Estate Value number. A unique identifier given to every certificate of real estate value. PIN - the 13-digit tax ID that uniquely identifies a taxable parcel. Sale_Date - the date of the sale. InRTOStudy - yes or no depending on whether the sale was used for the Minnesota Department of Revenue Sales Ratio Study. Only sales that are considered fair market value sales are included. Neighborhood - the name of the neighborhood the property is in. Ward - the number of the ward that the property is in. Address - the street address of the property. Grantee - the buyer name. Grantor - the seller name. Adjusted_Sale_Price - the sale price after accounting for seller-paid adjustments. Gross_Sale_Price - the unadjusted sale price. Downpayment - the dollar value of the initial downpayment X - the X coordinate of the parcel centroid of the sold property Y - the Y coordinate of the parcel centroid of the sold property

The coordinates are expressed in the NAD 83 Hennepin County HARN coordinate system (WKID: 103734)

We collected open and publicly available data resources from the web from administrative, county- or state-level institutions in the United States and integrated and harmonized cadastral parcel data, tax assessment data, and building footprint data for 33 counties, where building footprint data and building construction year information was available. The result of this effort is a unique dataset which we call the Multi-Temporal Building Footprint Dataset for 33 U.S. Counties (MTBF-33). MTBF-33 contains over 6.2 million building footprints including their construction year, and is available in ESRI Shapefile format (Spatial reference system: SR-ORG:7480), organized per county. We compared the MTBF-33 dataset quantitatively to other building footprint data sources, achieving an overall F-1 score of 0.93. Moreover, we compared the MTBF-33 dataset qualitatively to urban extents from historical maps and find high levels of agreement. The MTBF-33 dataset can be used to support historical building stock assessments, to derive retrospective depictions of built-up areas from 1900 to 2015, at fine spatial and temporal grain and can be used for data validation purposes, or to train statistical learning approaches aiming to extract historical information on human settlements from remote sensing data, historical maps, or similar data sources.

Data sources: Boulder County (Colorado) Open Data Catalog / Florida Geographic Data Library / Hillsborough County, Florida / City of Tampa / Manatee County, Florida / Sarasota County, Florida / City of Evansville, Vanderburgh County, Indiana / Baltimore County Government, Maryland / Bureau of Geographic Information (MassGIS), Commonwealth of Massachusetts, Executive Office of Technology and Security Services / City of Boston / MetroGIS, Minnesota Geospatial Commons, Minnesota Geospatial Information Office, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, and Washington County, Minnesota / Monmouth County, New Jersey / City of New York / Mecklenburg County, North Carolina. Data scraping was performed in 2016.