25
FHWA Roadway Safety Data Program Webinar for FHWA Safety Field February 26, 2013 1

Thompson Roadway Safety Data Program

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Thompson Roadway Safety Data Program

FHWARoadway Safety Data Program

Webinar for FHWA Safety FieldFebruary 26, 2013

1

Page 2: Thompson Roadway Safety Data Program

2

Benefits of Safety Data • Use of integrated roadway, traffic, and crash

data in analysis can lead to more efficient use of funds and improved safety

Improved Safety

Outcomes

Better Targeted Safety

Investments

More Informed Decision Making

Improved Data

Collection

Page 3: Thompson Roadway Safety Data Program

3

MAP-21 - Safety Data Systems• States shall have in place a safety data system

sufficient to guide the Highway Safety Improvement Program (HSIP) and Strategic Highway Safety Plan (SHSP) processes.

Page 4: Thompson Roadway Safety Data Program

4

MAP-21 Guidance• Types of roadways covered• Types of data included• Geolocation of safety data to a common highway

basemap• Analysis and evaluation capabilities• Subset of Model Inventory of Roadway Data

Elements to be collected (referred to as the MIRE Fundamental Data Elements)

Page 5: Thompson Roadway Safety Data Program

5

System Requirements:Types of Roads• HSIP applies to all public roads• Data to be collected for all public roads, including:– State owned/maintained roads– Non State owned/maintained roads– Roads on tribal lands– Public roads on Federal lands

Page 6: Thompson Roadway Safety Data Program

6

System Requirements:Types of Data• Safety data to be collected includes:– Crash data– Roadway data– Traffic data– At RR grade crossings, highway and train traffic

• Identify fatalities and serious injuries on all public roads by location

• Diverse data sets should be able to be linked or integrated

Page 7: Thompson Roadway Safety Data Program

7

System Requirements: Geolocation of Safety Data• Crash, roadway and traffic data should be linkable

by geolocation to a basemap that is inclusive of all public roads within a State.

• August 7 2012, Memorandum on Geospatial Network for All Public Roads requires states to update LRS networks to include all public roads by June 15, 2014

Page 8: Thompson Roadway Safety Data Program

8

System Requirements:Analysis and Evaluation Capabilities• Ability to perform problem ID and countermeasure analysis• ID hazardous locations• Develop strategic and performance based safety goals• Advance State capabilities for data collection, analysis and

integration• Determine priorities and schedules for correction of

hazardous locations and conditions • Establish an evaluation process to assess results achieved by

safety projects

Page 9: Thompson Roadway Safety Data Program

9

Subset of Model Inventory of Roadway Elements (MIRE) to be Collected• MAP-21 required the establishment of a subset of

MIRE elements that are useful for roadway safety• Subset enables jurisdictions to analyze crash

experience of roadway networks relative to the expected average crash frequency given roadway and traffic characteristics at specific locations

Page 10: Thompson Roadway Safety Data Program

10

Subset of Model Inventory of Roadway Elements (MIRE) to be Collected – Cont.• For roads > 400 AADT subset includes:– Road segment elements– Intersection elements– Interchange/ramp elements

• For roads < 400 AADT subset includes: – Road segment elements– Intersection elements

Page 11: Thompson Roadway Safety Data Program

11

Subset of MIRE for Roads > 400 AADTRoadway Segment• Segment Identifier• Route Number• Route/street Name• Federal Aid/Route Type• Rural/Urban Designation• Surface Type• Begin Point Segment

Descriptor• End Point Segment Descriptor• Segment Length

• Direction of Inventory• Functional Class• Median Type• Access Control• One/Two-Way Operations• Number of through lanes• AADT• AADT Year• Type of Governmental

Ownership

Page 12: Thompson Roadway Safety Data Program

12

Subset of MIRE for Roads > 400 AADTIntersection• Unique Junction Identifier• Location Identifier for Road 1

Crossing Point• Location Identifier for Road 2

Crossing Point• Intersection/Junction Geometry• Intersection/Junction Traffic

Control• AADT [for each Intersection

Road]• AADT Year [for each Intersecting

Road]

Page 13: Thompson Roadway Safety Data Program

13

Subset of MIRE for Roads > 400 AADTInterchange/Ramp• Unique Interchange Identifier• Location Identifier for

Roadway at Beginning Ramp Terminal

• Location Identifier for Roadway at Ending Ramp Terminal

• Ramp Length• Roadway Type at Beginning

Ramp Terminal• Roadway Type at Ending

Ramp Terminal

• Interchange Type• Ramp AADT• Year of Ramp AADT• Functional Class• Type of Governmental

Ownership

Page 14: Thompson Roadway Safety Data Program

14

Subset of MIRE for Roads < 400 AADT

Roadway Segment• Segment Identifier• Functional Class• Surface Type• Type of Governmental

