Minnesota Crash Mapping Analysis Tool (MnCMAT) & Crash Data

1. 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 March 2012

2. 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) • Overview • Case Studies • Demonstration • Analyzing the Data • Green Sheets • Top 200 Intersection/Top 150 Sections • Rates vs Density • Traffic Engineering Fundamentals Handbook • Wrap-up

3. Data Source and Criteria • Sources • Police Accident Report • Paper • Electronic • Citizen (public) Report • 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

4. Police Accident Report (PAR) Overlay Report

5. Police Accident Report (PAR) Overlay (Front) Overlay (Back)

7. Citizen Accident Report Report (Front) Report (Back)

8. D-16 Manual “…promote uniformity and comparability of motor vehicle traffic statistics..” http://downloads.nsc.org/pdf/D16.1_Classification_Manual.pdf

9. D-16: Sample (53 pages)

10. Model Minimum Uniform Crash Criteria (MMUCC) “…provide a minimum, standardized data set for describing crashes of motor vehicles..” http://www.mmucc.us/

11. A Crash is NOT a simple event…. PERSON LEVEL CRASH LEVEL VEHICLE LEVEL

12. Importance of Data Elements (Top 3) • Education • County/city location • Seat belt usage • Drinking • Enforcement • Corridor location • Time of day • Day of week • Engineering • Location • Location • Location

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

14. Route Systems • State • 01: Interstate • 02: US Trunk Highway • 03: Mn Trunk Highway • 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.

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

16. Route Number (8 digits) • Trunk Highways (Systems 1 – 3) • Leading zeroes not needed • ISTH35W (stored as 0000035W) • USTH169 (stored at 00000169) • MNTH7 (stored as 00000007) • City Streets (MSAS and MUN) • First 4 digits are city number (NOT state aid number, but census number) • MSAS10400101(Duluth) • MUN 12500065(Faribault) • ALL OTHERS • First 2 digits are county number • CSAH02000001(Anoka county) • CR19000101(Dakota county)

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

18. Interchange Element Sketches

19. Crash Level Data Elements • Non-Location • When • Date • Time • Day of week • Light conditions • What • Type • Weather conditions • Road Conditions • Speed limit • Work Zone • Etc. • Severity • For CRASH, derived from most severe injury/fatality • Number killed • Number Injured

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

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

22. Transportation Information System (TIS) • Created in 1970’s • Mainframe: • User ID • SPF, JCL, TSO, ACF2 • #?!#!!!! (not user friendly) • Huge users manual • Reports fixed format

23. Generation 1 – 1970’s and 1980’sList Accidents by Ref Point (paper)

24. Generation 2 – 1990’sExcel spreadsheets Crash Level Vehicle/Person Level

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

26. Generation 3 – 2000’sMnCMAT

27. Presentation Overview • Development of Program • MnCMAT Features • Case Studies • Gaining Access • Questions and Demonstration

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

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

30. Basics of MnCMAT Program MnCMAT GIS Based Mapping System MnDOT Mainframe Data T.I.S. Data is Generated from Law Enforcement and Citizen Crash Reports

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

32. Basic MnCMAT Crash Analysis Process • Step 1 • Select Area to be Analyzed

33. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

34. State Wide Selection

35. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

36. Single County Selection

37. Multiple County Selection

38. County Selection

39. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

40. MnCMAT Toolbars

41. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

42. Selection by Rectangle

43. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

44. Selection by Polygon

45. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

46. Selection by Circle

47. MnCMAT Data • Covers Entire State • Primary Selection by County, District, Tribal Government, or State • Multiple Secondary Selection Methods • Rectangle • Polygon • Circle • Roadway Segments

48. Selection by Road Segment

49. Select Location with Find Location Selection • County • City • Intersection • Crash Number • XY Coordinate

50. Crash Data Using Stacks