This file contains approximately 481,000 crime reports from Seattle, WA covering a span of approximately 10 years. For each crime offense this file includes date and time information, crime categories and description, police department information including sector, beat, and precinct, and neighborhood name.

This data represents crime reported to the Seattle Police Department (SPD). Each row contains the record of a unique event where at least one criminal offense was reported by a member of the community or detected by an officer in the field. This data is the same data used in meetings such as SeaStat (https://www.seattle.gov/police/information-and-data/seastat) for strategic planning, accountability and performance management.

These data contain offenses and offense categorization coded to simulate the standard reported to the FBI under the National Incident Based Reporting System (NIBRS) and used to generate Uniform Crime Report (UCR) summary statistics. As these records evolve, daily and are continually refreshed, they will not match official UCR statistics. They represent a more accurate state of the record.

Previous versions of this data set have withheld approximately 40% of crimes. This updated process includes all records of crime reports logged in the Departments Records Management System (RMS) since 2008, which are tracked as part of the SeaStat process. In an effort to safeguard the privacy of our community, offense reports will only be located to the “beat” level. Location specific coordinates will no longer be provided.

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. In addition to the Departments patrol deployment areas, these data contain the “Neighborhood” where the crime occurred, if available. This coding is used to align crime data with the Micro Community Policing Plan (MCPP). For more information see: https://www.seattle.gov/police/community-policing/about-mcpp.

As with any data, certain condition and qualifications apply: 1) These data are refreshed, daily and represent the most accurate, evolved state of the record.

2) Due to quality control processes, these data will lag between 2 and 6 weeks. Most changes will occur within that record and reports logged in the last 2 weeks should be treated as volatile. Analysts may wish to remove these records from their analysis.

3) Not all offenses are reported here, only the primary offense as determined by the “Hierarchy Rule.” For more information on NIBRS and UCR, see the FBI (https://ucr.fbi.gov/nibrs-overview).

4) This dataset contains records of offenses that occurred prior to “go-live” of the existing RMS. Records are queried based on the full population of data and are not constrained by “Occurred Date.”

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

All recorded police reports as taken from https://data.seattle.gov/Public-Safety/Seattle-Police-Department-Police-Report-Incident/7ais-f98f

The Seattle Police Department (SPD) replaced its Records Management System (RMS) in May 2019. To preserve data quality and continuity between systems (2008-Present), SPD relied on the National Incident-Based Reporting System (NIBRS). The standardization of crime classifications allows for comparison over time. For more information on definitions and classifications, please visit https://www.fbi.gov/services/cjis/ucr/nibrs.

Additional groupings are used to analyze crime in SPD’s Crime Dashboard. Violent and property crime categories align with best practices. For additional inquiries, we encourage the use of the underline data to align with the corresponding query.

Disclaimer: Only finalized (UCR approved) reports are released. Those in draft, awaiting approval, or completed after the update, will not appear until the subsequent day(s). Data is updated once every twenty-four hours. Records and classification changes will occur as a report makes its way through the approval and investigative process.

This dataset aggregates Seattle Police Department crime statistics with spatial ZIP code boundaries and US Census data to determine the property crime rate per 1,000 residents. The following sources were used to create this dataset:

King County ZIP Code Boundaries

Source: https://data-seattlecitygis.opendata.arcgis.com/datasets/SeattleCityGIS::zip-codes/explore

King County provides approximate ZIP code boundaries, updated quarterly and published by the city of Seattle.

SPD Crime Data: 2008-Present

Source: https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5

The Seattle Police Department publishes data for reported crimes from 2008 to the present, refreshed daily. This data includes whether the crime is classified as against a person, against property, or against society.

2020 ACS 5-year estimates for population

Source: https://data.census.gov/cedsci/table?q=population%20seattle&g=0400000US53%248600000&tid=ACSDP5Y2020.DP05

The US Census Department American Community Survey (ACS) publishes 5-year estimates of population by a variety of geographies, including ZIP Code Tabulation Areas (ZCTAs), geographic approximations of each ZIP code.

Data Processing

Using the pandas and geopandas libraries within python, the following processing steps were followed to prepare this dataset: - Converted the date and time reported field in the SPD dataset to a datetime object and extracted the year - Filtered to crimes reported between 2008 and 2021 - Filtered to only crimes against property - Dropped rows with null values for year, crime against category, longitude, or latitude - Performed a spatial join using the latitude and longitude for each report in the SPD data to append a ZIP code from the King County ZIP Code boundary shapefile - Summarized to calculate a count of property crimes reported for each combination of year and ZIP code - Summarized by ZIP code to calculate the count of years with at least one crime reported and the total number of property crimes reported - Calculated the average number of property crimes reported per year in each ZIP code - Merged with the ACS population estimates - Calculated the number of property crimes reported per year per 1,000 population for each zip code

Photo by Justus Hayes: https://www.pexels.com/photo/a-bicycle-chained-to-a-metal-post-6355944/

Violent Part 1 crime statistics by 1990 census tract.

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Seattle Police Department (City) in Washington, including incidents, statistics, demographics, and detailed incident information.

These incidents are based on initial police reports taken by officers when responding to incidents around the city. The information enters our Records Management System (RMS) and is then transmitted out to data.seattle.gov. This information is published within 6 to 12 hours after the report is filed into the system.

These offenses correspond to the Police Report Incidents http://data.seattle.gov/dataset/Seattle-Police-Department-Police-Report-Incident/7ais-f98f

Seattle Police Department In-Car Video Dropped Frame Report

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 dataset is all the Police responses to 9-1-1 calls within the city. Police response data shows all officers dispatched. To protect the security of a scene, the safety of officers and the public, and sensitive ongoing investigation, these events are added to the data.seattle.gov only after the incident is considered safe to close out. Data is refreshed on a 4 hour interval.

These incidents are based on initial police reports taken by officers when responding to incidents around the city. The information enters our Records Management System (RMS) and is then transmitted out to data.seattle.gov. This information is published within 6 to 12 hours after the report is filed into the system.

Seattle Part 1 Crime stats by precinct The precinct and beat data can be found at http://data.seattle.gov/Government/Seattle-Police-Department-Beats/nnxn-434b

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.

These offenses correspond to the Police Report Incidents http://data.seattle.gov/dataset/Seattle-Police-Department-Police-Report-Incident/7ais-f98f

Content

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.

Context

This is a dataset hosted by the City of Seattle. The city has an open data platform found here and they update their information according the amount of data that is brought in. Explore New York City using Kaggle and all of the data sources available through the City of Seattle organization page!

• Update Frequency: This dataset is updated daily.

Acknowledgements

This dataset is maintained using Socrata's API and Kaggle's API. Socrata has assisted countless organizations with hosting their open data and has been an integral part of the process of bringing more data to the public.

Cover photo by Marina Vitale on Unsplash
Unsplash Images are distributed under a unique Unsplash License.

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Port of Seattle (Other) in Washington, including incidents, statistics, demographics, and detailed incident information.

This dataset records police responses to 911 calls in the city of Seattle.

Acknowledgements

This dataset was kindly made available by the City of Seattle. They update the data daily; you can find the original version here.

Inspiration

• The study discussed in this Atlantic article reviewing 911 calls in Milwaukuee found that that incidents of police violence lead to large drops in the number of 911 calls. Does this hold true for Seattle as well? This dataset technically only contains the responses to 911 calls rather than the calls themselves, but it should be feasible to use the responses as a decent proxy for calls.

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Seattle-Tacoma-Bellevue, WA Metropolitan Statistical Area (MSA), including incidents, statistics, demographics, and agency information across multiple jurisdictions.