Geospatial data about Pittsylvania County, Virginia Parcels. Export to CAD, GIS, PDF, CSV and access via API.
GIS Layer showing the 2002 VBMP (Virginia Base Mapping Project) County Boundary of Pittsylvania County with their related 2002 VBMP County Boundary Data.
GDB Version: ArcGIS Pro 3.3Additional Resources:Shapefile DownloadShapefile Download (Clipped to VIMS shoreline)Administrative Boundary Data Standard REST Endpoint (Unclipped) - REST Endpoint (Clipped)The Administrative Boundary feature classes represent the best available boundary information in Virginia. VGIN initially sought to develop an improved city, county, and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from an extraction of features 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 appropriate feature classes where locality data were a superior representation of boundaries. Administrative Boundary geodatabase and shapefiles are unclipped to hydrography features by default. The clipped to hydro dataset is included as a separate shapefile download below.
These parcel boundaries represent legal descriptions of property ownership, as recorded in various public documents in the local jurisdiction. The boundaries are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys. Tax parcel boundaries have not been edge-matched across municipal boundaries.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Data was compiled from published sources by US Geological Survey geoscientists Mark J. Mihalasky, Susan M. Hall and Robert A. Zielinski. This dataset was provided to the U.S. Energy Information Administration in February of 2019 to facilitate updating of national uranium resource distribution maps. The location of uranium provinces, districts and select important deposits located outside of these broader regions was taken from a variety of sources listed alphabetically below.Adams S.S.; Smith R.B., 1981, Geology and recognition criteria for sandstone uranium deposits in mixed fluvial-shallow marine sedimentary sequences, South Texas; U.S. Department of Energy Report GJBX-4(81), 145 p.Colorado Geological Survey, 2018, Uranium Districts – Colorado; published on the Colorado Geological Survey website at http://coloradogeologicalsurvey.org/energy-resources/uranium2/map/.Chenoweth, W.L., 1980, Uranium in Colorado; Rocky Mountain Association of Geologists, 1980 Symposium, p. 217-224Gloyn, R.W.; Bon, R.L.; Wakefield, S.; Krahulec, K., 2005, Uranium and vanadium map of Utah; Map 215, Utah Department of Natural Resources, Utah Geological Survey, 1:750,000 scale, 1 sheet. Metadata download at: https://gis.utah.gov/data/energy/uranium/Gregory R.W., 2016, Uranium: Geology and Applications; Wyoming State Geological Survey Public Information Circular No 46, 36 p.Keith, S.B.; Gest, D.E.; DeWitt, E; 1983, Metallic mineral districts of Arizona; Arizona Bureau of Geology and Mineral Technology, Geological Survey Branch, Tucson, AZ, 1:1,000,000 scale, 1 sheetKyle L, Beahm D, 2013, NI 43-101 preliminary economic assessment update (revised), Coles Hill uranium property, Pittsylvania County, VA USA; prepared by Lyntek Incorporated, Lakewood, CO; 2013, 126 p. Figure 1.1.McLemore, V.T. and Chenoweth, W.L., 1989, Uranium resources in New Mexico; New Mexico Bureau of Mines and Minerals Resources, Resource Map 18, 36 p. Available at: https://geoinfo.nmt.edu/faq/mining/home.html
This layer contains the boundaries of the VDOT Area Headquarters (AHQ) zones of responsibility. These areas are important as they designate which AHQ is responsible for road maintenance in that area. Additionally, in certain areas of Virginia (the Virginia independent cities, and Arlington and Henrico Counties), maintenance responsibility of local roads is devolved to the local government. These areas have been been removed.July 2016 changes - changed Residency and Residency Codes for the AHQ's in the new Residencies of Louisa and AbingdonChanges made in July 2015 to change several Area HQ boundaries for Leesburg Residency / Loudoun County. These changes result in some non-contiguous island and donut polygons. These are necessary to transfer certain unpaved routes from one Area to another. Changes made in Franklin Co.
This is a polygon coverage of Physiographic Divisions in the conterminous United States cropped to the state boundary of Virginia. It was automated from Fenneman's 1:7,000,000-scale map, "Physical Divisions of the United States," which is based on eight major 1946 divisions, 25 provinces, and 86 sections representing distinctive areas having common topography, rock types and structure, and geologic and geomorphic history.
Polygon layer representing the Fiscal Stress of Virginia's Cities and Counties. Data from VA Dept of Housing and Community Development and Virginia Admin Boundaries Dataset (VGIN). For more information please see the current report: https://www.dhcd.virginia.gov/fiscal-stress
This data set contains the boundaries for Virginia Department of Transportation residencies. It provides information on VDOT residency and district codes and names. The main change since the last release was to move from reliance on census boundaries to using the boundaries provided by the Virginia Geographic Information Network (VGIN). Those boundaries were dissolved to form these polygons with the exception of one boundary in Culpeper County which was modified by tracing the outline of an Area Headquarter boundary and merging this polygon with that covering Louisa County.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Geospatial data about Pittsylvania County, Virginia Parcels. Export to CAD, GIS, PDF, CSV and access via API.