This data represents the functional classification data represented on LRS 23.1. Functional classification is the process by which streets and highways are grouped into classes, or systems, according to the character of service they are intended to provide. Basic to this process is the recognition that individual roads and streets do not serve travel independently in any major way, but serve as part of an overall network. Most travel involves movement throughout the network of roadways. It becomes necessary to determine how this travel can be channelized within the network in a logical and efficient manner. Functional classification defines the nature of this channelization process by defining the part that any particular road or street should play in serving the flow of trips through a highway network. The Virginia Department of Transportation's (VDOT) Transportation and Mobility Planning Division (TMPD) is responsible for maintaining the Commonwealth’s official Federal Functional Classification System. TMPD determines the functional classification of the road by type of trips, expected volume, what systems the roadway connects and whether the proposed functional classification falls within the mileage percentage thresholds established by the Federal Highway Administration (FHWA).

This data represents the functional classification data represented on LRS 22.1. Functional classification is the process by which streets and highways are grouped into classes, or systems, according to the character of service they are intended to provide. Basic to this process is the recognition that individual roads and streets do not serve travel independently in any major way, but serve as part of an overall network. Most travel involves movement throughout the network of roadways. It becomes necessary to determine how this travel can be channelized within the network in a logical and efficient manner. Functional classification defines the nature of this channelization process by defining the part that any particular road or street should play in serving the flow of trips through a highway network. The Virginia Department of Transportation's (VDOT) Transportation and Mobility Planning Division (TMPD) is responsible for maintaining the Commonwealth’s official Federal Functional Classification System. TMPD determines the functional classification of the road by type of trips, expected volume, what systems the roadway connects and whether the proposed functional classification falls within the mileage percentage thresholds established by the Federal Highway Administration (FHWA).

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.

THIS MAP SHOWS THE FOLLOWING:Designated Highways on the state-maintained system. The National Network and Virginia Qualifying Highways include all interstates and certain other highways respectively, with one road-mile of access permissible off these routes to access terminals, fuel, food, rest, and repairs (except in cities and towns, or in Henrico and Arlington Counties where permission is required from those localities). The Virginia Access portion includes certain other primary and secondary routes where no access is allowed off the system. LIMITATIONS & EXCLUSIONS REGARDING TRUCK ROUTES & RESTRICTIONS PROVIDED ON THIS MAP1. The information presented applies only to the highway systems maintained by the Virginia Department of Transportation (VDOT). Additional STAA access or restrictions may apply in incorporated cities and towns, and on secondary roads (numbered 600 or higher) in Henrico and Arlington Counties.2. Access to, or restrictions on, the indicated routes for the specified vehicles is applicable unless other restrictions or limitations apply due to weight, height, or width; incidents or construction; or as otherwise indicated by signs on the highway.3. To the best of our knowledge the information provided is updated on a weekly basis or as received from Districts. It is the responsibility of the highway user to ensure their information is current and correct.A permit for additional access off the state maintained system may be requested by contacting the Department of Motor Vehicles at (804) 497-7135. For additional access in cities and towns and in Henrico and Arlington Counties contact officials in those localities.

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 640,000 features representing around 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). Only official VDOT route number routes are included in this feature service. For the network including street name routes, please use the official release map package here.Geometry and Attribution:The Linear Referencing System (LRS) data contained within this feature class provides route centerline geometry that is segmented at each intersection and supplies key descriptive attribution for each segment (i.e. edge) record. The feature class also depicts overlapping routes (e.g. Interstate 64 and Interstate 95) as two separate collinear features, one on top of the other. Routes built in the prime and non-prime directions are included. Each road centerline record has a master route record assigned. In addition, local Virginia Geographic Information Network (VGIN) street names are attributed to each edge where possible.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).

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.

Prince William County Street Centerlines - Street centerlines are segmented at intersections, hydrography, zip code boundary, jurisdictional boudaryies including town boundaries and election boundaries. The layer is attributed with street name, address ranges, and other related information, full information is defined in other parts of the metadata, and in the PWC Data Dictionary. The layer can be used for creating maps, network routing and address geocoding. This data layer is the production data and is then loaded into shared data schemas for the 911 CAD system, Regional and State projects.

Abstract: This feature class consists of approximately 41,000 features which represent physical structures that Interstate, Primary, Secondary and Urban roads travel under or over on all Virginia Department of Transportation maintained roadways. The Linear Referencing System is based on the Virginia Department of Transportation's source system of record for road inventory, the Roadway Inventory Management System (RIMS).Geometry and Attribution: The dynamically generated points contained within this feature class portray the beginning of structures represented on the master route in the prime and the end of structures in the non-prime directions of travel. All point locations are positioned on Linear Referencing System geometry based on latitudinal and longitudinal coordinates initially obtained from heads-up digitizing in the Geographic Information System. Structure coordinates are currently maintained in the Roadway Network System by the Structures and Bridge Division. Features on or along the road (culverts, bridges, tunnels, parallel footbridges, etc…) and also features crossing the road (overpasses, culverts, perpendicular foot bridges, etc.) are depicted in this data. Business attributes for all features are derived from Pontis (Bridge Management System), the structure source system of record.Purpose: This feature class serves as the Structure and Bridge Division's spatial reference allowing BrM (Bridge Management System) data to be viewed, analyzed and mapped within Geographic Information System applications.

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.