GDOT MAP 21 RC Training September 7th, 2016

Moving Ahead for Progress in the 21st Century MAP-21, the Moving Ahead for Progress in the 21st Century Act (P.L. 112-141), was signed into law by President Obama on July 6, 2012 More information can be found at: https://www.fhwa.dot.gov/map21/

Federal Goals of MAP 21 Setting the course for transportation investment in highways, MAP-21 Strengthens America’s highways Establishes a performance-based program Creates jobs and supports economic growth Supports the Department of Transportation’s (DOT) aggressive safety agenda Streamlines Federal highway transportation programs Accelerates project delivery and promotes innovation

High Level Overview This is for local roads only No collection is necessary for state roads No geometry changes will be made to the data Any new roads identified will have to go through the Georgia DOT process to be on boarded into the data set Any abandoned roads will have to go through the same process through Georgia DOT Any roads that are unclaimed will be noted for GDOT

High Level Overview This project consists of three major data buckets. They are verifiable data elements, traffic control devices and road names Contact locals Integrate local data Generate event tables Document where locals do not have data or will not participate

Local Government Contact GARC will contact each of the local jurisdictions to ascertain whether they have data or can provide the firsthand knowledge for their jurisdiction for each of the data items Explain why they should have it MAP 21 Mandate Safety Inventory

Local Government Contact Explain why they should share Good for the community Verification of local information Data is used in funding models LMIG and other funding

Integrate Local Data While this is primarily a verification project not a field project it is expected that local data will be integrated when supplied as an example road names may be a conflation process. Some local information can be verified wholesale As an example a RC meets with the local government and they may relay the information in real time and update the data at the same time

Generate event tables The end product should include the data in the form of event tables for each of the data elements The event tables should have the: The data item Begin mile point End mile point Route identifier

Documentation There will be times that the local governments do not have the information, time, etc.. We ask that when this occurs that it is documented and reported in the supplied template: Jurisdiction Contact Reason Don’t have it Don’t have the resources Don’t want to participate

Data Element Buckets Verifiable elements Traffic Control Device Ownership Operation Number of Lanes Surface Type Median Type Traffic Control Device Road Name

Ownership GARC shall verify the existing data and adjust where values are missing or have changed working with the jurisdiction The primary focus of verification being on county and city or municipal government especially on boundaries

Ownership This should be the first item verified If they don’t own it they should not have official say on any of the other items Full universe and then conflicts negotiated In addition to the Ownership value there will be a Jurisdiction field Please note – If the road is boundary for a city then the road is a city road

Operation The RCs shall verify the existing data and adjust where values are missing or have changed Ask jurisdiction do you have any reversible lanes? Code all of these as 3 - Reverse (Time of day) Ask jurisdiction do you have any one way roads? Code all of these as 1 - One-way (non-restricted) All other roads should be two way traffic Code these as 2 - Two-way (non-restricted)

Operation Discuss Alleys with Jurisdictions Remind them that in order to be considered they need to notify GDOT that they are on system and meet the following criteria They must be named public roads They must have a traffic control device at the terminus where they intersect with another road These will be the only roads that could possibly be One lane two way Still work on this

Number of Lanes How many roads are more than two lanes? Does it carry traffic and capacity? This is the number of through lanes and does not include auxiliary lanes (center turn lanes, turn lanes, etc..) We are looking for predominant condition The RCs shall verify the existing data and adjust where values are missing or have changed

Number of Lanes The lane number is captured by the value in the Increasing side or Decreasing side (direction of inventory) Example – A standard two way two lane road would have the following values: Increasing = 1 Decreasing = 1

Surface Type Data will be delivered to ITOS for distribution to GARC with a Paved/Unpaved value RC will be able to verify the existing data and adjust where values are missing or have changed If local data is available populate the additional field with paved type - Other, Concrete or Asphalt

Median Type Do you have any local divided roads? Yes/No If they are divided and they have information about the median type then populate the type 1 - Grass 2 - Soil, stone 3 - Concrete If the road has temporary dividers which will become permanent then these will be a “Yes” Does not include small tabs, neighborhood entrances, etc.. – must be median separated

Traffic Control Device Three types of traffic control devices Traffic Light Stop Sign (includes flashing overhead red beacon) Yield Sign Order of precedence 1st order local road on state highway 2nd order local paved on local paved 3rd order local unpaved on local paved 4th order local unpaved on local unpaved

Road Names This is not a domain value. The RCs shall verify the existing data and adjust where values are missing or have changed Local roads only The NENA naming standard will be applied as part of the final delivery process by ITOS