Police Training Improvement Program

1. Police Training Improvement Program Date Location

2. Agenda • Reasons data collected/Data quality • Information Sharing Challenges for Researchers • What you can do to help • KY Specific issues

3. Information Sharing Challenges for Researchers Reg Souleyrette, PhD, PE

4. the challenges researchers face in … • Finding • Accessing • Using • Sharing safety-related data and information. • Data • Methods

5. Safety Data (Core traffic records systems)

6. Performance Measures -The Quality “Six Pack” • Timeliness (need depends on use) • Accuracy (spatial, temporal, attribute) • Consistency/Uniformity • Definitions (e.g., MMUCC) • Over time • Completeness • Records (rows) – e.g., by agency • Items (columns) – e.g., MIRE • Ability to integrate (spatial, key field, personal identifiers, etc.) • Accessibility

7. Quality varies … • By State, Agency, and System • Over time • By researcher’s time available, effort, and “connections” – often best in the state they live in – some firms/universities have excellent connections with multiple states and use it as a competitive advantage in winning work • By data steward time, care and willingness • According to legal limitations (and perceived legal limitations/risk aversion) • By type (e.g., inattention) • By who you talk to (e.g., TRCC) Many times, the quality is “unknown” or not asked about

13. e.g., roadway completeness … Inventory data on all roads? The “quadrennial needs” legacy State system as a percent of all public roads Yes Some, quality issue, or working on it No No Response

14. e.g., medical integration and accessibility

15. Spatial accuracy – there’s a lot to it…

16. Where are the roads? (Incorrect or incomplete cartography) Feature under construction Feature not represented Alignment Off Alignment OK

17. Where are the roads? (Improving cartography) Alignment moves Alignment stays put

18. Where are the crashes? • Crashes are not necessarily point events • Some crashes may be located using different methods and degree of accuracy • Temporal (e.g. link node to lat long) • Spatial (e.g., state police v. local) • Techno (GPS v. smart map) • LRS-based location methods such as route-milepoint or milepost. ?

19. What’s “the” traffic volume on “the” road? • Need traffic level for the year the crash happened • May require multiple files or even systems • Potential changes to existing alignments, e.g. expansion of a two lane road to a four lane expressway, change of jurisdiction (and name), etc • Was the road even there then? Is the road still there?

20. How to segment the road system? • Requirements • Logical breaks (engineering and public) • Relationship to inventory data • Long enough for manageability and presentation • Short enough to reflect important changes • Clear and understandable to use • Facility location and type • What is rural/urban? Character is important … Designated “rural”

21. What is an intersection crash? Can use attributes and/or proximity… Red: probable, Yellow: spatial @ 75’, Blue: possible + spatial

22. Challenges • Finding (Google, identification of responsible authority – not just who has the data, research librarian, student lit review, personal awareness, ask somebody/list serve, description/metadata; survey) • Accessing – ranges from freely available on the internet to requesting/pestering/going up the chain of command to MOU to NA • Using – statistics, models, HSM, … quality • Sharing – ownership, permission, documentation/metadata

23. KYOPSCompleting/Reviewing Collision Reports Alvin E. Cook - Lexington Police

25. Map It must be used to identify collision locations • Remember we never use roadway aloneLocation must be intersection with, between streets, ramp, or private property/parking lot. Map It will provide all streets when you use the drop down feature EXCEPT when private property/parking is utilized.

26. CLICK HERE

27. Ramps When selecting a ramp… • Identify the ramp • Then select “SAVE” (this will automatically enter the cross streets) • MAKE SURE “RAMP DIRECTION” boxes (on left side of screen) • Have N, E, S, or W entered. • Ramps will not list names of roadways. NEVER CHANGE THE CENTER STREET NAME AS LISTED IN MAP IT.

28. You MUST have an intersecting street for intersection collisions. Select the intersecting street by using the drop down feature in MAP IT. • You MUST have cross streets for between streets collisions. Select the between streets by using the drop down feature in MAP IT. • DO NOT select the same cross streets UNLESS MAP IT does not provide different cross streets in the drop down feature.

29. Number of Lanes Only count the number of through traffic lanes for the roadway that the collision occurred. DO NOT COUNT TURNING LANES OR EMERGENCY LANES • IE; Nicholasville Road at Alumni Drive. Nicholasville Road has 4 through lanes. • IE; Man O War Blvd at Boston Rd. Man O War Blvd has 4 through lanes. • IE: E. Main St at N. Limestone. E. Main St has 3 through lanes.

