1 / 39

Crash Data Quality A Pragmatic Approach

Learn about the importance of data quality, the process of obtaining quality data, and how it can improve information and decision-making. Explore examples of timeliness, completeness, and accuracy in crash data.

kinah
Télécharger la présentation

Crash Data Quality A Pragmatic Approach

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. Crash Data QualityA Pragmatic Approach Aug 7, 2016 Joe McCarthy – JDI Consulting

  2. 35,200 Source: NHTSA Press Release, July 1 JDI/WYDOT - HWS Performance Measures

  3. The Role of Quality Data TRF at Baltimore

  4. My Key Points • Need data about data quality • Data quality as a process • Getting that data • Data to info to improve JDI/WYDOT - HWS Performance Measures

  5. Data about Data Quality • How are things currently • How good / bad overall • Which parts are good or bad • What are the trends • Are things getting better or worse • Where is improvement most needed Source: esdf.org JDI/WYDOT - HWS Performance Measures

  6. Crash Data Flow Trooper/ Officer enters Supervisor reviews, approves Submit to Owner Owner corrects errors Analysts use the data

  7. Quality Process & Crash Data Act Trooper/ Officer enters Supervisor reviews, approves Submit to Owner Owner corrects errors Analysts use the data Monitor / Track JDI/WYDOT - HWS Performance Measures

  8. Some Specific Examples • Timeliness • Completeness (Unknowns in Critical Elements) • Accuracy (Locations) JDI/WYDOT - HWS Performance Measures

  9. Timeliness • Goal: • Ensure records available when needed • Measure: • Number of days between event and available in database • Information of interest: • Statewide average (overall) • % Over 10 days (to spot outliers) • By agency; to focus improvement efforts • Trends JDI/WYDOT - HWS Performance Measures

  10. Crash Timeliness Data Points Submit timestamp Submitting agency Event timestamp Officer Enters Report Supervisor reviews, approves HWS reviews, accepts HWS corrects data Analysts use the data JDI/WYDOT - HWS Performance Measures

  11. Crash Timeliness Data PD SO LEA HWP • Crash Fields • Report ID • Incident Date Crash Records • Submittal Fields • Report ID • Agency • Submit Date Submittal Data JDI/WYDOT - HWS Performance Measures

  12. Resulting Timeliness Data Table • Submittal Fields • Report ID • Agency • Submit Date • Crash Fields • Report ID • Incident Date JDI/WYDOT - HWS Performance Measures

  13. Timeliness – Information (1) • Average # days: 7.73 • Percent exceeding 10 days: 8.2 TRF at Baltimore

  14. Timeliness – Information (2) • Most improved agencies • Reduced submittal time JDI/WYDOT - HWS Performance Measures

  15. Timeliness PM Benefits • Know that average timeliness is fine • Know that there are some serious outliers • Know the outlier agencies • Can track changes over time • Can take adapted actions • Quarterly reports to agencies • Offered training • Offered assistance • Have seen significant improvements JDI/WYDOT - HWS Performance Measures

  16. Completeness - Critical Elements • Goal: • Improve critical element data (not “unknown”) • Measure: • Percent of critical elements “unknown” • Exclude hit & run crashes • Information of interest • Which elements have most unknown • Which agencies enter most unknowns • Trends, changes JDI/WYDOT - HWS Performance Measures

  17. Element Unknown Data PD SO LEA HWP • Crash Fields • Report ID • Element data Crash Records • Submittal Fields • Report ID • Submit date • Agency Submittal Data JDI/WYDOT - HWS Performance Measures

  18. Resulting Unknown Data Table • Crash Fields • Report ID • Element data • Submittal Fields • Report ID • Submitted date • Agency JDI/WYDOT - HWS Performance Measures

  19. Completeness – Critical Elements JDI/WYDOT - HWS Performance Measures

  20. Completeness – Critical Elements TRF at Baltimore

  21. Completeness – Critical Elements TRF at Baltimore

  22. Completeness PM Benefits • Know which elements have most unknowns • Know which agencies enter most unknowns • Can track changes over time • Can take adapted actions, e.g. • Improve manual, form, etc. for confusing elements • Inform agencies regarding relative performance • Offer assistance JDI/WYDOT - HWS Performance Measures

  23. Accuracy - Location • Goal: • Improve location accuracy • Measure: • Percent of records without validation errors in location • A valid location provided • If more than one location method, they are equivalent • Information of interest • Statewide % (quantify issue, baseline) • Trends JDI/WYDOT - HWS Performance Measures

  24. GeoLocation Side Bar • Point location of the crash – 3 methods • Route & Milepost • Latitude & Longitude • Intersection & Offset • Conversion between them in GIS • Deduce data from the location • Link to other data using the location JDI/WYDOT - HWS Performance Measures

  25. Crash Location JDI/WYDOT - HWS Performance Measures

  26. Crash Location Methods • 42.8330 -108.7307 • ML20B @ 121.457 • 0.52 mi NW of BELLEVUE @ LEEDY JDI/WYDOT - HWS Performance Measures

  27. Data Deduced (GIS) From Location • City: Lander • County: Fremont • WYDOT District: 5 • … JDI/WYDOT - HWS Performance Measures

  28. Data Linked by Location • Number lanes: 4 • Speed Limit: 45 MPH • Rumble strips: N • … JDI/WYDOT - HWS Performance Measures

  29. Crash Location Accuracy Ideally, valid at time of entry Corrected by HWS Officer Enters Report Supervisor reviews, approves HWS reviews, accepts HWS corrects data Analysts use the data Measure % valid (submitted) Measure % valid (corrected) JDI/WYDOT - HWS Performance Measures

  30. Valid Location Data Table JDI/WYDOT - HWS Performance Measures

  31. Location Accuracy Results • % of records without validation errors in location • Baseline: 65% for 2015 • After location correction by HWS • Next steps • Breakdown by agency • Measure before correction by HWS TRF at Baltimore

  32. Location Accuracy PM Benefits • Know that location accuracy needs attention • Even with “location wizard” • Even after HWS corrections • Can take adapted actions • Pursue map-based crash reporting capability • Improve location QC JDI/WYDOT - HWS Performance Measures

  33. Operations - Correcting the Location • Goal: • Improve organization efficiency • Operational measures: • Time to correct • Percent validation errors after correction • Information of interest • General efficiency (baseline) • Relative performance of staff (to focus support) JDI/WYDOT - HWS Performance Measures

  34. Crash Location Accuracy Ideally, valid at time of entry Corrected by HWS Officer Enters Report Supervisor reviews, approves HWS reviews, accepts HWS corrects data Analysts use the data Measure % valid (submitted) Measure % valid (corrected) JDI/WYDOT - HWS Performance Measures

  35. Collecting Operational Data QAF WYDOT’s crash data quality assurance framework • REPORT ID • Field • Who fixed • How long Additional Data Crash Data Corrected location data Data about the correction JDI/WYDOT - HWS Performance Measures

  36. Operational Data Table JDI/WYDOT - HWS Performance Measures

  37. Operational PM Benefits • Know that location corrections are inadequate • Can track changes over time • Can take adapted actions • Monitor organizational efficiency • Currently monitor accuracy of corrections • Add monitoring of time • Pursue improved correction tools JDI/WYDOT - HWS Performance Measures

  38. Take-Away Points • Data quality as a process • Need data about data quality • Getting that data • Data to info to improve JDI/WYDOT - HWS Performance Measures

  39. Questions? Comments? Thank You! JoeGMcCarthy@yahoo.com

More Related