U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
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.
Violent Part 1 crime statistics by 1990 census tract.
These offenses correspond to the Police Report Incidents http://data.seattle.gov/dataset/Seattle-Police-Department-Police-Report-Incident/7ais-f98f
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.
In 2023, the District of Columbia had the highest reported violent crime rate in the United States, with 1,150.9 violent crimes per 100,000 of the population. Maine had the lowest reported violent crime rate, with 102.5 offenses per 100,000 of the population. Life in the District The District of Columbia has seen a fluctuating population over the past few decades. Its population decreased throughout the 1990s, when its crime rate was at its peak, but has been steadily recovering since then. While unemployment in the District has also been falling, it still has had a high poverty rate in recent years. The gentrification of certain areas within Washington, D.C. over the past few years has made the contrast between rich and poor even greater and is also pushing crime out into the Maryland and Virginia suburbs around the District. Law enforcement in the U.S. Crime in the U.S. is trending downwards compared to years past, despite Americans feeling that crime is a problem in their country. In addition, the number of full-time law enforcement officers in the U.S. has increased recently, who, in keeping with the lower rate of crime, have also made fewer arrests than in years past.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
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.