1. ITE District 6 June 27, 2006 Incorporating Incident Data into a Freeway Data Archive for Improved Performance Measurement ITE District 6 June 27, 2006 Suman Tasnim, Robert L. Bertini, Kristin A. Tufte Jessica Potter Computer Science Undergrad ITS Lab Portland State University

2. ITE District 6 June 27, 2006 PORTAL Website http://portal.its.pdx.edu

3. ITE District 6 June 27, 2006 Objective Incorporate incident data into PORTAL PORTAL: Portland Oregon Regional Transportation Archive Listing –US DOT ADUS framework –Archives 20-second speed, occupancy, volume data for Portland, OR area freeways –Begun July 2004, 502 inductive loop detectors in the Portland Metro area –Also archive: weather, traffic counts, bus AVL data coming soon Why incident data? –20,000 reported incidents/year in the Portland, OR area –Improve incident response & more accurate performance measures

4. ITE District 6 June 27, 2006 Incident Data Description Incident data from ODOT ATMS (Advanced Transportation Management Systems) Database 139,484 incidents from July 30, 1999 – Dec 31, 2005 Data entered by operators at the ODOT TMOC (Traffic Management Operations Center)

5. ITE District 6 June 27, 2006 Portland Metro / ODOT Region 1

6. ITE District 6 June 27, 2006 Life of an Incident Incident Occurs Incident Reported Incident Confirmed Dispatch Response Incident Cleared Reported as Cleared Congestion Ends

7. ITE District 6 June 27, 2006 Example Entries for One Incident Operators make many entries per incident Each entry has 92 fields –Primary Route, Confirm Time, Incident Type (crash, debris, stall, etc.) On average 4.1 entries per incident IdLanes Affected Confirm Time Last Update Time Primary Route Direc- tion Police Response 11342 2005-12-15 17:05:05 I-20510 11341 2005-12-15 17:05:05 2005-12-15 17:08:23 I-20511 11340 2005-12-15 17:05:05 2005-12-15 17:10:15 I-20511

8. ITE District 6 June 27, 2006 Example Entries for One Incident Resulting Incident Record: IdLanes Affected DurationHighway IdPolice Response 113425:1031 IdLanes Affected Confirm Time Last Update Time Primary Route Direc -tion Police Response 11342 2005-12-15 17:05:05 I-20510 11341 2005-12-15 17:05:05 2005-12-15 17:08:23 I-20511 11340 2005-12-15 17:05:05 2005-12-15 17:10:15 I-20511

9. ITE District 6 June 27, 2006 Data Cleaning Challenges Many different names for a freeway –i205, i-205, I205, I-205, 205 Many different ways to specify location on freeway. –Milepost (3%) –Geolocated (19%) –Landmark in location comments –Exit Name –Street nearby that is not an exit –Bridge name –No Specification

10. ITE District 6 June 27, 2006 Cleaning Process Multiple Entries  Single Record –Duration derived from “confirm time” and “last update time” –Final record reflects highest severity during the incident –Highway ID derived from “primary route” and “direction id” –Flags in incident record indicate if a particular action occurred at any time during an incident –UTLFlag derived from comment field

11. ITE District 6 June 27, 2006 Incident Data Analysis PORTAL –Volume –Speed –Occupancy –Weather Incident Data Cleaning Result –Traffic analysis –Duration analysis –Incidents compared with VMT and VHT –On-the-fly graphs

12. ITE District 6 June 27, 2006 Speed Contour Map I-205 NB Just South of Hwy 212 Milepost 2005-11-15 Highway I-205 Northspeed 00:00 04:00 08:00 12:00 16:00 20:00 00:00 Time Data Provided by Oregon DOT 4 6 8 10 12 14 16 18

13. ITE District 6 June 27, 2006 Incidents By Type and Number of Lanes (1999-2005) N=120,819N=116,233* *incidents with complete lane location data

14. ITE District 6 June 27, 2006 Incidents by Location (1999-2005) N=120,819

15. ITE District 6 June 27, 2006 Incident Tree (2005) N = 14253 * In-Lane 37.3% Shoulder 62.7% Crash 41.1% Stall 58.9% Crash 10.3% Stall 89.7% One Lane 71.8% Multi-Lane 28.2% One Lane 98.8% Multi-Lane 1.2% * Incidents with complete lane location data

16. ITE District 6 June 27, 2006 Crashes and Precipitation (2005)

17. ITE District 6 June 27, 2006 Incident Statistics (1999-2005)* HighwayFull Length Incidents/ Mile/Day Monitored Length Incidents/VMT (x10 -6 )** I-5 NB250.3123.027.5 I-5 SB250.3120.726.6 1-205 NB250.1820.074.6 1-205 SB250.2024.124.7 OR 217N70.136.942.7 *Selected highways; table includes located incidents only **2005 incidents only, Incidents reported on Full Length, VMT calculated on Monitored Length

18. ITE District 6 June 27, 2006 Incidents and VMT by Month (1999-2005)

19. ITE District 6 June 27, 2006 Incidents by Hour and Type (1999-2005) Hour of Day Number of Incidents

20. ITE District 6 June 27, 2006 Conclusion & Future Work Incident data cleaning –Start with multiple entries –Condense to one record Data analysis with clean data Incorporate into PORTAL

21. ITE District 6 June 27, 2006 Acknowledgements ODOT –Hau Hagedorn –Jack Marchant PORTAL Team National Science Foundation

22. ITE District 6 June 27, 2006 PORTAL Website http://portal.its.pdx.edu

23. ITE District 6 June 27, 2006 Thank You

24. ITE District 6 June 27, 2006 EXTRAS

25. ITE District 6 June 27, 2006 Incident Statistics (1999-2005)* HighwayFull LenInc/Mile/DayMonitored LenIncidents/VMT** I-5 NB250.3123.027.5 I-5 SB250.3120.726.6 1-205 NB250.1820.074.6 1-205 SB250.2024.124.7 I-84 EB650.063.716.9 I-84 WB650.0710.538.8 US 26 EB520.0513.337.6 US 26 WB520.088.4130.3 I-405N40.300- I-405S40.342.4720.1 OR 217N70.136.942.7 OR 217S70.1110.782.4 *Table includes located incidents only *2005 incidents only, VMT is x10^-6