Development of A Statewide Crash Map: Merging and Mapping State and Nonstate Crashes Onto a Single Network

Transcription

1 Development of A Statewide Crash Map: Merging and Mapping State and Nonstate Crashes Onto a Single Network 2011 GIS-T Symposium Hershey, PA Tuesday, March 29, 2011 Andrew Graettinger, Ph.D. University of Alabama Xiao Qin, Ph.D. South Dakota State University 1

2 PROJECT OVERVIEW Create a Single Statewide Crash Map by Combining Two Separate LRS and Automating Crash Placement METHODOLOGY Highway Crashes Local Road Crashes QA/QC Procedures PROJECT TIMEFRAME Outline 2

3 Bill Bremer, FHWA Safety Team Member Susie Forde, DTIM DOT Project Lead Andy Graettinger, UA Technical Lead CRASH MAPPING AND ANALYSIS Rebecca Szymkowski, DTSD DOT Co-Project Lead Steven Parker TOPS Project Manager Xiao Qin, SDSU CMAT Team Lead Jonathan DuChateau, DBM DOT Enterprise System Integration Project Team 3

4 Locate State and Off-state crashes on single map Have the ability to display multiple years of crash data Perform GIS-enabled safety analysis query functions Statewide Project Scope 4

5 LINK-LINK (UA): Transfer hand-coded highway crashes from state trunk network (STN) to local roads (WISLR) LRSs. C-MAT (SDSU): Automate mapping of local road crashes based on police crash report attributes. WisTransPortal (UW TOPS): Integrate statewide map into existing online crash data query and analysis tools. Project Components 5

6 Demonstration of Automatic Mapping of Wisconsin Local Crash Locations (2006) Prototype C-MAT development, tested on Madison 2003 crash data State and non-state Network Integration (2007) Identifying differences and similarities between STN and WISLR Local Safety Decision Support System (2008) C-MAT enhancements, application to additional jurisdictions Crash Mapping and Analysis Phase 1 (2009) LINK-LINK methodology development Crash Mapping and Analysis Phase 2 (2010) Combined statewide map for and future Project History 6

7 LINK-LINK: State and Non-State Merge 7

8 Identified and categorized the differences between STN and WISLR US Highway 12, Dane County State & Non-State Network Mapping Integration Jan 2007 Aug

9 QA/QC METHOD SHOWING DATA MOVED FROM STN TO WISLR Outlined and tested possible merge methods Site methods Site_STN Site_AccessPoint Link_link methods Uncalibrated Calibrated Wisconsin Crash Mapping Phase I (Sep 2007 July 2009) 9

10 The goal of Phase I was to determine the merging method that would yield the most accurate results with least disruption to WisDOT business practice Method Effort to: Type Category Subcategory Develop Edit Populate Maintain Site Site_STN High Medium High High Site_AccessPoint Medium High Low Low Link Link_Link Uncalibrated Low Low Low Medium Calibrated Low Low Medium Medium Wisconsin Crash Mapping Phase I 10

11 Wisconsin Crash Mapping Phase II Link_Link Method Example A (100) i (317) AccPt = STN part = STN full * (WILSR part / WISLR full) (100 60) * (158 / ( )) = 30 STN Links WISLR Links STNid STN start STN end WISLRid WISLR start WISLR end A 0 60 i A ii A iii 0 53 Flag Columns 11

12 Link checks Check for all STN links & valid WISLR link IDs Flag checks Gore Points Visual checks WISLR links Access Points Connector lines Quality Check / Assurance 12

13 Statewide Progress Percentage (By STN Links) 4% 31% 65% Current Completed Incomplete 13

14 281,300 RP crash records for ,691 crashes on coded STN links 100% of crashes moved successfully to WISLR Crash Points STN Links County Outline 14

15 C-MAT: Crash Mapping Automation Tool 15

