FHWA MIRE Reassessment

Robert Pollack and Dr. Carol Tan, FHWAKim Eccles, VHB

October 27, 2015

Overview • MIRE Background • Purpose of Project• Methodology• MIRE Recommendations– Overall Structure – Roadway Segment– Roadway Alignment– Roadway Junction

• Next Step

Background

MIRE• MIRE – Model Inventory of Roadway Elements

• Recommended listing of roadway and traffic elements critical to safety management

• Data dictionary – definition, attributes, etc.

• V 1.0 released in 2010

Why MIRE?

Role of Improved Data Collection

Why MIRE?• Using roadway/traffic data merged with crash

data enables users to:– Develop relationships of safety to roadway features and

user exposure.– Better identify location and characteristics of crashes.– Better determine appropriate countermeasures and

strategies.– Evaluate the effectiveness of safety treatments.

Benefits of MIRE: Beyond Safety• Benefit for: – Decision Makers– Asset Management– Infrastructure– Operations– Maintenance

• Link with other data they might otherwise not have access to – Better data, improved decision making.

Federal Data Requirements • Moving Ahead for Progress in the 21 Century Act

(MAP-21) – Requires States have in place a safety data system – Requires States to collect a subset of MIRE – FDEs

• Highway Performance Monitoring System (HPMS)– Requires geospatial network on all public roads

• FHWA Guidance for State Data Systems: http://www.fhwa.dot.gov/map21/guidance/guidesafetydata.cfm

Current Status • Five years since MIRE V 1.0. • Advances in safety analyses techniques• Increased awareness of the importance of quality

data in safety analysis• Additional Federal requirements

Project Purpose

Purpose• Conduct assessment of MIRE V 1.0• Develop MIRE V 2.0 • Meet the needs of the safety community &

improve compatibility w/ FHWA data requirements

Methodology

Methodology Overview Assess MIRE V 1.0 relevant to other FHWA

databases/data standards • Recommend revisions to MIRE V 1.0• Vet recommended revisions with

practitioners• Develop MIRE V 2.0

Evaluated Datasets, Standards, Dictionaries

• HPMS - Highway Performance Monitoring System Field Manual

• TMG - Traffic Monitoring Guide • FMIS - Fiscal Management System • NBI - National Bridge Inventory • LTPP - Long-Term Pavement Performance • NPS RIP - National Park Service Road Inventory Program • SHRP2 RID - Strategic Highway Research Program 2

Roadway Information Database

Evaluation • Datasets reviewed for: • Name• Definition• Attributes• Prescribed accuracy• Use of data• QA/QC procedures• Collection method• Collection/update frequency

Data Summary

Methodology Overview

• Assess MIRE V 1.0 relevant to other FHWA databases/data standards

Recommend revisions to MIRE V 1.0• Vet recommended revisions with

practitioners• Develop MIRE V 2.0

Methodology: Develop Recommended Revisions • Recommendations developed based on cross-

walk matrix and feedback from FHWA Offices • Recommendations developed for:– General Findings/Structure – Roadway Segment– Roadway Alignment– Roadway Junction

Methodology Overview

• Assess MIRE V 1.0 relevant to other FHWA databases/data standards

• Recommend revisions to MIRE V 1.0Vet recommended revisions with

practitioners• Develop MIRE V 2.0

Methodology Overview: Vet Recommended Revisions • Four vetting sessions:– 1st Session: During 2015 TRB’s 5th International

Conference on Transportation Systems Performance Measurement and Data, Denver, Colorado, June 3, 2015

– 2nd Session: Online, June 23, 2015– 3rd Session: Online, July 23, 2015– 4th Session: Online, August 26, 2015

• More than 150 practitioners attended

Recommended Revisions

Organization• Recommendations are categorized into four

categories:– General findings/structure – Roadway segment data– Roadway alignment data– Roadway junction data

Recommended Revisions:General Findings /Structure

General Findings

• Introduction text out of date• Additional text needed:– MAP-21 – Fundamental Data Elements (FDE)– All Roads Network of Linear Referenced Data (ARNOLD)– A discussion on changing/emerging areas - including bicyclists

and pedestrians– A discussion on ADA

• Improved crosswalk table between MIRE and Safety Analyst

General Structure

• 202 elements divided into three categories:– Roadway segments– Roadway alignments– Roadway junctions

I. Roadway Segment Descriptors I.a. Segment Location/Linkage Elements I.b. Segment Roadway Classification I.c. Segment Cross Section

