The Digital Geologic-GIS Map of Richmond National Battlefield Park and Vicinity, Virginia is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (rich_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (rich_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (rich_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (rich_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (rich_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (rich_geology_metadata_faq.pdf). Please read the rich_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Virginia Division of Geology and Mineral Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (rich_geology_metadata.txt or rich_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

GIS data provided by the City of Richmond, VA to promote ease of access to information and knowledgeability about the area. Available downloads include shapefiles for hydrology, soil, floodplains, and other data.

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) Database (MTDB). The MTDB 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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2010 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

The Digital Geologic-GIS Map of the Richmond Quadrangle, Virginia is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (rchm_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (rchm_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (rchm_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (rich_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (rich_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (rchm_geology_metadata_faq.pdf). Please read the rich_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Virginia Division of Geology and Mineral Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (rchm_geology_metadata.txt or rchm_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Point feature class representing Richmond Public Schools.

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) Database (MTDB). The MTDB 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 MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB 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.

Hospitals in the city of Richmond, Virginia. Originally derived from the ldmk_PointOfInterest feature class maintained by DIT-GIS.

This is the parcel lines used to build the parcel polygons.The shape length is the distance of the drawn line.The Legal Length is the distance of the known length from a deed or plat.Often these two do not agree because this GIS mapping is not legal surveys but mapping for tax assessments.

These data provide an accurate high-resolution shoreline compiled from imagery of Port of Richmond, VA . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coastal Cartographic Object Attribute...

Resource Protection Areas are used in the City's permitting processes, as State regulations and local ordinances can effect development activities in these areas. Development activities can have an impact upon water quality issues of the Chesapeake Bay tributaries within the City of Richmond.

City Parks owned and operated by the City of Richmond.

These data were automated to provide an accurate high-resolution historical shoreline of James River, Southeast Richmond, Virginia suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://www.fisheries.noaa.gov/inport/item/39808

This data archive is a collection of GIS files and FGDC metadata prepared in 1995 for the Northampton County Planning Office by the Virginia Coast Reserve LTER project at the University of Virginia with support from the Virginia Department of Environmental Quality (DEQ) and the National Science Foundation (NSF). Original data sources include: 1:100,000-scale USGS digital line graph (DLG) hydrography and transportation data; 1:6,000-scale boundary, road, and railroad data for the town of Cape Charles from VDOT; 1:190,000-scale county-wide general soil map data and 1:15,540-scale detailed soil data for the Cape Charles area digitized from printed USDA soil survey maps; a land use and vegetation cover dataset (30 m. resolution) created by the VCRLTER derived from a 1993 Landsat Thematic Mapper satellite image; 1:20,000-scale plant association maps for 10 seaside barrier and marsh islands between Hog and Smith Islands, inclusive, prepared by Cheryl McCaffrey for TNC in 1975 and published in the Virginia Journal of Science in 1990; and 1993 colonial bird nesting site data collected by The Center for Conservation Biology (with partners The Nature Conservancy, College of William and Mary, University of Virginia, USFWS, VA-DCR, and VA-DGIF). Contents: HYDROGRAPHY Based on USGS 1:100,000 Digital Line Graph (DLG) data. Files: h100k_arc_u84 (streams, shorelines, etc.) and h100k_poly_u84 (marshes, mudflats, etc.). Note that the hydrographic data has been superseded by the more recent and more detailed USGS National Hydrography Dataset, available for the entire state of Virginia at "ftp://nhdftp.usgs.gov/DataSets/Staged/States/FileGDB/HighResolution/NHDH_VA_931v210.zip" (see http://nhd.usgs.gov/data.html for more information). A static 2013 version of the NHD data that includes shapefiles extracted from the original ESRI geodatabase format data and covering just the watersheds of the Eastern Shore of VA can also be found in the VCRLTER Data Catalog (dataset VCR14223). TRANSPORTATION Based on USGS 1:100,000 Digital Line Graph (DLG) data for the full county, and 1:6,000 VDOT data for the Cape Charles township. Files: 1:100k Transportation (lines) from USGS DLG data: rtf100k_arc_u84 (roads), rrf100k_arc_u84 (railroads), and mtf100k_arc_u84 (airports and utility transmission lines). Files: 1:6000 street, boundary, and rail line data for the town of Cape Charles, 1984, prepared by Virginia Department of Highways and Transportation Information Services (Division 1221 East Broad Street, Richmond, Virginia 23219). Streets correct through December 31,1983. Georeferencing corrected in 2014 for shapefiles only, using same methodology described for VCR14218 dataset. File : town_u84_adj (town_arc_u84old is the older unadjusted data). Note that the transportation data has been superseded by more recent and more detailed data contained in dataset VCR14222 of the VCRLTER Data Catalog. The VCR14222 data contains 2013 U.S. Census Bureau TIGER/Line road and airfield data supplemented by railroad and transmission lines digitized from high resolution VGIN-VBMP 2013 aerial imagery and additionally has boat launch locations not available here. SOILS General soil map for Northampton county (1:190k), and detailed soil map for Cape Charles and Cheriton areas (1:15,540) from published the USDA Soil Conservation Service's 1989 "Soil Survey of Northampton County, Virginia" digitized at UVA by Ray Dukes Smith: soilorig_poly_u84 (uses original shorelines from source maps), soil_poly_u84 (substitutes shorelines from 1993 landcover classification data), and cc_soil_poly_u84 (Cape Charles & Cheriton detailed data, map sheets 13 and 14). Note that the soil data has been superseded by more recent and more detailed SSURGO soil data from the USDA's Natural Resources Conservation Service (NRCS), which has seamless soil data from the 1:15,540 map series in tabular and GIS formats for the full county, as well as for all counties in VA and other states. A static 2013 version of the SSURGO data that contains merged data for Accomack and Northampton Counties can be found in the VCRLTER Data Catalog (dataset VCR14220). LANDUSE/LANDCOVER VCR Landuse and Vegetation Cover, 1993, created by Guofan Shao (VCRLTER) based on 30m resolution Landsat Thematic Mapper (TM) satellite imagery taken on July 28, 1993. Cropped to include just Northampton County. Landcover is divided into 5 classifications: (1) Forest or shrub, (2) Bare Land or Sand, (3) Planted Cropland, Grassland, or Upland Marsh, (4) Open Water, and (5) Low Salt Marsh. File = nhtm93s3_poly_u84. No spatial adjustments necessary. An outline of the county showing the shorelines based on the above 1993 TM classification is included as the shapefile:outline_poly_u84; however, no spatial adjustment has been applied. Note that a similar landuse/landcover classification based on the same... Visit https://dataone.org/datasets/knb-lter-vcr.223.2 for complete metadata about this dataset.

Used to map the shared City boundaries with Henrico County to the north and Chesterfield County to the south. All thematic GIS areas are to adhere to this commonly used boundary.Edited by GIS professionals in the city's Assessor's Office.

These data were automated to provide an accurate high-resolution historical shoreline of Richmond, VA suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://inport.nmfs.noaa.gov/inport/item/39808

An ArcGIS OnLine map of National Historic Districts and National Historic Sites. Districts that are listed on the National Register of Historic Places (National Historic designation) and the Virginia Landmarks Register (State designation). Districts may logically carry either both designations or the State designation alone. Both of these programs are administered by the Virginia Department of Historic Resources in conjunction with the City of Richmond Bureau of Housing and Neighborhood Preservation. Properties that fall within these districts may be entitled to various development incentives. Note that some districts overlap.

This feature class combines Parcel geography information with land ownership data from the city's Computer Aided Mass Appraisal (CAMA) system. In instances of multiple ownership records (PINs) for one parcel feature, each parcel will be duplicated or "stacked."Nomenclature:cads_- short for "cadastral" - the prefix used to identify GIS data related to property and property assessment.Parcel- each geometry is a single parcel feature.Asr- short for Assessor.View- This feature class is generated from a SQL spatial view of property records and parcel geometry.The schema definition of the feature class is as follows:ParcelID - UniqueID for a Parcel.PIN - Property Identification Number.CountOfPIN - Number of PIN values per parcel.OwnerName - Name of the property owner.AsrLocationBldgNo - Address number of the property.MailAddress - Property Owner mailing address.MailCity - Property Owner mailing address city.MailState - Property Owner mailing address state.MailZip - Property Owner mailing address Zip Code.AssessmentDate - Date of the last property assessment.LandValue - Total valuation of the land.DwellingValue - Total valuation of the dwelling.TotalValue - LandValue + DwellingValue. Total value of the property.LandSqFt - Square footage of the land.ProvalAsmtNhood - The "Assessment Neighborhood" code that city of Richmond property assessors use to identify distinct neighborhoods. Proval is the name of the city's CAMA system.TaxExemptCode - Tax-exempt property code, if applicable.PropertyClassID - City property class code.PropertyClass - City property class name. Corresponds to PropertyClassID.LandUse - Land use.

Completed Bicycle Infrastructure for the City of Richmond, Virginia. This layer includes Bike Lanes, Non-Motorized Shared Spaces, Paved Off-Roadway Paths, and Shared Roadways.

As part of the construction review and permitting process, Soil types convey information about their erodibility and potential erosion problems. Soils information is used in GIS mapping and geospatial analyses.

base_StreamLine originated from DPU's stm_Stream feature class. A copy of it was placed into the Basemap dataset for the purpose of supporting basic base map map service(s). The data is not dynamic, as streams do not change. Base mapping sources can be more isolated and not be dependent upon or interfer with DPU stormwater activities.base_StreamLine was also cleaned-up of extra fields established by DPU that serve no purpose for supporting base mapping: LifeCycleStatus, ProjectNumber, ProjectName,Accessible, FromAssetID, ToAssetID, Enabled, StormwaterTraceWeight, WaterwayImpairment, TMDLPresent, MultipleTMDLs, and RiskConditionScore.