Geospatial data about Pittsylvania County, Virginia Parcels. Export to CAD, GIS, PDF, CSV and access via API.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

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.

The Virginia Geographic Information Network (VGIN) has coordinated the development and maintenance of a statewide Parcels data layer in conjunction with local governments across the Commonwealth. The Virginia Parcel dataset is aggregated as part of the VGIN Local Government Data Call update cycle. Localities are encouraged to submit data bi-annually and are included into the parcel dataset with their most recent geography.Attributes for these Virginia parcels are limited to locality identification and parcel id. Tax parcel boundaries have not been edge-matched across municipal boundaries but they are associated by local government FIPS and locality name.The boundaries are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys. Not all localities within the Commonwealth of Virginia have confirmed a digital record for parcel geography or submit data with a bi-annual frequency.GDB Version: ArcGIS Pro 3.3Additional Resources:Shapefile DownloadREST EndpointVirginia Parcels: Local Schema Tables

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 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.

The purpose of this data set is to provide a geographic representation of the location of each state mile marker sign in the Commonwealth, and is to be used in a number of other products and projects. The locations of state mile marker signs on interstates and primary routes are important sources for various traffic studies as well as information for travelers. This GIS layer displays the locations and corresponding information of state mile marker signs. The signs may have been placed close but not exactly at the mile point due to geographic restrictions.Attribute NameContentsFIDInternal Feature NumberShapeFeature GeometryHTRISDEFHTRIS Definition in the Roadway InventoryROADSIDELocations of Mile Marker Posts (Right, Left, or Median)LATITUDEGPS latitude for each Mile Marker point in decimal degreesLONGITUDEGPS longitude for each Mile Marker point in decimal degreesSIGNSTYLE0: Small & Non-MUTCD Compliant, 1: MUTCD Standard (D10-1, D10-2 or D10-3), 2: MUTCD Enhanced (D10-4 or D10-5)SIGNVALUENumeric Value from the Sign Text except NULL, -1, and -2 valuesSIGNTEXTFull Sign TextM_JURISDICMaintenance Jurisdiction Code

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).

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.

The main source of the crash data is owned and maintained by the Virginia Department of Motor Vehicle (DMV). DMV’s Traffic Records Electronic Data System (TREDS) is a state-of-the-art data system maintained by the DMV Highway Safety Office (HSO) that automates and centralizes all crash data in Virginia. Per data sharing use agreement with DMV, VDOT publishes the non-privileged crash data through Virginia Roads data portal. In providing this data, VDOT assumes no responsibility for the accuracy and completeness of the data. In the process of recording and compiling the data, some deletions and/or omissions of data may occur and VDOT is not responsible for any such occurrences. The most recent data contained in this dataset is preliminary and subject to change.

Please be advised that, under Title 23 United State Code – Section 407, this crash information cannot be used in discovery or as evidence in a Federal or State court proceeding or considered for other purposes in any action for damages against VDOT or the State of Virginia arising from any occurrence at the location identified.

All users shall comply with and be subject to all applicable laws and regulations, whether federal or state, in connection with any of the receipt and use of DMV data including, but not limited to, (1) the Federal Drivers Privacy Protection Act (18 U.S.C. § 2721 et seq.), (2) the Government Data Collection and Dissemination Practices Act (Va. Code § 2.2-3800 et seq.), (3) the Virginia Computer Crimes Act (Va. Code § 18.2-152.1 et seq.), (4) the provisions of Va. Code §§ 46.2-208 and 58.1-3, and (5) any successor rules, regulations, or guidelines adopted by DMV with regard to disclosure or dissemination of any information obtained from DMV records or files.

This service is Virginia data from the 2011 release of the Census Bureau TIGER/Line Shapefile for national counties or equivalent boundaries (tl_2011_us_county.shp)The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.The primary legal divisions of most States are termed counties. In Virginia, cities are independent of any county organization and thus constitute primary divisions. These incorporated places are known as independent cities and are treated as equivalent to counties for purposes of data presentation.The 2010 Census boundaries for counties and equivalent entities are as of January 1, 2010, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

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.