I.c.1. Surface Descriptors I.c.2. Lane Descriptors I.c.3. Shoulder Descriptors I.c.4. Median Descriptors

I.d. Roadside Descriptors I.e. Other Segment Descriptors I.f. Segment Traffic Flow Data I.g. Segment Traffic Operations/Control Data I.h. Other Supplemental Segment Descriptors

II. Roadway Alignment Descriptors II.a. Horizontal Curve Data II.b. Vertical Grade Data

III. Roadway Junction Descriptors III.a. At-Grade Intersection/Junctions

III.a.1. At-Grade Intersection/Junction General Descriptors III.a.2. At-Grade Intersection/Junction Descriptors (Each Approach)

III.b. Interchange and Ramp Descriptors III.b.1. General Interchange Descriptors III.b.2. Interchange Ramp Descriptors

General Structure • Each element includes:– Definition– List of attributes (coding)– Priority rating– How it relates to elements in HPMS and

safety tools (SafetyAnalyst, HSM)– Illustration

DELET

E

Data Element Example129. Intersecting AngleDefinition: The measurement in

degrees of the smallest angle between any two legs of the intersection. This value will always be within a range of 0 to 90 degrees.

Attributes: DegreesPriority: CriticalHPMS/Tool Requirements:

HSM/IHSDM (Required)

Recommended Revisions:Roadway Segments

I. Roadway Segment Descriptors I.a. Segment Location/Linkage Elements I.b. Segment Roadway Classification I.c. Segment Cross Section

I.c.1. Surface Descriptors I.c.2. Lane Descriptors I.c.3. Shoulder Descriptors I.c.4. Median Descriptors

I.d. Roadside Descriptors I.e. Other Segment Descriptors I.f. Segment Traffic Flow Data I.g. Segment Traffic Operations/Control Data I.h. Other Supplemental Segment Descriptors

General Overview• Majority of the revisions to segments elements – 21. Federal Aid/ Route Type– 27. Pavement Roughness/Condition– 31. Number of Through Lanes– 43. Right Shoulder Type & 47. Left Shoulder Type – 56. Median Barrier Presence/Type – 67. Roadside Rating– 101. Toll Facility – 106. Bridge Numbers for Bridges in Segment

Currently: 21. Federal Aid/Route Type Definition: Federal-aid/National Highway System (NHS) route type. Attributes: • Route is non Federal-aid • Route is Federal-aid, but not on NHS (i.e., all non-NHS routes functionally classified as

Interstate, Other Freeways & Expressways, Other Principal Arterials, Minor Arterials, Major Collectors, and Urban Minor Collectors)

• Route is on NHS • NHS connector to Major Airport • NHS connector to Major Port Facility • NHS connector to Major Amtrak Station • NHS connector to Major Rail/Truck Terminal • NHS connector to Major Inter City Bus Terminal • NHS connector to Major Public Transportation or Multi-Modal Passenger Terminal • NHS connector to Major Pipeline Terminal • NHS connector to Major Ferry Terminal Priority: Critical HPMS/Tool Requirements: HPMS (Full Extent and Ramps)

Element: 21. Federal Aid/Route TypeRecommendation: Split into two data elements:• Federal Aid: Indicate if inventory route is Federal

aid• NHS: Used to indicate route’s function

Element: 21. Federal Aid• Attributes: – Route is non Federal-aid.– Route is Federal-aid, but not on NHS (i.e., all non-NHS

routes functionally classified as Interstate, Other Freeways & Expressways, Other Principal Arterials, Minor Arterials, Major Collectors, and Urban Minor Collectors).

– Route is on NHS.

Element: 22. Route Type• Attributes matched to the HPMS as follows:

– Non Connector NHS.– Major Airport.– Major Port Facility.– Major Amtrak Station.– Major Rail/Truck Terminal.– Major Inter City Bus Terminal.– Major Public Transportation or Multi-Modal Passenger Terminal.– Major Pipeline Terminal.– Major Ferry Terminal.

Currently: 27. Pavement Roughness/ Condition

Definition: The numeric value used to indicate pavement roughness. Attributes: • International Roughness Index (IRI), reported as an

integer to the nearest inch per mile. Priority: Value Added Preferred HPMS/Tool Requirements: HPMS (Full Extent and Ramps*, Sample*)

Element: 27. Pavement Roughness / Condition

Recommendation: Change the name to “International Roughness Index” to match to the HPMS and the LTPP as well as to make it more straight forward to users

