<?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>2013</pubdate>
<title>Boundaries.DBO.VA_COUNTY</title>
<edition>2013</edition>
<geoform>vector digital data</geoform>
<onlink>http://www2.census.gov/geo/tiger/TIGER2013/COUNTY/tl_2013_us_county.zip</onlink>
</citeinfo>
</citation>
<descript>
<abstract>The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.</abstract>
<purpose>VA_COUNTY is a feature class representing locality (county and city) boundaries in the Commonwealth of Virginia. This dataset was derived from Census TIGER data supplemented with data made available from the cities and counties themselves.</purpose>
<Subject_Entity>United States,US</Subject_Entity>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>201206</begdate>
<enddate>201305</enddate>
</rngdates>
</timeinfo>
<current>Publication Date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>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>-179.231086</westbc>
<eastbc>179.859681</eastbc>
<northbc>71.441059</northbc>
<southbc>-14.601813</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>ISO 19115 Topic Categories</themekt>
<themekey>boundaries</themekey>
</theme>
<theme>
<themekt>None</themekt>
<themekey>Nation</themekey>
<themekey>Polygon</themekey>
</theme>
<place>
<placekt>ANSI INCITS 38:2009 (Formerly FIPS 5-2), ANSI INCITS 31:2009 (Formerly FIPS 6-4),ANSI INCITS 454:2009 (Formerly FIPS 8-6), ANSI INCITS 455:2009(Formerly FIPS 9-1), ANSI INCITS 446:2008 (Geographic Names Information System (GNIS))</placekt>
<placekey>United States</placekey>
<placekey>U.S.</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</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>
</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 Series (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>201206</begdate>
<enddate>201305</enddate>
</rngdates>
</timeinfo>
<srccurr>Publication Date</srccurr>
</srctime>
<srccitea>MAF/TIGER</srccitea>
<srccontr>All line segments</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>2013</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<indspref>Federal Information Processing Series (FIPS), ANSI, and feature names.</indspref>
<direct>Vector</direct>
<ptvctinf>
<esriterm Name="studyArea_Outline">
<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>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137</semiaxis>
<denflat>298.257</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed Name="studyArea_Outline">
<enttyp>
<enttypl>VA_COUNTY</enttypl>
<enttypd>Current County and Equivalent National</enttypd>
<enttypds>U.S. Census Bureau</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<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">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">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>
</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</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>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>http://www2.census.gov/geo/tiger/TIGER2013/COUNTY/tl_2013_us_county.zip</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>The online copy of the TIGER/Line Shapefiles 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>
</distinfo>
<metainfo>
<metd>20130615</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch</cntorg>
</cntorgp>
<cntaddr>
<addrtype>Mailing</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_2013_us_county.shp.xml</Metadata_File_Identifier>
<Metadata_Language>eng</Metadata_Language>
</metainfo>
<Esri>
<CreaDate>20240530</CreaDate>
<CreaTime>16055700</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">studyArea_Outline</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">-37232800.000000</westBL>
<eastBL Sync="TRUE">838232.743935</eastBL>
<southBL Sync="TRUE">-28884600.000000</southBL>
<northBL Sync="TRUE">400171.848248</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemSize Sync="TRUE">0.000</itemSize>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</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;WGS_1984_Web_Mercator_Auxiliary_Sphere&amp;quot;,GEOGCS[&amp;quot;GCS_WGS_1984&amp;quot;,DATUM[&amp;quot;D_WGS_1984&amp;quot;,SPHEROID[&amp;quot;WGS_1984&amp;quot;,6378137.0,298.257223563]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Mercator_Auxiliary_Sphere&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,0.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,0.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,0.0],PARAMETER[&amp;quot;Auxiliary_Sphere_Type&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,3857]]&lt;/WKT&gt;&lt;XOrigin&gt;-20037700&lt;/XOrigin&gt;&lt;YOrigin&gt;-30241100&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;102100&lt;/WKID&gt;&lt;LatestWKID&gt;3857&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20231121</SyncDate>
<SyncTime>08564900</SyncTime>
<ModDate>20231121</ModDate>
<ModTime>08564900</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>FGDC</ArcGISProfile>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.3.41833</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">studyArea_Outline</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-180.000000</westBL>
<eastBL Sync="TRUE">180.000000</eastBL>
<northBL Sync="TRUE">39.605539</northBL>
<southBL Sync="TRUE">-70.300000</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idPurp>VA_COUNTY is a feature class representing locality (county and city) boundaries in the Commonwealth of Virginia. This dataset was derived from Census TIGER data supplemented with data made available from the cities and counties themselves.</idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<searchKeys>
<keyword>Virginia</keyword>
<keyword>administrative</keyword>
<keyword>boundary</keyword>
<keyword>boundaries</keyword>
<keyword>Nation</keyword>
<keyword>Polygon</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The VA_COUNTY feature class is not an official boundary description and should not be used as one. Best efforts were undertaken to ensure the correctness of Administrative Boundary data by using the best source available throughout the Commonwealth of Virginia, however, all warranties regarding the accuracy of the map data and any representation or inferences derived there from are hereby expressly disclaimed.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<idCredit>Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project</idCredit>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<distInfo>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
</distInfo>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3857"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.18.3(9.3.1.2)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="studyArea_Outline">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdDateSt Sync="TRUE">20231121</mdDateSt>
</metadata>
