Skip to main content
U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Skip to content
This is a Non-Federal dataset covered by different Terms of Use than See Terms

1.25 Police Body Cameras (summary)

Metadata Updated: February 9, 2024

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 InformationSource: Police calls for service, officer activity, axon metadata.Contact: Wil PriceContact E-Mail: wil_price@tempe.govData Source Type: ExcelPreparation 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: AnnuallyPublish Method: ManualData Dictionary

Access & Use Information

Public: This dataset is intended for public access and use. Non-Federal: This dataset is covered by different Terms of Use than See Terms License: Creative Commons Attribution

Downloads & Resources


Metadata Created Date September 2, 2022
Metadata Updated Date February 9, 2024

Metadata Source

Harvested from City of Tempe Data.json Harvest Source

Additional Metadata

Resource Type Dataset
Metadata Created Date September 2, 2022
Metadata Updated Date February 9, 2024
Publisher City of Tempe
Data First Published 2020-01-06T22:31:31.000Z
Data Last Modified 2023-10-11T19:56:45.684Z
Category geospatial
Public Access Level public
Metadata Context
Schema Version
Catalog Describedby
Harvest Object Id 8fdc030d-5d09-42ad-b159-8526ec3e23f0
Harvest Source Id ceea1675-8276-45f1-b45c-bb28dba71955
Harvest Source Title City of Tempe Data.json Harvest Source
Homepage URL
Metadata Type geospatial
Old Spatial {{extent:computeSpatialProperty}}
Source Datajson Identifier True
Source Hash 041d1054dc14b6bbf1643095f72fe66f46736546fd004d778c984435146ce605
Source Schema Version 1.1

Didn't find what you're looking for? Suggest a dataset here.

An official website of the GSA's Technology Transformation Services

Looking for U.S. government information and services?