| Towns & Jurisdictions of Loudoun County, VA | |
|
Data format: SDE Feature Class File or table name: GISDBB.GISBROW.TOWNS_POLY Coordinate system: Lambert Conformal Conic Theme keywords: boundaries, Town, Jurisdiction, Incorporated, municipality, airport |
|
|
Abstract:
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). |
|
Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.
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).
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.
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.
publication date
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. 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.
1 Harrison Street SE, 2nd Floor
MS 65
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.
Topologically clean
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.
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%.
Lovettsville
Round Hill: cogo from instrument #20040927-0103733 by Wolford & Chen
Middleburg
Leesburg
Hamilton
Hamilton
Washington Dulles International Airport
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.
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.
Hillsboro and Purcellville have no verifiable, recorded map source and comprise parcels identified by the Dept. of Financial Services as within those towns' limits.
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 <#all> 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.
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.
County participates in a SDE Feature Data Set Topology called LANDRECORDS.
Name of town or incorporated area
Loudoun County
Source that created or updated feature class
Loudoun County
Internal feature number.
ESRI
Date that feature is created or edited
Loudoun County
Feature geometry.
ESRI
CO_UPD_SOURCE: Source that created or updated feature class
Source Definition 0 Undetermined 1 Legacy 2 County 3 Contract
1 Harrison Street SE, 2nd Floor
MS 65
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, either 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.
ESRI Personal Geodatabase Feature Class
ESRI Shapefile
AutoCad Digital Exchange File
Size limit: 4.5 GB. Visit our website at: http://www.loudoun.gov/omagi, click on "Loudoun County Mapping Documents & Order Forms." The "Forms" directory will lead you to custom & 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.
1 Harrison Street SE., 2nd Floor
MS 65