Data Fields:

SUP -- "Yes" indicates that a shared use path or other bike/ped facilities should be accommodated on this project. This information was added in Amendment 2.

NewID -- Amendment 2 created a few new roadway projects but this shape file (which came from the online version) did not have the MTP ID field. So, NEWID contains the ID only for the new projects that resutled from Amendment 2.

AQYear -- This is the completion date. It was originally set up for: projects before 2035, it is based on the draft 18-27 STIP; projects in 2035, 2045 and 2055 (in CTP, but not in MTP) values were mostly based on the 2040 MTP.

OldAQY-- Do not use. This is the 2040 AQYear that is used for comparisons.

ModAQY-- Do not use. This version followed the OldAQY values.

EplusC-- This is based on the draft 18-27 STIP. The project is committed (EplusC = y) if there is right-of-way or construction funding in the first five years of the draft 18-27 STIP.

Cost -- This is total cost, including public, private, tolls (bond proceeds), etc. Andy used the FY 16-25 TIP and feasibility studies, and Yanzhe Yin used the NCDOT cost workbook for the other proejects. SPOT costs were found to be too high and therefore only used if there was no other option. Notice: The NCDOT cost workbook did not have an option for a two-lane C&G. We might need to add costs to the two-lane C&G roadway projects.

CostSrce -- This is the source or method for the Cost calculation.

OldCost-- Do not use. This is the 2040 MTP cost that is used for comparisons.

SPOTCost-- Do not use. This is for comparisons.

ProjID-- Many ProjID values are from the 2040 MTP process. Andy added 300 and 400 value IDs to the new CTP projects.

Project-- Used most common name for roadways. Thus, US or NC designation is not always used first in the roadway name.

STI-- This is the STI funding category.

RegSig-- This is the FHWA regionally significant designation.