1 / 35

GIS-ALAS: Accident Location and Analysis System

GIS-ALAS: Accident Location and Analysis System. Sponsored by the Iowa Department of Transportation Office of Transportation Safety. Why Crash Analysis Systems?. >100 persons killed/day (>37,000 in 1996) 8.8 million crashes per year in USA 2.3 million injuries

fadhila
Download Presentation

GIS-ALAS: Accident Location and Analysis System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GIS-ALAS: Accident Location and Analysis System Sponsored by the Iowa Department of Transportation Office of Transportation Safety

  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. 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. 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. CAD Node Maps

  6. Past/present ALAS

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

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

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

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

  11. MapBasic defines 3 tables A, B and C Crash Information MIF MapInfo Paper crash records ArcView Crash Information (for ArcView-ALAS) text 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 - ... text fortran ABBBC ArcView Crash Information (for Explorer-ALAS)

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

  13. Avenue Scripts

  14. GIS ALAS PC ALAS GIS ALAS PC ALAS PC ALAS GIS ALAS

  15. Logical Query

  16. Spatial Query

  17. Error Checking Possible error

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

  19. Phase II • refine gis-alas and explorer alas • currently building explorer ABBBC database (99%!) • working with past UNI work. future? • intersection analysis capabilities (work with UI?) • link-node lat/long conversion process • assess avenue of saints as case study • tech transfer, TRAINING!!! (how to use, why it's useful!) • Jan - Oct 98

  20. Applications: Collision Diagram Software Interface

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

  22. 13 Total Accidents Fatalities Total Sev. Total Acc. 4 Fatal Accidents Fatal Acc. Prop. Dmg. Total Inj. 8 Fatalities 4 Injury Accidents 2 Major Injuries 3 Minor Injuries 3 Possible Injuries 5 PDO Accidents 65 Total Severity 2 Ran Stop Sign 3 FTYROW From Stop Sign 1 FTYROW Making Left-Turn 3 Speed too Fast for Condition 4 None Apparent Aerial photo integration File Request Search Report Analysis Defaults Help F1 View Details, Sorted by:

  23. WWW.CTRE.IASTATE.EDU

More Related