1.25 Police Body Cameras (summary)

This dataset contains annual data, including number of events (count of arrivals to calls for service, up to one per officer per call), and number of events with at least one matching video. This data is the basis for the compliance percentage for Performance Measure 1.25.

This page provides data for the Police Body Cameras performance measure.

The performance measure dashboard is available at 1.25 Police Body Cameras.

Additional Information

Source: Police calls for service, officer activity, axon metadata.
Contact: Wil Price
Contact E-Mail: wil_price@tempe.gov
Data Source Type: Excel
Preparation Method: 1. Calls for service. Police calls for service are limited to the time period under consideration. Cancelled calls, test calls, and callback call types are removed. 2. Officer unit history. Raw unit history data may contain two officers per unit. Data is split and recombined so that each officer maintains an inpidual record. Unit history is limited to calls for service at which an officer has a documented arrival, and at which an officer spent at least one minute at the scene. When an officer has multiple arrivals to a single call, the first arrival and last clear time are selected to calculate the duration of the call, then superfluous arrivals are removed. Records in which Unit history is matched to the calls for service dataset by primary key (call number). 3. Axon meta data. Axon meta data is matched to unit history first on officer, then on month and week, in a full outer join. Data is next matched on the call number reported in the metadata, and then to call number based on video recorded date/time and officer unit history date/time. Records are selected where there is either a match on call number or on date/time.
Publish Frequency: Annually
Publish Method: Manual
Data Dictionary
Organization: City of Tempe
Last updated: 2024-02-09T15:01:39.748759
Tags: body-worn-camera, bwc, safe-and-secure-communities