1. 1 Safety Data in a GIS Environment: New Tools for the Four Es Sponsored by the Iowa Department of Transportation Office of Transportation Safety Reginald R. Souleyrette Tim R. Strauss Iowa State University Prepared for the 24th International Forum on Traffic Records and Highway Information Systems July 26-28, 1998 Minneapolis, Minnesota

2. 2 Why Crash Analysis Systems? >100 persons killed/day (>37,000 in 1996) 8.8 million crashes per year in USA 2.3 million injuries vast amount of uncoordinated data powerful/low cost computing potentially huge B/C source: NHTSA 1997

3. 3 Past/present ALAS (PC-ALAS) PC-based system User-friendly interface, easy to learn About 700,000 crashes over 10 years Provides easy access to data Several Uses: –obtain accident statistics by time and location –query database by accident/driver characteristics –generate reports on-screen, to a file, to the printer

4. 4 Current Difficulties Node numbers must be identified from tables or paper maps Difficult to analyze patterns Does not readily support integration of additional data Hard to identify crash “hot spots” and to analyze causes and countermeasures

5. 5

6. 6 Past/present ALAS

7. 7

8. 8

9. 9

10. 10

11. 11

12. 12 GIS-ALAS Project Goals Develop geographic/map-based ALAS Use Power of GIS Portable, accessible, windows based Free users from node maps statewide coverage supports highway safety analysis facilitate integration with other data

13. 13 Software Selection GIS World list –distribution –development language –vendor stability short list (pre-Geomedia) –ESRI (ArcView, Arcview Publisher, ArcExplorer, MapObjects) –Mapinfo –Caliper (Maptitude)

14. 14

15. 15 Software Selection (cont.) ESRI chosen –ISU site license (low cost development) –dynamic segmentation –network analysis –tech. Support (ISU GIS Facility) –FHWA platform –web application (MapObjects, Internet Mapper) –ArcExplorer, ArcPublisher May migrate later

16. 16 Crash Locations text Text - node ID, x, y MapBasic interpolation program MapInfo Crash Locations CAD node file MGE (unit conversion) Text - node ID, lat, long MapInfo Node Locations Paper crash records DB2 - ID - from node - to node - distance - crash information MIF ArcView Crash Locations x’ y’

17. 17

18. 18 DB2 - ID - location information - A (crash) records - B (driver 1) record - B (driver 2) record - … - C (1st 3 injuries) record - C (2nd 3 injuries) record -... Crash Information Paper crash records MapBasic defines 3 tables A, B and C MapInfo text MIF ArcView Crash Information (for ArcView-ALAS) text fortran ABBBC ArcView Crash Information (for Explorer-ALAS)

19. 19 Background Data IDMS Base Records (DOT) - ADT - pavement type - lane width -... CAD Roads (DOT) - State - County - Local Text file - vertices - information MapInfo/MapBasic aggregate to county level MIFArcView CAD Hydrology (DOT) DXF Rail (BTS) BTS preprocessor

20. 20

21. 21 Avenue Scripts

22. 22 PC ALAS GIS ALAS

23. 23 Usability Study Evaluate capabilities Assess documentation Identify bugs and problems in data Identify differences between users' and designers' perceptions Report user difficulties Report on success of revision

24. 24 Logical Query

25. 25 Spatial Query

26. 26 Visual Display of Crash Frequencies

27. 27 Possible error Error Checking

28. 28

29. 29

30. 30

31. 31

32. 32 Animal-related Crashes

33. 33 Applications: Collision Diagram Software Interface

34. 34 Emergency Response Applications Emergency response areas Nearest facility/shortest path to crash Impact of “Avenue of the Saints” on emergency response CODES - linking crash and hospital records

35. 35 EMS Response Areas

36. 36 Aerial Photo Integration

37. 37 Fire Districts Response Changes

38. 38

39. 39 Software enhancements Fire Service Application/Avenue of the Saints Model integration Training Ongoing Efforts

40. 40 x Nearest node 2nd nearest node in opposite direction 150 ft. 42.340912 N 94.182790 W 3405 3412 42.340912 N 94.182790 W from 3405, to 3412, 150 ft.

41. 41 WWW.CTRE.IASTATE.EDU

42. 42