Virginia Dept. of Conservation and Recreation - DSWC 20040816 2004 vector digital data jurisdiction boundaries 2004 update Richmond, Virginia Virginia DCR-DSWC Basis is the USGS 7.5 minute topo quad DRGs withheld bva04_dp_Dissolve Jurisdiction boundaries for all counties (95) and cities (39) in Virginiaat a precision that is, at a minimum, from heads-up digitizing off of DRGs. These are the jurisdiction boundaries used by Virginia DCR to geocodeany geographic information with a jurisdiction FIPS code. This datasetwas developed and is maintained at an accuracy intended to meet the statewide mission of DCR and are not intended to be a legal representation of any single jurisdictional boundary. 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). Intended Use:This dataset is intended to represent jurisdictional boundaries at a statewide level for the express purpose of geocoding DCR data. While created and maintained with reasonable care, it should be considered planning grade for single jurisdictions or small regions. Preference should always be given to boundary files provided by the respective jurisdictions.Origin:Version 1 jurisdiction boundaries were originally digitized at ISSL,VPI&SU in 1989 off of the USGS 7.5 minute quadrangle maps. Somemodifications 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 quadmaps or maps supplied by various jurisdictions and the Virginia DOT,all of which were at a better scale than the quads but were not alwaysdone to map accuracy standards. These newly digitized products were usedto replace older existing boundaries. Changes were made to theboundaries of 34 jurisdictions between the first and 1995 versions.Version 2004:Version 2004 varies from version 1995 in many ways. The major differencesare that almost all of the linework has been recaptured at a betterresolution, and linework has been added to delineate what is in ajurisdiction from what a local government has jurisdiction over. Theimproved resolution was realized by overlaying the linework of version 1995onto enhanced DRGs and recapturing linework via heads-up digitizing onimages which are enlarged beyond the 1:24,000 scale of the original papermaps. The determinations of what areas of the state are truly within anylocal jurisdictions versus being within the state but outside of all localjurisdictions was assisted by the Virginia Attorney General's Office.Additionally, as these boundaries were being recaptured as part of theNWBD development, jurisdiction boundaries that coexisted as watershedboundaries were modified to align with the watershed boundaries as theywere defined in the NWBD versus aligning with jurisdiction boundariesas they were drawn on the USGS topographic quads. These situations arenoted in the line attribute table.Other than the improved linework due to the DRG use and NWBD developmentas noted above, the following changes were made between versions 1995 and2004:(1) Clifton Forge is removed as it is no longer a city. (2) The shorelineboundaries of jurisdictions bordering the Chesapeake Bay and Atlantic Oceanhave been recaptured off of DOQQs. (3) The offshore waters of Virginia havebeen added to the 3 nautical mile limit. (4) The boundary between PrinceGeorge and Sussex and between Sussex and Surry has been altered (DisputantaSouth quad). (5) The boundary of Emporia has been altered. (6) The boundarybetween Lynchburg and Amherst was altered. (7) The boundary between Danvilleand Pittsylvania Co was altered. (8) The boundary of Williamsburg has beenaltered based on its representation on their web site. (9) The stateboundary has been altered from Smith Point to Rhodes Point. In particular,it originates further southeast on the line extending from Smith Point thanpreviously portrayed on 7.5 minute topo maps. (10) The boundary betweenFauquier and Prince William has been altered. (11) The boundary betweenGiles and Monroe County, WV has been altered. (12) The boundary betweenLouisa and Goochland was altered to reflect the boundary as displayed onVDOT county maps. (13) Minor adjustments were made to the boundary ofNorton. (14) Minor adjustments were made to the boundary of Bristol.Territorial waters within the Commonwealth have been determined with theassistance of the Virginia Attorney General's Office. As advised by thatoffice, and in accordance with section 15.2-3105 of the Code of Virginia,Chesapeake Bay waters, Atlantic Ocean waters, and the tidal tributaries tothese bodies of water, are not considered part of any local jurisdiction.In other words, "the normal activities of counties and cities do not extendoff shore". Section 15.2-3105 extends the boundary of local jurisdictionsalong the Chesapeake Bay or Atlantic Ocean to "embrace all wharfs, piers,docks, and other structures, except bridges and tunnels that have been ormay hereafter be erected along the waterfront". Therefore shorelines thatinclude these structures are now used to define the jurisdictionboundaries along the Chesapeake Bay and Atlantic Ocean. While tidal riversof these bodies are also part of this decree, it would be difficult toaccurately portray local jurisdiction boundaries excluding all tidal watersof the Bay and the Atlantic. It would also produce a version of jurisdictionboundaries for Virginia unlikely to be used by the agencies of the statewho this layer is intended to assist. Therefore, an apparent limit arc hasbeen added across tidal waters to delineate the Chesapeake Bay and AtlanticOcean proper from their tidal tributaries. These artificial boundaries havebeen attributed as such.The same legal source also advises that in accordance with Sections16.1-69.29 and 17.1-516, the local jurisdictions of the Commonwealth havebeen given "concurrent territorial jurisdiction [to the district and circuitcourts of counties on each side of any river, watercourse, or bay,] over somuch thereof as shall be opposite to such counties". Likewise, localjurisdictions have been authorized by Section 29.1-744.C to enact ordinancesregulating vessels and the conduct of people within the territorial limits,including the marginal adjacent Atlantic Ocean. This section extends theterritorial limits of the seaside jurisdictions out three miles into theAtlantic Ocean. Accordingly, this version of the jurisdiction boundariescontains the delineations of the Chesapeake Bay and Atlantic Ocean asnecessary to portray these stated territorial jurisdictions, including anequidistance mid-Bay boundary that will not align with the mid-Bayboundary found in federal spatial layers showing jurisdiction boundariesin Virginia.It is possible to only display the arcs defining jurisdictions, versus alsoshowing arcs which only define areas that jurisdictions have jurisdictionover. One method would be to dissolve this shapefile on the fips and/orfips2 field. Dissolving on fips will create a new polygon shapefilecontaining areas within the local jurisdiction. This shapefile will havea separate polygon for the Chesapeake Bay and the Atlantic territorialwaters. Dissolving on fips2 will result in a new polygon shapefilecontaining all the areas which the local jurisdictions have jurisdictionover. This is particularly relevant if you are using ArcView. en REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground. 20010801 present Publication date of sources Complete Updated whenever known boundary changes are made and maps of said changescan be obtained. However, there is no process in place to assure that DCRis aware of such changes when they occur.Upcoming modifications will include the infusion of boundaries fromlocal governments where those boundaries are agreeable to parties onboth sides, ridge modifications from more precise topographic sources,and more current and precise shorelines from the hydrography developedfrom the VA Base Map Imagery. -83.837829 -75.094146 39.471482 36.462665 -373533.577122 379400.005252 60037.551354 385287.791812 Esri Metadata Portal Required Keywords boundaries jurisdiction cities counties none Virginia none Crediting VA DCR for dataset development is requested. Karl Huber Virginia Dept. of Conservation & Recreation - DSWC mailing and physical address

