FHWA MIRE Reassessment

1. FHWA MIRE Reassessment ATSIP Traffic Records Forum August 9, 2016 Carol Tan, PhD, FHWA Nancy Lefler, VHB

2. Overview • MIRE Background • Purpose of Project • Methodology • Recommended Revisions • Next Steps • Questions/Comments

3. Background

4. 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

5. Why MIRE? Role of Improved Data Collection

6. Federal Data Requirements • MAP-21 / FAST ACT • 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 on State Safety Data Systems: http://safety.fhwa.dot.gov/legislationandpolicy/fast/ssds_guidance.cfm

7. 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

8. Project Purpose

9. Purpose • Conduct assessment of MIRE V 1.0 • Develop recommended revisions • Develop MIRE V 2.0 • Goal - Meet the needs of the safety community & improve compatibility w/ FHWA data requirements

10. Methodology

11. 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 & across FHWA Offices • Develop MIRE V 2.0

12. 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

13. 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 • HSM-Highway Safety Manual

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

15. Data Summary

16. 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

17. 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

18. 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

19. Methodology Overview: Vet Recommended Revisions • Four Practitioner Vetting Sessions: • 1 In-person: 2015 TRB’s 5th Conference on Transportation Systems Performance Measurement and Data, Colorado, June 3, 2015 • 3 Webinars: June – Aug 2015 • More than 150 practitioners attended • FHWA Panel – February 3, 2016 • Reps from Safety, Planning, Asset Management, Operations, AASHTO, ITE, NACE, FMCSA

20. Recommended Revisions

21. Organization • Recommendations are categorized into four categories: • General findings/structure • Roadway segment data • Roadway alignment data • Roadway junction data

22. Recommended Revisions:General Findings /Structure

23. General Findings • Purpose/intended use of MIRE getting lost on States • Many States still not receiving the message that MIRE is a recommendation/starting point to improving their roadway data for safety

24. General Findings (Continued) • Recommended Revisions: • Introduction – update and condense • Overall Structure – revise to be more in-line with how States collect/store data • Structure of each element – revise to be more user-friendly

25. Introduction • Text out of date • The Introduction will include: • What MIRE is • Why it was developed • Intended use • Criteria for inclusion/exclusion • Importance of geo-spatial location • MAP-21/FAST Act requirements • All Roads Network of Linear Referenced Data (ARNOLD) • Rulemaking • Fundamental Data Elements • Newly published HSIP and Safety Performance Management Measures Final Rules

26. Introduction (continued) • The Introduction will include (continued): • Discussion on Integration (with other data) • Description of other types of data that can be integrated, e.g., roadside features • Language on MMUCC and linkage between MMUCC and MIRE • Language on linking crash, roadway, and traffic • Callout boxes to focus text • A list of resources • MIRE Management Information Systems (MIRE MIS) Resources • Case studies • Discussion on changing/emerging areas - including bicyclists and pedestrians, new elements in the unpublished HSM • Discussion on ADA • Language on safety related pavement data

27. Introduction (continued) • Condense text when possible • Move detailed information to Appendix • Add “How to Use MIRE” flow diagram

28. Current General Structure • 202 elements divided into three categories: • Roadway segments • Roadway alignments • Roadway junctions

29. 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

30. Recommended General Structure • Condense/simplify categories and subcategories into 6 basic data types: • Segment • Intersection • Intersection Leg • Interchange/Ramp • Horizontal Curve • Vertical Grade

31. Current Element Structure • Each element includes: • Name • Definition • List of attributes (coding) • Priority rating • How it relates to elements in HPMS and safety tools (SafetyAnalyst, HSM) • Illustration

32. Recommended Element Structure • Add indicator for FDE • Remove “Priority” • Revise “Attribute” to “Recommended Attributes” • Add crosswalk table

33. Crosswalk Table • List the corresponding HPMS and other database elements (database, elements name, number) for each relevant database • Include HSM data requirements • Include a comparison of MIRE to each database in a separate table in the Appendix, each database will have its own Appendix

34. Example: 54. Median Type – Current 54. Median Type Definition: The type of median present on the segment. Attributes: • Undivided • Flush paved median (at least 4 ft in width) • Raised median • Depressed median • Two-way left turn lane • Railroad or rapid transit • Divided, separate grades without retaining wall • Divided, separate grades with retaining wall • Other divided Priority: Critical HPMS/Tool Requirements: (Sample), HSM/IHSDM (Required), SafetyAnalyst (Required)

35. Example: 54. Median Type – Revised Format 54. Median Type FDE Definition: The type of median present on the segment. Recommended Attributes: • Undivided • Flush paved median (at least 4 ft in width) • Raised median • Depressed median • Two-way left turn lane • Railroad or rapid transit • Divided, separate grades without retaining wall • Divided, separate grades with retaining wall • Other divided

36. Example: : 54. Median Type – Revised Format (Continued) Crosswalk Table: Note: “—” indicates that the dataset does not include this specific MIRE element.

37. General Findings /Structure Additional questions/feedback?

38. Recommended Revisions:Roadway Segments

39. 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

40. General Overview • Majority of the revisions to segments elements • 21. Federal Aid/ Route Type • 27. Pavement Roughness/Condition • 31. Number of Through Lanes • 35. Auxiliary Lane Presence/Type • 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

41. 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)

42. 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, HOT, HOV/HOT, and transit lanes to the existing excluding list • Add a note for other types of lanes

43. Currently: 35. Auxiliary Lane Presence/Type Definition: The presence and type of auxiliary lane present on the segment. Center two-way left turn lanes and HOV lanes are not included here. They are included under Element 54. Median Type and Elements 37. HOV Lane Types and 38. HOV Lanes respectively.. Attributes: • Climbing lane • Passing lane • Exclusive continuous right-turn lane • Other

44. Currently: 35. Auxiliary Lane Presence/Type Recommendation: add the following attributes: • Part-time shoulder use • Part-time lane use • Special use lane

45. Currently: 56. Median Barrier Presence / Type Definition: 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)

46. 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.

47. Currently: 67. Roadside Rating Definition: A rating of the safety of the roadside, ranked on a seven-point categorical scale from 1 (best) to 7 (worst). Attributes: • Rating = 1 • Wide clear zones greater than or equal to 30 ft from the pavement edgeline. • Sideslope flatter than 1:4. • Recoverable. • Rating = 2 • Clear zone between 20 and 25 ft from pavement edgeline. • Sideslope about 1:4. • Recoverable • Rating = 3…………… Priority: Critical Alternative HPMS/Tool Requirements: HSM/IHSDM (Required)

49. Element:67. Roadside Rating • Keep this element • HSM uses this element to predict safety effect of rural two-lane two-way roads

50. 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)