Thompson Roadway Safety Data Program


Published on

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Thompson Roadway Safety Data Program

  1. 1. FHWARoadway Safety Data ProgramWebinar for FHWA Safety FieldFebruary 26, 20131
  2. 2. Benefits of Safety Data2• Use of integrated roadway, traffic, and crashdata in analysis can lead to more efficientuse of funds and improved safetyImprovedSafetyOutcomesBetterTargetedSafetyInvestmentsMoreInformedDecisionMakingImprovedDataCollection
  3. 3. MAP-21 - Safety Data Systems• States shall have in place a safety data systemsufficient to guide the Highway SafetyImprovement Program (HSIP) and StrategicHighway Safety Plan (SHSP) processes.3
  4. 4. MAP-21 Guidance• Types of roadways covered• Types of data included• Geolocation of safety data to a common highwaybasemap• Analysis and evaluation capabilities• Subset of Model Inventory of Roadway DataElements to be collected (referred to as the MIREFundamental Data Elements)4
  5. 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 lands5
  6. 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 publicroads by location• Diverse data sets should be able to be linked orintegrated6
  7. 7. System Requirements:Geolocation of Safety Data• Crash, roadway and traffic data should be linkableby geolocation to a basemap that is inclusive of allpublic roads within a State.• August 7 2012, Memorandum on GeospatialNetwork for All Public Roads requires states toupdate LRS networks to include all public roads byJune 15, 20147
  8. 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 andintegration• Determine priorities and schedules for correction ofhazardous locations and conditions• Establish an evaluation process to assess results achievedby safety projects8
  9. 9. Subset of Model Inventory of RoadwayElements (MIRE) to be Collected• MAP-21 required the establishment of a subset ofMIRE elements that are useful for roadway safety• Subset enables jurisdictions to analyze crashexperience of roadway networks relative to theexpected average crash frequency given roadwayand traffic characteristics at specific locations9
  10. 10. Subset of Model Inventory of RoadwayElements (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 elements10
  11. 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 SegmentDescriptor• End Point SegmentDescriptor• Segment Length• Direction of Inventory• Functional Class• Median Type• Access Control• One/Two-Way Operations• Number of through lanes• AADT• AADT Year• Type of GovernmentalOwnership11
  12. 12. Subset of MIRE for Roads > 400 AADTIntersection• Unique Junction Identifier• Location Identifier for Road 1Crossing Point• Location Identifier for Road 2Crossing Point• Intersection/JunctionGeometry• Intersection/Junction TrafficControl• AADT [for each IntersectionRoad]• AADT Year [for eachIntersecting Road]12
  13. 13. Subset of MIRE for Roads > 400 AADTInterchange/Ramp• Unique InterchangeIdentifier• Location Identifier forRoadway at BeginningRamp Terminal• Location Identifier forRoadway at Ending RampTerminal• Ramp Length• Roadway Type at BeginningRamp Terminal• Roadway Type at EndingRamp Terminal• Interchange Type• Ramp AADT• Year of Ramp AADT• Functional Class• Type of GovernmentalOwnership13
  14. 14. Subset of MIRE for Roads < 400 AADTRoadway Segment• Segment Identifier• Functional Class• Surface Type• Type of GovernmentalOwnership• Number of Through Lanes• AADT• Begin Point SegmentDescriptor• End Point SegmentDescriptor• Rural/Urban DesignationIntersection• Unique Junction Identifier• Intersection/JunctionGeometry• Location Identifier for Road1 Crossing Point• Location Identifier for Road2 Crossing Point• Intersection/Junction TrafficControl14
  15. 15. MAP-21 Eligible Safety Data Collection,Analysis, and Improvement Activities• “Highway safety improvement projects aredefined as strategies, activities and projects on apublic road that are consistent with a State’s SHSPand correct or improve a hazardous road locationor feature or address a highway safety problem.”• Collection, analysis and improvement of safetydata is specifically identified as an eligible projectwithin the definition of a HSIP15
  16. 16. Complementary Processes• MAP-21 specifies that State efforts to advancetheir capabilities for safety data collection,analysis and integration be conducted in amanner 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 Plan16
  17. 17. State Safety Data Guidance Links• Guidance on State Safety Data Systems• Question & Answer on State Safety Data Systems
  18. 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 DataInvestments• Highway Safety Manual (HSM) ImplementationSupport18 Krammes
  19. 19. Roadway Safety Data CapabilitiesAssessment• 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 action19 Strawder
  20. 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• TrainingData Management• Guidance on dataintegration• Value of good datamanagement practices• Glossary of terms• Noteworthy practicesData Interoperability• Noteworthy TRCC practices• Value of linking data• Data “Focus States”• Training20
  21. 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 data21 Pollack
  22. 22. Safety Data Technical Assistance• Crash Data Improvement Program• Roadway Data Improvement Program• Roadway Data Extraction Technical AssistanceProgram (planned)• “Flexible” Technical Assistance (Planned)22 Pollack
  23. 23. Benefit-Cost Analysis Methodology forSafety 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 prioritization23 Thompson
  24. 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 assistance24 Smith
  25. 25. New Efforts• Case Studies of Noteworthy Roadway Safety Dataand Analysis Practices• Toolbox of Resources to Improve States’ RoadwaySafety Data and Analysis Practices• Good Practices Guide and Pilots of IntegratingState and Local Roadway Safety Data• Business Case for Roadway Safety Data andAnalysis Improvements25