How are you modeling MIRE intersections and interchanges?

06-10-2019 12:24 PM
Labels (1)
New Contributor III

The MIRE FDE for intersections and interchanges is required on all non-local paved roads by September 30, 2026. 

- Has your agency begun collection of MIRE FDE for intersections and interchanges?

- How is your agency modeling MIRE-compliant intersections and interchanges? 

- What resources would be helpful for your agency to meet this deadline (i.e. guidance, software/tools, etc)?  

2 Replies
New Contributor

At Arkansas DOT we use Transcend’s Intersection Manager (IM).  IM generates unique intersection point locations and approach extents, along with each data item required to support the Model Inventory of Roadway Elements (MIRE) data required for intersections and for use in Safety Analyst and Highway Safety Improvement Program (HSIP) analyses.  With the addition of user defined/compiled complex interchange polygons IM also supports the interchange and ramp MIRE data requirements.  In addition, IM accommodates Road crossings, including rail, pedestrian, bicycle and other user definable crossing types, and it can be configured to programmatically locate these crossings from GIS data sources.  We find it to be a great "all in one" package to meet the MIRE Intersection requirement.  Other resources that would be helpful is additional guidance on what the data submittal requirements will look like and any guidance on expectations.


At KDOT we are also beginning to use Transcends Intersection Manager.  It;s a nice relational setup that takes advantage of the Roads and Highways and Geodatabase capabilities to relational join the junction and segment data based on MIRE concepts.  Its a good capability and it forces you to think about the level of detail and abstraction of intersection geometries into or related to your roads and highways network.

I think now the challenge is to collect the data we do not yet have into that model by 2026.   Every compliant DOT has submitted a plan by now. 

I think we could use AI, something like mapillary, in addition to consulting, contracting with a provider, or a small task workforce applied to obtain traffic signs and signal information related to turn protections, prohibitions, channelization, and traffic controls.  Some of the traffic controls information do involve coordinated intergovernmental relations between traffic engineers, planners and consultants.  By 2026 we should be able to relate the point sign and control information into the LRS and intersection data.