Currently: 31. Number of Through Lanes Definition: The total number of through lanes on the segment. This excludes auxiliary lanes, such as collector-distributor lanes, weaving lanes, frontage road lanes, parking and turning lanes, acceleration/deceleration lanes, toll collection lanes, shoulders, and truck climbing lanes. Attributes: • Numeric Priority: Critical HPMS/Tool Requirements: HPMS (Full Extent and Ramps), HSM/IHSDM (Required), SafetyAnalyst (Required)

Element: 31. Number of Through Lanes

Recommendation: • Retain Version 1.0 definition but add clarification to text:

– “It is the number of through lanes in the direction of inventory. If the road is inventoried in both directions together, this would be the number of through lanes in both directions. If the road is inventoried separately for each direction, this would be the number of through lanes in one single direction.”

• Add an illustration• Add HOV to existing excluding list• Add a note for other types of lanes

Currently: 43. Right Shoulder TypeDefinition: The predominant shoulder type on the right side of road in the direction of inventory. Attributes: • None • Surfaced shoulder exists - bituminous concrete (AC) • Surfaced shoulder exists - Portland Cement Concrete surface (PCC) • Stabilized shoulder exists (stabilized gravel or other granular material with or

without admixture) • Combination shoulder exists (shoulder width has two or more surface types;

e.g., part of the shoulder width is surfaced and part of the width is earth) • Earth shoulder exists Priority: Critical HPMS/Tool Requirements: HPMS (Sample), HSM/IHSDM (Required), SafetyAnalyst (Optional)

Currently: 47. Left Shoulder TypeDefinition: Shoulder type on left side of roadway in direction of inventory. For undivided roads and divided roads with one direction of inventory, this will be the outside shoulder on the opposing side. Note that information on paved width of the inner (left) shoulder is included under median descriptors (see Element 49. Left Paved Shoulder Width). Attributes: • None • Surfaced shoulder exists - bituminous concrete (AC) • Surfaced shoulder exists - Portland Cement Concrete surface (PCC) • Stabilized shoulder exists (stabilized gravel or other granular material with or without

admixture) • Combination shoulder exists (shoulder width has two or more surface types; e.g., part

of the shoulder width is surfaced and part of the width is earth) • Earth shoulder exists Priority: Critical HPMS/Tool Requirements: HSM/IHSDM (Required), SafetyAnalyst (Optional)

Element: 43. Right Shoulder Type & 47. Left Shoulder Type

Recommendation: Add “curb” to the existing attribute list

Currently: 56. Median Barrier Presence / TypeDefinition: The presence and type of median barrier on the segment. Attributes: • None • Unprotected • Curbed • Rigid barrier system (i.e., concrete) • Semi-rigid barrier system (i.e., box beam, W-beam strong post, etc.) • Flexible barrier system (i.e., cable, W-beam weak post, etc.) • Rigidity unspecified Priority: Critical HPMS/Tool Requirements: HPMS (Sample)

Element: 56. Median Barrier Presence / Type

Recommendation: Revise attributes to match the HPMS:• None.• Unprotected. • Curbed.• Positive Barrier- unspecified. • Positive Barrier flexible. • Positive Barrier semi-rigid.• Positive Barrier rigid.

Currently: 67. Roadside RatingDefinition: A rating of the safety of the roadside, ranked on a seven-point categorical scale from 1 (best) to 7 (worst). Attributes: • Rating = 1

o Wide clear zones greater than or equal to 30 ft from the pavement edgeline.o Sideslope flatter than 1:4.o Recoverable.

• Rating = 2o Clear zone between 20 and 25 ft from pavement edgeline.o Sideslope about 1:4.o Recoverable

• Rating = 3……………

Priority: Critical Alternative HPMS/Tool Requirements: HSM/IHSDM (Required)

Element:67. Roadside Rating

• Remove this element from MIRE

Currently: 101. Toll Facility Definition: Presence and typed of toll facility on the segment. Attributes: • No toll • Toll paid in one direction only, non-high-occupancy toll (non-HOT)

lanes • Toll paid in both directions, non-HOT lanes • Toll paid in one direction, HOT lanes • Toll paid in both directions, HOT lanes Priority: Critical HPMS/Tool Requirements: HPMS (Full Extent)

Element: 101. Toll Facility

Recommendation: Add “Other Special Tolls” to the existing attribute list

