| description:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The 2050 Master Transportation Plan shows a master street network for the City of Chesapeake. It was created by combining traffic demand model data with state centerline data. It shows both existing roads and proposed future roads with projected 2050 traffic volumes. It was adopted as part of the 2045 Comprehensive Plan by City Council on January 20, 2026. </SPAN></P><P><SPAN STYLE="font-style:italic;font-weight:bold;">Future updates</SPAN><SPAN>: This layer will be updated periodically to include new roads recommended by adopted Small Area Plans or City Council actions. </SPAN></P><P><SPAN STYLE="font-style:italic;">Coordinate System</SPAN><SPAN STYLE="font-weight:bold;">: </SPAN><SPAN>VA State Plane South (EPSG 3968)</SPAN></P><P><SPAN>The 2050 MTP layer contains a myriad of fields. A brief description is provided below.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Road Classification</SPAN></P><UL><LI><P><SPAN STYLE="font-weight:bold;">lane_type </SPAN><SPAN>- Road type (8 Lane Freeway, 6 Lane Aerial NEW, etc.) - This layer is used for the map symbology it combines road type, number of lanes, or new or existing roadways</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">segment_exists </SPAN><SPAN>- Y = existing road; N = proposed road</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">Road Names</SPAN></P><UL><LI><P><SPAN STYLE="font-weight:bold;">street_name - </SPAN><SPAN>this layer combines the street name, type, and directional prefixes and suffixes</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">rte_name</SPAN><SPAN> - route name</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">Traffic Model Network</SPAN></P><UL><LI><P><SPAN STYLE="font-weight:bold;">id -</SPAN><SPAN>Link ID in the traffic model</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">a -</SPAN><SPAN> Node IDS (shows direction of travel see Node.shp</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">b -</SPAN><SPAN> Node IDS (shows direction of travel see Node.shp</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">distance - </SPAN><SPAN>actual road length in feet</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">2050 Traffic Volumes</SPAN></P><UL><LI><P><SPAN STYLE="font-weight:bold;">am_v</SPAN><SPAN> - AM peak hour volume</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">pm_v </SPAN><SPAN> - PM peak hour volume</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">md_v - </SPAN><SPAN>midday peak hour volume</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">nt_v - </SPAN><SPAN>nighttime peak hour volume</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">allday_v - </SPAN><SPAN>Total daily volume</SPAN></P></LI></UL><P><SPAN STYLE="font-weight:bold;">Roadway Capacity</SPAN></P><UL><LI><P><SPAN STYLE="font-weight:bold;">am_link_ca</SPAN><SPAN> - AM peak capacity</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">pm_link_ca</SPAN><SPAN> - PM peak capacity</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">md_link_ca</SPAN><SPAN> - Midday peak capacity</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">nt_link_ca </SPAN><SPAN>- Nighttime peak capacity</SPAN></P></LI></UL><P><SPAN STYLE="font-style:italic;">To find congested roads, compare volume vs capacity. If pm_v > pm_link_ca, the road is over capacity.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Road Characteristics:</SPAN></P><UL><LI><P><SPAN STYLE="font-weight:bold;">factype - </SPAN><SPAN>road classification (1 = Interstate, 3 = Principal Arterial, 4 = Major Arterial, 5 = Minor Arterial, 6 = Collector, 8 = Local)</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">lanes - </SPAN><SPAN>number of lanes</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">e-lanes </SPAN><SPAN>- existing lanes</SPAN></P></LI><LI><P><SPAN STYLE="font-weight:bold;">p-lanes - </SPAN><SPAN>proposed lanes</SPAN></P></LI></UL><P><SPAN>Fields that are not needed but are in the table. The alias has been updated to say these fields are not needed.:</SPAN></P><OL><LI><P><SPAN STYLE="font-style:italic;">Processing leftovers </SPAN><SPAN STYLE="font-weight:bold;">- </SPAN><SPAN>objectid_1, objectid_12, fid1, fid2, shape_length_1, shape_length12</SPAN></P></LI><LI><P><SPAN STYLE="font-style:italic;">VDOT tracking stuff </SPAN><SPAN>- rcl_id, vdot_edge_id, local_id, mfips, geometry_source, geometry_edit_date, street_name_source, address_range_source</SPAN></P></LI><LI><P><SPAN STYLE="font-style:italic;">Address ranges </SPAN><SPAN>- left_from_address, right_to_address, etc - not used in MTP</SPAN></P></LI><LI><P><SPAN STYLE="font-style:italic;">Street name parts </SPAN><SPAN STYLE="font-weight:bold;">-</SPAN><SPAN> street_prefix_direction, street_suffix, etc. - The street names have been combined into a single layer</SPAN></P></LI><LI><P><SPAN STYLE="font-style:italic;">Other technical fields - </SPAN><SPAN>mtfcc, segment_type, reversible</SPAN></P></LI><LI><P><SPAN STYLE="font-style:italic;">Miscellaneous</SPAN><SPAN> - WSP edit, dual_carrier, one way, reversible</SPAN></P></LI></OL><P><SPAN>This data layer was updated to include complete field aliases and the fields were rearranged so that the ones that were not needed appear at the end of the table.</SPAN><SPAN /><SPAN> 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. </SPAN></P></DIV></DIV></DIV> |