16 Improve data and decision support for crash information and analysis by providing a single statewide crash map. The goal can be achieved through the following objectives: 1. Strengthen mapping capability for local crashes 2. Explore the potential of mapping state highway crashes 3. Develop a single statewide file of crash locations on WISLR 4. Develop QA/QC processes and procedures that will be implemented in C-MAT Goal and Objectives: C-MAT 16

17 Issues that contribute to inaccurate crash map location: Crash data (MV-4000) C-MAT Software WISLR Crash Location Considerations 17

18 1. Highway Name Processing Location description inconsistency between crash reports and the WISLR table, e.g. state and county highways. 2. Neighboring Municipalities MV4000 coded crashes to a different municipality than the WISLR data. 3. Spelling / Matching Algorithm Spelling errors, wrong highway or street type, wrong prefix/suffix, nuisance information (street block, address numbers, etc), and the combination of two or more. 4 Incomplete Segments In WISLR Links not represented (private road) in WISLR 5. Multiple Locations Found A series of issues in this category (horseshoe (H), name change (N), fork (F), loop termini (L), etc) Focus Areas for Node-level Map 18

19 1. Intersection direction not found 2. Intersection distance longer than the link length Focus Areas for Link-level Map 19

20 Focus Areas Solutions Status Highway Name Processing Neighboring Municipalities Incomplete Segments In WISLR Multiple Locations Found Spelling / Matching Algorithm Add designated highway type Parse concatenated names Define match priority Clean nuisance information Design a query to find neighboring municipalities n.a. Fix duplicates due to municipality errors Flag as H, F, N, or L Design procedure to map Multi-phase matching (a modified D-L algorithm) Completed on 12/31/10 Completed on 01/31/11 Future implementation Completed on 02/28/11 On-going Intersection Direction Intersection Distance Add route names to links Calculate link compass direction Priority match Add route names to links Calculate link length and offset On-going On-going Solutions 20

21 Total Crash Map Percentage Unique Duplicate 13% 12% 10% 61% 64% 69% Crashes* 586,724 Crashes in total, including 312,513 on local roads and 274,211 on state highways 12/1/2010 1/1/2011 2/1/2011 Local Roads Crash Map Percentage State Highways Crash Map Percentage Unique Duplicate Unique Duplicate 6% 7% 7% 14% 19% 18% 71% 73% 80% 49% 54% 56% 12/1/2010 1/1/2011 2/1/ /1/2010 1/1/2011 2/1/2011 Milestones 21

22 Quality Control Activities Establish comprehensive flags to: Provide confidence level Facilitate manual cleanup Provide feedback about MV4000 crash data Provide debugging details Evaluate map accuracy by comparing C-MAT output with moved state highway crashes. Evaluate map accuracy by comparing C-MAT output with Google maps output Evaluate WISLR update impact on C-MAT Evaluate subset of sample crashes manually QA/QC for C-MAT 22

23 Manual Review of Statewide Crash Map Random Sample of Crash Records: 90 crash records per county: 30 highway, 60 local roads Approximately 1% of total crashes for Basic Categories: Mapped Correctly Mapped Incorrectly Not Mapped Possible Cause: Data Issue GIS / LRS Issue C-MAT / LINK-LINK Issue QA/QC Procedure 23

24 WISDOT CRASH MAP CURRENT AND FUTURE City of Madison Crashes

25 ESTIMATED COMPLETION FOR STATEWIDE CRASH MAP / SAFETY ANALYSIS QUERY TOOL Pilot Phase Complete Link_Link / C-MAT / QA/QC Safety Analysis Query Tool Dev Function / System Test Staged Deployment END 2011 User Access WisDOT Regional Safety Engineers Other WisDOT Stakeholders External Users Project Timeframe 25

26 Project Management Susie Forde Chief, Data Management Section Wisconsin Department of Transportation Bureau of State Highway Programs Steven Parker IT Program Manager, TOPS Lab University of Wisconsin-Madison Department of Civil and Environmental Engineering Contact Information 26