62 datasets found
  1. People shot to death by U.S. police 2017-2024, by race

    • statista.com
    Updated May 27, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Statista (2025). People shot to death by U.S. police 2017-2024, by race [Dataset]. https://www.statista.com/statistics/585152/people-shot-to-death-by-us-police-by-race/
    Explore at:
    Dataset updated
    May 27, 2025
    Dataset authored and provided by
    Statistahttp://statista.com/
    Area covered
    United States
    Description

    Sadly, the trend of fatal police shootings in the United States seems to only be increasing, with a total 1,173 civilians having been shot, 248 of whom were Black, as of December 2024. In 2023, there were 1,164 fatal police shootings. Additionally, the rate of fatal police shootings among Black Americans was much higher than that for any other ethnicity, standing at 6.1 fatal shootings per million of the population per year between 2015 and 2024. Police brutality in the U.S. In recent years, particularly since the fatal shooting of Michael Brown in Ferguson, Missouri in 2014, police brutality has become a hot button issue in the United States. The number of homicides committed by police in the United States is often compared to those in countries such as England, where the number is significantly lower. Black Lives Matter The Black Lives Matter Movement, formed in 2013, has been a vocal part of the movement against police brutality in the U.S. by organizing “die-ins”, marches, and demonstrations in response to the killings of black men and women by police. While Black Lives Matter has become a controversial movement within the U.S., it has brought more attention to the number and frequency of police shootings of civilians.

  2. A

    ‘Police Killings US’ analyzed by Analyst-2

    • analyst-2.ai
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com), ‘Police Killings US’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/kaggle-police-killings-us-57e7/latest
    Explore at:
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    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 ---

  3. d

    NYPD Shooting Incident Data (Year To Date)

    • catalog.data.gov
    • data.cityofnewyork.us
    • +2more
    Updated Apr 19, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    data.cityofnewyork.us (2025). NYPD Shooting Incident Data (Year To Date) [Dataset]. https://catalog.data.gov/dataset/nypd-shooting-incident-data-year-to-date
    Explore at:
    Dataset updated
    Apr 19, 2025
    Dataset provided by
    data.cityofnewyork.us
    Description

    List of every shooting incident that occurred in NYC during the current calendar year. This is a breakdown of every shooting incident that occurred in NYC during the current calendar year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning before being posted on the NYPD website. Each record represents a shooting incident in NYC and includes information about the event, the location and time of occurrence. In addition, information related to suspect and victim demographics is also included. This data can be used by the public to explore the nature of police enforcement activity. Please refer to the attached data footnotes for additional information about this dataset.

  4. Fatal Police Shootings

    • figshare.com
    • kaggle.com
    pdf
    Updated Mar 5, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    RN Uma; Alade Tokuta; Rebecca Zulli Lowe; Adrienne Smith (2024). Fatal Police Shootings [Dataset]. http://doi.org/10.6084/m9.figshare.14552130.v4
    Explore at:
    pdfAvailable download formats
    Dataset updated
    Mar 5, 2024
    Dataset provided by
    figshare
    Figsharehttp://figshare.com/
    Authors
    RN Uma; Alade Tokuta; Rebecca Zulli Lowe; Adrienne Smith
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    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.

  5. Data from: Felonious Homicides of American Police Officers, 1977-1992

    • catalog.data.gov
    • s.cnmilf.com
    • +2more
    Updated Mar 12, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Institute of Justice (2025). Felonious Homicides of American Police Officers, 1977-1992 [Dataset]. https://catalog.data.gov/dataset/felonious-homicides-of-american-police-officers-1977-1992-25657
    Explore at:
    Dataset updated
    Mar 12, 2025
    Dataset provided by
    National Institute of Justicehttp://nij.ojp.gov/
    Description

    The study was a comprehensive analysis of felonious killings of officers. The purposes of the study were (1) to analyze the nature and circumstances of incidents of felonious police killings and (2) to analyze trends in the numbers and rates of killings across different types of agencies and to explain these differences. For Part 1, Incident-Level Data, an incident-level database was created to capture all incidents involving the death of a police officer from 1983 through 1992. Data on officers and incidents were collected from the Law Enforcement Officers Killed and Assaulted (LEOKA) data collection as coded by the Uniform Crime Reporting (UCR) program. In addition to the UCR data, the Police Foundation also coded information from the LEOKA narratives that are not part of the computerized LEOKA database from the FBI. For Part 2, Agency-Level Data, the researchers created an agency-level database to research systematic differences among rates at which law enforcement officers had been feloniously killed from 1977 through 1992. The investigators focused on the 56 largest law enforcement agencies because of the availability of data for explanatory variables. Variables in Part 1 include year of killing, involvement of other officers, if the officer was killed with his/her own weapon, circumstances of the killing, location of fatal wounds, distance between officer and offender, if the victim was wearing body armor, if different officers were killed in the same incident, if the officer was in uniform, actions of the killer and of the officer at entry and final stage, if the killer was visible at first, if the officer thought the killer was a felon suspect, if the officer was shot at entry, and circumstances at anticipation, entry, and final stages. Demographic variables for Part 1 include victim's sex, age, race, type of assignment, rank, years of experience, agency, population group, and if the officer was working a security job. Part 2 contains variables describing the general municipal environment, such as whether the agency is located in the South, level of poverty according to a poverty index, population density, percent of population that was Hispanic or Black, and population aged 15-34 years old. Variables capturing the crime environment include the violent crime rate, property crime rate, and a gun-related crime index. Lastly, variables on the environment of the police agencies include violent and property crime arrests per 1,000 sworn officers, percentage of officers injured in assaults, and number of sworn officers.

  6. Fatal Police Shootings in the US (2015-2020)

    • kaggle.com
    Updated Jun 1, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Larxel (2020). Fatal Police Shootings in the US (2015-2020) [Dataset]. https://www.kaggle.com/datasets/andrewmvd/police-deadly-force-usage-us/code
    Explore at:
    CroissantCroissant is a format for machine-learning datasets. Learn more about this at mlcommons.org/croissant.
    Dataset updated
    Jun 1, 2020
    Dataset provided by
    Kagglehttp://kaggle.com/
    Authors
    Larxel
    License

    Attribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0)https://creativecommons.org/licenses/by-nc-sa/4.0/
    License information was derived automatically

    Area covered
    United States
    Description

    About this dataset

    The Washington Post compiled a dataset of every fatal shooting in the United States by a police officer in the line of duty since Jan. 1, 2015.

    In 2015, The Post began tracking more than a dozen details about each killing by culling local news reports, law enforcement websites and social media and by monitoring independent databases such as Killed by Police and Fatal Encounters. The available features are: - Race of the deceased; - Circumstances of the shooting; - Whether the person was armed; - Whether the victim was experiencing a mental-health crisis; - Among others.

    In 2016, The Post is gathering additional information about each fatal shooting that occurs this year and is filing open-records requests with departments. More than a dozen additional details are being collected about officers in each shooting.

    The Post is documenting only those shootings in which a police officer, in the line of duty, shot and killed a civilian — the circumstances that most closely parallel the 2014 killing of Michael Brown in Ferguson, Mo., which began the protest movement culminating in Black Lives Matter and an increased focus on police accountability nationwide. The Post is not tracking deaths of people in police custody, fatal shootings by off-duty officers or non-shooting deaths.

    The FBI and the Centers for Disease Control and Prevention log fatal shootings by police, but officials acknowledge that their data is incomplete. In 2015, The Post documented more than two times more fatal shootings by police than had been recorded by the FBI. Last year, the FBI announced plans to overhaul how it tracks fatal police encounters.

    How to use this dataset

    Acknowledgements

    If you use this dataset in your research, please credit the authors.

    BibTeX

    @misc{wapo-police-shootings-bot , author = {The Washington Post}, title = {data-police-shootings}, month = jan, year = 2015, publisher = {Github}, url = {https://github.com/washingtonpost/data-police-shootings} }

    License

    CC BY NC SA 4.0

    Splash banner

    Image by pixabay avaiable on pexels.

  7. A

    ‘🚓 Fatal Police Shootings’ analyzed by Analyst-2

    • analyst-2.ai
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com), ‘🚓 Fatal Police Shootings’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/kaggle-fatal-police-shootings-fdc5/8b11e8dc/?iid=015-737&v=presentation
    Explore at:
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    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 ---

  8. Shootings

    • data.boston.gov
    csv
    Updated Jul 12, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Boston Police Department (2025). Shootings [Dataset]. https://data.boston.gov/dataset/shootings
    Explore at:
    csv(376), csv(2)Available download formats
    Dataset updated
    Jul 12, 2025
    Dataset authored and provided by
    Boston Police Departmenthttps://bpdnews.com/
    Description

    The Shootings dashboard contains information on shooting incidents where a victim was struck by a bullet, either fatally or non-fatally; that occurred in the City of Boston and fall under Boston Police Department jurisdiction. The dashboard does not contain records for self-inflicted gunshot wounds or shootings determined to be justifiable. Information on the incident, and the demographics of victims are included. This information is updated based on analysis conducted by the Boston Regional Intelligence Center under the Boston Police Department Bureau of Intelligence and Analysis. The data is for 2015 forward, with a 7 day rolling delay to allow for analysis and data entry to occur.

  9. f

    Fatal Police Violence

    • figshare.com
    pdf
    Updated Mar 5, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    RN Uma; Alade Tokuta; Rebecca Zulli Lowe; Adrienne Smith (2024). Fatal Police Violence [Dataset]. http://doi.org/10.6084/m9.figshare.12946988.v5
    Explore at:
    pdfAvailable download formats
    Dataset updated
    Mar 5, 2024
    Dataset provided by
    figshare
    Authors
    RN Uma; Alade Tokuta; Rebecca Zulli Lowe; Adrienne Smith
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Police killings dataset (not just shooting, but by any means) is from https://mappingpoliceviolence.org/ that covers the period 2013-2023. This includes the Washington Post (WaPo) dataset on shooting victims.The curated datasets are included here along with a research question and guiding questions.See the codebook for full details.

  10. T

    PDI (Police Data Initiative) Officer Involved Shootings

    • data.cincinnati-oh.gov
    application/rdfxml +5
    Updated Jul 13, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Cincinnati (2025). PDI (Police Data Initiative) Officer Involved Shootings [Dataset]. https://data.cincinnati-oh.gov/Safety/PDI-Police-Data-Initiative-Officer-Involved-Shooti/r6q4-muts
    Explore at:
    json, xml, application/rdfxml, csv, tsv, application/rssxmlAvailable download formats
    Dataset updated
    Jul 13, 2025
    Dataset authored and provided by
    City of Cincinnati
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Description

    This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.

    Data Description: This data represents officer involved shooting incidents by the Cincinnati Police Department. An officer involved shooting (OIS) may be defined as the discharge of a firearm, which may include accidental and intentional discharges, by a police officer, whether on or off duty.

    Data Creation: This data is created through reporting by the Cincinnati Police Department.

    Data Created By: The source of this data is the Cincinnati Police Department.

    Refresh Frequency: This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.

    CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/c64e-ybfz/

    Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

    Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

    Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

    Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

  11. A

    ‘US Police Shootings’ analyzed by Analyst-2

    • analyst-2.ai
    Updated Jan 28, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com) (2022). ‘US Police Shootings’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/kaggle-us-police-shootings-bef9/06301fe4/?iid=009-815&v=presentation
    Explore at:
    Dataset updated
    Jan 28, 2022
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    United States
    Description

    Analysis of ‘US Police Shootings’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/ahsen1330/us-police-shootings on 28 January 2022.

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

    Context

    In the recent killings, a hot topic came into being, "Racism". So, I chose to gather some data to take out some insights and analyze the story around racism in America. I downloaded the raw data from kaggle and prepared it for visualization while correcting values, handling missing content, normalization and categorization

    Content

    It contains basic data about people like their name, age, gender and race. Along with it, is the shooting/killing information, like date of event, where it happened? how they were shot? did they attack? Were they holding weapons? Did they show any mental illness? Was the policeman wearing a camera/was the incident recorded? Did the suspect flee? Apart from that, a category column holds type of weapon used by the suspect

    Acknowledgements

    Kagglers

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

  12. C

    7th dist Shootings Jan 1st to Date

    • data.cityofchicago.org
    Updated Jul 13, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Chicago Police Department (2025). 7th dist Shootings Jan 1st to Date [Dataset]. https://data.cityofchicago.org/Public-Safety/7th-dist-Shootings-Jan-1st-to-Date/xczp-pcja
    Explore at:
    csv, application/rssxml, application/rdfxml, xml, tsv, application/geo+json, kmz, kmlAvailable download formats
    Dataset updated
    Jul 13, 2025
    Authors
    Chicago Police Department
    Description

    This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at PSITAdministration@ChicagoPolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data are updated daily. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

  13. C

    Violence Reduction - Victims of Homicides and Non-Fatal Shootings

    • data.cityofchicago.org
    • catalog.data.gov
    Updated Jul 13, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Chicago (2025). Violence Reduction - Victims of Homicides and Non-Fatal Shootings [Dataset]. https://data.cityofchicago.org/Public-Safety/Violence-Reduction-Victims-of-Homicides-and-Non-Fa/gumc-mgzr
    Explore at:
    csv, tsv, application/rdfxml, application/rssxml, xml, kml, application/geo+json, kmzAvailable download formats
    Dataset updated
    Jul 13, 2025
    Dataset authored and provided by
    City of Chicago
    Description

    This dataset contains individual-level homicide and non-fatal shooting victimizations, including homicide data from 1991 to the present, and non-fatal shooting data from 2010 to the present (2010 is the earliest available year for shooting data). This dataset includes a "GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized-access dataset, but with "UNKNOWN" in the shooting column.

    Each row represents a single victimization, i.e., a unique event when an individual became the victim of a homicide or non-fatal shooting. Each row does not represent a unique victim—if someone is victimized multiple times there will be multiple rows for each of those distinct events.

    The dataset is refreshed daily, but excludes the most recent complete day to allow the Chicago Police Department (CPD) time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.

    A version of this dataset with additional crime types is available by request. To make a request, please email dataportal@cityofchicago.org with the subject line: Violence Reduction Victims Access Request. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup.

    How does this dataset classify victims?

    The methodology by which this dataset classifies victims of violent crime differs by victimization type:

    Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.

    To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset. For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Victims dataset do not align with the homicide/non-fatal shooting categorization:

    1. In instances where a homicide victimization does not correspond to an IUCR code 0110 or 0130, we set the IUCR code to "01XX" to indicate that the victimization was a homicide but we do not know whether it was a first-degree murder (IUCR code = 0110) or a second-degree murder (IUCR code = 0130).
    2. When a non-fatal shooting victimization does not correspond to an IUCR code that signifies a criminal sexual assault, robbery, or aggravated battery, we enter “UNK” in the IUCR column, “YES” in the GUNSHOT_I column, and “NON-FATAL” in the PRIMARY column to indicate that the victim was non-fatally shot, but the precise IUCR code is unknown.

    Other violent crime victims: For other violent crime types, we refer to the IUCR classification that exists in CPD's victim table, with only one exception:

    1. When there is an incident that is associated with no victim with a matching IUCR code, we assume that this is an error. Every crime should have at least 1 victim with a matching IUCR code. In these cases, we change the IUCR code to reflect the incident IUCR code because CPD's incident table is considered to be more reliable than the victim table.

    Note: The definition of “homicide” (shooting or otherwise) does not include justifiable homicide or involuntary manslaughter. This dataset also excludes any cases that CPD considers to be “unfounded” or “noncriminal.” Officer-involved shootings are not included.

    Note: The initial reporting officer usually asks victims to report demographic data. If victims are unable to recall, the reporting officer will use their best judgment. “Unknown” can be reported if it is truly unknown.

    Note: In some instances, CPD's raw incident-level data and victim-level data that were inputs into this dataset do not align on the type of crime that occurred. In those instances, this dataset attempts to correct mismatches between incident and victim specific crime types. When it is not possible to determine which victims are associated with the most reliable crime determination, the dataset will show empty cells in the respective demographic fields (age, sex, race, etc.).

    Note: Homicide victims names are delayed by two weeks to allow time for the victim’s family to be notified of their passing.

    Note: The initial reporting officer usually asks victims to report demographic data. If victims are unable to recall, the reporting officer will use their best judgment. “Unknown” can be reported if it is truly unknown.

    Note: This dataset includes variables referencing administrative or political boundaries that are subject to change. These include Street Outreach Organization boundary, Ward, Chicago Police Department District, Chicago Police Department Area, Chicago Police Department Beat, Illinois State Senate District, and Illinois State House of Representatives District. These variables reflect current geographic boundaries as of November 1st, 2021. In some instances, current boundaries may conflict with those that were in place at the time that a given incident occurred in prior years. For example, the Chicago Police Department districts 021 and 013 no longer exist. Any historical violent crime victimization that occurred in those districts when they were in existence are marked in this dataset as having occurred in the current districts that expanded to replace 013 and 021."

  14. A

    ‘Data Police shootings’ analyzed by Analyst-2

    • analyst-2.ai
    Updated Jan 28, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com) (2022). ‘Data Police shootings’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/kaggle-data-police-shootings-4d9b/latest
    Explore at:
    Dataset updated
    Jan 28, 2022
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Analysis of ‘Data Police shootings’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://www.kaggle.com/mrmorj/data-police-shootings on 28 January 2022.

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

    The FBI and the Centers for Disease Control and Prevention log fatal shootings by police, but officials acknowledge that their data is incomplete. In 2015, The Post documented more than two times more fatal shootings by police than had been recorded by the FBI. Last year, the FBI announced plans to overhaul how it tracks fatal police encounters.

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

  15. Fatal Police Shootings (2013-2016) & County Level Data

    • figshare.com
    txt
    Updated May 30, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    John Hamilton Bradford (2023). Fatal Police Shootings (2013-2016) & County Level Data [Dataset]. http://doi.org/10.6084/m9.figshare.5099536.v8
    Explore at:
    txtAvailable download formats
    Dataset updated
    May 30, 2023
    Dataset provided by
    Figsharehttp://figshare.com/
    Authors
    John Hamilton Bradford
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    This is a set of csv files including a number of variables including fatal police shootings and other crime and socioeconomic covariates at different levels of geographical aggregation from 2013-2016. Five of the files use only the Washington Post data covering years 2015 and 2016, whereas the other five files utilize fatal police shootings of civilians for years 2013-2016, combining the Lott & Moody (2016) data for years 2013-2015 and Washington Post data for 2016. Other variables are included from the American Community Survey (ACS), the FBI's Uniform Crime Reports (UCR), the Law Enforcement Management and Administrative Statistics (LEMAS), Stanford Education Data Archive (SEDA), the US Census, and the Local Area Unemployment Statistics (LAUS) provided by the Bureau of Labor Statistics (BLS). The base file is the county-level data. The two files labelled "tenk" consist of regions with at least 10,000 residents. Counties with fewer than 10,000 residents are combined with adjacent counties, ranked by population in ascending order, so that counties with fewer than 10,000 residents are iteratively combined with adjacent neighbors with the fewest residents until they reach the threshold of 10,000 residents. The same algorithm is used to produce regions with 100,000 and 1 million residents. The final two files are state-level aggregations.

  16. C

    Violence Reduction - Victim Demographics - Aggregated

    • data.cityofchicago.org
    • s.cnmilf.com
    • +1more
    application/rdfxml +5
    Updated Jul 13, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Chicago (2025). Violence Reduction - Victim Demographics - Aggregated [Dataset]. https://data.cityofchicago.org/Public-Safety/Violence-Reduction-Victim-Demographics-Aggregated/gj7a-742p
    Explore at:
    application/rssxml, csv, json, application/rdfxml, xml, tsvAvailable download formats
    Dataset updated
    Jul 13, 2025
    Dataset authored and provided by
    City of Chicago
    Description

    This dataset contains aggregate data on violent index victimizations at the quarter level of each year (i.e., January – March, April – June, July – September, October – December), from 2001 to the present (1991 to present for Homicides), with a focus on those related to gun violence. Index crimes are 10 crime types selected by the FBI (codes 1-4) for special focus due to their seriousness and frequency. This dataset includes only those index crimes that involve bodily harm or the threat of bodily harm and are reported to the Chicago Police Department (CPD). Each row is aggregated up to victimization type, age group, sex, race, and whether the victimization was domestic-related. Aggregating at the quarter level provides large enough blocks of incidents to protect anonymity while allowing the end user to observe inter-year and intra-year variation. Any row where there were fewer than three incidents during a given quarter has been deleted to help prevent re-identification of victims. For example, if there were three domestic criminal sexual assaults during January to March 2020, all victims associated with those incidents have been removed from this dataset. Human trafficking victimizations have been aggregated separately due to the extremely small number of victimizations.

    This dataset includes a " GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized dataset, but with "UNKNOWN" in the shooting column.

    The dataset is refreshed daily, but excludes the most recent complete day to allow CPD time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.

    How does this dataset classify victims?

    The methodology by which this dataset classifies victims of violent crime differs by victimization type:

    Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.

    To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset.

    For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Victims dataset do not align with the homicide/non-fatal shooting categorization:

    1. In instances where a homicide victimization does not correspond to an IUCR code 0110 or 0130, we set the IUCR code to "01XX" to indicate that the victimization was a homicide but we do not know whether it was a first-degree murder (IUCR code = 0110) or a second-degree murder (IUCR code = 0130).
    2. When a non-fatal shooting victimization does not correspond to an IUCR code that signifies a criminal sexual assault, robbery, or aggravated battery, we enter “UNK” in the IUCR column, “YES” in the GUNSHOT_I column, and “NON-FATAL” in the PRIMARY column to indicate that the victim was non-fatally shot, but the precise IUCR code is unknown.

    Other violent crime victims: For other violent crime types, we refer to the IUCR classification that exists in CPD's victim table, with only one exception:

    1. When there is an incident that is associated with no victim with a matching IUCR code, we assume that this is an error. Every crime should have at least 1 victim with a matching IUCR code. In these cases, we change the IUCR code to reflect the incident IUCR code because CPD's incident table is considered to be more reliable than the victim table.

    Note: All businesses identified as victims in CPD data have been removed from this dataset.

    Note: The definition of “homicide” (shooting or otherwise) does not include justifiable homicide or involuntary manslaughter. This dataset also excludes any cases that CPD considers to be “unfounded” or “noncriminal.”

    Note: In some instances, the police department's raw incident-level data and victim-level data that were inputs into this dataset do not align on the type of crime that occurred. In those instances, this dataset attempts to correct mismatches between incident and victim specific crime types. When it is not possible to determine which victims are associated with the most recent crime determination, the dataset will show empty cells in the respective demographic fields (age, sex, race, etc.).

    Note: The initial reporting officer usually asks victims to report demographic data. If victims are unable to recall, the reporting officer will use their best judgment. “Unknown” can be reported if it is truly unknown.

  17. u

    Police Annual Statistical Report - Shooting Occurrences

    • data.urbandatacentre.ca
    • ckan0.cf.opendata.inter.prod-toronto.ca
    • +1more
    Updated Oct 3, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Police Annual Statistical Report - Shooting Occurrences [Dataset]. https://data.urbandatacentre.ca/dataset/city-toronto-police-annual-statistical-report-shooting-occurrences
    Explore at:
    Dataset updated
    Oct 3, 2024
    Description

    The Toronto’s Police Service Annual Statistical Report (ASR) is a comprehensive overview of police related statistics including reported crimes, victims of crime, search of persons, firearms, traffic collisions, personnel, budget, communications, public complaints, regulated interactions and other administrative information. This dataset includes all shooting occurrences from 2014 to 2019 by occurred date aggregated by Division. This data includes all shooting-related events reported to the Toronto Police Service, including, but not limited to, those that may have been deemed unfounded after investigation. Data is accurate as of the date and time of reporting. In accordance with the Municipal Freedom of Information and Protection of Privacy Act, the Toronto Police Service has taken the necessary measures to protect the privacy of individuals involved in the reported occurrences. No personal information related to any of the parties involved in the occurrence will be released as open data. The data has been aggregated by year, category, subtype and geographic division. As there is no criminal offence code for shootings, a shooting occurrence number may also be present in other data sets including, but not limited to, assault and robbery. Note: The further breakdown of this information at the event level will be made available in the future releases of the Shootings open data. Shootings in this data set include both firearm discharges and shooting events, which are defined as follows: Shooting Event/Occurrence: Any incident in which a projectile is discharged from a firearm (as defined under the Criminal Code of Canada) and injures a person. This excludes events such as suicide and police involved firearm discharges. Firearm Discharge: Any incident where evidence exists that a projectile was discharged from a firearm (as defined under the Criminal Code of Canada) including accidental discharge (non-police), celebratory fire, drive-by etc. Persons Injured (previously classified as “victims”): A person who was struck by a bullet(s) as a result of the discharge of a firearm (as defined under the Criminal Code of Canada). This excludes events such as suicide, police-involved event or where the weapon used was not a real firearm (such as pellet gun, air pistol, “sim-munition” etc.) Injury Levels

  18. US Police Shootings

    • kaggle.com
    Updated Jul 30, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Ahsen Nazir (2020). US Police Shootings [Dataset]. https://www.kaggle.com/ahsen1330/us-police-shootings/notebooks
    Explore at:
    CroissantCroissant is a format for machine-learning datasets. Learn more about this at mlcommons.org/croissant.
    Dataset updated
    Jul 30, 2020
    Dataset provided by
    Kaggle
    Authors
    Ahsen Nazir
    Area covered
    United States
    Description

    Context

    In the recent killings, a hot topic came into being, "Racism". So, I chose to gather some data to take out some insights and analyze the story around racism in America. I downloaded the raw data from kaggle and prepared it for visualization while correcting values, handling missing content, normalization and categorization

    Content

    It contains basic data about people like their name, age, gender and race. Along with it, is the shooting/killing information, like date of event, where it happened? how they were shot? did they attack? Were they holding weapons? Did they show any mental illness? Was the policeman wearing a camera/was the incident recorded? Did the suspect flee? Apart from that, a category column holds type of weapon used by the suspect

    Acknowledgements

    Kagglers

  19. T

    PDI (Police Data Initiative) Crime Incidents

    • data.cincinnati-oh.gov
    application/rdfxml +5
    Updated Jul 13, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Cincinnati (2025). PDI (Police Data Initiative) Crime Incidents [Dataset]. https://data.cincinnati-oh.gov/Safety/PDI-Police-Data-Initiative-Crime-Incidents/k59e-2pvf
    Explore at:
    tsv, application/rdfxml, csv, json, xml, application/rssxmlAvailable download formats
    Dataset updated
    Jul 13, 2025
    Dataset authored and provided by
    City of Cincinnati
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Description

    Note: Due to the RMS change for CPS, this data set stops on 6/2/2024. For records beginning on 6/3/2024, please see the dataset at this link: https://data.cincinnati-oh.gov/safety/Reported-Crime-STARS-Category-Offenses-/7aqy-xrv9/about_data

    The combined data will be available by 3/10/2025 at the linke above.

    Data Description: This data represents reported Crime Incidents in the City of Cincinnati. Incidents are the records, of reported crimes, collated by an agency for management. Incidents are typically housed in a Records Management System (RMS) that stores agency-wide data about law enforcement operations. This does not include police calls for service, arrest information, final case determination, or any other incident outcome data.

    Data Creation: The Cincinnati Police Department's (CPD) records crime incidents in the City through Records Management System (RMS) that stores agency-wide data about law enforcement operations.

    Data Created By: The source of this data is the Cincinnati Police Department.

    Refresh Frequency: This data is updated daily.

    CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/8eaa-xrvz

    Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

    Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

    Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

    Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

  20. c

    CMPD Officer-Involved Shootings - Incidents

    • data.charlottenc.gov
    Updated May 27, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Charlotte (2025). CMPD Officer-Involved Shootings - Incidents [Dataset]. https://data.charlottenc.gov/datasets/cmpd-officer-involved-shootings-incidents
    Explore at:
    Dataset updated
    May 27, 2025
    Dataset authored and provided by
    City of Charlotte
    Area covered
    Description

    An Officer Involved Shooting (OIS) is the discharge of a firearm, whether accidental or intentional, by a police officer, whether on or off duty. For the purposes of this posting, an OIS will only refer to the instances in which an officer discharged a firearm at a person. CMPD posts Officer Involved Shootings in an effort to create greater transparency of the actions of our employees. It is important to us that members of the community are informed whenever an officer discharges his/her firearm at a person and whether the shooting follows department policies and procedures. We believe that your trust and confidence in the Charlotte-Mecklenburg Police Department will increase as you understand what our officers encounter and how we hold them accountable for their actions. The CMPD is continuously reviewing and improving our practices to reduce the likelihood of deadly force incidents. The following is a complete list of OIS tables posted on the Charlotte Open Data Portal:1) Officer Involved Shootings – Incidents: contains INCIDENT_ID (for joining to other OIS tables), year and month recorded, location, district attorney legal review status, descriptive narrative of incident2) Officer Involved Shootings – Individuals: contains INCIDENT_ID (for joining to other OIS tables) as well as individual’s race, gender, age, and injury type3) Officer Involved Shootings – Officers: contains INCIDENT_ID (for joining to other OIS tables) as well as officer’s race, gender, years of service, and CMPD policy violation status. Please note that the relationship of the Incidents table to the Individuals table is one-to-many, and the relationship of the Incidents table to the Officers table is one-to-many.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Statista (2025). People shot to death by U.S. police 2017-2024, by race [Dataset]. https://www.statista.com/statistics/585152/people-shot-to-death-by-us-police-by-race/