203 Governor Street, Suite 206

Richmond Virginia 23219-2094 USA 804 371 7484 804 371 2630 karl.huber@dcr.virginia.gov 0830-1800 DCR-DSWC is credited with the linework revisions of version 1995. The almostcomplete redigitizing of version 2004 from DRGs was done by Virginia Tech -Biological Systems Engineering staff working at DCR-DSWC. Legal assistancewas provided by Frederick Fisher, Senior Assistant Attorney General in theVirginia Office of the Attorney General. ESRI ArcCatalog 9.3.1.3500 ISSL 1989 1 map jurisdiction boundaries version 1 Blacksburg, Virginia ISSL VDOT 19930101 1993 map County Road Map Atlas 1993 Volume Richmond, Virginia VDOT VDOT 1992 1991 map City Road Map 1991 Volume Richmond, Virginia VDOT USDA-NRCS 2000 2000 map Enhanced DRGs Virginia Quads Ft Worth, Texas USDA-NRCS Shapefile Jurisdiction FIPS code assignment to the polygons of this dataset arecorrect except as noted here.(1)The code of Virginia does not assign the Chespaeake Bay waters tolocal jurisdictions. Therefore, the bay polygon has been assigned thefabricated FIPS code of 901 by DCR. Likewise, the offshore Atlanticwaters within the 3 mile zone are assigned the fabricated FIPS code of903. (2)The Hampton Roads area has been assigned as an area which Hamptonhas jurisdiction over, based on best available sources. (3)The stateFIPS code (51) is not appended to any local jurisdiction FIPS code. All arcs are used to define jurisdiction boundaries or areas of assignedjurisdiction. There are no dangling arcs, nor does any polygon contain morethan one label. There are, however, more polygons than there arejurisdictions because the shoreline is being used to define jurisdictionboundaries along the Atlantic and in the Chesapeake Bay. Thus many islandswhich are not connected to the mainland now appear as separate polygons ofjurisdictions. 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 partof any jurisdiction in Virginia except the state itself, the border betweenthe jurisdictions of Virginia and the state owned waters of the Bay andAtlantic is always fluctuating. Using shorelines as boundaries in this layerwas limited to defining (a) the Chesapeake Bay from the tidal rivers and anyadjoining land, and (b) the barrier islands of the Atlantic shore from theocean. DOQQs were used for this task. The DOQQ for the northeast corner ofthe Tangier Island quad was insufficient for capturing the shorelines of theislands in that area. That portion of the south Potomac River shore whichdefines the border between Virginia and Maryland should also have been capturedfrom DOQQs. Shore linework will eventually be replaced by the shorelines inthe hydrography portion of the Virginia Base Map product. (2) Buena Vistaboundaries (and the related portion of Rockbridge County boundaries) areapproximate due to incomplete base maps. (3) No town boundaries are includedin this coverage. They would be a welcome addition if a process to update andmaintain them can be arranged. (4) Adjoining states claim boundaries which donot always coincide with the state boundary of Virginia as found in this layer.Attempts to resolve these discrepancies have been complicated by the lack ofknowledge and documentation held by the agencies of these states on thesource of the boundaries which they use. Furthermore, as in Virginia, thereis more than one version of the boundaries of these states being used by thevarious state agencies of those states and by various federal agencies. The accuracy of boundaries for jurisdictions as they appear on the 7.5minute quadrangle maps is unknown. USGS map accuracy standards forthe 7.5 minute quadrangles would indicate minimumal distortion.However, it is apparent that jurisdiction boundaries which might beintended to be coterminous with ridge lines do not always follow theridge lines as defined during Virginia's watershed boundary delineationsas performed on DRGs. It is unclear as to whether or not thesejurisdiction boundaries should therefore be moved to where DCR hasdelineated watershed boundaries. Such adjustments have been performed inthis version but noted where they have occurred due to the indecision.Other potential problems are due to the age of the source maps ratherthan in the cartographic representation of the boundaries as made on themaps. The latest seamless DRGs were used in this task. Boundaries fromthese 7.5 minute maps were compared to those defined in the VDOT countyand city map series. Inconsistencies were researched to determine themost accurate representation. While resulting accuracies are sufficientfor work at the state scope, they are not as accurate as those thatcould be developed by the jurisdictions themselves in some cases.Some updates were done from maps which could not attain minimal RMSerror when digitized. Updates to linework performed in version 2004produced improved accuracies due to the ability to capture linework offof zoomed-in DRGs. Updates to the shorelines, however, are even morecurrent and precise since they were captured from DOQQs. Atlantic andChesapeake Bay shore boundaries are always changing, however, due torapidly shifting sands and tidal fluctuations. Therefore all shorelinesare approximate despite attempts to capture them in detail. Similarerosion based changes occur along the many stretches of the southernshoreline of the Potomac River that define the boundary between Virginiaand Maryland. An issue which arises from this erosion is whether or notthe boundary changes along with the shoreline. Discussions with stateemployees who were deemed to have some knowledge of this issue indicatesthat they do. 0.61 meters ground distance resolution ISSL 1989 24000 USGS 7.5 minute quads 1949 1987 out of date 1989 jurisdiction bounds base upon which updates were made for version 1995 DCR-DSWC 1995 24000 USGS 7.5 minute quads 1949 1987 out of date 1995 jurisdiction bounds base upon which updates were made for version 2004 Digitize - the refined linework for jurisdiction boundaries and6th order hydrologic unit (hu) boundaries was captured by overlayingversion 1995 of the jurisdiction/hu dataset on enhanced DRGs andperforming heads-up digitizing of linework needing refinement. 200208 Gina Beale VA DCR-DSWC Update - where city/county boundaries had been changed since the dateof the DRG publications, the previously captured linework of thesechanges were inserted into the refined linework. If changes had notbeen previously captured, the best representation of those changes wereobtained and captured, after which they were added to this dataset. 200210 Gina Beale and Andrea Styles VA DCR-DSWC Additions - mid-Bay boundary was created via spatial processing.Other open water boundaries were added, including those in Atlantic. 200302 Andrea Styles VA DCR-DSWC Label Attribution - FIPS codes were added to the polygon attributetable during editing. This included the FIPS of the jurisdiction whichthe polygon lied within and the FIPS of the jurisdiction which thecourts of said jurisdiction have jurisdiction over. 200404 Gina Beale VA DCR-DSWC Attribute Arcs - the boundary lines of this data set were attributedwith references to the source of each arc. 200407 Gina Beale VA DCR-DSWC Project - the joint jurisdiction boundary & NWBD boundary cover wasprojected from the UTM plane coordinate system (latest zone to be edited)to the Lambert projection. 200408 Gina Beale VA DCR-DSWC Dissolve - this data set created by dissolving (on FIPS and FIPS2) thethe cover of combined jurisdiction and watershed boundaries as digitizedfor NWBD development in Virginia. 200408 Gina Beale VA DCR-DSWC Project - the standard version of the cover of this layer was projectedto decimal degrees for eventual use in ArcView. 200408 Gina Beale VA DCR-DSWC Format Conversion - the decimal degree version of the cover of thislayer was converted to a shapefile using the ARCSHAPE command. 200408 Gina Beale VA DCR-DSWC Metadata imported. withheld 08504700 Dataset copied. withheld 08534800 Dataset copied. withheld 08323700 Dataset copied. withheld 10051000 Metadata imported. withheld 20080211 14205900 Dataset copied. withheld 20080212 09510000 Dataset copied. withheld 20100129 14155300 Dataset copied. withheld 20100129 14311100 Dataset copied. withheld 20130506 10491100 Vector Simple FALSE 0 TRUE FALSE coordinate pair 0.000000 0.000000 meters North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983 Lambert_Conformal_Conic_Virginia 1.000000 Explicit elevation coordinate included with horizontal coordinates va_counties attributes of lines in shapefile ESRI Feature Class 0 COUNTYNAME OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. FIPS FIPS SmallInteger 2 5 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. SHAPE feature type ESRI polyline line defining polygon ESRI Coordinates defining the features. Shape Geometry 8 0 0 Shape Feature geometry. ESRI Coordinates defining the features. COUNTYNAME String 50 0 0 Shape.STArea() Shape.STArea() Double 0 0 0 Shape.STLength() Shape.STLength() Double 0 0 0 bva04_dp.dbf attributes of polygons in shapefile ESRI SHAPE feature type ESRI polygon polygon ESRI AREA area of polygon in square shapefile units ESRI 0.00000 0.259040 PERIMETER perimeter of polygon in shapefile units ESRI 0.000643 24.578 5 BVA04_D_ internal feature number ESRI 1 173 BVA04_D_I user-assigned feature number ESRI 1 172 FIPS Either the federal code for the jurisdiction within VA (1-840)or a code assigned to areas of the state not within any localjurisdiction (901-903). Codes less than 500 are for counties,those between 500 and 899 are cities. US Commerce and VA DCR 001 903 FIPS2 Federal jurisdiction code for the local Virginia jurisdiction which hasjurisdiction over the area of the polygon. This field's value will bedifferent than that of FIPS only for areas within Virginia that are notwithin any local jurisdiction. Codes less than 500 are for counties,those between 500 and 899 are cities. US Commerce 001 840 JURIS name of jurisdiction jurisdictions of VA political units of Virginia State of Virginia fipsac.dbf area of jurisdictions VA DCR FIPS Either the federal code for the jurisdiction within VA (1-840)or a code assigned to areas of the state not within any localjurisdiction (901-903). Codes less than 500 are for counties,those between 500 and 899 are cities. US Commerce and VA DCR 001 903 FIPSAC The area within jurisdiction FIPS in acres as calculated from the coverbva04_l while in an albers projection, North American standards. ESRI 1127.79 934675.50 5 fips2ac.dbf area jurisdictions have jurisdiction over VA DCR FIPS2 Federal jurisdiction code for the local Virginia jurisdiction which hasjurisdiction over the area of the polygon. This field's value will bedifferent than that of FIPS only for areas within Virginia that are notwithin any local jurisdiction. Codes less than 500 are for counties,those between 500 and 899 are cities. US Commerce 001 840 FIPS2AC The area which jurisdiction FIPS2 has jurisdiction over, in acres, ascalculated from the cover bva04_l while in an albers projection,North American standards. ESRI 0.00 773986.40 5 Karl Huber Virginia Dept. of Conservation & Recreation - DSWC mailing and physical address

