The police shootings data is from the database maintained by Washington Post at https://github.com/washingtonpost/data-police-shootings (version 2) that covers the period 2015-2023.The curated datasets are included here along with a research question and guiding questions.See the codebook for full details.

Analysis of ‘Police Killings US’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/azizozmen/police-killings-us on 13 February 2022.

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

"In 2015, The Washington Post began to log every fatal shooting by an on-duty police officer in the United States. In that time there have been more than 5,000 such shootings recorded by The Post. After Michael Brown, an unarmed Black man, was killed in 2014 by police in Ferguson, Mo., a Post investigation found that the FBI undercounted fatal police shootings by more than half. This is because reporting by police departments is voluntary and many departments fail to do so. The Washington Post’s data relies primarily on news accounts, social media postings, and police reports. Analysis of more than five years of data reveals that the number and circumstances of fatal shootings and the overall demographics of the victims have remained relatively constant..." SOURCE ==> Washington Post Article

For more information about this story

This dataset has been prepared by The Washington Post (they keep updating it on runtime) with every fatal shooting in the United States by a police officer in the line of duty since Jan. 1, 2015.

2016 PoliceKillingUS DATASET
2017 PoliceKillingUS DATASET
2018 PoliceKillingUS DATASET
2019 PoliceKillingUS DATASET
2020 PoliceKillingUS DATASET

Features at the Dataset:

The file fatal-police-shootings-data.csv contains data about each fatal shooting in CSV format. The file can be downloaded at this URL. Each row has the following variables:

• id: a unique identifier for each victim
• name: the name of the victim
• date: the date of the fatal shooting in YYYY-MM-DD format
• manner_of_death: shot, shot and Tasered
• armed: indicates that the victim was armed with some sort of implement that a police officer believed could inflict harm
  • undetermined: it is not known whether or not the victim had a weapon
  • unknown: the victim was armed, but it is not known what the object was
  • unarmed: the victim was not armed
• age: the age of the victim
• gender: the gender of the victim. The Post identifies victims by the gender they identify with if reports indicate that it differs from their biological sex.
  • M: Male
  • F: Female
  • None: unknown
• race:
  • W: White, non-Hispanic
  • B: Black, non-Hispanic
  • A: Asian
  • N: Native American
  • H: Hispanic
  • O: Other
  • None: unknown
• city: the municipality where the fatal shooting took place. Note that in some cases this field may contain a county name if a more specific municipality is unavailable or unknown.
• state: two-letter postal code abbreviation
• signs of mental illness: News reports have indicated the victim had a history of mental health issues, expressed suicidal intentions or was experiencing mental distress at the time of the shooting.
• threat_level: The threat_level column was used to flag incidents for the story by Amy Brittain in October 2015. http://www.washingtonpost.com/sf/investigative/2015/10/24/on-duty-under-fire/ As described in the story, the general criteria for the attack label was that there was the most direct and immediate threat to life. That would include incidents where officers or others were shot at, threatened with a gun, attacked with other weapons or physical force, etc. The attack category is meant to flag the highest level of threat. The other and undetermined categories represent all remaining cases. Other includes many incidents where officers or others faced significant threats.
• flee: News reports have indicated the victim was moving away from officers
  • Foot
  • Car
  • Not fleeing

The threat column and the fleeing column are not necessarily related. For example, there is an incident in which the suspect is fleeing and at the same time turns to fire at gun at the officer. Also, attacks represent a status immediately before fatal shots by police while fleeing could begin slightly earlier and involve a chase. - body_camera: News reports have indicated an officer was wearing a body camera and it may have recorded some portion of the incident.

SOURCE

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

Analysis of ‘🚓 Fatal Police Shootings’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/yamqwe/fatal-police-shootingse on 13 February 2022.

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

About this dataset

The Washington Post has tracked fatal police shootings in the US since 2015, using news and police reports as well as social media and databases like Killed by Police and Fatal Encounters.

The collected data include the race, gender, and age of the deceased, the circumstances of the shooting, and whether the person was armed or experiencing a mental-health crisis.

The Washington Post updates visualizations of the data and provides more information about methodology on the Fatal Force page.

Source: https://github.com/washingtonpost/data-police-shootings
Updated: synced daily
License: CC BY-NC-SA

This dataset was created by Data Society and contains around 7000 samples along with Is Geocoding Exact, Armed, technical information and other features such as: - Body Camera - State - and more.

How to use this dataset

• Analyze Latitude in relation to Manner Of Death
• Study the influence of Name on Age
• More datasets

Acknowledgements

If you use this dataset in your research, please credit Data Society

Start A New Notebook!

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

The Washington Post spent a year determining how many children have been affected by school shootings, beyond just those killed or injured. To do that, reporters attempted to identify every act of gunfire at a primary or secondary school during school hours since the Columbine High massacre on April 20, 1999. Using Nexis, news articles, open-source databases, law enforcement reports, information from school websites, and calls to schools and police departments, The Post reviewed more than 1,000 alleged incidents, but counted only those that happened on campuses immediately before, during or just after classes. Shootings at after-hours events, accidental discharges that caused no injuries to anyone other than the person handling the gun, and suicides that occurred privately or posed no threat to other children were excluded. Gunfire at colleges and universities, which affects young adults rather than kids, also was not counted. After finding more than 200 incidents of gun violence that met The Post’s criteria, reporters organized them in a database for analysis. Because the federal government does not track school shootings, it’s possible that the database does not contain every incident that would qualify. To calculate how many children were exposed to gunfire in each school shooting, The Post relied on enrollment figures and demographic information from the U.S. Education Department, including the Common Core of Data and the Private School Universe Survey. The analysis used attendance figures from the year of the shooting for the vast majority of the schools. Credits: Research and Reporting: John Woodrow Cox, Steven Rich and Allyson Chiu Production and Presentation: John Muyskens and Monica Ulmanu Per the terms of the Creative Commons license, CISER notes that: 1. the license for this dataset is attached as the files license.htm and license.pdf. A brief version of the Creative Commons license is also included but users should familiarize themselves with the full license before using. 2. the licensed material is located at https://github.com/washingtonpost/data-school-shootings 3. Several of the files have been modified from the format presented at the above url including creating pdf versions of the documentation files and adding SAS, Stata, and SPSS versions through the use of StatTransfer 13. 4. These adapted versions of the original files are also released through the same Creative Commons license as the original with the same license elements.