30. Traffic Control • All intersection collisions MUST have one of the following; • Stop Sign • Stop and Go Signal • Yield Sign An advisory speed sign is yellow in color. DO NOT use advisory speed sign for REGULATORY SPEED SIGN (BLACK & WHITE).

31. Property Damage • Officers must use standard list provide in the MDC resource.

32. Contributing Human Factors. Unit 1 MUST have a contributing factor. * Avoid using INATTENTION * If you select DISTRACTION – YOU MUST EXPLAIN THE DISTRACTION IN THE NARRATIVE. * Avoid using NOT UNDER PROPER CONTROL – most of the time this is too fast for conditions. Example of not under proper control would be foot slips off brake and unit strikes unit already stopped in front. * On Hit and Run collision you must complete all entries that you have information on. IE; contributing human factor – may be 97 (other) because you can not determine if the unit was backing etc. 1st event should be other motor vehicle or select what the unit struck- do not leave blank. * When using 97 (other) in any collision other than hit and run you must attempt to explain in narrative.

33. Officer put INATTENTION for Human Factor • Should Be Fail to Yield Right of Way • *NOTE* Is this narrative correct? Unit 1 should be the at fault Unit.

34. Officer put INATTENTION as Human Factor • Could Be Following Too Close • Or if Unit 2 not moving could be Not Under Proper Control

35. Officer put INATTENTION • Should be Improper Backing

36. Officer put INATTENTION AS HUMAN FACTOR. • SHOULD BE DISREGARDING TRAFFIC CONTROL DEVICE • Narrative not correct (last line) (car s/b card)

37. Supplements You have two options to complete a supplement crash report: 1. You can open the report from your “ACCEPTED” folder (a) open the report and change or add information, continue to finish and then re-transmit 2. You can retrieve the report from KYOPS: (a) open KYOPS and go to Tools (top of screen) and right click to display drop down menu, select “Retrieve Collision/Crime Report”. Enter your user ID and password and then complete the required fields. *** Hit & Run Reports*** Supplement to Hit and Run reports: Hit and Run reports are reassigned to the Hit & Run Unit within 24 hours of being accepted in KYOPS for further investigation. Please inform the Hit & Run Unit that you have completed a supplement or reassigned a hit and run report so the Unit has the most up to date report.

38. Evaluation Of The Accuracy Of Kentucky’s Traffic Crash Data Eric Green, GISP, MSCE, PE

39. Agenda • Review of results from two research studies on location • Recommendations: how can YOU make the data better? • Where a crash should be located? • Other suggested improvements

40. Reporting Location

41. 2004 Report • Data from January to June of 2003 • GPS added in 2000, required June 1st, 2002 • Accuracy by County, Route and Milepoint (CRMP) • Linear reference system • 55% correct • Accuracy by GPS • Using Magellan SporTrak handheld unit • 58% correct

42. Random Sample • 222 random crashes from 2009 were reviewed • All had GPS generated by the MapIt system • This was considered the reported location • The presumed location was derived from: • Report narratives • Addresses • Intersecting or between roads • The accuracy of each location was classified: • YES – within 500 feet of actual location • NO – outside of 500 feet from actual location • UNKNOWN – unable to determine actual location

43. Random Sample Results

44. Random Sample Results • If the unknown location were removed: • 152 of the 167 or 92% were accurate • 92% can be compared to a similar study conducted 6 years ago which yielded: • 58% were correct by GPS • 55% were correct by CRMP

45. Crashes Coded as Inaccurate • GPS is not consistent with address/reference (12 crashes) • No reference point (1 crash) • These could be a result of the officer needing to "guess" where to click on the mapping system • Additional reference systems could help minimize this error

46. Crash Database Analysis • Latest data containing the MapIt-based location • October 1st, 2007 to December 31st, 2009 • 334,354 crashes • Data were plotted using CRMP data • GPS data was assigned to all plotted CRMP crashes • The distance between the GPS location and the CRMP location was calculated

47. Crash Data Potted by GPS

48. Crash Data plotted by GPS Showing County Check

49. Average Distance by Year (Usable) *2007 only represents 3 months of the year

50. Paper and Modified MapIt Crashes by Submission Type