Virginia's jurisdiction boundaries

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Virginia Dept. of Conservation and Recreation - DSWC
Publication_Date: 20040816
Title: Virginia's jurisdiction boundaries
Edition: 2004
Geospatial_Data_Presentation_Form: map
Series_Information:
Series_Name: jurisdiction boundaries
Issue_Identification: 2004 update
Publication_Information:
Publication_Place: Richmond, Virginia
Publisher: Virginia DCR-DSWC
Other_Citation_Details: Basis is the USGS 7.5 minute topo quad DRGs
Description:
Abstract:
Jurisdiction boundaries for all counties (95) and cities (39) in Virginia at a precision that is, at a minimum, from heads-up digitizing off of DRGs.
Purpose:
These are the jurisdiction boundaries used by Virginia DCR to geocode any geographic information with a jurisdiction FIPS code. They were developed prior to, and for, the development of Virginia's 14 digit hydrologic unit boundaries and updated from 2002-2004 as part of the development of the National Watershed Boundary Dataset (NWBD).
Supplemental_Information:
Origin:

Version 1 jurisdiction boundaries were originally digitized at ISSL, VPI&SU in 1989 off of the USGS 7.5 minute quadrangle maps. Some modifications were made at that time given the date of some quads. The line and attribute data were delivered to the VA DCR in DLG3 format.

Revisions:

Version 1995: Version 1995 was made at the Virginia DCR, using version 1 as a base, as part of the development of Virginia's 14 digit hydrologic unit layer. At that time the jurisdiction boundaries were updated using newer quad maps or maps supplied by various jurisdictions and the Virginia DOT, all of which were at a better scale than the quads but were not always done to map accuracy standards. These newly digitized products were used to replace older existing boundaries. Changes were made to the boundaries of 34 jurisdictions between the first and 1995 versions.

Version 2004: Version 2004 varies from version 1995 in many ways. The major differences are that almost all of the linework has been recaptured at a better resolution, and linework has been added to delineate what is in a jurisdiction from what a local government has jurisdiction over. The improved resolution was realized by overlaying the linework of version 1995 onto enhanced DRGs and recapturing linework via heads-up digitizing on images which are enlarged beyond the 1:24,000 scale of the original paper maps. The determinations of what areas of the state are truly within any local jurisdictions versus being within the state but outside of all local jurisdictions was assisted by the Virginia Attorney General's Office.

Additionally, as these boundaries were being recaptured as part of the NWBD development, jurisdiction boundaries that coexisted as watershed boundaries were modified to align with the watershed boundaries as they were defined in the NWBD versus aligning with jurisdiction boundaries as they were drawn on the USGS topographic quads. These situations are noted in the line attribute table.

Other than the improved linework due to the DRG use and NWBD development as noted above, the following changes were made between versions 1995 and 2004: (1) Clifton Forge is removed as it is no longer a city. (2) The shoreline boundaries of jurisdictions bordering the Chesapeake Bay and Atlantic Ocean have been recaptured off of DOQQs. (3) The offshore waters of Virginia have been added to the 3 nautical mile limit. (4) The boundary between Prince George and Sussex and between Sussex and Surry has been altered (Disputanta South quad). (5) The boundary of Emporia has been altered. (6) The boundary between Lynchburg and Amherst was altered. (7) The boundary between Danville and Pittsylvania Co was altered. (8) The boundary of Williamsburg has been altered based on its representation on their web site. (9) The state boundary has been altered from Smith Point to Rhodes Point. In particular, it originates further southeast on the line extending from Smith Point than previously portrayed on 7.5 minute topo maps. (10) The boundary between Fauquier and Prince William has been altered. (11) The boundary between Giles and Monroe County, WV has been altered. (12) The boundary between Louisa and Goochland was altered to reflect the boundary as displayed on VDOT county maps. (13) Minor adjustments were made to the boundary of Norton. (14) Minor adjustments were made to the boundary of Bristol.