Ownership• Number of Through Lanes• AADT• Begin Point Segment

Descriptor• End Point Segment Descriptor• Rural/Urban Designation

Intersection• Unique Junction Identifier• Intersection/Junction

Geometry• Location Identifier for Road 1

Crossing Point• Location Identifier for Road 2

Crossing Point• Intersection/Junction Traffic

Control

Page 15: Thompson Roadway Safety Data Program

15

MAP-21 Eligible Safety Data Collection, Analysis, and Improvement Activities• “Highway safety improvement projects are

defined as strategies, activities and projects on a public road that are consistent with a State’s SHSP and correct or improve a hazardous road location or feature or address a highway safety problem.”

• Collection, analysis and improvement of safety data is specifically identified as an eligible project within the definition of a HSIP

Page 16: Thompson Roadway Safety Data Program

16

Complementary Processes• MAP-21 specifies that State efforts to advance

their capabilities for safety data collection, analysis and integration be conducted in a manner complements the Highway Safety Plan (NHTSA) and the Commercial Vehicle Safety Plan (FMCSA).

• The State TRCC • The State’s Traffic Records Strategic Plan– MIRE FDE Implementation Plan

Page 17: Thompson Roadway Safety Data Program

17

State Safety Data Guidance Links• Guidance on State Safety Data Systems

http://www.fhwa.dot.gov/map21/guidance/guidesafetydata.cfm

• Question & Answer on State Safety Data Systemshttp://www.fhwa.dot.gov/map21/qandas/qassds.cfm

Page 18: Thompson Roadway Safety Data Program

18

Roadway Safety Data Program• Roadway Safety Data Capability Assessment• Model Inventory of Roadway Elements (MIRE)

Management Information System (MIS)• Safety Data Technical Assistance Programs• Benefit-Cost Analysis Methodology for Safety Data

Investments• Highway Safety Manual (HSM) Implementation

Support

http://safety.fhwa.dot.gov/rsdp/Contact:Ray Krammes

Page 19: Thompson Roadway Safety Data Program

19

Roadway Safety Data Capabilities Assessment

• Individual State assessments: State Action Plans• National assessment: Final Report• 4 peer exchanges:– Help States refine and implement Action Plans– Identify States’ priorities for national action

http://safety.fhwa.dot.gov/rsdp/Contact:Esther Strawder

Page 20: Thompson Roadway Safety Data Program

20

States’ Priorities for National ActionData Collection• Noteworthy practices• Case studies• MAP-21 FDE guidance• Data on local roads• Technical assistance• Value of data improvementsData Analysis• Value of good analysis• Noteworthy practices• Training

Data Management• Guidance on data integration• Value of good data

management practices• Glossary of terms• Noteworthy practicesData Interoperability• Noteworthy TRCC practices• Value of linking data• Data “Focus States”• Training

Page 21: Thompson Roadway Safety Data Program

21

Model Inventory of Roadway Elements

• MIRE Version 1.0: Listing & definition of elements• MIRE Management Information System– MIRE MIS structure– Performance measures for MIRE data– MIRE element collection mechanisms– MIRE intersection data extraction methods– Application of “collective information” to MIRE data

http://safety.fhwa.dot.gov/rsdp/Contact:Bob Pollack

Page 22: Thompson Roadway Safety Data Program

22

Safety Data Technical Assistance• Crash Data Improvement Program• Roadway Data Improvement Program• Roadway Data Extraction Technical Assistance

Program (planned)• “Flexible” Technical Assistance (Planned)

http://safety.fhwa.dot.gov/rsdp/Contact:Bob Pollack

Page 23: Thompson Roadway Safety Data Program

23

Benefit-Cost Analysis Methodology for Safety Data Investments • Costs– Data collection– Data base operations and maintenance– Locating and coding crashes– Data storage

• Benefits– Reduced staff time from:

• More efficient project identification• Streamlined evaluation

– Crash savings from:• Faster project programming• Improved project prioritization

http://safety.fhwa.dot.gov/rsdp/Contact:Stuart Thompson

Page 24: Thompson Roadway Safety Data Program

24

HSM Implementation Support• Resources–HSM Implementation Guide for Managers–HSM Integration Guide –HSM Case Studies–HSM Training Guide – SPF Development/Calibration Guide

• Tools– Systemic Project Selection Tool – IHSDM–CMF Clearinghouse

• Training (NHI & Resource Center)• Technical assistance

http://safety.fhwa.dot.gov/rsdp/Contact:Mshadoni Smith

Page 25: Thompson Roadway Safety Data Program

25

New Efforts• Case Studies of Noteworthy Roadway Safety Data

and Analysis Practices• Toolbox of Resources to Improve States’ Roadway

Safety Data and Analysis Practices• Good Practices Guide and Pilots of Integrating

State and Local Roadway Safety Data• Business Case for Roadway Safety Data and

Analysis Improvements