This layer contains the boundaries for Virginia Department of Transportation districts.Automatically updated when VDOTAdministrativeBoundaries (FeatureServer) is updated. VDOT Districts is the third layer in the AGOL VDOTAdministrativeBoundaries feature service.

Administrative boundaries for the Commonwealth of Virginia, VDOT Operational Regions, VDOT Districts, VDOT Residencies, and VDOT Area Headquarter boundaries.

This data set contains the jurisdiction boundaries for all counties (96) cities (40), and towns (118) in the Commonwealth of Virginia. It provides information on VDOT districts and residencies. This layer was formed by joining the base boundary polygon layer provided by VGIN to a table of VDOT business data, providing the fields needed to allow this layer to be used for many VDOT applications.

This map provides information on speed limits that are posted on state-maintained roadways in Virginia. Cities and towns set their own speed limits and these are not available to show on the map. Zoom in on the map to display the speed limits. Speed limits exist for all roads however; where this information is not available for mapping, they are not displayed. Most roads where speed limits are not shown are either rural, secondary roads (routes numbered 600 or greater) where a statutory 55 mph speed limit typically applies, or subdivision streets where a statutory 25 mph speed limit usually applies. These statutory speed limits are often are not posted on these roads. Click on any roadway to display the speed limit information.

This map is related to HB – 143 § 33.2-280.2 (Effective January 1, 2025) Utility work database which stipulates The Virginia Department of Transportation map any permits issued to utility companies for work in a residential neighborhood .

§ 33.2-280.2. (Effective January 1, 2025) Utility work database.

A. As used in this section:

"Service connection" means any utility facility installed overhead or underground between a distribution main, pipelines, conduits, lines, wires, or other sources of supply and the premises of the individual customer.

"Utility work" means the construction, installation, removal, or substantial maintenance of a privately, publicly, or cooperatively owned line, facility, or system for producing, transmitting, or distributing telecommunications, cable television, electricity, gas, oil, petroleum products, water, steam, storm water not connected with highway drainage, or any other similar commodity, including any fire or police signal system. "Utility work" does not include emergency maintenance or repairs or any work directly related to any individual service connection or service drop.

B. The Department shall establish and maintain a publicly accessible database and map of all utility work that has been approved by the Department and will occur within a highway right-of-way in a residential neighborhood, as specified by the utility. Such database shall include the location where such work will occur, the start date of such work, the projected end date of such work, the company administering such work, and any other relevant information; however, under no circumstances shall such database and map provide information on any (i) utility work within a right-of-way not maintained by the Department; (ii) critical utility infrastructure, as designated by the utility, that, upon disclosure, has the potential to jeopardize security or critical services, including Critical Energy Infrastructure Information and Controlled Unclassified Information; or (iii) information the permittee has designated as confidential. Such information shall be available in the database at least seven days prior to the start date of any such utility work and shall be deleted from such database 90 days after the completion of such work.

This layer contains the boundaries for Virginia Department of Transportation operational regions.Automatically updated when VDOTAdministrativeBoundaries (FeatureServer) is updated. VDOT Operational Regions is the second layer in the AGOL VDOTAdministrativeBoundaries feature service.

This map is related to HB – 143 § 33.2-280.2 (Effective January 1, 2025) Utility work database which stipulates The Virginia Department of Transportation map any permits issued to utility companies for work in a residential neighborhood .

§ 33.2-280.2. (Effective January 1, 2025) Utility work database.

A. As used in this section:

"Service connection" means any utility facility installed overhead or underground between a distribution main, pipelines, conduits, lines, wires, or other sources of supply and the premises of the individual customer.

"Utility work" means the construction, installation, removal, or substantial maintenance of a privately, publicly, or cooperatively owned line, facility, or system for producing, transmitting, or distributing telecommunications, cable television, electricity, gas, oil, petroleum products, water, steam, storm water not connected with highway drainage, or any other similar commodity, including any fire or police signal system. "Utility work" does not include emergency maintenance or repairs or any work directly related to any individual service connection or service drop.

