creating road intersection map data for mmitss “ the nmap file” webinar #… · nmap file...

of 25 /25
Chuck Felice Utah Department of Transportation April 17, 2018 Creating Road Intersection MAP Data for MMITSS “ The NMAP File” UDOT’s Methodology in Creating NMAP Files

Author: others

Post on 10-May-2020




0 download

Embed Size (px)


  • Chuck FeliceUtah Department of Transportation

    April 17, 2018

    Creating Road Intersection MAP Data for MMITSS

    “ The NMAP File”

    UDOT’s Methodology in Creating NMAP Files

  • 2

    “Multi-Modal Intelligent Traffic Signal System is the next generation of traffic signal systems that seeks to provide a comprehensive traffic information framework to service all modes of transportation, including general vehicles, transit, emergency vehicles, freight fleets, and pedestrians and bicyclists in a connected vehicle environment.”

    Transit Signal Priority (TSP): This application allows transit agencies to manage bus service by adding the capability to grant buses priority based on a number of factors. The application provides the ability for transit vehicles to communicate passenger count data, service type, scheduled and actual arrival time, and heading information to roadside equipment via an on-board device.”

    • Designed and created at the University of Arizona by Larry Head

    • UDOT is using MMITSS for TSP and broadcasting of SPaT and MAP information

    What is MMITSS?

  • 3

    • An urban arterial west of downtown Salt Lake City 30 signalized intersections (25 have DSRC road side units) 11 miles long Varies from 5 to 7 lanes ADT: 18,000 to 40,000; 60,000 peak at I-215 Truck Traffic: 24% Econolite Cobalt and Intelight MaxTime controllers Full fiber connectivity

    • Transit Signal Priority UTA Bus Route 217 Goal: Improve schedule reliability

    from 88% to 94%

    UDOT MMITSS Corridor: Redwood Road

  • 4

    • An ASCII text file which contains intersection map data required by MMITSS

    • MMITSS uses NMAP files to create J2735 MAP Messages (March 2016 release)

    • Components of the NMAP File

    • Intersection Information• Identification Number• Intersection Attributes (bit field definitions)• Reference Point (latitude, longitude)

    The MMITSS NMAP File

  • 5

    • Components of the NMAP File (cont’d)

    • Approach Information• Number of Approaches in the intersection• Approach Type (approach or an egress)• Number of traffic lanes in the approach

    The MMITSS NMAP File

  • 6

    • Components of the NMAP File (cont’d)

    • Traffic Lane Information• Lane identification number• Lane type (numeric value 1 – 5, 1 = motorized vehicle lane)• Lane attributes (bit field definitions)• Lane width (centimeters)• Number of lane nodes for a specified lane• Lane node coordinates (latitude, longitude)• Number of connected lanes• Connected lane identifiers

    The MMITSS NMAP File

  • 7

    • ESRI ArcMap GIS Application

    • Google 6 Inch per Pixel Satellite Imagery (validated by field surveys)

    • Microsoft Excel

    • Notepad++ file editor

    • NMAP File Parser / Validation (C++ application)

    Software Tools and Imagery used in NMAP Creation

  • 8

    • Create road intersection reference point and lane nodes in ArcMap using Google imagery.

    • Export reference point and lane node data and coordinates (latitude, longitude) to a Microsoft Excel worksheet.

    • Add additional road intersection information to spreadsheet required for NMAP file format.

    • Transfer data from worksheet to NMAP file (NMAP file is created by and edited within the Notepad++ file editor).

    • Validate the NMAP file by processing it with the NAMP Parser / Validation application.

    • NMAP file is now ready to used by the MMITSS software.

    NMAP File Creation Workflow

  • 9

    NMAP File Creation Workflow

    ESRI ArcMAP Screen

  • 10

    NMAP File Creation Workflow

    Microsoft Excel Worksheet

  • 11

    NMAP File Creation Workflow

  • 12

    NMAP File Creation Workflow

    NMAP File being edited in Notepad++

  • 13

    NMAP File Creation Workflow

    MAP_Name 4610SouthRedwoodRoadReduced.nmapRSU_ID 4610SouthRedwoodRoadIntersectionID 7605Intersection_attributes 00110011 /* elevation: Yes, lane width: Yes, Node data 16 bits, node offset solution: cm, geometry: Yes, navigation: Yes */Reference_point 40.6698353 -111.9388660 13110 /* lat, long, elevation (in decimeters) */No_Approach 8Approach 1Approach_type 1 /* 1: approach, 2: egress */No_lane 2Lane 1.1Lane_ID 1Lane_type 1 /* 1 to 5, for this intersection all 1: motorized vehicle lane */Lane_attributes 0000000000101010 /* Approach path, straight permitted, right turn permitted, no u-turn, turn on red, */Lane_width 365 /* in centimeter = 12 feet */No_nodes 21.1.1 40.6698529 -111.93866331.1.2 40.6698459 -111.9369704No_Conn_lane 26.1 4 /* Lane 1.1, Straight ahead */8.1 3 /* Lane 1.1, Right turn */end_laneLane 1.2Lane_ID 2Lane_type 1 /* 1 to 5, for this intersection all 1: motorized vehicle lane */Lane_attributes 0000000001010100 /* Approach path, left turn permitted, yield, u-turn allowed, no turn on red */Lane_width 305 /* in centimeter = 10 feet */No_nodes 21.2.1 40.6698201 -111.93866371.2.2 40.6698190 -111.9384932No_Conn_lane 14.3 2 /* Lane 1.2, Left Turn */end_laneend_approach..end_map


  • 14

    NMAP File Creation Workflow

    NMAP File Validation Application

  • 15

    Small Road Intersection

  • 16

    Large Road Intersection

  • 17

    Lessons Learned

    • Good informative documentation is a must. Much time was spent determining what needed to be in the NMAP file: where information for the attribute bit field attributions could be found; how many lane nodes should be created for each lane; and other “gotcha’s”. Searching on the internet was done to obtain the above mentioned information along with making phone calls to people. Better documentation could have solved these problems and lessened the learning curve on how to create a NMAP file.

    • NMAP file size is limited to approximately 1300 bytes. This limitation is due to the message packet size being sent from one DSRC radio to another DSRC radio. This size limitation issue required the number of lane nodes to be kept at a minimum. Future MapData compression algorithms should reduce these size limitations.

    • The manual workflow process has given insight into how the process could be sped up using software to automate many of the tasks in creating a NMAP file.

    • Intersections under construction.

  • 18

    UDOT MMITSS Corridor: Provo, Utah Bus Rapid Transit Project

    • An urban arterial in downtown Provo and Orem, Utah• 47 signalized intersections with DSRC road side units• Approximately 12 miles long• Varies from 3 to 9 lanes• Econolite Cobalt controllers• Full fiber connectivity• Goal: Schedule reliability at 94%

  • 19

    UDOT MMITSS Corridor: Provo, Utah Bus Rapid Transit Project


  • 20

    Road Intersection under Construction

  • 21

    Road Intersection under Construction

  • 22

    Road Intersection under Construction

  • 23

    Future Needs

    • Best Practices Guide for collecting intersection geometry

    • Best Practices Guide for creating MAP Data.

    • Methodology for automating MAP Data messages / file creation

    • Validation of MAP Data Messages / files.

    • Human readable form of MAP Data (XML / JSON).

  • 24

    • “MMITSS Final ConOps Applications User Guide” – University of Arizona and others, Version 3.0, October 21, 2012

    • “MMITSS Field Applications User Guide” – University of Arizona, Version 1.0, July 7, 2015

    • “Signal Phase and Timing and Related Message Binary Format (BLOB) Details” – FHWA Office of Operations Research and Development, Draft February 17, 2012

    • An example of a NMAP file – “MMITSS Source Code Configuration Files directory”

    Documents Referenced for NMAP File Creation

  • 25


    Chuck FeliceUtah Department of [email protected]: 801-718-4327

    mailto:[email protected]

    Slide Number 1Slide Number 2Slide Number 3Slide Number 4Slide Number 5Slide Number 6Slide Number 7Slide Number 8Slide Number 9Slide Number 10Slide Number 11Slide Number 12Slide Number 13Slide Number 14Slide Number 15Slide Number 16Lessons LearnedUDOT MMITSS Corridor: Provo, Utah Bus Rapid Transit ProjectSlide Number 19Slide Number 20Slide Number 21Slide Number 22Future NeedsSlide Number 24Slide Number 25