{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "This layer shows the 2050 Master Transportation Plan network for the City of Chesapeake, adopted as part of the 2045 Comprehensive Plan.", "description": "

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>

Future updates<\/SPAN>: This layer will be updated periodically to include new roads recommended by adopted Small Area Plans or City Council actions. <\/SPAN><\/P>

Coordinate System<\/SPAN>: <\/SPAN>VA State Plane South (EPSG 3968)<\/SPAN><\/P>

The 2050 MTP layer contains a myriad of fields. A brief description is provided below.<\/SPAN><\/P>

Road Classification<\/SPAN><\/P>

  • lane_type <\/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>

  • segment_exists <\/SPAN>- Y = existing road; N = proposed road<\/SPAN><\/P><\/LI><\/UL>

    Road Names<\/SPAN><\/P>

    • street_name - <\/SPAN>this layer combines the street name, type, and directional prefixes and suffixes<\/SPAN><\/P><\/LI>

    • rte_name<\/SPAN> - route name<\/SPAN><\/P><\/LI><\/UL>

      Traffic Model Network<\/SPAN><\/P>

      • id -<\/SPAN>Link ID in the traffic model<\/SPAN><\/P><\/LI>

      • a -<\/SPAN> Node IDS (shows direction of travel see Node.shp<\/SPAN><\/P><\/LI>

      • b -<\/SPAN> Node IDS (shows direction of travel see Node.shp<\/SPAN><\/P><\/LI>

      • distance - <\/SPAN>actual road length in feet<\/SPAN><\/P><\/LI><\/UL>

        2050 Traffic Volumes<\/SPAN><\/P>

        • am_v<\/SPAN> - AM peak hour volume<\/SPAN><\/P><\/LI>

        • pm_v <\/SPAN> - PM peak hour volume<\/SPAN><\/P><\/LI>

        • md_v - <\/SPAN>midday peak hour volume<\/SPAN><\/P><\/LI>

        • nt_v - <\/SPAN>nighttime peak hour volume<\/SPAN><\/P><\/LI>

        • allday_v - <\/SPAN>Total daily volume<\/SPAN><\/P><\/LI><\/UL>

          Roadway Capacity<\/SPAN><\/P>

          • am_link_ca<\/SPAN> - AM peak capacity<\/SPAN><\/P><\/LI>

          • pm_link_ca<\/SPAN> - PM peak capacity<\/SPAN><\/P><\/LI>

          • md_link_ca<\/SPAN> - Midday peak capacity<\/SPAN><\/P><\/LI>

          • nt_link_ca <\/SPAN>- Nighttime peak capacity<\/SPAN><\/P><\/LI><\/UL>

            To find congested roads, compare volume vs capacity. If pm_v > pm_link_ca, the road is over capacity.<\/SPAN><\/P>

            Road Characteristics:<\/SPAN><\/P>

            • factype - <\/SPAN>road classification (1 = Interstate, 3 = Principal Arterial, 4 = Major Arterial, 5 = Minor Arterial, 6 = Collector, 8 = Local)<\/SPAN><\/P><\/LI>

            • lanes - <\/SPAN>number of lanes<\/SPAN><\/P><\/LI>

            • e-lanes <\/SPAN>- existing lanes<\/SPAN><\/P><\/LI>

            • p-lanes - <\/SPAN>proposed lanes<\/SPAN><\/P><\/LI><\/UL>

              Fields that are not needed but are in the table. The alias has been updated to say these fields are not needed.:<\/SPAN><\/P>

              1. Processing leftovers <\/SPAN>- <\/SPAN>objectid_1, objectid_12, fid1, fid2, shape_length_1, shape_length12<\/SPAN><\/P><\/LI>

              2. VDOT tracking stuff <\/SPAN>- rcl_id, vdot_edge_id, local_id, mfips, geometry_source, geometry_edit_date, street_name_source, address_range_source<\/SPAN><\/P><\/LI>

              3. Address ranges <\/SPAN>- left_from_address, right_to_address, etc - not used in MTP<\/SPAN><\/P><\/LI>

              4. Street name parts <\/SPAN>-<\/SPAN> street_prefix_direction, street_suffix, etc. - The street names have been combined into a single layer<\/SPAN><\/P><\/LI>

              5. Other technical fields - <\/SPAN>mtfcc, segment_type, reversible<\/SPAN><\/P><\/LI>

              6. Miscellaneous<\/SPAN> - WSP edit, dual_carrier, one way, reversible<\/SPAN><\/P><\/LI><\/OL>

                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> 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>", "summary": "This layer shows the 2050 Master Transportation Plan network for the City of Chesapeake, adopted as part of the 2045 Comprehensive Plan.", "title": "VBMP RCL", "tags": [ "Chesapeake VA", "Planning", "MTP 2050", "2045 Comp Plan" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 500000, "maxScale": 5000, "spatialReference": "", "accessInformation": "Virginia Geographic Information Network (VGIN), Virginia Department of Transportation (VDOT), Virginia local government GIS, Chesapeake Planning", "licenseInfo": "

                For Reference Only<\/SPAN><\/P>

                <\/P><\/DIV><\/DIV><\/DIV>", "portalUrl": "" }