B. The Department shall establish and maintain a publicly accessible database and map of all utility work that has been approved by the Department and will occur within a highway right-of-way in a residential neighborhood, as specified by the utility. Such database shall include the location where such work will occur, the start date of such work, the projected end date of such work, the company administering such work, and any other relevant information; however, under no circumstances shall such database and map provide information on any (i) utility work within a right-of-way not maintained by the Department; (ii) critical utility infrastructure, as designated by the utility, that, upon disclosure, has the potential to jeopardize security or critical services, including Critical Energy Infrastructure Information and Controlled Unclassified Information; or (iii) information the permittee has designated as confidential. Such information shall be available in the database at least seven days prior to the start date of any such utility work and shall be deleted from such database 90 days after the completion of such work.

Overview

VDOT divides Virginia into 9 maintenance districts, when a snow event requires streets to be plowed the affected areas are color coded. A mobilization scale of 1 to 5 is used to measure the severity level. In general, an event with a mobilization of three or greater will trigger plowing activities and the district will be shaded in blue. For mobilizations less than 3, the district will be shaded gray and limited plowing may be conducted on major highways. When there is no event level, the district will have no shading. The Mobilization Plan, Road Status and Help links on the page will provide detailed information on snow events and removal operations.

Local Operations

As the map is zoomed into a particular location, street level plowing activity may be displayed. VDOT is testing two different technologies to determine the best solution for showing the progress of snow plowing in the Commonwealth and the method to display the plowing progress in the districts will vary. The following sections will explain how snow plowing activity will be displayed during a mobilization level of 3 or greater.

Northern Virginia & Fredericksburg

In Northern Virginia (Nova) and Fredericksburg, the districts are divided up by service areas know as Local Area Headquarters and then further sub-divided into neighborhoods. These subdivisions are visible as you zoom into the district. When plowing is underway, the location of plow trucks is updated every two minutes and the neighborhoods are color coded depending on their stage of completion.

Remaining Districts

The balance of the state at this time will not be displaying plowing activities for neighborhoods. However, once plowing is underway, the location of snow plow trucks is updated every two minutes.

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.

This feature class consists of approximately 195,000 features representing over 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS). Geometry and Attribution: The Linear Referencing System (LRS) data contained within this feature class provides dissolved route segmentation (i.e. routes are not segmented when they intersect other routes), thus rendering one table record per route. Multi-part geometry is created where routes are noncontiguous (e.g. a valid physical gap exists because another route is the master). The feature class only depicts master routes, those are routes built in the prime direction and on divided roadways where the non-prime direction is the master. Each road centerline record has a master route record assigned. Measures: The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions). Purpose: This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located. Note: The overlap and non-prime measures are for reference only and have not been fully validated for accuracy or completeness.

Where it is understood that the rule of "once in always in" should be applied in the effort to map VDOT’s MS4 Service Area. And so, the 2000, 2010, and 2020 Census Urbanized Areas (CUAs) were merged in GIS and then dissolved to remove internal crossover boundaries—creating a seamless and uniform boundary.

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 and manages the development of a consistent, seamless, statewide digital road centerline file with address, road name, and state route number attribution, as part of the Virginia Base Mapping Program (VBMP). The Road Centerline Program (RCL) leverages the Commonwealth"s investment in the VBMP digital orthophotography and is focused on creating a single statewide, consistent digital road file.The RCL data layer is a dynamic dataset supported and maintained by Virginia"s Local Governments, VDOT, and VGIN. VBMP RCL is extracted and provided back to local governments and state agencies in many geographic data sets every quarter.GDB Version: ArcGIS Pro 3.3Additional Resources:Routable RCL With Network Dataset GDB(ArcGIS Pro 3.2)Shapefile DownloadREST EndpointRoad Centerline Data StandardArcGIS LYR FileHistorical RCL & Ancillary Centerlines -Contact VGIN

