Minnesota Crash Mapping Analysis Tool (MnCMAT) & Crash Data Mark Vizecky (Va-Sis-Ski) State Aid for Local Transportation Program Support Engineer Sulmaan Khan State Aid for Local.
Download ReportTranscript Minnesota Crash Mapping Analysis Tool (MnCMAT) & Crash Data Mark Vizecky (Va-Sis-Ski) State Aid for Local Transportation Program Support Engineer Sulmaan Khan State Aid for Local.
Minnesota Crash Mapping Analysis Tool (MnCMAT) & Crash Data Mark Vizecky (Va-Sis-Ski) State Aid for Local Transportation Program Support Engineer Sulmaan Khan State Aid for Local Transportation Assistant Project Development Engineer February 2015 Agenda Welcome - Introductions Sources of Crash Data Crash Detail Levels Methods of Retrieval Transportation Information System (TIS) (Gen 1) Excel Spreadsheet (Gen 2) MnCMAT (Gen 3) Analyzing the Data Overview Case Studies Demonstration Green Sheets Top 200 Intersection/Top 150 Sections Rates vs Density Traffic Engineering Fundamentals Handbook Wrap-up Data Source and Criteria Sources Police Accident Report Citizen (public) Report Paper Electronic Paper Electronic Criteria (D-16 manual) Fatality, Injury or Property Damage >$1,000 Roadway open to the public Death must be within 30 days for fatality Intentional and medical caused NOT counted http://www.dot.state.mn.us/stateaid/crash-flowchart.html Police Accident Report (PAR) Overlay Report Police Accident Report (PAR) Overlay (Front) Overlay (Back) Citizen Accident Report Report Report (Front) (Back) New Crash Reporting System University of Minnesota Human First Lab contracted to identify ways to improve crash report form using human factors to: Moving forward, Minnesota will use entirely electronic crash reports Appriss is developing the new system University of Minnesota Human First Lab providing usability testing support to Appriss as new system is being developed Additional features in the new system will include: Improve accuracy Speed Reliability Meaningfulness of crash report data Information bubbles with additional information about the crash report to support law enforcement officers as they enter data Only pertinent questions to the crash will be shown New crash report environment will be available to all law enforcement in January 2016 D-16 Manual “…promote uniformity and comparability of motor vehicle traffic statistics..” http://www-nrd.nhtsa.dot.gov/Pubs/07D16.pdf D-16: Sample (53 pages) Model Minimum Uniform Crash Criteria (MMUCC) “…provide a minimum, standardized data set for describing crashes of motor vehicles..” http://mmucc.us/sites/default/files/MMUCC_4th_Ed.pdf A Crash is NOT a simple event…. PERSON LEVEL CRASH LEVEL VEHICLE LEVEL Importance of Data Elements Education Enforcement County/city location Seat belt usage Drinking Corridor location Time of day Day of week Engineering Location Location Location (Top 3) Crash Level data elements Location Route System Route Number Reference point (nnn+00.111 is wild guess) Interchange element Reliability Numbers = DPS only, Alpha = MnDOT 1 or A – Confident (within feet) 2 or B – Less confident (within .25 mi) 3 or C - Best guess (within 1 mile) 4 or D - Wild guess (within county or city) City County Route Systems State City 05: Municipal State Aid (MSAS) 10: Municipal (M) County 04: County State Aid Highway (CSAH) 07: County Road Other 08/09: Township (Organized/Unorganized) 14: State Forest road 23: Airport Roads 24:Private roads (no ref points) 30: Alleys (no ref points) Etc. 01: Interstate 02: US Trunk Highway 03: Mn Trunk Highway Crash Level data elements Location Route System Route Number Reference point (nnn+00.111 is wild guess) Interchange element Reliability Numbers = DPS only, Alpha = MnDOT 1 or A – Confident (within feet) 2 or B – Less confident (within .25 mi) 3 or C - Best guess (within 1 mile) 4 or D - Wild guess (within county or city) City County Route Number (8 digits) Trunk Highways (Systems 1 – 3) Leading zeroes not needed City Streets (MSAS and MUN) First 4 digits are city number (NOT state aid number, but census number) ISTH 35W (stored as 0000035W) USTH 169 (stored at 00000169) MNTH 7 (stored as 00000007) MSAS 10400101 (Duluth) MUN 12500065 (Faribault) ALL OTHERS First 2 digits are county number CSAH 02000001 (Anoka county) CR 19000101 (Dakota county) Crash Level data elements Location Route System Route Number Reference point (nnn+00.111 is wild guess) Interchange element Reliability Numbers = DPS only, Alpha = MnDOT 1 or A – Confident (within feet) 2 or B – Less confident (within .25 mi) 3 or C - Best guess (within 1 mile) 4 or D - Wild guess (within county or city) City County Interchange Element Sketches Interchange Element Sketches Question: How large should the selection area be at this interchange? C B A Crash Level Data Elements Non-Location When What Date Time Day of week Light conditions Type Weather conditions Road Conditions Speed limit Work Zone Etc. Severity For CRASH, derived from most severe injury/fatality Number killed Number Injured Person Level Data Elements Who Non-Public (Name, Address) we do NOT get Age Gender Condition Alcohol Drugs License restrictions/endorsements Safety Equipment Seat Belts Air bags Helmet Severity Vehicle Level Data Elements Vehicle info Type Make Body type Actions Contributing factors (up to 2) Sequence of Events (up to 4) Pre-accident Action Most harmful event Direction of Travel Transportation Information System (TIS) Created in 1970’s Mainframe: User ID SPF, JCL, TSO, ACF2 #?!#!!!! (not user friendly) Huge users manual Reports fixed format Generation 1 – 1970’s and 1980’s List Accidents by Ref Point (paper) Generation 2 – 1990’s Excel spreadsheets Crash Level Vehicle/Person Level Pro’s – ALL Methods Important TIS Mainframe Traffic/Rate capabilities Has intersection/section capabilities Has sophisticated multi file linkages The only practical option for some analysis Excel Easy to use – well known software Sort and filter Updated easily MnCMAT Mapping Charting Filtering Generation 3 – 2000’s MnCMAT Presentation Overview Development of Program MnCMAT Features Case Studies Gaining Access Questions and Demonstration Brief History of MnCMAT Developed in Iowa late 1990’s – early 2000’s Iowa DOT & CTRE @ ISU Original named Crash Mapping Analysis Tool (CMAT) Introduced to Minnesota in 2006 Via County Engineers Funded by Local Road Research Board (LRRB) Project Research Implementation Committee (RIC) State Aid for Local Transportation (SALT) Crash Analysis Tool Classification Macroscopic Tool Large Area Coverage Trends and Statistics Microscopic Tool Drill Down Capabilities Filters Selection Capabilities GIS Base Mapping Tool Visual Tool Charts Maps Reports Data Files Basics of MnCMAT Program MnCMAT Crash Occurs MnDOT Mainframe Data Transportation Information System (T.I.S.) GIS Based Mapping System Location Crash Type Road Condition Driver Data XXXXXX XXXXXX XXXXXX XXXXXX T.I.S. Data is Generated from Law Enforcement and Citizen Crash Reports Average Delay to “Real Time” Crash Data Uploaded to TIS 1 6 Updated 4 times each year Data Available to Locals M Crash Data Received by MnDOT Crash Reports Completed Data Available to MnDOT 3 Crash Report Submitted to DVS 120 28* M Avg. Day(s) to Complete Task 3 Crash Data Upload to MnCMAT 25* 1 14 Crash Located *The following process flow and duration is only the average time to complete each task. Crash reports can and do take longer to complete a task(s), impacting the cumulative days. Crash Data - 2013 Total Per Day All All Roadways Roadways Total Co Roadway Per Day Co Roadway Total City Roadway Per Day City Roadway 76,754 20,435 56 21,872 60 211 Yearly Reports by Agency State Patrol 23,121 County Sheriff 8,607 City Police 39,786 Citizen 4,990 State Patrol 585 County Sheriff 5,231 City Police 13,102 Citizen 1,436 State Patrol 302 County Sheriff 811 City Police 18,776 Citizen 1,882 Data Source: Minnesota Crash Mapping Analysis Tool (MnCMAT) 02/06/2015 Crash Location Density City Roadways All Roadways Co Roadways Data Source: Minnesota Crash Mapping Analysis Tool (MnCMAT) 02/06/2015 Basic MnCMAT Crash Analysis Process Step 1 Select Area to be Analyzed Step 2 Apply Filtering Criteria Step 3 Generate Output Maps Charts Reports Data Files Basic MnCMAT Crash Analysis Process Step 1 Select Area to be Analyzed MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments State Wide Selection MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments Single County Selection Multiple County Selection County Selection MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments MnCMAT Toolbars MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments Selection by Rectangle MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments Selection by Polygon MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments Selection by Circle MnCMAT Data Covers Entire State Primary Selection by County, District, Tribal Government, or State Multiple Secondary Selection Methods Rectangle Polygon Circle Roadway Segments Selection by Road Segment Select Location with Find Location Selection County City Intersection Crash Number XY Coordinate Time to Locate a Crash • 40 hrs x 52 wks = 2080 • Vacation = 80 hours • Holidays = 80 hours • Sick time = 16 hours • Education = 24 hours • Breaks = 120 hours • Dept Mtgs = 21 hours • Annual Inservices = 2 hours • Non productive time = 343 hours • Remaining hours = 1737 hours 69,279 reported crashes 2012 1737 productive work hrs x 60 mins/hr = 104,220 productive work mins 104,220 productive work mins/69,279 reported crashes 2012 1.5 productive work mins/reported crash 4 coders 1.5 x 4 = 6.0 productive work mins/reported crash @ 69 reports per day This is not actual productivity data. This information is from a medical coding productivity assessment and only used for illustrative purposes. Find that Crash Crash Number 111990118 in Dakota Co Where? Who? What? When? Why? How? Crash Data Using Stacks Basic MnCMAT Crash Analysis Process Step 1 Select Area to be Analyzed Step 2 Apply Filtering Criteria Filter Selection Filter Categories City Contributing Factor 1 Contributing Factor 2 County Crash Diagram Crash Severity Day of Month Day of Week Driver Age Driver Condition Driver Gender First Harmful Event Investigating Officer Light Condition MnDOT District Month Number of Fatalities Number of Vehicles Relation to Intersection Reliability of Information Road Design Roadway Character Speed Limit Surface Conditions System Class Time of Day Traffic Control Device Travel Direction Tribal Govt. Type of Crash Type of Work Zone Vehicle Action Vehicle Travel Direction Vehicle Type Weather Conditions Year Filters Within MnCMAT Select the data applicable to the situation of interest. Single or multiple filters may be applied. Each filter provides “AND” logic between filter categories and “OR” logic within each filter Active Filter Selection Statistics Filters Within MnCMAT Select the data applicable to the situation of interest. Single or multiple filters may be applied. Each filter provides “AND” logic between filter categories and “OR” logic within each filter Filters Within MnCMAT OR AND Question: How many ROR crashes with a severity of K or A occurred at this interchange? Basic MnCMAT Crash Analysis Process Step 1 Select Area to be Analyzed Step 2 Apply Filtering Criteria Step 3 Generate Output Maps Charts Reports Data Files Graphical Outputs View of Crash Incidents in Larger Area Wide Area Crash Locations with Stacks Data Exports Crash Data Exports as a CSV or Shape File Crash Data Exported as a CSV or Shape File Charts Crash Severity Day of Week Reports Summary Report Detail Report Crash Type Summary Report Driver and Time Summary Top 100 Intersections Report Top 100 Segments Report Case Study No. 1 Crash Severity for Lane Departures Crashes Q. “What is the crash severity for lane departure crashes in the City of Faribault between 2009-2013?” Steps Needed for Case 1 1. Select Crash Data (circle with red, blue and yellow graphic), then select Crash Filters. 2. Select City under Location Filters, then check Faribault. 3. Select Crash Year under Attribute Filters, then check years 2009-2013. 4. Select Crash Diagram and select crash codes pertaining to lane departure crashes. (sideswipe passing/opposing, Ran off Road-Left/Right and head on) 5. Click OK. 6. Select Charts, then select Crash Severity under the dropdown menu, then select Add Chart Lane Departure Crashes by Severity Lane Departure Crashes by Severity • • The previous slide illustrates that most crashes between 2009-2013 involved property damage followed by possible injury crashes. There was a total of 321 crashes during this time frame. Case Study No. 2 Q. “What are the most dominant crash diagram types resulting from chemical impairment as the 1st contributing factor in the City of Faribault?” Steps Needed for Case 2 1. Select Crash Data, then select Crash Filters. 2. Select City under Location Filters and then check Faribault. 3. Select Contributing Factor 1 under Attribute Filters and then check Chemical Impairment. 4. Click OK. 5. Select Charts, then select Diagram under the dropdown menu, then select Add Chart Crash Diagram resulting from Chemical Impairment in Faribault Crash Diagram resulting from Chemical Impairment in Faribault The bar chart on the previous slide illustrates that the three most occurring crashes as a result of chemical impairment are rear end, ran off the road (right side) and ran off road (left side) There was a total of 53 crashes. Case Study No. 3 Q. “What number of reported crashes involve younger (under 21) inexperienced drivers as the 1st contributing factor that ran off the road in Faribault?” Steps Needed for Case 3 1. Select Crash Data, then select Crash Filters. 2. Select City, and then check Faribault. 3. Select Driver Age, then check appropriate boxes for Drivers under 21. 4. Select Contributing Factor 1, then check Inexperience. 5. Select Crash Diagram and select crash codes pertaining to lane departure crashes. (sideswipe passing/opposing, Ran off Road-Left/Right and head on), then click Ok. 6. Select Charts, then select Diagram under the dropdown menu, then select Add Chart. Distracted Young Drivers Online MnCMAT Tool Inexperienced Young Drivers The crash reports indicate that there was one head on, two ran off road right side, and one ran off road left side crashes. Case Study No. 4 Q. “How many young drivers (<21) were involved in K & A crashes that was a result of disregarding a traffic device as the 1st contributing factor within the Metro District ?” Steps Needed for Case 4 1. Select Create New Project, then select the Metro District and click OK. 2. Select Crash Data, then select Crash Filters, then select Crash Severity and select the appropriate codes for K & A crashes. 3. Select Driver Age and select the appropriate ages for drivers under 21. 4. Select Contributing Factor 1 and select Disregard Traffic Device, and click OK. 5. Select Charts, then select Crash Severity under the dropdown menu, and then select Add Chart. Young (<21) Drivers involved in K & A crashes by Disregarding Traffic Devices in Metro District Young (<21) Drivers involved in K & A crashes by Disregarding Traffic Devices in Metro District The graphs on the previous slide show that there were a total of 115 K & A crashes involving young drivers disregarding traffic devices Of the 115 crashes, 94 crashes (over 80%) were incapacitating accidents Summary The proceeding case studies are very basic examples of use of MnCMAT. More complicated reports may be run. Even more complicated reports that require information on data not contained in MnCMAT (for example, seat belt use of non-drivers) would require special reports. MnCMAT Distribution Being Supplied by MnDOT – State Aid No additional software required No Cost to City or County Agencies or Other Entities Approved by a City or County Approval Form for Use MnCMAT’s Website http://www.dot.state.mn.us/stateaid/crashmapping.html DISCLAIMER Knowledge is power…with great power, comes great responsibility. The State, County and Municipal Transportation Authorities of Minnesota make no representation or warranties, express or implied, with respect to the reuse of the data provided herewith, regardless of its format or means no guarantee or representation to the user as to the accuracy, currentness, suitability, or reliability of this data for any purpose. The of its transmission. There is user accepts that data “as is”, and assumes all risks associated with its use. The State, County and Municipal Transportation Authorities of Minnesota assume no responsibility, actual or consequential damage, as a result of any user’s reliance of this data. By submitting this form, you are stating that you understand that this Engineering Judgment must be used when interpreting all data. application is only a tool and that You are also agreeing that you understand that the data set used by this program is subject to errors and changes, therefore not to be assumed as absolute. The Minnesota Department of Transportation, State Aid Division maintains all rights to this application and may revoke your privileges of use at any time. No Guarantee http://www.keyc.com/story/24635744/forsberg-raises-concern-over-crash-numbersfor-mankato-roundabout Revoke Your Privileges MnCMAT Support Contact Mark Vizecky Sulmaan Khan 651-366-3839 651-366-3829 [email protected] Intersection “Green sheets” Section Top Intersections – per location Crash costs – Step 1 Get Minnesota Data Crashes Fatalities Injury A Injury B Injury C Vehicles Fatal 1,569 1,724 411 555 512 2,730 Severity A 5,674 - 6,636 1,735 1,494 9,991 Severity B 26,975 - - 33,928 6,824 48,788 Severity C 49,894 - - - 65,755 96,651 PDO 186,839 - - - - 340,915 Total 270,950 1,724 7,047 36,218 74,585 499,074 Step 2 – get current year costs from FHWA Year GDP Deflator Fatal A injury B Injury C Injury PDO 2003 106.41 $3,065,246 $212,209 $42,442 $22,400 $2,358 2004 109.43 $3,152,240 $218,232 $43,646 $23,036 $2,425 2005 112.74 $3,247,587 $224,833 $44,967 $23,732 $2,498 Step 3 – calculate cost for current year Severity Fatal Costs Fatal $5,598,840,847 Severity A Severity B Severity C PDO Injury A Costs Injury B Costs Injury C Costs Sum Costs Crashes Cost per Crash $92,293,939 $24,956,461 $12,150,974 * $5,728,242,220 1,569 $3,650,887 $1,491,991,660 $77,994,561 $35,456,161 * $1,605,442,382 5,674 $282,947 $1,525,626,673 $161,937,828 * $1,687,564,501 26,975 $62,561 $1,560,522,001 * $1,560,522,001 49,894 $31,277 $851,654,840 186,839 $4,558 PDO Costs $851,654,840 *PDO costs are not shown due to incorporation into other crash severities. Crash Costs Crash Severity 2013 Cost New 2014 Cost $6,800,000 $10,300,000 Severity A $540,000 $550,000 Severity B $160,000 $160,000 Severity C $80,000 $81,000 $3,300 $7,400 Fatal PDO Top Sections – per mile Crash Rates Determined by dividing observed crash frequency by measure of exposure Crash Rate = Crash Frequency Exposure/Unit of Time Frequency (Crashes/Year) Crash Rates Rate = Y/X 9 Short Comings: 6 •Assumes a linear relationship •Drives prioritization toward low volume routes 3 Y X 5,000 10,000 AADT 15,000 Crash Density For Intersections Density = Crashes For Sections Density = Crashes/Miles Rates or Density ? Severity Rates For Intersections SR = ((F*5)+(A*4)+(B*3)+(C*2)+(PD)) (EV * Days) Where EV = Entering Vehicles. For Sections SR = ((F*5)+(A*4)+(B*3)+(C*2)+(PD)) (ADT*Length * Days) CRASH FACTS – annual report by DPS •Provides a statistical summary Minnesota’s reported crashes Section I - All Crashes Section II - Alcohol-Related Section III - Safety Equipment Section IV - Motorcycle Section V - Truck Section VI - Pedestrian Section VII - Bicycle Section VIII - School Bus Section IX - Train Section X - Teen Drivers Section XI - Senior Drivers https://dps.mn.gov/divisions/ots/reports-statistics/pages/crash-facts.aspx Fundamentals Book http://www.dot.state.mn.us/stateaid/trafficsafety.html Crash Modification Factors (CMFs) http://www.cmfclearinghouse.org/ Books Worth Reading The Drunkard’s Walk Traffic HSIP Program Challenge to determine where to focus safety funds Black spots are infrequent on local roads Fatal and Severe injury crashes are random on local roads County Roads Trunk Highway 2,089 Severe Crashes 2,168 Severe Crashes 45,000 miles of road 12,000 miles of road 0.05 severe crashes per mile 0.18 severe crashes per mile Questions?