Please review this brief video for a better understanding of how these data are created: https://www.youtube.com/watch?v=lvTCjVHxpAU

This data represents police response activity. Each row is a record of a Call for Service (CfS) logged with the Seattle Police Department (SPD) Communications Center. Calls originated from the community and range from in progress or active emergencies to requests for problem solving. Additionally, officers will log calls from their observations of the field.

Previous versions of this data set have withheld approximately 40% of calls. This updated process will release more than 95% of all calls but we will no longer provide latitude and longitude specific location data. In an effort to safeguard the privacy of our community, calls will only be located to the “beat” level. Beats are the most granular unit of management used for patrol deployment. To learn more about patrol deployment, please visit: https://www.seattle.gov/police/about-us/about-policing/precinct-and-patrol-boundaries.

As with any data, certain conditions and qualifications apply:

1) These data are queried from the Data Analytics Platform (DAP), and updated incrementally on a daily basis. A full refresh will occur twice a year and is intended to reconcile minor changes.

2) This data set only contains records of police response. If a call is queued in the system but cleared before an officer can respond, it will not be included.

3) These data contain administrative call types. Use the “Initial” and “Final” call type to identify the calls you wish to include in your analysis.

We invite you to engage these data, ask questions and explore.

Note! Subject Data is temporarily unavailable, while we chase down a bug. Please excuse the inconvenience (DGAL-8).

This data represents records of police reported stops under Terry v. Ohio, 392 U.S. 1 (1968). Each row represents a unique stop.

- Each record contains perceived demographics of the subject, as reported by the officer making the stop and officer demographics as reported to the Seattle Police Department, for employment purposes.

- Where available, data elements from the associated Computer Aided Dispatch (CAD) event (e.g. Call Type, Initial Call Type, Final Call Type) are included.

Records of Officer Involved Shootings (OIS) from 2005 to the present, including a brief narrative synopsis. Beginning in Q3 2023, the summary will be replaced with a link to the FRB findings documented, prepared for public release. A link for each OIS will be embedded in the file. Data set does not contain records from active investigations. Data is visualized in a dashboard on the SPD public site (https://www.seattle.gov/police/information-and-data/use-of-force-data/officer-involved-shootings-dashboard), please reference as a guide for use. Dashboard is available for download.

Updates are posted twice a year (January and July), as cases complete the inquest process (https://kingcounty.gov/services/inquest-program.aspx).

Use of force data also available here: https://data.seattle.gov/Public-Safety/Use-Of-Force/ppi5-g2bj and is updated daily. Data includes Type III - OIS.

A list of all public data requests made to the Seattle Police Department 2016 to December 2020. Requester names have been anonymized. Request summaries have been redacted to remove personally identifiable information (e.g. names, addresses, phone numbers, etc.) entered by the requester.

Data representing crisis contacts made by officers of the Seattle Police Department. Data is denormalized to represent the one to many relationship between the record and the reported disposition of the contact.

**USE CAUTION WHEN COUNTING**

Under the current business process, every seizure (4th Amendment of the US Constitution) conducted under the evidentiary standard of Probable Cause (PC) is documented in the RMS (Mark43). In addition to physical arrests made by officers, the system is configured to capture warrants, and summons arrests (where the officer is affecting a PC seizure on the authority of someone else (the court) and administrative arrest types that document updates to the identity of the subject who was arrested and additional charges. In total, 12 types of arrest are captured in the source.

Note: This data set includes counts of arrest reports written which are distinct from physical, in-custody events. All counts herein reflect either total counts of arrest reports by the selected filter parameters, and/or the total number of reports written per subject.

This table shows all disciplinary appeals by Seattle Police officers since 2016. The Seattle City Attorney's Office Employment Section handles all employee appeals of discipline and shares status updates with OPA.

Multiple rows with the same OPA case number indicate more than one officer appealed discipline under that case.

This dataset represents complaints against employees of the Seattle Police Department (SPD). The data is pulled from dynamic, live databases and is subject to change. Each row represents an individual allegation of misconduct from a Complainant against an individual SPD employee. A single OPA case may contain one or more Complainant(s), Named Employee(s), and Allegation(s) against each Named Employee. Data is denormalized to represent the one-to-many relationship between the Complaint and all the associated allegations. **USE CAUTION WHEN COUNTING**

The Seattle Police Department has different iterations of police beats as the city's needs evolved.  This layer represents what the beats looked like from 2017 to present.  

The Seattle Police Department has different iterations of police beats as the city's needs evolved.  This layer represents what the beats looked like from 2008 to 2015.  

The Seattle Police Department has different iterations of police beats as the city's needs evolved.  This layer represents what the beats looked like from 2015 to 2017.  

The Seattle Police Department has different iterations of police beats as the city's needs evolved.  This layer represents what the beats looked like prior to 2008.