SDE_VDOT_INTERSECTION_W_XY - Latitudinal and Longitudinal Junction Coordinates - Generalized placement of event data.Abstract: This feature class consists of approximately 440,000 features representing roadway intersections throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Roadway Inventory Management System (RIMS), the source system of record for road inventory. The Linear Referencing System (LRS) data contained within this feature class consists of Latitudinal and Longitudinal coordinate points portraying at-grade intersections, single/divided centerline geometry transitions and jurisdiction boundary changes on Virginia Department of Transportation maintained roadways. The data layer also provides a cross-reference between Roadway Inventory Management System (RIMS) "nodes" and the current Linear Referencing System (LRS) "junctions". This intersection extract has latitude and longitude coordinate attribution derived from the "FROM" and "TO" junctions where a valid INTERSECTION_ID (i.e. HTRIS node) exists. Purpose: This linear referenced data layer provides the junction point geometry for the underlying spatially enabled geometric network and a method to locate "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, turns, etc...) relative to Linear Referencing System junctions.

Annualized, Hourly and Classification count data for the TPB modeled region. Data are collected from state DOTs and processed by TPB staff.Layers IncludedAnnualized Traffic Volumes Historic AADT by Count Station This database contains the Annual Average Daily Traffic (AADT) estimates reported at permanent and short term counting stations in the TPB modeled region. Please note: Interstates in Virginia are typically represented by two stations (one in each direction) while Interstates in the other states are represented by one station. Therefore, the AADT estimates displayed for the stations on Virginia Intestates will be around half of the total for the directional roadway. The AADT estimates for recent years in this file are based on counts taken at the actual count station locations that are indicated by the station points. The AADT estimates for earlier years are based on volumes reported along roadway segments that the station points currently represent. Specific data sources for each state are listed below:District of ColumbiaAADT estimates since 2006 are based on counts taken at the station locations in the file for purpose of Federal HPMS reporting.AADT estimates prior to 2006 are based on Traffic Volume maps produced by DDOT (Formerly DC DPW).MarylandAADT estimates since 2000 are based on counts taken at the station locations in the file and reported by MD SHA.AADT estimates prior to 2000 are based on volumes reported by MD SHA in the Highway Location Reference documents and matched to links in the COG/TPB highway network. The volumes are shown at the count locations that currently represent those network links.VirginiaAADT estimates since 1997 are based on counts taken at the station locations in the file and reported by VDOT.AADT estimates prior to 1997 are based on volumes reported by VDOT in the Average Daily Traffic Volumes documents and matched to links in the COG/TPB highway network. The volumes are shown at the count locations that currently represent those network links.West VirginiaAADT estimates since 1999 are based on counts taken at the station locations in the file and reported by WV DOT.Traffic Counts by Network LinkThis layer was created by assigning the state DOT traffic counting station locations to their corresponding COG/TPB network links. Facility names and route numbers were added to the network. AADT Average Annual Daily Traffic (2016 - 2018), AAWDT Average Annual Weekday Daily Traffic (2016 - 2018) and Count Type (2016 - 2018) are included as well as Single Unit Truck Percent AAD (2018), Combination Unit Truck Percent AADT (2018), Bus Percent AADT (2018, only available for Maryland and Virginia), K Factor (2018), Dir Factor (2018), and Count Year (last year the link was counted). Count Type denotes the source of the count. Please note: for bi-directional roads, the AADT and AAWDT values for each location were divided in two and assigned to both network links that represent the Anode-Bnode direction and the Bnode-Anode direction. Therefore, in most cases the AADT/AAWDT values associated with an individual link in this network will be half of the AADT/AAWDT values reported at the associated individual count station point. Traffic Counts by External StationThis layer was created by placing points where major facilities cross the TPB Modeled Area boundary. In some cases, the external station represents more than one facility. The facility field indicates which road or roads the station represents. AADT and AAWDT estimates at external stations are provided for 2007 through 2022. Each external station is assigned to a state DOT traffic counting station(s). An effort was made to assign stations or combinations of stations that would come closest to measuring the traffic volume on each facility as it enters/exits the region. In some cases, these volumes are measured just inside the modeled area; in other cases, the volumes are measured just outside the modeled area. The external stations around the Baltimore Beltway are exceptions to this rule. These stations all measure the traffic just south of the Baltimore Beltway in order lessen the influence of traffic specific to Baltimore. AADT Average Annual Daily Traffic (2007 – 2022) and AAWDT Average Annual Weekday Daily Traffic (2007 – 2022) are included. Count Type denotes when the location was last counted. West Virginia does not report AAWDT, so the AADT values were increased by 5% to arrive at AAWDT estimates in West Virginia.