1 / 38

HILLSBOROUGH COUNTY TRAFFIC CRASH DATA MANAGEMENT SYSTEM

Outline. History of Crash Data Collection at HCSOGrant Funding Obtained through FDOTTraffic Analyst position establishedMilestones and AccomplishmentsWho is involved?What will the CDMS do? Tools and FunctionsHow do we use the CDMS today? . Crash Data Collection. Crash ReportData Entry into

lorin
Download Presentation

HILLSBOROUGH COUNTY TRAFFIC CRASH DATA MANAGEMENT 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. HILLSBOROUGH COUNTY TRAFFIC CRASH DATA MANAGEMENT SYSTEM Presented by John W. Chaffin Research and Development Bureau Crime Analysis Unit, Manager October 9, 2006

    2. Outline History of Crash Data Collection at HCSO Grant Funding Obtained through FDOT Traffic Analyst position established Milestones and Accomplishments Who is involved? What will the CDMS do? Tools and Functions How do we use the CDMS today?

    3. Crash Data Collection Crash Report Data Entry into Traffic Accident Reporting System (TARS) TARS written in late 1980’s TARS captures all fields of crash report excluding narrative TARS database is antiquated TARS does not have any data analysis tools

    4. TARS Database in Mapper Tars database set up in mapper Cabinet with 4 separate Rids containing pertinent crash data from report. The rids function separately but are mutually connected by the agency report. TARS was created in 1986 and was on the cutting edge of technology then for Traffic crash data management. But as Technology has changed drastically over the past 18 years, TARS has not. Tars database set up in mapper Cabinet with 4 separate Rids containing pertinent crash data from report. The rids function separately but are mutually connected by the agency report. TARS was created in 1986 and was on the cutting edge of technology then for Traffic crash data management. But as Technology has changed drastically over the past 18 years, TARS has not.

    5. Tars Code Tables Each column with data in the TARS database has a code table with values that correspond to data indicated on the crash report. Most of the code tables are represented by number values. Each column with data in the TARS database has a code table with values that correspond to data indicated on the crash report. Most of the code tables are represented by number values.

    6. Accident Info: Where, When, etc. Accident Information RID gives us about as much information as the CAD system. Where, Date, DOW, Time, Report#. Accident Information RID gives us about as much information as the CAD system. Where, Date, DOW, Time, Report#.

    7. Vehicle/Persons- Who, Vehicle, etc. Vehicle/Persons RID tells us what persons and vehicles were involved. Aside from the VEHICLE MAKE. This is not easily decipherable without great assistance from the code tables. Data is very HARD to extract. NO LOCATION FIELD. Vehicle/Persons RID tells us what persons and vehicles were involved. Aside from the VEHICLE MAKE. This is not easily decipherable without great assistance from the code tables. Data is very HARD to extract. NO LOCATION FIELD.

    8. Accident Detail – Contributing Causes, Harmful events, Weather, etc Looking at the ACCIDENT DETAIL RID, this data should tell us about the sequence of events that led to the crash, such as the drivers actions, road conditions, weather, etc. Again, NO LOCATION FIELD. This would be an discouraging task to try and extract data about crashes and map. Looking at the ACCIDENT DETAIL RID, this data should tell us about the sequence of events that led to the crash, such as the drivers actions, road conditions, weather, etc. Again, NO LOCATION FIELD. This would be an discouraging task to try and extract data about crashes and map.

    9. Citation Information The Citation RID is a little more informative, yet again lies the problem that it is in a different Rid and it is very time consuming and a painstaking task to match this data up to the other 3 rids for overall analysis and mapping. The Citation RID is a little more informative, yet again lies the problem that it is in a different Rid and it is very time consuming and a painstaking task to match this data up to the other 3 rids for overall analysis and mapping.

    10. CAD – Calls for Service Where and When Only Our best source of immediately available data to map is the CFS from our CAD system. The analyst can map this easily and quickly, yet it is limited in the data is provides: where and when. Our best source of immediately available data to map is the CFS from our CAD system. The analyst can map this easily and quickly, yet it is limited in the data is provides: where and when.

    11. HCSO Obtains Crash Data Analysis Grant Three year grant awarded by Florida Department of Transportation effective December 10, 2003 Traffic Analyst starts in Community Relations Section February 6, 2004 Hillsborough County Sheriff’s Office and Hillsborough County Public Works holds press conference February 13, 2004

    12. Milestones and Accomplishments February 19, 2004: First monthly meeting with Traffic Analyst at the Sheriff’s Traffic Operations Plan (STOP) committee meeting and first monthly traffic crash report, continuing monthly thereafter at each STOP meeting Top 20 Traffic Crash Corridors are identified during February 2004 Deployment of HCSO Traffic Units for Selective Enforcement Initiatives takes a paradigm shift after February 2004 monthly report is distributed Traffic Enforcement Initiatives begin in February 2004 targeting the identified crash corridors and continues Set up a database for tracking and mapping purposes to identify the last drinking location of DUI offenders for the Responsible Vendor Program

    13. Who’s Involved? Hillsborough County Sheriff’s Office Hillsborough County Public Works Florida Department of Transportation –D7 Florida Highway Patrol Tindale-Oliver and Associates, Inc. City of Tampa

    14. Using GIS Technology to Improve Analysis Streamline Accessibility to Traffic Crash Data Less time consuming and cumbersome to analyze data All data fields and related information in manageable GIS database More Focused Crash Analysis Red Light Running Crashes Speeding Related Crashes DUI Crashes Aggressive Driving Enforcement Unrestrained drivers Identification of Crash Corridors for Focused Enforcement Initiatives Moving towards a more integrated approach. We will have the data previously seen from Mapper snapshots in one Geodatabase using ArcGIS. The data will be in plain English and will allow the Analyst to be able to focus there efforts towards ANALYSIS rather than just modifying and aggregating the data from TARS so that it is understandable. Moving towards a more integrated approach. We will have the data previously seen from Mapper snapshots in one Geodatabase using ArcGIS. The data will be in plain English and will allow the Analyst to be able to focus there efforts towards ANALYSIS rather than just modifying and aggregating the data from TARS so that it is understandable.

    15. Getting the Data to GIS

    16. Crash Geodatabase

    17. Symbology Layers

    18. Symbology Layers

    19. Symbology Layers

    20. TOA Crash Data Tools

    21. TOA Crash Data Tools

    22. TOA Crash Data Tools

    23. TOA Crash Data Tools

    24. TOA Crash Data Tools

    25. TOA Crash Data Tools

    26. TOA Crash Data Tools

    27. TOA Crash Data Tools

    28. TOA Crash Data Tools

    29. TOA Crash Data Tools

    30. TOA Crash Data Tools

    31. TOA Crash Data Tools

    32. TOA Crash Data Tools

    33. What do we do at HCSO? Monthly Traffic Crash Report for STOP Frequency analysis (time and day) Spatial analysis (Layer summary by area) Comparative analysis of crash corridors Enforcement Activity analysis Monthly Traffic Fatality Summary Tracking and monitoring of responsible vendor database Requested crash data analysis for enforcement initiatives Crash analysis studies for command staff Assist public safety and traffic engineering agencies

    34. Monthly STOP Report

    35. Monthly STOP Report

    36. Traffic Fatality Summary for Command Staff

    37. Assisting Other Agencies

    38. Questions and Discussion

    39. HILLSBOROUGH COUNTY TRAFFIC CRASH DATA MANAGEMENT SYSTEM October 9, 2006

More Related