Violent Part 1 crime statistics by 1990 census tract.

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.

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.

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.

The King County Sheriff’s Office (KCSO) is providing offense report data captured in it's Records Management System (RMS) from 2020 to present. KCSO replaced its RMS in late 2018 and at the same time transitioned to the FBI’s National Incident-Based Reporting System (NIBRS). The NIBRS standardization of crime classifications allows for comparison over time and between agencies. For official KCSO NIBRS reporting, please visit the WASPC Crime in Washington Report: https://www.waspc.org/cjis-statistics---reports. Disclaimer: Only finalized (supervisor approved) reports are released. Those in draft, awaiting supervisor approval, or completed after the daily update of data, will not appear until the subsequent day(s). Data updates once every twenty-four hours. Records and classification changes will occur as a report makes its way through the approval and investigative process, thus reports might appear in the data set one day, but be removed the next day if there is a change in the approval status. This mirrors the fluidity of an investigation. Once a report is re-approved, it will show back up in the data set. Other than approval status, the report case status is factored into what can be released in the daily data set. As soon as a report case status matches the criteria for release, it will be included in the data set. For a list of offenses that are included in the data set, please see the attached pdf. Resources: - KCSO's 2019 crime data: https://data.kingcounty.gov/Law-Enforcement-Safety/King-County-Sheriff-s-Office-Incident-Dataset/rzfs-wyvy - Police District GIS shapefile: https://gis-kingcounty.opendata.arcgis.com/datasets/king-county-sheriff-patrol-districts-patrol-districts-area/explore - Police District key: https://data.kingcounty.gov/Law-Enforcement-Safety/KCSO-Patrol-Districts/ptrt-hdax/data - For more information on definitions and classifications, please visit https://www.fbi.gov/services/cjis/ucr/nibrs - SPD's Crime Data: https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5

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.

2017 Bias Incident Reports By Protected Class The Seattle Office for Civil Rights (SOCR) receives calls on the Bias Incident Reporting Line. Calls are received by front desk staff and logged. This dataset shows the amount of calls received each quarter of 2017 by protected class. A protected class is a characteristic of a person that is protected by the laws SOCR enforces such as race, gender identity, or disability. An “uncategorized” protected class means the caller did not provide a protected class. If you have questions about this data or want to learn more about the laws SOCR enforces, call 206-684-4500 or visit http://www.seattle.gov/civilrights. Visit Seattle Police Department’s Bias/Hate Crime Data site for information about bias/hate crimes: https://www.seattle.gov/police/information-and-data/bias-crime-unit/bias-crime-dashboard.

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.

Analysis of ‘Micro Community Policing Plans’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/9f4fb539-0715-44fe-a26e-7848e39f2de0 on 27 January 2022.

--- Dataset description provided by original source is as follows ---

--- Original source retains full ownership of the source dataset ---

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.