<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20260106</CreaDate>
<CreaTime>11511800</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">ParcelsHennepin</itemName>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">NAD_1983_UTM_Zone_15N</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.7'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_UTM_Zone_15N&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,500000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-93.0],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9996],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,26915]]&lt;/WKT&gt;&lt;XOrigin&gt;-5120900&lt;/XOrigin&gt;&lt;YOrigin&gt;-9998100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;26915&lt;/WKID&gt;&lt;LatestWKID&gt;26915&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20191031</SyncDate>
<SyncTime>19254400</SyncTime>
<ModDate>20191031</ModDate>
<ModTime>19254400</ModTime>
</Esri>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Tanya Mayer</rpIndName>
<rpOrgName>Metropolitan Council</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>651.602.1604</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>390 Robert Street North</delPoint>
<city>St. Paul</city>
<adminArea>MN</adminArea>
<postCode>55101-1805</postCode>
<eMailAdd>tanya.mayer@metc.state.mn.us</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt>20200121</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Tanya Mayer</rpIndName>
<rpOrgName>Metropolitan Council</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>651.602.1604</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>390 Robert Street North</delPoint>
<city>St. Paul</city>
<adminArea>MN</adminArea>
<postCode>55101-1805</postCode>
<eMailAdd>tanya.mayer@metc.state.mn.us</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<ordInstr>See Online Linkage Below</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>Shapefile</formatName>
<formatVer>ArcGIS: 9x</formatVer>
</distorFormat>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://gisdata.mn.gov/dataset/us-mn-state-metrogis-plan-regional-parcels</linkage>
</onLineSrc>
</distTranOps>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Metro Regional Parcel Dataset - (Updated Quarterly)</resTitle>
<date>
<pubDate>2020-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Metro Counties</rpOrgName>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
</idCitation>
<idAbs>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. &lt;b&gt;NOTICE&lt;/b&gt;: 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 &lt;a href="Metro_Regional_Parcel_Attributes.pdf" target=_blank&gt;Metro Regional Parcel Attributes&lt;/a&gt; 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 = http://www.hennepin.us/gisopendata
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</idAbs>
<idPurp>To view, analyze and display parcel data anywhere in the seven county metro area.</idPurp>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>See County website links in the Abstract for individual county contact information, or, Tanya Mayer</rpIndName>
<rpOrgName>Metropolitan Council</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>651.602.1604</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>390 Robert Street North</delPoint>
<city>St. Paul</city>
<adminArea>MN</adminArea>
<postCode>55101-1805</postCode>
<eMailAdd>tanya.mayer@metc.state.mn.us</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="006"/>
</maintFreq>
</resMaint>
<graphOver>
<bgFileName>withheld</bgFileName>
<bgFileDesc>Sample map showing the MetroGIS Regional Parcel Data.</bgFileDesc>
</graphOver>
<placeKeys>
<keyword>Twin Cities, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County</keyword>
</placeKeys>
<themeKeys>
<keyword>parcels, regional parcel data, cadastre, land ownership</keyword>
</themeKeys>
<searchKeys>
<keyword>Twin Cities, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County</keyword>
<keyword>parcels, regional parcel data, cadastre, land ownership</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>None. This dataset is public domain under the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13).</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington and the Metropolitan Council for their own internal business purposes. These organizations do not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, it is recommended that the GIS Data include a copy of this disclaimer and this metadata.</useLimit>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<othConsts>None. This dataset is public domain under the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). If the dataset is not available from the Online Linkage in Section 6, please contact the Distribution Contact Person.</othConsts>
</LegConsts>
</resConst>
<aggrInfo>
<aggrDSName>
<resTitle>Regional Parcel Dataset - Seven County Twin Cities Metropolitan Area
2002 - current</resTitle>
</aggrDSName>
<assocType>
<AscTypeCd value="001"/>
</assocType>
</aggrInfo>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<envirDesc>See Metadata for individual counties.</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>-94.012</westBL>
<eastBL>-92.732</eastBL>
<northBL>45.415</northBL>
<southBL>44.471</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>All county datasets are current to within 30 days of the Time Period of Content date unless otherwise noted.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2020-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<suppInfo>Twin Cities 7 County Metropolitan Area. This includes the counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington in Minnesota.</suppInfo>
</dataIdInfo>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>No attempt was made to edgematch or rubbersheet the seven counties, thus overlaps and gaps will exist between counties. Not all tax parcels are represented by a unique polygon. For example, a county might have one polygon representing a condominium complex. Some counties have provided an additional parcel points shape file that will include points to represent such tax parcels (e.g. a point for each individual condominium).</measDesc>
</report>
<report type="DQCompOm">
<measDesc>For parcel attributes, see Section 5 of this metadata.
Any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person listed in the individual county metadata. Inclusion of Condominiums in Polygon Dataset:
Some counties include condominium information within their polygon dataset and others do not. Some information on this topic is shown below. Contact each county for further information.
Dakota
One polygon is included in the polygon dataset for the geography of the larger common area of a condominium building or complex. Individual condominium units are only represented in the points dataset. Ramsey (July 2018) Polygons are included for all condominiums. The only 1 to many polygon/points are for manufactured homes. </measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>Each county provided parcel polygons and points with attributes in shape file format with UTM coordinates, to the Metropolitan Council. The Metropolitan Council checked each shape file to insure it had the specified field names, types, lengths and order. No attempt was made to edgematch or rubber sheet the parcel geography between counties.</stepDesc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<Indref>None</Indref>
</spatRepInfo>
<mdExtInfo>
<extOnRes>
<linkage>https://www.mngeo.state.mn.us/committee/standards/mgmg/metadata.htm</linkage>
</extOnRes>
</mdExtInfo>
<eainfo>
<overview>
<eaover>A standard set of attribute fields is included for each county. The attributes
are identical for the point and polygon datasets. Not all attributes fields are populated by each county.
The standard set of attributes changed to the MN Parcel Data Transfer Standard on January 1, 2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html A list of the attribute names is shown below. Detailed information about the attributes can be found in the &lt;a href="Metro_Regional_Parcel_Attributes.pdf" target=_blank&gt;Metro Regional Parcel Attributes&lt;/a&gt; document.
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)) </eaover>
<eadetcit>A detailed description of the attributes available in this dataset can be found in the &lt;a href="Metro_Regional_Parcel_Attributes.pdf" target=_blank&gt;Metro Regional Parcel Attributes&lt;/a&gt; document.</eadetcit>
</overview>
</eainfo>
</metadata>
