ArcGIS REST Services Directory Login
Home > services > Planning > Planning_GIS_Layers_upd (MapServer) > MTP 2050 - Adopted API Reference
JSON

Layer: MTP 2050 - Adopted (ID: 34)

Parent Layer: Transportation

Name: MTP 2050 - Adopted

Display Field: RTE_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

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. Future updates: This layer will be updated periodically to include new roads recommended by adopted Small Area Plans or City Council actions. Coordinate System: NAD 1983 State Plane Virginia South FIPS 4502 (US Feet)The 2050 MTP layer contains a myriad of fields. A brief description is provided below.Road Classificationlane_type - 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 roadwayssegment_exists - Y = existing road; N = proposed roadRoad Namesstreet_name - this layer combines the street name, type, and directional prefixes and suffexesrte_name - route nameTraffic Model Networkid -Link ID in the traffic modela - Node IDS (shows direction of travel see Node.shpb - Node IDS (shows direction of travel see Node.shpdistance - actual road length in feet2050 Traffic Volumesam_v - AM peak hour volumepm_v - PM peak hour volumemd_v - midday peak hour volument_v - nighttime peak hour volumeallday_v - Total daily volumeRoadway Capacityam_link_ca - AM peak capacitypm_link_ca - PM peak capacitymd_link_ca - Midday peak capacitynt_link_ca - Nighttime peak capacityTo find congested roads, compare volume vs capacity. If pm_v > pm_link_ca, the road is over capacity.Road Characteristics:factype - road classification (1 = Interstate, 3 = Prinicipal Arterial, 4 = Major Arterial, 5 = Minor Arterial, 6 = Collector, 8 = Local)lanes - number of lanese-lanes - existing lanesp-lanes - proposed lanesThis data layer was created through an iterative process. The new proposed MTP 2050 network was sent to the Planning department from the consultant. (v 10/6/2025). It was reviewed by Planning staff to ensure consistency with the adopted 2050 plan, and adopted small area plans. An online web app containing the adopted MTP 2050, the proposed MTP 2050 v 10_6_2025, a hosted MTP_2050_Update_NOTES layer, and supplemental layers was created so department staff could easily review the proposed MTP plan and record their comments. Team meetings were set up where the planner presented their findings to the larger group by Planning Area. Following these discussion, the GIS Specialist worked with each planner to incorporate their changes into a new MTP 2050 GIS layer, entitled MTP2050_v10_06_2025_edited_by_Ches_Plan_11_06_2025. The update geometry tool was used adjust the location of future roadways that did not coincide with the adopted MTP 2050 layer. New roads were added, and other segments extended to ensure connectivity. The notes layer was updated to ensure the changes had been made. The updated MTP 2050 v 11_06_2025 layer was sent back to the consultant for review and modeling.Upon review and modeling by the consultant, the proposed MTP 2050 layer was returned, the metadata and field alias' were updated. There were many fields that were not needed in the final layer. They included processing leftovers, VDOT tracking fields, Address Ranges, Street name parts, Technical Fields, and some miscellaneous fields. The fields were rearranged so that the unused fields appeared last. A copy of this layer is saved in the MTP_2050_reordered geodatabase. In a final review of the layer, the unneeded fields were removed and the layer was reprojected from NAD 1983 Virginia Lambert (meters), Projection Lambert Conformal Conic to NAD 1983 State Plane Virginia South FIPS 4502 (US feet), Projection Lambert Conformal Conic.) and the distance field was recalculated in feet. The previous MTP2050_adopted layer was removed from the City's GIS servers and replaced with this version.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.

Service Item Id: 98af486085f54f1888458af16e7441e1

Copyright Text: Virginia Geographic Information Network (VGIN), Virginia Department of Transportation (VDOT), Virginia local government GIS, Chesapeake Planning

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata