<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>U.S. Department of Commerce, U.S. Census Bureau, Geography Division</origin>
<pubdate>2010</pubdate>
<title>TIGER/Line Shapefile, 2010, 2010 county, Hennepin County, MN, 2010 Census Census Tract County-based</title>
<edition>2010</edition>
<geoform>vector digital data</geoform>
<onlink>http://www.census.gov/geo/www/tiger</onlink>
<ftname Sync="TRUE">PLANNING.CENSUS2010_TRACTS</ftname>
</citeinfo>
</citation>
<descript>
<abstract>The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area. </abstract>
<purpose>In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles.</purpose>
<Subject_Entity>Hennepin, MN, (27053)</Subject_Entity>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>201001</begdate>
<enddate>201007</enddate>
</rngdates>
</timeinfo>
<current>Publication Date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database. No changes or updates will be made to this version of the TIGER/Line Shapefiles. Future releases of TIGER/Line Shapefiles will reflect updates made to the Census MAF/TIGER database.</update>
</status>
<spdom>
<bounding>
<westbc>-93.767799</westbc>
<eastbc>-93.177201</eastbc>
<northbc>45.246618</northbc>
<southbc>44.785303</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">200000.000000</leftbc>
<rightbc Sync="TRUE">700000.000000</rightbc>
<bottombc Sync="TRUE">10000.000000</bottombc>
<topbc Sync="TRUE">350000.000000</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>ISO 19115 Topic Categories</themekt>
<themekey>boundaries</themekey>
</theme>
<theme>
<themekt>None</themekt>
<themekey>County or equivalent entity</themekey>
<themekey>Polygon</themekey>
<themekey>Census Tract</themekey>
<themekey>Tract</themekey>
</theme>
<place>
<placekt>INCITS.38-200x (R2004),INCITS.31-200x (R2007),INCITS.454-200x,INCITS 455-200x,INCITS 446-2008</placekt>
<placekey>United States</placekey>
<placekey>U.S.</placekey>
<placekey>County or Equivalent Entity</placekey>
<placekey>Hennepin</placekey>
<placekey>27053</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source.
The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.</useconst>
<Title_13_Restrictions>Yes, the data are free from Title 13 restrictions</Title_13_Restrictions>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch</cntorg>
</cntorgp>
<cntaddr>
<addrtype>Mailing address</addrtype>
<address>4600 Silver Hill Road, Stop 7400</address>
<city>Washington</city>
<state>DC</state>
<postal>20233-7400</postal>
<country>United States</country>
</cntaddr>
<cntvoice>301-763-1128</cntvoice>
<cntfax>301-763-4710</cntfax>
<cntemail>geo.tiger@census.gov</cntemail>
</cntinfo>
</ptcontac>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.4000</native>
<natvform Sync="FALSE">Feature Class</natvform>
</idinfo>
<Data_Set_Character_Set>8859part1</Data_Set_Character_Set>
<Data_Set_Language>eng</Data_Set_Language>
<dataqual>
<attracc>
<attraccr>Accurate against Federal Information Processing Standards (FIPS), FIPS Publication 6-4, and FIPS-55 at the 100% level for the codes and base names. The remaining attribute information has been examined but has not been fully tested for accuracy.</attraccr>
</attracc>
<logic>The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. All polygons are tested for closure.
The Census Bureau uses its internally developed geographic update system to enhance and modify spatial and attribute data in the Census MAF/TIGER database. Standard geographic codes, such as FIPS codes for states, counties, municipalities, county subdivisions, places, American Indian/Alaska Native/Native Hawaiian areas, and congressional districts are used when encoding spatial entities. The Census Bureau performed spatial data tests for logical consistency of the codes during the compilation of the original Census MAF/TIGER database files. Most of the codes for geographic entities except states, counties, urban areas, Core Based Statistical Areas (CBSAs), American Indian Areas (AIAs), and congressional districts were provided to the Census Bureau by the USGS, the agency responsible for maintaining FIPS 55. Feature attribute information has been examined but has not been fully tested for consistency.
For the TIGER/Line Shapefiles, the Point and Vector Object Count for the G-polygon SDTS Point and Vector Object Type reflects the number of records in the shapefile attribute table. For multi-polygon features, only one attribute record exists for each multi-polygon rather than one attribute record per individual G-polygon component of the multi-polygon feature. TIGER/Line Shapefile multi-polygons are an exception to the G-polygon object type classification. Therefore, when multi-polygons exist in a shapefile, the object count will be less than the actual number of G-polygons.</logic>
<complete>Data completeness of the TIGER/Line Shapefiles reflects the contents of the Census MAF/TIGER database at the time the TIGER/Line Shapefiles were created.</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Department of Commerce, U.S. Census Bureau, Geography Division</origin>
<pubdate>Unpublished material</pubdate>
<title>Census MAF/TIGER database</title>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>201001</begdate>
<enddate>201007</enddate>
</rngdates>
</timeinfo>
<srccurr>Publication Date</srccurr>
</srctime>
<srccitea>MAF/TIGER</srccitea>
<srccontr>The selected geographic and cartographic information (line segments) are derived from the U.S. Census Bureau's Master Address File Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database.</srccontr>
</srcinfo>
<procstep>
<procdesc>TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for all of the aforementioned geographic entities are then distributed among the shapefiles each containing attributes for line, polygon, or landmark geographic data. </procdesc>
<srcused>withheld</srcused>
<procdate>2010</procdate>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<procdate Sync="TRUE">20111201</procdate>
<proctime Sync="TRUE">15311300</proctime>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<indspref>Federal Information Processing Standards (FIPS), ANSI, and feature names.</indspref>
<direct>Vector</direct>
<ptvctinf>
<esriterm Name="GreenZoneBoundaries">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">FALSE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geodetic>
<horizdn>North American Datum of 1983 in the 48 contiguous states, the District of Columbia, Alaska, Hawaii, Puerto Rico, the Virgin Islands of the United States, and the Pacific Island Areas.</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137</semiaxis>
<denflat>298257</denflat>
</geodetic>
<cordsysn>
<geogcsn Sync="TRUE">GCS_User_Defined</geogcsn>
<projcsn Sync="TRUE">HENNEPIN COUNTY, MN</projcsn>
</cordsysn>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<plandu Sync="TRUE">survey feet</plandu>
<coordrep>
<absres Sync="TRUE">0.000328</absres>
<ordres Sync="TRUE">0.000328</ordres>
</coordrep>
</planci>
</planar>
</horizsys>
<vertdef>
<altsys>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
<altres Sync="TRUE">1.000000</altres>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="GreenZoneBoundaries">
<enttyp>
<enttypl>TRACT10.shp</enttypl>
<enttypd>2010 Census Census Tract County-based</enttypd>
<enttypds>U.S. Census Bureau</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">FID</attrlabl>
<attalias Sync="TRUE">FID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Id</attrlabl>
<attalias Sync="TRUE">Id</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">6</attwidth>
<atprecis Sync="TRUE">6</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch</cntorg>
</cntorgp>
<cntaddr>
<addrtype>Mailing address</addrtype>
<address>4600 Silver Hill Road, Stop 7400</address>
<city>Washington</city>
<state>DC</state>
<postal>20233-7400</postal>
<country>United States</country>
</cntaddr>
<cntvoice>301-763-1128</cntvoice>
<cntfax>301-763-4710</cntfax>
<cntemail>geo.tiger@census.gov</cntemail>
</cntinfo>
</distrib>
<distliab>No warranty, expressed or implied is made with regard to the accuracy of these data, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau in specific as to the spatial or attribute accuracy of the data. The act of distribution shall not constitute any such warranty and no responsibility is assumed by the U.S. government in the use of these files. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes do not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>TGRSHP (compressed)</formname>
<filedec>PK-ZIP, version 1.93 A or higher</filedec>
<transize Sync="TRUE">0.000</transize>
<dssize Sync="TRUE">0.000</dssize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>http://www.census.gov/geo/www/tiger</networkr>
</networka>
</computer>
</onlinopt>
<offoptn>
<offmedia>DVD-ROM (Only if offered offline)</offmedia>
<recfmt>ISO 9660</recfmt>
</offoptn>
</digtopt>
</digform>
<fees>The online copy of the TIGER/Line files may be accessed without charge.</fees>
<ordering>To obtain more information about ordering TIGER/Line shapefiles visit http://www.census.gov/geo/www/tiger </ordering>
</stdorder>
<techpreq>The TIGER/Line shapefiles contain geographic data only and do not include display mapping software or statistical data. For information on how to use the TIGER/Line shapefile data with specific software package users shall contact the company that produced the software.</techpreq>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
</distinfo>
<metainfo>
<metd>20100507</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch</cntorg>
</cntorgp>
<cntaddr>
<addrtype>Mailing address</addrtype>
<address>4600 Silver Hill Road, Stop 7400</address>
<city>Washington</city>
<state>DC</state>
<postal>20233-7400</postal>
<country>United States</country>
</cntaddr>
<cntvoice>301-763-1128</cntvoice>
<cntfax>301-763-4710</cntfax>
<cntemail>geo.tiger@census.gov</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<Metadata_Character_Set>8859part1</Metadata_Character_Set>
<Metadata_File_Identifier>tl_2010_27053_tract10.shp.xml</Metadata_File_Identifier>
<Metadata_Language>eng</Metadata_Language>
<langmeta Sync="TRUE">en</langmeta>
<mettc Sync="TRUE">local time</mettc>
</metainfo>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 10.2.2.3574</envirDesc>
<dataLang>
<languageCode Sync="TRUE" country="US" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">GreenZoneBoundaries</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">200000</westBL>
<eastBL Sync="TRUE">700000</eastBL>
<northBL Sync="TRUE">350000</northBL>
<southBL Sync="TRUE">10000</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-94.552622</westBL>
<eastBL Sync="TRUE">-92.603778</eastBL>
<northBL Sync="TRUE">45.476734</northBL>
<southBL Sync="TRUE">44.538427</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<descKeys>
<thesaName uuidref="723f6998-058e-11dc-8314-0800200c9a66"/>
<keyword Sync="TRUE">002</keyword>
</descKeys>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
<mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<linkage Sync="FALSE">withheld</linkage>
</onLineSrc>
<transSize Sync="TRUE">0.000</transSize>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">Shapefile</formatName>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="103734">HENNEPIN COUNTY, MN</identCode>
<idCodeSpace Sync="TRUE">ESRI</idCodeSpace>
<idVersion Sync="TRUE">10.2.1</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="GreenZoneBoundaries">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<Esri>
<SyncDate>20170214</SyncDate>
<SyncTime>09432200</SyncTime>
<ModDate>20170214</ModDate>
<ModTime>09432200</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">GreenZoneBoundaries</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<itemSize Sync="TRUE">0.000</itemSize>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_NAD_1983_HARN_Adj_MN_Hennepin</geogcsn>
<projcsn Sync="TRUE">NAD_1983_HARN_Adj_MN_Hennepin_Feet</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.1'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_HARN_Adj_MN_Hennepin_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_NAD_1983_HARN_Adj_MN_Hennepin&amp;quot;,DATUM[&amp;quot;D_NAD_1983_HARN_Adj_MN_Hennepin&amp;quot;,SPHEROID[&amp;quot;S_GRS_1980_Adj_MN_Hennepin&amp;quot;,6378418.941,298.2572221008827]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,500000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,100000.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-93.38333333333334],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,44.88333333333333],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,45.13333333333333],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,44.79111111111111],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;ESRI&amp;quot;,103734]]&lt;/WKT&gt;&lt;XOrigin&gt;-119096800&lt;/XOrigin&gt;&lt;YOrigin&gt;-98462100&lt;/YOrigin&gt;&lt;XYScale&gt;37656522.811400428&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.0032808333333333331&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;103734&lt;/WKID&gt;&lt;LatestWKID&gt;103734&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
</coordRef>
</DataProperties>
<CreaDate>20170214</CreaDate>
<CreaTime>09412700</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<mdDateSt Sync="TRUE">20170214</mdDateSt>
</metadata>