Currently: 106. Bridge Numbers for Bridges in SegmentDefinition: Bridge numbers from bridge file for bridges in segment (See discussion in Introduction). Attributes: • Bridge number for each bridge in the segment. Priority: Critical (unless addresses in Bridge File provide linkage to other inventory files – See discussion in Introduction) HPMS/Tool Requirements: None

Element: 106. Bridge Numbers for Bridges in Segment

Recommendation: Modify Version 1.0 definition to reflect NBI definition (“official structure number”)

New Element: Safety Edge

Recommendation: • Add a new element “Safety Edge”• Attributes:

o Yeso No

• Add a graphic or photo

Recommended Revisions: Roadway Alignment

General Overview• Only SHRP 2 and NPS RID include information on

alignments• SHRP 2 RID uses similar names and attributes,• SHRP 2 RID and NPS do not include definitions • SHRP 2 RID includes significantly different

prescribed accuracy• None of the data sources include

collection/update frequency

II.a. Horizontal Curve Data

107. Curve Identifiers and Linkage Elements 108. Curve Feature Type 109. Horizontal Curve Degree or Radius 110. Horizontal Curve Length 111. Curve Superelevation 112. Horizontal Transition/Spiral Curve Presence 113. Horizontal Curve Intersection/Deflection Angle 114. Horizontal Curve Direction

II.b. Vertical Grade Data

115. Grade Identifiers and Linkage Elements 116. Vertical Alignment Feature Type 117. Percent of Gradient 118. Grade Length 119. Vertical Curve Length

II. Roadway Alignment Descriptors

Currently: 107. Curve Identifiers And Linkage Elements

Definition: All elements needed to define location of each curve record and all elements necessary to link with other safety files. Attributes: • Route and location descriptors (e.g., route and beginning and

ending milepoints or route and beginning and ending spatial coordinates). Must be consistent with other MIRE files for linkage.

Priority: Critical HPMS/Tool Requirements: HSM/IHSDM (Required)

Element: 107. Curve Identifiers And Linkage Elements

Recommendation: Modify the element name to “Curve Identifiers”. Change the definition to “All elements needed to define location of each curve record.”

Recommended Revisions: Roadway Junctions

General Overview• HPMS uses broader names, detailed definitions,

different attributes• SHRP 2 RID does not provide definitions, complete

attribute lists for all data elements or collection/update frequency

• Prescribed accuracy is not provided in SHRP 2 RID or HPMS

• None of the datasets include QA/QC procedures

III. Roadway Junction DescriptorsIII.a. At-Grade Intersection/Junctions

III.a.1. At-Grade Intersection/Junction General Descriptors III.a.2. At-Grade Intersection/Junction

Descriptors (Each Approach) III.b. Interchange and Ramp Descriptors

III.b.1. General Interchange Descriptors III.b.2. Interchange Ramp Descriptors

Currently:126. Intersection/Junction Geometry

Definition: The type of geometric configuration that best describes the intersection/junction. Attributes: • T-Intersection • Y-Intersection • Cross-Intersection (four legs) • Five or more legs and not circular • Roundabout • Other circular intersection (e.g., rotaries, neighborhood traffic circles) • Non-conventional intersection (e.g. superstreet, median U-turn, displaced left turn) • Midblock pedestrian crossing See Figure 6 for additional detail. Priority: Critical HPMS/Tool Requirements: HSM/IHSDM (Required), SafetyAnalyst (Required)

Element: 126. Intersection/Junction GeometryRecommendation: Break down current attribute “Non-conventional intersection (e.g. superstreet, median U-turn, displaced left turn)” to provide a complete list of non-conventional intersections. Add illustrations for new attributes.

Element: 126. Intersection/Junction Geometry• Recommended additional attributes:– Restricted crossing U-turn (i.e., RCUT, J-turn,

Superstreet) intersection– Median U-turn (i.e., MUT, Michigan Left, Thru-turn)

intersection– Displaced left-turn (i.e., DLT, continuous flow, CFI)

intersection– Jughandle (i.e., New Jersey jughandle) intersection– Continuous green T intersection– Quadrant (i.e., quadrant roadway) intersection

Currently:182. Interchange TypeDefinition: Type of interchange. Attributes: • Diamond • Full cloverleaf • Partial cloverleaf • Trumpet • Three-leg directional • Four-leg all-directional • Semi-directional • Single entrances and/or exits (partial interchange) • Single point interchange (SPI) • Other (e.g., double crossover diamond, displaced left turn, diverging diamond) See Figure 18 for additional detail. Priority: Critical HPMS/Tool Requirements: SafetyAnalyst (Required)

