<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Minnesota Population Center</origin>
<pubdate>20070105</pubdate>
<title>2000 Metropolitan Statistical Areas/Consolidated Metropolitan Statistical Areas (MSACMSA), Historic US Metropolitan Areas</title>
<geoform Sync="TRUE">vector digital data</geoform>
<pubinfo>
<pubplace>Minneapolis, Minnesota</pubplace>
<publish>Minnesota Population Center</publish>
</pubinfo>
<onlink>http://www.nhgis.org</onlink>
<lworkcit/>
<ftname Sync="TRUE">US_msacmsa_2000</ftname>
</citeinfo>
</citation>
<descript>
<abstract>This is an updated shapefile of MSA boundaries - updated from the 10/26/2006 shapefile. NHGIS staff fixed some boundaries in New England. This boundary file contains metropolitan statistical areas (MSA) for the 2000 Census of Population and Housing. The Office of Management and Budget defined MSAs in 2000 and the U.S. Census Bureau tabulated and published data for these units. The electronic boundary file was produced by the Minnesota Population Center as part of the National Historical Geographic Information System (NHGIS) project. The NHGIS is an National Science Foundation-sponsored project (Grant No. BCS0094908) to create a digital spatial-temporal database of all available historical US aggregate census materials. The available shapefiles on the NHGIS site represent version 1.0 of historical US metropolitan statistical area boundary files for the 1950-2000 censuses. These electronic census tract boundary files were created by referencing the list of SMA component parts (available at http://www.census.gov/population/estimates/metro-city/00mfips.txt) and assigning MSA FIPS codes to the NHGIS' historic 2000 county boundaries. For the MSAs in New England, we constructed towns using boundaries derived from the 2000 TIGER/Line files and assigned the correct MSA fips codes to the towns. We assumed that town boundaries did not change between 1950 and 2000. The boundary files have been checked against currently available historical census aggregate data.</abstract>
<purpose>These data are based upon work supported by the National Science Foundation under Grant No. BCS0094908 - in infrastructure grant provided for the social sciences. Its purpose is twofold. First, the NHGIS created and freely distributes a database incorporating all available aggregate census information for the United States between 1790 and 2000. The database contains information for a wide variety of statistical (blocks, block groups, census tracts, metropolitan statistical areas) and administrative units (places, minor civil divisions, counties, states). Second, the NHGIS produced and freely distributes boundary files for small areas (census tracts and counties) in the United States. Boundary files for tracts are available for the 1910-2000 censuses, boundary files for states/territories and counties are available for the 1790-2000 censuses, and boundary files for metropolitan statistical areas are available for the 1950-2000 censuses.</purpose>
<supplinf>The Bureau of the Budget first defined county-based metropolitan areas for the 1950 Census of Population and Housing. Prior to 1950, minor civil division-based metropolitan districts were defined by the Census Bureau but were scrapped in favor of a county-based definition. Few agencies outside of the Census Bureau tabulated data at the minor civil division-level; therefore, they could not use the MCD-based districts for socioeconomic analyses. The definition of metropolitan areas has changed through time, with a major change occuring in 2002. Between 1950 and 2000, the definition was fairly stable with a few minor modifications, including name changes, through time. Essentially, a metropolitan area is "a core area containing a large population nucleus, together with adjacent communities that have a high degree of economic and social integration with that core" (U.S. Census Bureau 1994, 13-1). In 1950, the Bureau of the Budget defined standard metropolitan areas (SMAs) as "one or more counties that contain a city of 50,000 or more inhabitants, or contain a Census Bureau-defined urbanized area (UA) and have a total population of at least 100,000 (75,000 in New England). Counties containing the principal concentration of population - the largest city and surrounding densely settled area - are components...Additional counties qualify to be included by meeting a specified level of commuting to the counties containing the population concentration and by meeting certain other requirements of metropolitan character, such as a minimum population density or percentage of the population that is urban" (U.S. Census Bureau 1994, 13-1 - 13-2). In 1960, the Bureau of the Budget changed the name from standard metropolitan area (SMA) to a standard metropolitan statistical area (SMSA), which was the name until 1990, when the name was again changed to metropolitan statistical area (MSA). In 1980, standard consolidated statistical areas (SCSA) were introduced. These SCSAs are conglomerates of standard metropolitan statistical areas whose population exceeds one million people. In 1990, the Office of Management and Budget (the successor of the Bureau of the Budget) changed the names of metropolitan areas and introduced two new entities, the primary metropolitan statistical area (PMSA) and the New England County Metropolitan Area (NECMA). Standard metropolitan statistical area and standard consolidated statistical areas were changed to metropolitan statistical area (MSA) and consolidated metropolitan statistical area (CMSA). A PMSA is a "subarea...defined within an area that meets the requirements as an MSA and also has a population of one million or more" (U.S. Census Bureau 1994, 13-2). When a PMSA is defined, "the entire area of which they are parts becomes a CMSA. All territory within a CMSA is also within some PMSA" (U.S. Census Bureau 1994, 13-2). A New England County Metropolitan Area (NECMA) is a metropolitan area defined by whole counties, instead of towns or cities, in New England. More detailed information about metropolitan areas can be found in the U.S. Census Bureau's Geographic Area Reference Manual (http://www.census.gov/geo/www/garm.html) and the Bureau's website on metropolitan areas (http://www.census.gov/population/www/estimates/metrodef.html).</supplinf>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
<sngdate>
<caldate>2000</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>In work</progress>
<update>As work is completed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-127.649716</westbc>
<eastbc Sync="TRUE">-66.859859</eastbc>
<northbc Sync="TRUE">51.604785</northbc>
<southbc Sync="TRUE">23.285329</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">-2337186.293564</leftbc>
<rightbc Sync="TRUE">2139181.209329</rightbc>
<bottombc Sync="TRUE">-1295866.660567</bottombc>
<topbc Sync="TRUE">1565781.659379</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>historical</themekey>
<themekey>census of population and housing</themekey>
<themekey>census boundaries</themekey>
<themekey>census geography</themekey>
<themekey>census data</themekey>
<themekey>population</themekey>
<themekey>housing</themekey>
<themekey>metropolitan area</themekey>
<themekey>standard metropolitan area</themekey>
<themekey>metropolitan statistical area</themekey>
<themekey>standard metropolitan statistical area</themekey>
<themekey>consolidated metropolitan statistical area</themekey>
<themekey>primary metropolitan statistical area</themekey>
</theme>
<place>
<placekt>None</placekt>
</place>
<temporal>
<tempkt>None</tempkt>
</temporal>
</keywords>
<accconst>All persons are granted a limited license to use and distribute this documentation and the available data, subject to the use constraints listed below.</accconst>
<useconst>This dataset was produced with an intended application at the city, county, metropolitan, or state/territory level. Appropriate uses include thematic mapping of census data and spatial analysis of census data. These unaltered data may be redistributed by a third party. If these data are altered or incorporated into another dataset, they are not to be redistributed without also: altering the name of the dataset, including a Content Standars for Digital Geospatial Metadata (FGDC-STD-001-1998) compliant metadata file that describes the dataset and reflects the alteration steps that makes the new dataset different from this one, and citing this dataset in the metadata as a source for the altered dataset using the source citation specified below. If these digital data are used in the production of a report or in the compilation of a standalone printed map, then this dataset is to be cited in the report or on the map using the source citation specified below. The following source citation should be used when citing this dataset: John S. Adams, William C. Block, Mark Lindberg, Robert McMaster, Steven Ruggles, and Wendy Thomas, National Historical Geographic Information System: Pre-release Version 0.1, Minneapolis: Minnesota Population Center, University of Minnesota, 2004. No fee may be charged for use or distribution. Publications and research reports based on the database must cite it appropriately. Users are requested to send a copy of any publications, research reports, or educational material making use of the data or documentation. Printed matter should be sent to: NHGIS Minnesota Population Center University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Petra Noble</cntper>
<cntorg>Minnesota Population Center</cntorg>
</cntperp>
<cntpos>Research Fellow</cntpos>
<cntaddr>
<addrtype>physical address</addrtype>
<address>50 Willey Hall</address>
<address>225 19th Ave S</address>
<city>Minneapolis</city>
<state>Minnesota</state>
<postal>55455</postal>
<country>USA</country>
</cntaddr>
<cntvoice>612-625-7375</cntvoice>
<cntemail>nhgis@pop.umn.edu</cntemail>
</cntinfo>
</ptcontac>
<native Sync="FALSE">ESRI ArcCatalog 9.2.0.1324</native>
<natvform Sync="TRUE">Shapefile</natvform>
</idinfo>
<dataqual>
<attracc>
<attraccr>All attributes in this boundary file were checked against attributes in the available aggregate data to ensure accuracy and consistency. The boundary file may contain more or fewer MAs than the aggregate data file. </attraccr>
</attracc>
<logic>All spatial data have been reviewed to assure topological consistency and completeness. All polygons close and do not overlap. No voids exist within polygons. ArcGIS topology features classes were used to identify and fix topological errors (e.g., overlaps, voids, missing polygons) in the tract boundary datasets. The ArcGIS topology rules used to ensure logical consistency were 'Must not overlap' and 'Area Boundary must be Covered by Boundary of'.</logic>
<complete>Version 1.0 of the metropolitan area boundary files contains metropolitan areas (MA). Most MAs, although not all, have a matching record in the aggregate data files. Version 1.0 boundary files have not been generalized, and tracts containing parts of the following bodies of water do not have historically accurate coastlines: the Great Lakes, Atlantic Ocean, Pacific Ocean, and the Gulf of Mexico. No tracts overlap, no voids exist between tracts, and any polygon belongs to one and only one tract. Every MAhas a FIPS-like code (GISJOIN) that uniquely identifies it. The aggregate data file contains a matching code (GISJOIN) so that the files can be easily joined together.</complete>
<posacc>
<horizpa>
<horizpar>The horizontal positional accuracy of the source data (U.S. Census Bureau TIGER/Line 2000 files) can be found at http://www.census.gov/geo/www/tlmetadata/tl2kmeta.txt. To create historic county boundaries, we used existing TIGER lines whereever possible. When no TIGER line existed, we digitized new linework from scanned and rectified U.S. Census Bureau tract maps.</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Census Bureau</origin>
<pubdate>2000</pubdate>
<title>Census 2000 TIGER/Line files [machine-readable data files].</title>
<pubinfo>
<pubplace>Washington D.C.</pubplace>
<publish>U.S. Government Printing Office</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>various</srcscale>
<typesrc>online</typesrc>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Census Bureau</origin>
<pubdate>2001</pubdate>
<title>2000 Summary File 1 (SF1)</title>
<pubinfo>
<pubplace>Washington D.C.</pubplace>
<publish>U.S. Government Printing Office</publish>
</pubinfo>
<onlink>http://factfinder.census.gov</onlink>
</citeinfo>
</srccite>
<typesrc>digital tape media</typesrc>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Census Bureau</origin>
<pubdate>20050317</pubdate>
<title>Historical Metropolitan Area Definitions</title>
<pubinfo>
<pubplace>Washington, D.C.</pubplace>
<publish>U.S. Census Bureau, Population Division, Population Distribution Branch</publish>
</pubinfo>
<onlink>http://www.census.gov/population/www/estimates/pastmetro.html</onlink>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Office of Management and Budget</origin>
<pubdate>19990630</pubdate>
<title>METROPOLITAN AREAS AND COMPONENTS, 1999, WITH FIPS CODES</title>
<pubinfo>
<pubplace>Washington, D.C.</pubplace>
<publish>U.S. Census Bureau, Population Division, Population Distribution Branch</publish>
</pubinfo>
<onlink>http://www.census.gov/population/estimates/metro-city/99mfips.txt</onlink>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
</srcinfo>
<procstep>
<procdesc>Downloaded the historical metropolitan area definition file for the 2000 metropolitan statistical areas and created a dBase file from it. The historical metropolitan area definition file can be found at: http://www.census.gov/population/estimates/metro-city/00mfips.txt</procdesc>
</procstep>
<procstep>
<procdesc>Constructed 1990 New England towns and cities boundaries from the 2000 TIGER/Line files. These towns will serve as the boundaries of the standard metropolitan areas in New England.</procdesc>
<procsv>TGR2SHP 6.231</procsv>
</procstep>
<procstep>
<procdesc>Imported the 1990 New England towns and cities boundaries into ArcSDE.</procdesc>
<procsv>ArcCatalog</procsv>
</procstep>
<procstep>
<procdesc>Using the 2000 MSA definition file, we merged the New England towns and cities to create New England metropolitan areas.</procdesc>
<procsv>ArcMap</procsv>
</procstep>
<procstep>
<procdesc>Converted the New England metropolitan area polygons to a line feature class. These lines were used to cut New England counties to create the metropolitan areas.</procdesc>
<procsv>ArcCatalog</procsv>
</procstep>
<procstep>
<procdesc>Copied the 2000 historical county feature class to a new feature class that will hold the 2000 metropolitan statistical areas.</procdesc>
<procsv>ArcCatalog</procsv>
</procstep>
<procstep>
<procdesc>Edited the New England counties to create the metropolitan statistical areas.</procdesc>
<procsv>ArcMap</procsv>
</procstep>
<procstep>
<procdesc>Imported the historical metropolitan area definition dBase file to an ArcSDE table.</procdesc>
<procsv>ArcCatalog</procsv>
</procstep>
<procstep>
<procdesc>Joined the historical metropolitan area definition table to the 2000 MSA feature class. This step attached the MSA codes to the appropriate counties.</procdesc>
<procsv>ArcMap</procsv>
</procstep>
<procstep>
<procdesc>Dissolve the feature class on the MSA code to create the 2000 MSA boundaries.</procdesc>
<procsv>ArcMap</procsv>
</procstep>
<procstep>
<procdesc>Created topology for the dissolved feature class with two rules ("Must not have gaps" and "Must not overlap"). If there were any errors, we edited the original feature class and then re-dissolved on the MSA code.</procdesc>
<procsv>ArcCatalog</procsv>
</procstep>
<procstep>
<procdesc>Added the GISJOIN item to the dissolved feature class and calculated it equal to the MSA code.</procdesc>
<procsv>ArcMap</procsv>
</procstep>
<procstep>
<procdesc>Wrote FGDC-compliant metadata for the 2000 MSA boundaries.</procdesc>
<procsv>ArcCatalog</procsv>
</procstep>
<procstep>
<procdesc>Exported the 2000 MSA feature class to a shapefile for Internet dissemination.</procdesc>
<procsv>ArcMap</procsv>
</procstep>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20061030</date>
<time Sync="TRUE">07543000</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20061206</date>
<time Sync="TRUE">10083100</time>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="MSA_2000">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<plandu Sync="TRUE">meters</plandu>
<coordrep>
<absres Sync="TRUE">0.000000</absres>
<ordres Sync="TRUE">0.000000</ordres>
</coordrep>
</planci>
</planar>
<geodetic>
<horizdn Sync="TRUE">North American Datum of 1983</horizdn>
<ellips Sync="TRUE">Geodetic Reference System 80</ellips>
<semiaxis Sync="TRUE">6378137.000000</semiaxis>
<denflat Sync="TRUE">298.257222</denflat>
</geodetic>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">USA_Contiguous_Albers_Equal_Area_Conic</projcsn>
</cordsysn>
</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="MSA_2000">
<attr>
<attrlabl Sync="TRUE">MSACMSA</attrlabl>
<attalias Sync="TRUE">MSACMSA</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Unique 4-digit FIPS code identifying Metropolitan Statistical Areas/Consolidated Metropolitan Statistical Areas</attrdef>
<attrdefs>U.S. Census Bureau</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</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">GISJOIN</attrlabl>
<attalias Sync="TRUE">GISJOIN</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Unique 5-digit code used to join aggregate data to shapefiles</attrdef>
<attrdefs>NHGIS</attrdefs>
</attr>
<enttyp>
<enttypl Sync="TRUE">MSA_2000</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">GISJOIN2</attrlabl>
<attalias Sync="TRUE">GISJOIN2</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<attrdef>Alternate unique 4-digit code used to join aggregate data to shapefiles</attrdef>
<attrdefs>NHGIS</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Area</attrlabl>
<attalias Sync="TRUE">Shape_Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
<overview>
<eaover>The most important attribute in this shapefile is GISJOIN because it provides the link between the shapefile and the aggregate data files. Any aggregate data file obtained through the NHGIS data acces system will contain a GISJOIN attribute. Use this attribute to link the data with the shapefile for mapping purposes. Please note that values in GISJOIN begin with "G" in order to retain leading zeros. This update took effect on May 7, 2008. GISJOIN2 is an alternative linking attribute. GISJOIN2 is similar to GISJOIN except that its values do not begin with "G". GISJOIN2 may be used when linking to an aggregate data file extracted before May 7, 2008.
Other attributes in the shapefile include area (in square meters), perimeter (in meters), FID (a ArcGIS-generated unique identifier for each record), and MSA (unique FIPS code identifying the 2000 metropolitan statistical area).</eaover>
<dsoverv>This shapefile contains standard metropolitan areas for the Census of Population and Housing.</dsoverv>
</overview>
</eainfo>
<metainfo>
<metd Sync="TRUE">20080428</metd>
<metrd>20070105</metrd>
<metfrd>As necessary</metfrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Minnesota Population Center</cntorg>
<cntper>Petra Noble</cntper>
</cntorgp>
<cntaddr>
<address>50 Willey Hall</address>
<address>225 19th Avenue South</address>
<city>Minneapolis</city>
<state>Minnesota</state>
<postal>55455</postal>
<country>USA</country>
<addrtype>mailing address</addrtype>
</cntaddr>
<cntvoice>612-625-7375</cntvoice>
<cntemail>nhgis@pop.umn.edu</cntemail>
</cntinfo>
</metc>
<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
<langmeta Sync="TRUE">en</langmeta>
<mettc Sync="TRUE">local time</mettc>
</metainfo>
<Esri>
<ModDate>20240716</ModDate>
<ModTime>11015600</ModTime>
<CreaDate>20260807</CreaDate>
<CreaTime>12594400</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20240716</SyncDate>
<SyncTime>11015600</SyncTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">MSA_2000</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_NAD_1983_2011</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot (0.304800)</csUnits>
<projcsn Sync="TRUE">NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900_Ft_Intl</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/3.1.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_2011_StatePlane_South_Carolina_FIPS_3900_Ft_Intl&amp;quot;,GEOGCS[&amp;quot;GCS_NAD_1983_2011&amp;quot;,DATUM[&amp;quot;D_NAD_1983_2011&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;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,2000000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-81.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,32.5],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,34.83333333333334],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,31.83333333333333],UNIT[&amp;quot;Foot&amp;quot;,0.3048],AUTHORITY[&amp;quot;EPSG&amp;quot;,6570]]&lt;/WKT&gt;&lt;XOrigin&gt;-122907600&lt;/XOrigin&gt;&lt;YOrigin&gt;-92800700&lt;/YOrigin&gt;&lt;XYScale&gt;3048&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.0032808398950131233&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;103146&lt;/WKID&gt;&lt;LatestWKID&gt;6570&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
</Esri>
<mdDateSt Sync="TRUE">20240716</mdDateSt>
<distinfo>
<distrib>
<cntinfo>
<cntaddr>
<address>50 Willey Hall</address>
<address>225 19th Ave S</address>
<city>Minneapolis</city>
<state>MN</state>
<postal>55455</postal>
</cntaddr>
<cntorgp>
<cntorg>Minnesota Population Center</cntorg>
</cntorgp>
<cntvoice>612-625-7375</cntvoice>
<cntemail>nhgis@pop.umn.edu</cntemail>
</cntinfo>
</distrib>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
<stdorder>
<digform>
<digtinfo>
<transize Sync="TRUE">0.000</transize>
<dssize Sync="TRUE">0.000</dssize>
</digtinfo>
</digform>
</stdorder>
</distinfo>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.0.41833</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">MSA_2000</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">-2337186.293564</westBL>
<eastBL Sync="TRUE">2139181.209329</eastBL>
<northBL Sync="TRUE">1565781.659379</northBL>
<southBL Sync="TRUE">-1295866.660567</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-127.649716</westBL>
<eastBL Sync="TRUE">-66.859859</eastBL>
<northBL Sync="TRUE">51.604785</northBL>
<southBL Sync="TRUE">23.285329</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
</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>
<protocol Sync="TRUE">Local Area Network</protocol>
</onLineSrc>
<transSize Sync="TRUE">0.000</transSize>
</distorTran>
<distorFormat>
<formatName Sync="TRUE">Shapefile</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="6570">USA_Contiguous_Albers_Equal_Area_Conic</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.2.10(10.3.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="MSA_2000">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
</metadata>
