<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20200507</CreaDate>
<CreaTime>10225500</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Joint_Land_Management_Line</itemName>
<imsContentType Sync="FALSE" export="False">003</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">11688868.363958</westBL>
<eastBL Sync="TRUE">11793248.166458</eastBL>
<southBL Sync="TRUE">7019290.366667</southBL>
<northBL Sync="TRUE">7152445.046250</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983_HARN</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501_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/2.8.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983_HARN&amp;quot;,DATUM[&amp;quot;D_North_American_1983_HARN&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;,11482916.66666666],PARAMETER[&amp;quot;False_Northing&amp;quot;,6561666.666666666],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-78.5],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,38.03333333333333],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,39.2],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,37.66666666666666],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2924]]&lt;/WKT&gt;&lt;XOrigin&gt;-110512500&lt;/XOrigin&gt;&lt;YOrigin&gt;-88858000&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121918&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;2924&lt;/WKID&gt;&lt;LatestWKID&gt;2924&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20211207</SyncDate>
<SyncTime>18403100</SyncTime>
<ModDate>20211207</ModDate>
<ModTime>18403100</ModTime>
<ArcGISProfile>FGDC</ArcGISProfile>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<rpPosName>Metadata Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(703)771-5778</voiceNum>
<faxNum>(703)771-5075</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>1 Harrison Street SE., 2nd Floor</delPoint>
<delPoint>MS 65</delPoint>
<city>Leesburg</city>
<adminArea>VA</adminArea>
<postCode>20175</postCode>
<country>US</country>
<eMailAdd>mapping@loudoun.gov</eMailAdd>
</cntAddress>
<cntHours>8:00-4:30 EST, M-F</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20211207</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<rpPosName>Public Information Counter</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(703)771-5778</voiceNum>
<faxNum>(703)771-5075</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>MS 65</delPoint>
<delPoint>1 Harrison Street SE, 2nd Floor</delPoint>
<city>Leesburg</city>
<adminArea>VA</adminArea>
<postCode>20175</postCode>
<country>US</country>
<eMailAdd>mapping@loudoun.gov</eMailAdd>
</cntAddress>
<cntHours>8:00-4:30 EST, M-F</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees units="">Loudoun County distributes spatial data in ArcGIS database or shapefile &amp; DXF format for the cost of reproduction. Countywide spatial datasets may be purchased for $22 per DVD for up to 4.5 GB of data. There is a $100 surcharge to purchase countywide topography, and a $3 charge if the item is to be mailed. If the customer wants the data in DXF format and/or would like OMAGI to custom select specific geographic areas of the County, there is an additional $7 per 15 minute increment labor charge. Select aerial imagery is also available.</resFees>
<ordInstr>Size limit: 4.5 GB. Visit our website at: http://www.loudoun.gov/omagi, click on "Loudoun County Mapping Documents &amp; Order Forms." The "Forms" directory will lead you to custom &amp; standard (countywide) data order forms. Hardcopy maps may also be available; please contact the Mapping Office Public Information Counter for more information regarding all data requests.</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>DXF</formatName>
<formatSpec>AutoCad Digital Exchange File</formatSpec>
</distorFormat>
<distorFormat>
<formatName>GDB</formatName>
<formatSpec>ESRI Personal Geodatabase Feature Class</formatSpec>
</distorFormat>
<distorFormat>
<formatName>SHP</formatName>
<formatSpec>ESRI Shapefile</formatSpec>
</distorFormat>
<distorTran>
<offLineMed>
<medName>
<MedNameCd value="002"/>
</medName>
</offLineMed>
<unitsODist>Tiles</unitsODist>
</distorTran>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>withheld</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle Sync="FALSE">Towns &amp; Jurisdictions of Loudoun County, VA</resTitle>
<date>
<pubDate date="now"/>
</date>
<citRespParty>
<rpOrgName>Loudoun County, VA, Office of Mapping and Geographic Information (OMAGI)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
<PresFormCd Sync="FALSE" value=""/>
</presForm>
<citOnlineRes>
<linkage>withheld</linkage>
</citOnlineRes>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Commonwealth of Virginia grants certain powers to incorporated municipalities. There are seven towns in the County. Washington Dulles International Airport is also included due to its jurisdictional authority, but is not tracked by Loudoun's Management Information System (LMIS).&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>Town boundaries can define the limits of zoning, subdivision control limits, and other responsibilities of both the towns and the County. Jurisdictional authority is represented for each of the seven towns and Washington Dulles International Airport.</idPurp>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<rpPosName>Parcel Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(703)771-5778</voiceNum>
<faxNum>(703)771-5075</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>MS 65</delPoint>
<delPoint>1 Harrison Street SE, 2nd Floor</delPoint>
<city>Leesburg</city>
<adminArea>VA</adminArea>
<postCode>20175</postCode>
<country>US</country>
<eMailAdd>mapping@loudoun.gov</eMailAdd>
</cntAddress>
<cntHours>8:00-4:30 EST, M-F</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<placeKeys>
<thesaName>
<resTitle>none; Employee generated</resTitle>
</thesaName>
<keyword>Middleburg</keyword>
<keyword>County</keyword>
<keyword>Loudoun</keyword>
<keyword>Lovettsville</keyword>
<keyword>Round Hill</keyword>
<keyword>Dulles</keyword>
<keyword>Virginia</keyword>
<keyword>Purcellville</keyword>
<keyword>Hamilton</keyword>
<keyword>Leesburg</keyword>
<keyword>Hillsboro</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>none; Employee generated</resTitle>
</thesaName>
<keyword>Jurisdiction</keyword>
<keyword>municipality</keyword>
<keyword>Town</keyword>
<keyword>Incorporated</keyword>
<keyword>airport</keyword>
</themeKeys>
<searchKeys>
<keyword>Middleburg</keyword>
<keyword>County</keyword>
<keyword>Jurisdiction</keyword>
<keyword>Loudoun</keyword>
<keyword>Lovettsville</keyword>
<keyword>Round Hill</keyword>
<keyword>Dulles</keyword>
<keyword>Virginia</keyword>
<keyword>Purcellville</keyword>
<keyword>municipality</keyword>
<keyword>Town</keyword>
<keyword>Incorporated</keyword>
<keyword>Hamilton</keyword>
<keyword>Leesburg</keyword>
<keyword>Hillsboro</keyword>
<keyword>airport</keyword>
<keyword>boundaries</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;These data were generated for use by Loudoun County and are available to the public. These data are intended for use at 1:2400 scale or smaller. Acknowledgement of Loudoun County would be appreciated in products derived from this data.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Every reasonable effort has been made to assure the accuracy of these data. Loudoun County, Virginia does not assume any liability arising from the use of these data. These data are provided without warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular service. Reliance on these data is at the risk of the user.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<envirDesc Sync="FALSE">Esri ArcGIS 12.8.0.29751</envirDesc>
<suppInfo>The first town to be incorporated in Loudoun was Leesburg in 1757. Town boundaries are updated within 1-2 weeks of the date of receipt of recorded documents associated with annexations. Recorded documents are generally received from the Assessor's Office within 4-6 weeks of the date of recordation. Town boundaries are checked for coincidence with parcel boundaries approximately once every six months. Annexations occur fairly frequently in most Towns, often once a year. Parcels that are split by a town boundary are given unit numbers. For example, a MCPI (Map Cell Parcel Identifier) or PIN may be 123-45-6789. If this number was split by the town, the result would be 123-45-6789-001 indicating the County portion of that parcel, while the Town portion would be 123-45-6789-002. These units do not show in the County's GIS system, but are in the Assessor's database. Several Towns have an independent tax that is calculated from the pro-rated unit acreage. Data are stored in the corporate ArcSDE Geodatabase as a polygon feature class. The coordinate system is Virginia State Plane (North), Zone 4501, datum NAD83 HARN (vertical datum, if applicable, NAVD88), US Survey foot units.</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-77.776115</westBL>
<eastBL Sync="TRUE">-77.403677</eastBL>
<northBL Sync="TRUE">39.286619</northBL>
<southBL Sync="TRUE">38.918214</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<resMaint>
<maintFreq>
<MaintFreqCd value="002"/>
</maintFreq>
</resMaint>
<tpCat>
<TopicCatCd value="003"/>
</tpCat>
</dataIdInfo>
<mdConst>
<Consts>
<useLimit>This metadata reflects the source Geodatabase format and specific elements may not apply if your data is exported to SHP or DXF products. User must be aware that changes to data schema occur during data export that may not be reflected in this metadata, which represents Loudoun County's corporate geodatabase. Acknowledgement of Loudoun County would be appreciated in the use of this metadata.</useLimit>
</Consts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report dimension="" type="DQCompOm">
<evalMethDesc>Features may have been eliminated or generalized due to scale and intended use. To assist Loudoun County, Virginia in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data.</evalMethDesc>
</report>
<report dimension="" type="DQConcConsis">
<measDesc>Topologically clean</measDesc>
</report>
<report dimension="" type="DQCompOm">
<measDesc>Features may have been eliminated or generalized due to scale and intended use. To assist Loudoun County, Virginia in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data.</measDesc>
</report>
<report dimension="" type="DQQuanAttAcc">
<measDesc>Retention of attribute accuracy throughout the coverage to geodatabase feature class coversion process was ensured by a QA/QC programmatic check. To meet satisfactory QA/QC requirements the input coverage and output feature class must have, on a record by record basis, identical attribution when comparing all concatenated fields to all the user-defined attribution.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Retention of coordinate accuracy throughout the coverage to geodatabase feature class conversion process was ensured by a QA/QC programmatic check. To meet satisfactory QA/QC requirements the input coverage and output feature class must have the same record total, and on a record by record basis, area, perimeter, and length differential of less than +/- 0.5%.</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>Leesburg, Round Hill, Hamilton and Lovettsville were all original mylar plats that were digitized in 1994. Dulles Int'l Airport was digitized from mylar plat in 1999. Middleburg was digitized from original tax maps.
</stepDesc>
<stepDateTm date="now"/>
<stepProc>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<rpPosName>Parcel Coordinator</rpPosName>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Hillsboro and Purcellville have no verifiable, recorded map source and comprise parcels identified by the Dept. of Financial Services as within those towns' limits.
</stepDesc>
<stepDateTm>1999-01-25T00:00:00</stepDateTm>
<stepProc>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<rpPosName>GIS Analyst</rpPosName>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>This data set was part of a batch process that converted legacy data from ArcInfo coverage in Librarian to a single-tiled ArcInfo coverage in preparation for a final conversion to ArcSDE Geodatabase Feature Classes. Data were extracted from Librarian using the EXTRACT TOPOLOGICAL command. Multi-tiled data sets were extracted into multiple coverages and then combined based on the feature type(s). Layers with both polygon and arc feature classes were processed with the Arc commands MAPJOIN and DISSOLVE. Arc feature classes alone were processed with the Arc commands, APPEND and DISSOLVE. Layers with both arc and point feature classes and point feature classes alone were processed with the Arc command, APPEND. When used, the arc command, DISSOLVE, was given with the &lt;#all&gt; option. All coverages were then reprojected to HARN83 using the following .prj file specifications: INPUT PROJECTION STATEPLANE UNITS FEET ZONE 5551 DATUM NAD27 NADCON PARAMETERS OUTPUT PROJECTION STATEPLANE UNITS FEET FIPSZONE 4501 DATUM HPGN NADCON PARAMETERS END The dataset was then converted to a feature class in a geodatabase in ArcSDE.
</stepDesc>
<stepDateTm>2004-01-19T00:00:00</stepDateTm>
<stepProc>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<role>
<RoleCd value="009"/>
</role>
<rpPosName>GIS Analyst</rpPosName>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Annexation Plats are incorporated into Town boundaries periodically upon their recordation. The Source Information Source Citations describes the original source data for each Town. However, numerous annexations have occurred and are not individually enumerated.</stepDesc>
<stepProc>
<rpOrgName>Loudoun County, VA, OMAGI</rpOrgName>
<rpPosName>Parcel Coordinator</rpPosName>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<dataSource type="">
<srcDesc>Hamilton</srcDesc>
<srcScale>
<rfDenom>600</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Town of Hamilton</resTitle>
<date>
<pubDate>1990-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Dewberry &amp; Davis</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1990-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Leesburg</srcDesc>
<srcScale>
<rfDenom>12000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>The Town of Leesburg in Loudoun County, Virginia</resTitle>
<date>
<pubDate>1983-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Delashmutt Associates</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1983-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Round Hill: cogo from instrument #20040927-0103733 by Wolford &amp; Chen</srcDesc>
<srcScale>
<rfDenom>2400</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Loudoun County, Virginia - PCT Block V map</resTitle>
<date>
<pubDate>1982-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Air Survey &amp; Design</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1980-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Washington Dulles International Airport</srcDesc>
<srcScale>
<rfDenom>12000</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Washington Dulles International Airport Master Plan Property Map</resTitle>
<date>
<pubDate>1997-10-02</pubDate>
</date>
<citRespParty>
<rpOrgName>Metropolitan Washington Airports Authority</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Hamilton</srcDesc>
<srcScale>
<rfDenom>2400</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Boundary Plat Town of Hamilton</resTitle>
<date>
<pubDate>1969-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>O.B. Knight</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1969-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Lovettsville</srcDesc>
<srcScale>
<rfDenom>2400</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Town of Lovettsville Corporate Limits</resTitle>
<date>
<pubDate>1988-09-20</pubDate>
</date>
<citRespParty>
<rpOrgName>Chamberlin, Wolford, &amp; Chen</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1988-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Middleburg</srcDesc>
<srcMedName>
<MedNameCd value="027"/>
</srcMedName>
<srcCitatn>
<resTitle>Historical Taxmaps</resTitle>
<date>
<pubDate>1994-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Loudoun County Department of Financial Services</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1994-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource type="">
<srcDesc>Comma delimited text files were compiled by Dept. of Financial Services for all parcels within taxation jurisdiction of Hillsboro and Purcellville. Original source maps for existing data were unavailable, so these selected parcels formed the basis for these two Towns. Boundaries are thus dependent on original parcel plats comprising the towns. Maps at the town office in Purcellville were checked against against existing data. The source of the existing data could not readily be determined, but the existing data agreed with the Purcellville maps with the exception of recent annexations. The annexations were incorporated into the town boundary.</srcDesc>
<srcScale>
<rfDenom>0</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Tax Records for Hillsboro and Purcellville</resTitle>
<date>
<pubDate>1999-01-01</pubDate>
</date>
<citRespParty>
<rpOrgName>Loudoun County Dept. of Financial Services</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>1999-01-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>County participates in a SDE Feature Data Set Topology called LANDRECORDS.</stepDesc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<Indref>Loudoun County</Indref>
<VectSpatRep>
<geometObjs Name="Joint_Land_Management_Line">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2924" value="2924"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Joint_Land_Management_Line">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<eainfo>
<detailed Name="Joint_Land_Management_Line">
<enttyp>
<enttypl Sync="TRUE">Joint_Land_Management_Line</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID_1</attrlabl>
<attalias Sync="TRUE">OBJECTID_1</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">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">Integer</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">LEFT_FID</attrlabl>
<attalias Sync="TRUE">LEFT_FID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">RIGHT_FID</attrlabl>
<attalias Sync="TRUE">RIGHT_FID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Leng</attrlabl>
<attalias Sync="TRUE">Shape_Leng</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<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>
</detailed>
</eainfo>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</mdMaint>
</metadata>