Territorial waters within the Commonwealth have been determined with the assistance of the Virginia Attorney General's Office. As advised by that office, and in accordance with section 15.2-3105 of the Code of Virginia, Chesapeake Bay waters, Atlantic Ocean waters, and the tidal tributaries to these bodies of water, are not considered part of any local jurisdiction. In other words, "the normal activities of counties and cities do not extend off shore". Section 15.2-3105 extends the boundary of local jurisdictions along the Chesapeake Bay or Atlantic Ocean to "embrace all wharfs, piers, docks, and other structures, except bridges and tunnels that have been or may hereafter be erected along the waterfront". Therefore shorelines that include these structures are now used to define the jurisdiction boundaries along the Chesapeake Bay and Atlantic Ocean. While tidal rivers of these bodies are also part of this decree, it would be difficult to accurately portray local jurisdiction boundaries excluding all tidal waters of the Bay and the Atlantic. It would also produce a version of jurisdiction boundaries for Virginia unlikely to be used by the agencies of the state who this layer is intended to assist. Therefore, an apparent limit arc has been added across tidal waters to delineate the Chesapeake Bay and Atlantic Ocean proper from their tidal tributaries. These artificial boundaries have been attributed as such.

The same legal source also advises that in accordance with Sections 16.1-69.29 and 17.1-516, the local jurisdictions of the Commonwealth have been given "concurrent territorial jurisdiction [to the district and circuit courts of counties on each side of any river, watercourse, or bay,] over so much thereof as shall be opposite to such counties". Likewise, local jurisdictions have been authorized by Section 29.1-744.C to enact ordinances regulating vessels and the conduct of people within the territorial limits, including the marginal adjacent Atlantic Ocean. This section extends the territorial limits of the seaside jurisdictions out three miles into the Atlantic Ocean. Accordingly, this version of the jurisdiction boundaries contains the delineations of the Chesapeake Bay and Atlantic Ocean as necessary to portray these stated territorial jurisdictions, including an equidistance mid-Bay boundary that will not align with the mid-Bay boundary found in federal spatial layers showing jurisdiction boundaries in Virginia.

It is possible to only display the arcs defining jurisdictions, versus also showing arcs which only define areas that jurisdictions have jurisdiction over. One method would be to reselect polygons for FIPS values less than 900 and to then use the POLYGONS command to display them.

Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20010801
Ending_Date: present
Currentness_Reference: Publication date of sources
Status:
Progress: Complete
Maintenance_and_Update_Frequency:
Updated whenever known boundary changes are made and maps of said changes can be obtained. However, there is no process in place to assure that DCR is aware of such changes when they occur.