Element: 182. Interchange Type

Recommendation: Break down current attribute “Other (e.g., double crossover diamond, displaced left turn, diverging diamond)”to provide a complete list of non-conventional interchanges. Add illustrations for new attributes.

182. Interchange Type• Recommended additional attributes:– Diverging diamond (i.e., DDI, double-crossover

diamond, DCD) interchange– Double roundabout (i.e., double raindrop) interchange– Single roundabout (i.e., single raindrop) interchange– Quadrant

Currently: 155. Approach Left Turn Protection

Definition: Presence and type of left turn protection on the approach. Attributes: • Unsignalized • Signalized with no left turn protection (i.e., permissive) • Protected, all day • Protected, peak hour only • Protected permissive, all day • Protected permissive, peak hour only • Other Priority: Critical HPMS/Tool Requirements: HSM/IHSDM (Required), SafetyAnalyst (Required)

Element: 155. Approach Left Turn Protection

Recommendation: Add “Protected-permissive with flashing yellow arrow signal” to the existing attribute list

Currently: 190. Ramp Number of Lanes

Definition: Maximum number of lanes on ramp. Attributes: Numeric Priority: Critical HPMS/Tool Requirements: SafetyAnalyst (Optional)

Element: 190. Ramp Number of Lanes

Recommendation: Add the following text to the definition from HPMS: “Include the predominant number of (through) lanes on the ramp. Do not include turn lanes (exclusive or combined) at the termini unless they are continuous (turn) lanes over the entire length of the ramp.”

Currently:131. Intersection/Junction Traffic Control

Definition: Traffic control present at intersection/junction. Attributes: • Uncontrolled • Two-way stop • All-way stop • Yield sign • Signalized (with ped signal) • Signalized (w/o ped signal) • Railroad crossing, gates and flashing lights • Railroad crossing, flashing lights only • Railroad crossing, stop-sign controlled • Railroad crossing, crossbucks only • Other Priority: Critical HPMS/Tool Requirements: HSM/IHSDM (Required), SafetyAnalyst (Required)

Element: 131. Intersection/Junction Traffic ControlRecommendation: • Condense attributes “Signalized (with ped signal)” and

“Signalized (w/o ped signal)” into one attribute “Signalized.”

• Add one separate element for pedestrian traffic control “Pedestrian Signal Presence/Type”

New Element: Pedestrian Signal Presence/TypeAttributes: • None.• Pedestrian Signal with countdown indicator (with APS)• Pedestrian Signal with countdown indicator (w/o APS)• Pedestrian Signal without countdown indicator (with APS)• Pedestrian Signal without countdown indicator (w/o APS)

Add illustrations/photos for the new element

Currently:132. Signalization Presence/TypeDefinition: Presence and type of signalization at intersection/junction. Attributes: • No signal • Uncoordinated fixed time • Uncoordinated traffic actuated • Progressive coordination (with several signals along either road) • System coordination (e.g., real-time adapative systemwide) • Railroad crossing signal (includes signal-only and signal and gates) • Other Priority: Value added HPMS/Tool Requirements: SafetyAnalyst (Required)

Element: 132. Signalization Presence/TypeRecommendation: • Modify the existing attribute “Uncoordinated

traffic actuated” to “Uncoordinated motorist actuated”

• Add one attribute “Uncoordinated non-motorist actuated”

Currently: 157 Crosswalk Presence/Type

Definition: Presence and type of crosswalk crossing this approach leg. Attributes: • Unmarked crosswalk • Marked crosswalk • Marked crosswalk with supplemental devices (e.g., in-street yield signs, in-

pavement warning lights, pedestrian bulb outs, etc.) • Marked crosswalk with refuge island • Marked with refuge island and supplemental devices (e.g., in-street yield

signs, in-pavement warning lights, pedestrian bulb outs, etc.) • Pedestrian crossing prohibited at this approach • Other • Priority: Critical • HPMS/Tool Requirements: None

Element: 157. Crosswalk Presence/Type

Recommendation: • Add on attribute “Raised Crosswalk”• Add illustrations

Next Steps

Next Steps• Vet final recommendations with FHWA Technical

Working Group• Incorporate all revisions and develop MIRE V 2.0.

Additional Feedback/Questions

Thank you

FHWA Robert Pollack, Robert.Pollack@dot.govDr. Carol Tan, Carol.Tan@dot.gov

VHB Kim Eccles, keccles@vhb.comNancy Lefler, nlefler@vhb.com