The regional parcel layer for Hampton Roads covers a majority of the 17 member jurisdictions of the HRPDC. This collaborative parcels layer is assembled by processing each available jurisdiction's live map service within the HRGEO server to create a single parcel layer for the region with a common data standard. The most highly requested fields are included, however not all localities share all fields publicly and so more detailed assessment data must still be obtained from the locality. Also, the parcels are not edge-matched between boundaries. Last update: August 2024Full metadata is available on the parcels page at HRGEO.
This layer was assembled from data from Esri's SSURGO Downloader in May 2018. Esri compiled the most popular fields from the many tables in the SSURGO data into one layer. Individual watersheds were downloaded, merged, and clipped for Hampton Roads. Follow link for full metadata.
This layer depicts the Chesapeake Bay Preservation Act (CBPA) areas in Hampton Roads, Virginia, categorized into three delineations: Resource Protection Areas (RPA) include both tidal and connected non-tidal wetlands, as well as tidal shores, and a landward riparian buffer of 100 feet which has the greatest potential to protect and benefit water quality. Resource Management Areas (RMA) area adjacent to the RPA and have the potential to damage water quality without proper management. Only those RMA areas that have a designated boundary are in included in this layer. Some localities define the RMA as the remaining area of the locality that is not in the RPA and therefore no separate boundary is needed.Intensely Developed Areas (IDA) must be designated in the city or county code. Not all localities have designated IDAs. An IDA overlays redevelopment areas that may otherwise be subjected to stricter enforcement of the RPA.Note that the areas provided in this layer are meant for general planning use. Use the CBPA Address Locator application to see if a property is in or near the CBPA. Consult with local CBPA staff for questions about the determination and enforcement of CBPA areas. Data last updated: September 2020
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Hampton Roads, Virginia OSM GIS Data
This file depicts the 11 Phase I and Phase II MS4s (Municipal Separate Storm Sewer System) in Hampton Roads, within the Chesapeake Bay watershed. Data compiled in 2018, reflects delineated service areas between 2015 and 2018. Excludes VDOT MS4, state lands, VPDES permittees, and direct discharges for Hampton, Norfolk, VA Beach, Chesapeake, Newport News, and Suffolk.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Zip Code 23651 covering Fort Monroe in Hampton, Virginia GIS dataset.
This layer compiles future land use for Hampton Roads localities, reflecting conditions circa 2023. The planning horizon for each locality differs; the year is noted in the attribute table. Some localities have provided new/updated data since the last update (2016/2019), while others have approved using previous data. Each locality maintains its land use categories. However, the Hampton Roads Transportation Planning Organization (HRTPO) developed a regional land use data schema in 2011 as regionally consistent land use categories are essential to modeling for the Long-Range Transportation Plan. Full metadata on the regional land use categories can be found by visiting the following website. This document contains the data dictionary for the attributes.The regional land use codes are divided into Major and Minor categories, and the local land use category is also preserved in the table. The localities each reviewed the crosswalk between their categories and the regional assignment.
This layer includes public K-12 public schools (including public preschools and specialty programs) and K-12 private schools in Hampton Roads. Private preschools and daycares are not included. The public schools data is comprehensive with source information obtained from each public school district in the region. The private school data was obtained from several sources and may not have identified every school. Sources consulted for private schools include the National Center for Education Statistics, Virginia Council for Private Education, and the Association of Christian Schools International. Data is updated for 2019-2020 school year.
This layer represents airport grounds and airport runways within the Hampton Roads, Virginia region. All airports have a boundary, and most have at least one runway. This data is derived from the USA Airport Areas layer created by Esri.
This layer defines the area on land or water intended to be used either wholly or in part for the arrival; departure and surface movement of aircraft/helicopters. This layer is derived from the Airports layers created by the FAA Aeronautical Informational Services.
This layer contains the 2010 Census Blocks for the Hampton Roads region. Only the boundaries are included - no demographics attributes are contained in the layer.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Langley Air Force Base, Hampton, Virginia 23665 zip code GIS dataset.
The Communities at Sea maps use Vessel Trip Report location point data as input to create density polygons representing visitation frequency ("fisherdays"). The data show total labor including crew time and the time spent in transit to and from fishing locations. They do not show other variables such as vessel value or number of pounds landed. The results can be interpreted as maps of "community presence." This layer shows data for the dredge fishing gear group for Hampton, VA from 2011-2015.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Virginia's 1st Congressional District GIS
original data sets in .kml (high and low resolution), now also in .geojson, .topojson, and .shp.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Neighborhoods GIS Layers
The city of Williamsburg's Information Technology Department serves these up for the public as shapefiles.
Converted to GeoJSON, and TopoJSON where applicable.
ref:
http://www.williamsburgva.gov/Index.aspx?page=793
This group includes the following items: 1. Hampton Roads Elevation Certificate Building Footprints: includes only building footprints where final elevation certificates are available, with elevations reported in the vertical datum provided on the elevation certificate (NGVD 29 or NAVD 88). 2. Hampton Roads Elevation Certificate Parcels: includes only parcels where final elevation certificates are available, with elevations reported in the vertical datum provided on the elevation certificate (NGVD 29 or NAVD 88). Elevation certificates were collected from the following 12 localities: Chesapeake, Franklin, Gloucester County, Hampton, James City County, Newport News, Norfolk, Portsmouth, Southampton County, Suffolk, Virginia Beach, and York County. Localities included in the current inventory were able to provide digital elevation certificate copies. This inventory is not complete for the region, and elevation certificates will continue to be added to the database when available. The elevation certificate database was developed by HRPDC staff with support from the Center for Geospatial, Science, Education, and Analytics at Old Dominion University (ODU). We would like to acknowledge Manuel Solano (ODU) for his contributions to the Gloucester County and City of Norfolk elevation certificate data development.Building footprints are courtesy the VGIN statewide building footprints layer and locality GIS departments. Building attributes and parcels are courtesy of the Hampton Roads Regional Parcels layer and locality GIS departments. Current flood zones are courtesy of the FEMA National Flood Hazard Layer, with base flood elevations reported in NAVD 1988 where available. A complete list of attribute descriptions is available here. Created 2/8/2019Updated 10/10/2020
FEMA flood zones for multiple localities in Hampton Roads, Virginia were combined into one layer. Latest update: September 2019
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Wetlands GIS Layer
The city of Williamsburg's Information Technology Department serves these up for the public as shapefiles.
Converted to GeoJSON, and TopoJSON where applicable.
ref:
http://www.williamsburgva.gov/Index.aspx?page=793
Geospatial data about Hampton County, Virginia 1 FT Contours. Export to CAD, GIS, PDF, CSV and access via API.
These data were automated to provide an accurate high-resolution historical shoreline of Chesapeake Bay in the Vicinity of Hampton, 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
The regional parcel layer for Hampton Roads covers a majority of the 17 member jurisdictions of the HRPDC. This collaborative parcels layer is assembled by processing each available jurisdiction's live map service within the HRGEO server to create a single parcel layer for the region with a common data standard. The most highly requested fields are included, however not all localities share all fields publicly and so more detailed assessment data must still be obtained from the locality. Also, the parcels are not edge-matched between boundaries. Last update: August 2024Full metadata is available on the parcels page at HRGEO.