1.25 Police Body Cameras (summary)

<p>Contains annual data, including number of calls uploaded and number of calls with a matching video. This data is the basis for the compliance percentage for Performance Measure 1.25.</p><p><strong>Preparation Method Change</strong></p><p>Before 2024, the data team manually combined police call records, officer activity logs, and Axon video information to show when officers used their body-worn cameras for City of Tempe’s priority emergency calls (priority 1 and 2). Starting as a transition process in 2024, Axon now automatically creates this report by connecting the City of Tempe’s priority emergency calls (priority 1 and 2) with any matching body-camera videos that officers upload. This automated process improves consistency and reduces manual handling of data.</p><p><strong>Prior to 2024:</strong></p><ol><li><strong>Calls for Service (CFS):</strong> Police Calls for Service were limited to the selected time period. Cancelled calls, test calls, and callback call types were removed. City of Tempe’s priority emergency calls (priority 1 and 2) were identified.</li><li><strong>Officer Unit History: </strong>Raw unit history data may contain two officers per unit. Data were split and recombined so each officer maintained an individual record. Unit history was limited to calls for service where an officer had a documented arrival and spent at least one minute on scene. When multiple arrivals occurred for a single call, the first arrival and last clear time were selected to calculate duration and superfluous arrivals were removed. Unit history was matched to the CFS dataset by primary key (call number).</li><li><strong>Axon Metadata:</strong> Axon metadata were matched to unit history first by officer, then by month and week, using a full outer join. Additional matching was performed 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 were selected where there was either a match on call number or on date/time.</li></ol><p><br /><strong>Transition Starting in 2024:</strong></p><p>Data preparation transitioned to an automated Axon-generated report linking Tempe Police Department Calls for Service (CFS) data to Body-Worn Camera (BWC) videos uploaded to the Axon system. The automated report references priority 1 and 2 CFS and identifies corresponding BWC videos uploaded for those calls to generate the activation rate. <strong>The annual compliance percentage using the new process will be available after 2025, once all 2025 data are complete.</strong><br /><br />The performance measure dashboard is available at&nbsp;<a target='_blank' href='https://safe-and-secure-communities-tempegov.hub.arcgis.com/pages/police-body-cameras' rel='nofollow ugc noopener noreferrer'>1.25 Police Body Cameras</a>.</p><p><a target='_blank' href='https://tempe.gitbook.io/data-dictionary/1.25-police-body-cameras' rel='nofollow ugc noopener noreferrer'><span style='font-size:18px;'><strong>Data Dictionary</strong></span></a></p><p><span style='font-size:18px;'><strong>Additional Information</strong></span></p><p><strong>Source: </strong>Police calls for service, officer activity, Axon metadata.<br /><br /><strong>Contact: </strong>Jeanne Pennington<br /><br /><strong>Contact E-Mail:</strong> <a href='mailto:jeanne_pennington@tempe.gov' rel='nofollow ugc'>jeanne_pennington@tempe.gov</a><br /><br /><strong>Data Source Type:</strong> Web-based automated system<br /><br /><strong>Preparation Method: </strong>An automated report generated by Axon linking Tempe Police Department Calls For Service (CFS) data to Body Worn Camera (BWC) video uploaded to the Axon system. Axon referenced priority 1 and 2 CFS and videos for those CFS that have been uploaded to generate the activation rate.<br /><br /><strong>Publish Frequency:</strong> Annually<br /><br /><strong>Publish Method:</strong> Manual<br />&nbsp;</p>

Tags: body-worn-camera, bwc, safe-and-secure-communities
Organization: City of Tempe