Organization logo

People shot to death by U.S. police 2017-2024, by race

Explore at:
122 scholarly articles cite this dataset (View in Google Scholar)
Dataset updated
May 27, 2025
Dataset authored and provided by
Statistahttp://statista.com/
Area covered
United States
Description

Sadly, the trend of fatal police shootings in the United States seems to only be increasing, with a total 1,173 civilians having been shot, 248 of whom were Black, as of December 2024. In 2023, there were 1,164 fatal police shootings. Additionally, the rate of fatal police shootings among Black Americans was much higher than that for any other ethnicity, standing at 6.1 fatal shootings per million of the population per year between 2015 and 2024. Police brutality in the U.S. In recent years, particularly since the fatal shooting of Michael Brown in Ferguson, Missouri in 2014, police brutality has become a hot button issue in the United States. The number of homicides committed by police in the United States is often compared to those in countries such as England, where the number is significantly lower. Black Lives Matter The Black Lives Matter Movement, formed in 2013, has been a vocal part of the movement against police brutality in the U.S. by organizing “die-ins”, marches, and demonstrations in response to the killings of black men and women by police. While Black Lives Matter has become a controversial movement within the U.S., it has brought more attention to the number and frequency of police shootings of civilians.

Search
Clear search
Close search
Google apps
Main menu