Upcoming modifications will include the infusion of boundaries from local governments where those boundaries are agreeable to parties on both sides, ridge modifications from more precise topographic sources, and more current and precise shorelines from the hydrography developed from the VA Base Map Imagery.

Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -83.675
East_Bounding_Coordinate: -75.176
North_Bounding_Coordinate: 39.466
South_Bounding_Coordinate: 36.541
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: jurisdiction
Theme_Keyword: cities
Theme_Keyword: counties
Place:
Place_Keyword_Thesaurus: none
Place_Keyword: Virginia
Access_Constraints: none
Use_Constraints: Crediting VA DCR for dataset development is requested.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Karl Huber
Contact_Organization: Virginia Dept. of Conservation & Recreation - DSWC
Contact_Address:
Address_Type: mailing and physical address
Address: 203 Governor Street, Suite 206
City: Richmond
State_or_Province: Virginia
Postal_Code: 23219-2094
Country: USA
Contact_Voice_Telephone: 804 371 7484
Contact_Facsimile_Telephone: 804 371 2630
Contact_Electronic_Mail_Address: karl.huber@dcr.virginia.gov
Hours_of_Service: 0830-1800
Data_Set_Credit:
DCR-DSWC is credited with the linework revisions of version 1995. The almost complete redigitizing of version 2004 from DRGs was done by Virginia Tech - Biological Systems Engineering staff working at DCR-DSWC. Legal assistance was provided by Frederick Fisher, Senior Assistant Attorney General in the Virginia Office of the Attorney General.
Native_Data_Set_Environment: UNIX ARC/INFO v7.2.1 cover /gis/dswc/jbnd/bva04_l
Cross_Reference:
Citation_Information:
Originator: ISSL
Publication_Date: 1989
Title: Virginia's jurisdiction boundaries
Edition: 1
Geospatial_Data_Presentation_Form: map
Series_Information:
Series_Name: jurisdiction boundaries
Issue_Identification: version 1
Publication_Information:
Publication_Place: Blacksburg, Virginia
Publisher: ISSL
Cross_Reference:
Citation_Information:
Originator: VDOT
Publication_Date: 19930101
Title: County Road Map Atlas
Edition: 1993
Geospatial_Data_Presentation_Form: map
Series_Information:
Series_Name: County Road Map Atlas
Issue_Identification: 1993 Volume
Publication_Information:
Publication_Place: Richmond, Virginia
Publisher: VDOT
Cross_Reference:
Citation_Information:
Originator: VDOT
Publication_Date: 1992
Title: City Road Maps
Edition: 1991
Geospatial_Data_Presentation_Form: map
Series_Information:
Series_Name: City Road Map
Issue_Identification: 1991 Volume
Publication_Information:
Publication_Place: Richmond, Virginia
Publisher: VDOT
Cross_Reference:
Citation_Information:
Originator: USDA-NRCS
Publication_Date: 2000
Title: Enhanced DRGs of Virginia
Edition: 2000
Geospatial_Data_Presentation_Form: map
Series_Information:
Series_Name: Enhanced DRGs
Issue_Identification: Virginia Quads
Publication_Information:
Publication_Place: Ft Worth, Texas
Publisher: USDA-NRCS


Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Jurisdiction FIPS code assignment to the polygons of this dataset are correct except as noted here. (1)The code of Virginia does not assign the Chespaeake Bay waters to local jurisdictions. Therefore, the bay polygon has been assigned the fabricated FIPS code of 901 by DCR. Likewise, the offshore Atlantic waters within the 3 mile zone are assigned the fabricated FIPS code of 903. (2)The Hampton Roads area has been assigned as an area which Hampton has jurisdiction over, based on best available sources. (3)The state FIPS code (51) is not appended to any local jurisdiction FIPS code.
Logical_Consistency_Report:
All arcs are used to define jurisdiction boundaries or areas of assigned jurisdiction. There are no dangling arcs, nor does any polygon contain more than one label. There are, however, more polygons than there are jurisdictions because the shoreline is being used to define jurisdiction boundaries along the Atlantic and in the Chesapeake Bay. Thus many islands which are not connected to the mainland now appear as separate polygons of jurisdictions.
Completeness_Report:
This dataset is in need of additional refinement, including the following. (1) While it has been concluded that the Bay and Atlantic waters are not part of any jurisdiction in Virginia except the state itself, the border between the jurisdictions of Virginia and the state owned waters of the Bay and Atlantic is always fluctuating. Using shorelines as boundaries in this layer was limited to defining (a) the Chesapeake Bay from the tidal rivers and any adjoining land, and (b) the barrier islands of the Atlantic shore from the ocean. DOQQs were used for this task. The DOQQ for the northeast corner of the Tangier Island quad was insufficient for capturing the shorelines of the islands in that area. That portion of the south Potomac River shore which defines the border between Virginia and Maryland should also have been captured from DOQQs. Shore linework will eventually be replaced by the shorelines in the hydrography portion of the Virginia Base Map product. (2) Buena Vista boundaries (and the related portion of Rockbridge County boundaries) are approximate due to incomplete base maps. (3) No town boundaries are included in this coverage. They would be a welcome addition if a process to update and maintain them can be arranged. (4) Adjoining states claim boundaries which do not always coincide with the state boundary of Virginia as found in this layer. Attempts to resolve these discrepancies have been complicated by the lack of knowledge and documentation held by the agencies of these states on the source of the boundaries which they use. Furthermore, as in Virginia, there is more than one version of the boundaries of these states being used by the various state agencies of those states and by various federal agencies.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
The accuracy of boundaries for jurisdictions as they appear on the 7.5 minute quadrangle maps is unknown. USGS map accuracy standards for the 7.5 minute quadrangles would indicate minimumal distortion. However, it is apparent that jurisdiction boundaries which might be intended to be coterminous with ridge lines do not always follow the ridge lines as defined during Virginia's watershed boundary delineations as performed on DRGs. It is unclear as to whether or not these jurisdiction boundaries should therefore be moved to where DCR has delineated watershed boundaries. Such adjustments have been performed in this version but noted where they have occurred due to the indecision. Other potential problems are due to the age of the source maps rather than in the cartographic representation of the boundaries as made on the maps. The latest seamless DRGs were used in this task. Boundaries from these 7.5 minute maps were compared to those defined in the VDOT county and city map series. Inconsistencies were researched to determine the most accurate representation. While resulting accuracies are sufficient for work at the state scope, they are not as accurate as those that could be developed by the jurisdictions themselves in some cases. Some updates were done from maps which could not attain minimal RMS error when digitized. Updates to linework performed in version 2004 produced improved accuracies due to the ability to capture linework off of zoomed-in DRGs. Updates to the shorelines, however, are even more current and precise since they were captured from DOQQs. Atlantic and Chesapeake Bay shore boundaries are always changing, however, due to rapidly shifting sands and tidal fluctuations. Therefore all shorelines are approximate despite attempts to capture them in detail. Similar erosion based changes occur along the many stretches of the southern shoreline of the Potomac River that define the boundary between Virginia and Maryland. An issue which arises from this erosion is whether or not the boundary changes along with the shoreline. Discussions with state employees who were deemed to have some knowledge of this issue indicates that they do.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: 0.61 meters
Horizontal_Positional_Accuracy_Explanation: ground distance resolution
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: ISSL
Publication_Date: 1989
Title: VirGIS jurisdiction boundaries, version 1
Source_Scale_Denominator: 24000
Type_of_Source_Media: USGS 7.5 minute quads
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1949
Ending_Date: 1987
Source_Currentness_Reference: out of date
Source_Citation_Abbreviation: 1989 jurisdiction bounds
Source_Contribution: base upon which updates were made for version 1995
Source_Information:
Source_Citation:
Citation_Information:
Originator: DCR-DSWC
Publication_Date: 1995
Title: VirGIS jurisdiction boundaries, version 1995
Source_Scale_Denominator: 24000
Type_of_Source_Media: USGS 7.5 minute quads
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1949
Ending_Date: 1987
Source_Currentness_Reference: out of date
Source_Citation_Abbreviation: 1995 jurisdiction bounds
Source_Contribution: base upon which updates were made for version 2004
Process_Step:
Process_Description:
Digitize - the refined linework for jurisdiction boundaries and 6th order hydrologic unit (hu) boundaries was captured by overlaying version 1995 of the jurisdiction/hu dataset on enhanced DRGs and performing heads-up digitizing of linework needing refinement.
Process_Date: 200208
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Gina Beale
Contact_Organization: VA DCR-DSWC
Process_Step:
Process_Description:
Update - where city/county boundaries had been changed since the date of the DRG publications, the previously captured linework of these changes were inserted into the refined linework. If changes had not been previously captured, the best representation of those changes were obtained and captured, after which they were added to this dataset.
Process_Date: 200210
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Gina Beale and Andrea Styles
Contact_Organization: VA DCR-DSWC
Process_Step:
Process_Description:
Additions - mid-Bay boundary was created via spatial processing. Other open water boundaries were added, including those in Atlantic.
Process_Date: 200302
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Andrea Styles
Contact_Organization: VA DCR-DSWC
Process_Step:
Process_Description:
Label Attribution - FIPS codes were added to the polygon attribute table during editing. This included the FIPS of the jurisdiction which the polygon lied within and the FIPS of the jurisdiction which the courts of said jurisdiction have jurisdiction over.
Process_Date: 200404
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Gina Beale
Contact_Organization: VA DCR-DSWC
Process_Step:
Process_Description:
Attribute Arcs - the boundary lines of this data set were attributed with references to the source of each arc.
Process_Date: 200407
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Gina Beale
Contact_Organization: VA DCR-DSWC
Process_Step:
Process_Description:
Project - the joint jurisdiction boundary & NWBD boundary cover was projected from the UTM plane coordinate system (latest zone to be edited) to the Lambert projection noted in the spatial_reference_information section below.
Process_Date: 200408
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Gina Beale
Contact_Organization: VA DCR-DSWC
Process_Step:
Process_Description:
Dissolve - this data set created by dissolving (on FIPS and FIPS2) the the cover of combined jurisdiction and watershed boundaries as digitized for NWBD development in Virginia.
Process_Date: 200408
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Gina Beale
Contact_Organization: VA DCR-DSWC


Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Label point
Point_and_Vector_Object_Count: 173
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 1119
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains
Point_and_Vector_Object_Count: 174


Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Lambert Conformal Conic
Lambert_Conformal_Conic:
Standard_Parallel: 37.0
Longitude_of_Central_Meridian: 39.5
Latitude_of_Projection_Origin: -79.5
False_Easting: 0.00000
False_Northing: 0.00000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 1.0
Ordinate_Resolution: 1.0
Planar_Distance_Units: METERS
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137
Denominator_of_Flattening_Ratio: 298.257222101


Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: BVA04_L.AAT
Entity_Type_Definition: attributes of lines in cover
Entity_Type_Definition_Source: ESRI
Attribute:
Attribute_Label: FNODE#
Attribute_Definition: internal number of from-node
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 1089
Attribute:
Attribute_Label: TNODE#
Attribute_Definition: internal number of to-node
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 1089
Attribute:
Attribute_Label: LPOLY#
Attribute_Definition: internal number of polygon to the left of arc
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 172
Attribute:
Attribute_Label: RPOLY#
Attribute_Definition: internal number of the polygon to the right of arc
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 173
Attribute:
Attribute_Label: LENGTH
Attribute_Definition: length of arc in cover units
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 3.001
Range_Domain_Maximum: 85707.51
Attribute:
Attribute_Label: BVA04_L#
Attribute_Definition: internal feature number
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 1224
Attribute:
Attribute_Label: BVA04_L-ID
Attribute_Definition: user-assigned feature number
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 7
Range_Domain_Maximum: 12851
Attribute:
Attribute_Label: SOURCE
Attribute_Definition: a code defining source of linework
Attribute_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 1
Enumerated_Domain_Value_Definition:
Captured from lines found on USDA DRGs of USGS 7.5 minute quads.
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2
Enumerated_Domain_Value_Definition:
Shorelines captured from DOQQs where they define jurisdiction boundaries. This code applies to arcs defining local jurisdiction lands from state land along the Chesapeake Bay or Atlantic Ocean.
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 3
Enumerated_Domain_Value_Definition:
Apparent limit added across tidal waters to separate tidal waters within a jurisdiction from the Chesapeake Bay or Atlantic Ocean.
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 4
Enumerated_Domain_Value_Definition: from 2000 TIGER
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5
Enumerated_Domain_Value_Definition: from jurisdiction supplied maps
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 6
Enumerated_Domain_Value_Definition: Lines derived by DCR where no other definitive source existed.
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 7
Enumerated_Domain_Value_Definition:
Linework developed by DCR using USDA DRGs of USGS 7.5 minute quads as the basis. These lines do not exist on the maps.
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 8
Enumerated_Domain_Value_Definition:
Linework developed by DCR using NOAA charts as the basis. These lines do not exist on the charts
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 9
Enumerated_Domain_Value_Definition:
Apparent limit added across tidal waters to separate tidal waters within a jurisdiction from the Chesapeake Bay or Atlantic Ocean. These differ from source value 3 in that they are also watershed boundaries.
Enumerated_Domain_Value_Definition_Source: VADCR
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 10
Enumerated_Domain_Value_Definition: from VDOT source materials
Enumerated_Domain_Value_Definition_Source: VADCR
Detailed_Description:
Entity_Type:
Entity_Type_Label: BVA04_L.PAT
Entity_Type_Definition: attributes of polygons in cover
Entity_Type_Definition_Source: ESRI
Attribute:
Attribute_Label: AREA
Attribute_Definition: area of polygon in square coverage units
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 182.44
Range_Domain_Maximum: 2533633512.01
Attribute:
Attribute_Label: PERIMETER
Attribute_Definition: perimeter of polygon in coverage units
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 63.60
Range_Domain_Maximum: 2333130.57
Attribute:
Attribute_Label: BVA04_L#
Attribute_Definition: internal feature number
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 173
Attribute:
Attribute_Label: BVA04_L-ID
Attribute_Definition: user-assigned feature number
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 172
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
Either the federal code for the jurisdiction within VA (1-840) or a code assigned to areas of the state not within any local jurisdiction (901-903). Codes less than 500 are for counties, those between 500 and 899 are cities.
Attribute_Definition_Source: US Commerce and VA DCR
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 001
Range_Domain_Maximum: 903
Attribute:
Attribute_Label: JURIS
Attribute_Definition: name of jurisdiction
Attribute_Definition_Source: jurisdictions of VA
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: political units of Virginia
Codeset_Source: State of Virginia
Attribute:
Attribute_Label: FIPS2
Attribute_Definition:
Federal jurisdiction code for the local Virginia jurisdiction which has jurisdiction over the area of the polygon. This field's value will be different than that of FIPS only for areas within Virginia that are not within any local jurisdiction. Codes less than 500 are for counties, those between 500 and 899 are cities.
Attribute_Definition_Source: US Commerce
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 001
Range_Domain_Maximum: 840
Detailed_Description:
Entity_Type:
Entity_Type_Label: BVA04_L.AREA
Entity_Type_Definition: area of jurisdictions
Entity_Type_Definition_Source: VA DCR
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
Either the federal code for the jurisdiction within VA (1-840) or a code assigned to areas of the state not within any local jurisdiction (901-903). Codes less than 500 are for counties, those between 500 and 899 are cities.
Attribute_Definition_Source: US Commerce and VA DCR
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 001
Range_Domain_Maximum: 903
Attribute:
Attribute_Label: FIPS2
Attribute_Definition:
Federal jurisdiction code for the local Virginia jurisdiction which has jurisdiction over the area of the polygon. This field's value will be different than that of FIPS only for areas within Virginia that are not within any local jurisdiction. Codes less than 500 are for counties, those between 500 and 899 are cities.
Attribute_Definition_Source: US Commerce
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 001
Range_Domain_Maximum: 840
Attribute:
Attribute_Label: FIPSAC
Attribute_Definition:
The area within jurisdiction FIPS in acres as calculated from the cover bva04_l while in an albers projection, North American standards.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1127.79
Range_Domain_Maximum: 934675.50
Attribute:
Attribute_Label: FIPS2AC
Attribute_Definition:
The area which jurisdiction FIPS has jurisdiction over, in acres, as calculated from the cover bva04_l while in an albers projection, North American standards.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 0.00
Range_Domain_Maximum: 773986.40


Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Karl Huber
Contact_Organization: Virginia Dept. of Conservation & Recreation - DSWC
Contact_Address:
Address_Type: mailing and physical address
Address: 203 Governor Street, Suite 206
City: Richmond
State_or_Province: Virginia
Postal_Code: 23219-2094
Country: USA
Contact_Voice_Telephone: 804 371 7484
Contact_Facsimile_Telephone: 804 371 2630
Contact_Electronic_Mail_Address: karl.huber@dcr.virginia.gov
Hours_of_Service: 0830-1800
Resource_Description: statewide 1:24000 jurisdiction boundaries
Distribution_Liability: none
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ARC/INFO export file of cover
Format_Version_Number: 7.2.1
File_Decompression_Technique:
Uncompressed (ESRI) export has been Lempel-Ziv compressed. Uncompress on UNIX or use WinZip.
Transfer_Size: 2.91 MB in compressed form
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: DCR ftp site
Access_Instructions:
Email distribution contact to request this data via ftp. Instructions for retrieval will be sent back.
Online_Computer_and_Operating_System: Sun Enterprise with Solaris (UNIX).
Fees: none
Ordering_Instructions: may be ordered by phone but email preferred
Turnaround: a couple of days max if requeseted in native form
Custom_Order_Process:
If you cannot use this layer in the stated projection and datum, and you cannot reproject it yourself, it can be requested from DCR in another projection.


Metadata_Reference_Information:
Metadata_Date: 20040813
Metadata_Review_Date: 20040830
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Karl Huber
Contact_Organization: Virginia Dept. of Conservation & Recreation - DSWC
Contact_Address:
Address_Type: mailing and physical address
Address: 203 Governor Street, Suite 206
City: Richmond
State_or_Province: Virginia
Postal_Code: 23219-2094
Country: USA
Contact_Voice_Telephone: 804 371 7484
Contact_Facsimile_Telephone: 804 371 2630
Contact_Electronic_Mail_Address: karl.huber@dcr.virginia.gov
Hours_of_Service: 0830-1800
Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Access_Constraints: none

Generated by mp version 2.5.4 on Tue Apr 4 13:21:18 2006