203 Governor Street, Suite 206

Richmond Virginia 23219-2094 USA 804 371 7484 804 371 2630 karl.huber@dcr.virginia.gov 0830-1800 statewide 1:24000 jurisdiction boundaries none shapefile made from ARC/INFO cover 3.3 All files of the shapefile and related database tables have beencompressed and collected into a ZIP file. Uncompress on XP or useWinZip. 6.15 MB for all files of shapefile 0.000 withheld Email distribution contact to request this data via ftp.Instructions for retrieval will be sent back. Sun Enterprise with Solaris (UNIX). none may be ordered by phone but email preferred a couple of days max if requeseted in native form If you cannot use this layer in the stated projection and datum, andyou cannot reproject it yourself, it can be requested from DCR inanother projection. 20091228 20040830 Karl Huber Virginia Dept. of Conservation & Recreation - DSWC REQUIRED: The organization responsible for the metadata information. REQUIRED: The person responsible for the metadata information. mailing and physical address

203 Governor Street, Suite 206

Richmond Virginia 23219-2094 USA 804 371 7484 804 371 2630 karl.huber@dcr.virginia.gov 0830-1800 FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time none en 20250623 13581900 FALSE 20250623 18062800 20250623 18062800 va_counties 002 Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet <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.5.0'><WKT>PROJCS[&quot;NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet&quot;,GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433]],PROJECTION[&quot;Lambert_Conformal_Conic&quot;],PARAMETER[&quot;False_Easting&quot;,11482916.66666666],PARAMETER[&quot;False_Northing&quot;,3280833.333333333],PARAMETER[&quot;Central_Meridian&quot;,-78.5],PARAMETER[&quot;Standard_Parallel_1&quot;,36.76666666666667],PARAMETER[&quot;Standard_Parallel_2&quot;,37.96666666666667],PARAMETER[&quot;Latitude_Of_Origin&quot;,36.33333333333334],UNIT[&quot;Foot_US&quot;,0.3048006096012192],AUTHORITY[&quot;EPSG&quot;,2284]]</WKT><XOrigin>-111140599.99983302</XOrigin><YOrigin>-91532099.999618471</YOrigin><XYScale>7812.4999927240387</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0010240000009536748</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102747</WKID><LatestWKID>2284</LatestWKID></ProjectedCoordinateSystem> 1.0 Esri ArcGIS 13.5.0.57366 va_counties -373533.577122 379400.005252 385287.791812 60037.551354 1 -83.837829 -75.094146 39.471482 36.462665 1 ISO 19115 Geographic Information - Metadata DIS_ESRI1.0 dataset 002 withheld Local Area Network 0.000 Shapefile Enterprise Geodatabase Feature Class Lambert_Conformal_Conic_Virginia EPSG 5.3(9.0.0) 0 20250623