VDEQ Spring SITESThe VDEQ Spring SITES database contains data describing the geographic locations and site attributes of natural springs throughout the commonwealth. This data coverage continues to evolve and contains only spring locations known to exist with a reasonable degree of certainty on the date of publication. The dataset does not replace site specific inventorying or receptor surveys but can be used as a starting point. VDEQ's initial geospatial dataset of approximately 325 springs was formed in 2008 by digitizing historical spring information sheets created by State Water Control Board geologists in the 1970s through early 1990s. Additional data has been consolidated from the EPA STORET database, the U.S. Geological Survey's Ground Water Site Inventory (GWSI) and Geographic Names Inventory System (GNIS), the Virginia Department of Health SDWIS database, the Virginia DEQ Virginia Water Use Data Set (VWUDS), the Commonwealth of Virginia Division of Water Resources and Power Bulletin No. 1: "Springs of Virginia" by Collins et al., 1930 as well as several VDWR&P Surface Water Supply bulletins from the 1940's - 1950's. A 1992 Virginia Department of Game and Inland Fisheries / Virginia Tech sponsored study by Helfrich et al. titled "Evaluation of the Natural Springs of Virginia: Fisheries Management Implications", a 2004 Rockbridge County groundwater resources report written by Frits van der Leeden, and several smaller datasets from consultants and citizens were evaluated and added to the database when confidence in locational accuracy was high or could be verified with aerial or LIDAR imagery. Significant contributions have been made throughout the years by VDEQ Groundwater Characterization staff site visits as well as other geologists working in the region including: Matt Heller at Virginia Division of Geology and Mineral Resources (VDMME), Wil Orndorff at the Virginia Department of Conservation and Recreation Karst Program (VDCR), and David Nelms and Dan Doctor of the U.S. Geological Survey (USGS). Substantial effort has been made to improve locational accuracy and remove duplication present between data sources. Hundreds of spring locations that were originally obtained using topographic maps or unknown methods were updated to sub-meter locational accuracy using post-processed differential GPS (PPGPS) and through the use of several generations of aerial imagery (2002-2017) obtained from Virginia's Geographic Information Network (VGIN) and 1-meter LIDAR, where available. Scores of new spring locations were also obtained by systematic quadrangle by quadrangle analysis in areas of the Shenandoah Valley where 1-meter LIDAR datasets where obtained from the U.S. Geological Survey. Future improvements to the dataset will result when statewide 1-meter LIDAR datasets becomes available and through continued field work by DEQ staff and other contributors working in the region. Please do not hesitate to contact the author to correct mistakes or to contribute to the database.VDEQ_Springs_FIELD_MEASUREMENTSThe VDEQ Spring FIELD MEASUREMENTS database contains data describing field derived physio-chemical properties of spring discharges measured throughout the Commonwealth of Virginia. Field visits compiled in this dataset were performed from 1928 to 2019 by geologists with the State Water Control Board, the Virginia Division of Water and Power, the Virginia Department of Environmental Quality, and the U.S. Geological Survey with contributions from other sources as noted. Values of -9999 indicate that measurements were not performed for the referenced parameter. Please do not hesitate to contact the author to add data to the database or correct errors.VDEQ_Springs_WQThe VDEQ_Spring_WQ database is a geodatabase containing groundwater sample information collected from springs throughout Virginia. Sample specific information include: location and site information, measured field parameters, and lab verified quantifications of major ionic concentrations, trace element concentrations, nutrient concentrations, and radiological data. The VDEQ_Spring_WQ database is a subset of the VDEQ GWCHEM database which is a flat-file geodatabase containing groundwater sample information from groundwater wells and springs throughout Virginia. Sample information has been correlated via DEQ Well # and projected using coordinates in VDEQ_Spring_SITES database. The GWCHEM database is comprised of historic groundwater sample data originally archived in the United States Geological Survey (USGS) National Water Information System (NWIS) and the Environmental Protection Agency (EPA) Storage and Retrieval (STORET) data warehouse. Archived STORET data originated as groundwater sample data collected and uploaded by Virginia State Water Control Board Personnel. While groundwater sample data in the STORET data warehouse are static, new groundwater sample data are periodically uploaded to NWIS and spring laboratory WQ data reflect NWIS downloaded on 9/30/2019. Recent groundwater sample data collected by Virginia Department of Environmental Quality (DEQ) personnel as part of the Ambient Groundwater Sampling Program are entered into the database as lab results are made available by the Division of Consolidated Laboratory Services (DCLS). When possible, charge balances were calculated for samples with reported values for major ions including (at a minimum) calcium, magnesium, potassium, sodium, bicarbonate, chloride, and sulfate. Reported values for Nitrate as N, carbonate, and fluoride were included in the charge balance calculation when available. Field determined values for bicarbonate and carbonate were used in the charge balance calculation when available. For much of the legacy DEQ groundwater sample data, bicarbonate values were derived from lab reported values of alkalinity (as mg/CaCO3) under the assumption that there was no contribution by carbonate to the reported alkalinity value. Charge balance values are reported in the "Charge Balance" column of the GWCHEM geodatabase. The closer the charge balance value is to unity (1), the lower the assumed charge balance error.In order to preserve the numerical capabilities of the database, non- numeric lab qualifiers were given the following numeric identifiers:- (minus sign) = less than the concentration specified to the right of the sign-11110 = estimated-22220 = presence verified but not quantified-33330 = radchem non-detect, below sslc-4440 = analyzed for but not detected-55550 = greater than the concentration to the right of the zero-66660 = sample held beyond normal holding time-77770 = quality control failure. Data not valid.-88880 = sample held beyond normal holding time. Sample analyzed for but not detected. Value stored is limit of detection for proces in use.-11120 = Value reported is less than the criteria of detection.-9999 = no data (parameter not quantified)A more in depth descprition and hydrogeologic analysis of the database can be found hereAn in Depth data fact sheet can be found here