"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 w...

This dataset contains information on fatal police deaths in the United States. The data includes the victim's rank, name, department, date of death, and cause of death. The data spans from 1791 to the present day. This dataset will be updated on monthly basis. Data Scrapped from this website :- https://www.odmp.org/

New Version Features -> With the new web scrapper I have upgraded dataset with more information. 1) The new dataset version is "police_deaths_USA_v6.csv" and "k9_deaths_USA_v6.csv". 2) Splitted the dataset into 2 different datasets 1 for Human Unit and other for K9 Unit. 3) Check out the new web scrapper code in this file "final_scrapper_program_with_comments.ipynb". 4) Also added the correction file which is needed to adjust some data points from K9 dataset. 5) Extended data of Human Unit dataset to 13 Features. 6) Extended data of K9 Unit dataset to 14 Features.

The police_deaths dataset contains 13 variables:

1) Rank -> Rank assigned or achieved by the police throughout their tenure.

2) Name -> The name of the person.

3) Age -> Age of the person.

4) End_Of_Watch -> The death date on which the the person declared as dead.

5) Day_Of_Week -> The day of the week [Sunday, Monday, etc.].

6) Cause -> The cause of the death.

7) Department -> The department's name where the person works.

8) State -> The state where the department is situated.

9) Tour -> The Duration of there Tenure.

10) Badge -> Badge of the person.

11) Weapon -> The Weapon by which the officer has been killed.

12) Offender -> Offender / Killer this says what happened to the offender after the incident was he/she [Arrested, Killed, etc.].

13) Summary -> Summary of the police officer and also the summary of the incident of what happened ? How he/she died ?, etc.

The k9_deaths dataset contains 14 variables:

1) Rank -> Rank assigned or achieved by the K9 throughout their tenure.

2) Name -> The name of the K9.

3) Breed -> Breed of the K9.

4) Gender -> Gender of the K9.

5) Age -> Age of the K9.

6) End_Of_Watch -> The death date on which the the person declared as dead.

7) Day_Of_Week -> The day of the week [Sunday, Monday, etc.].

8) Cause -> The cause of the death.

9) Department -> The department's name where the K9 was assigned.

10) State -> The state where the department is situated.

11) Tour -> The Duration of there Tenure.

12) Weapon -> The Weapon by which the officer has been killed.

13) Offender -> Offender / Killer this says what happened to the offender after the incident was he/she [Arrested, Killed, etc.].

14) Summary -> Summary of the K9 dog and also the summary of the incident of what happened ? How he/she died ?, etc.

Acknowledgements:

The original dataset was collected by FiveThirtyEight and it contains police death data from 1791 to 2016. Here is the link -> https://data.world/fivethirtyeight/police-deaths.

The reason I made this dataset is because it had not been updated since 2016 and the scrapping script was outdated, so I decided to make a new scrapper and update the dataset till present. I got this idea from the FiveThirtyEight group and a fellow kaggler, Satoshi Datamoto, who uploaded the dataset on kaggle. Thank you for inspiration.

Tableau Visualization link :- https://public.tableau.com/app/profile/mayuresh.koli/viz/USALawEnforcementLineofDutyDeaths/main_dashboard

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.

Law Enforcement Locations:Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies.

Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police).

In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state.

Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset.

Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes.

TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection.

This dataset is comprised completely of license free data.

FBI entities are intended to be excluded from this dataset, but a few may be included.

The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes.

With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer).

Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries.

"#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields.

Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results.

All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.

The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 12/07/2006 and the newest record dates from 10/23/2009Use Cases: 1. An assessment of whether or not the total police capability in a given area is adequate.

1. A list of resources to draw upon in surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can help to determine those entities who are able to respond the quickest.

2. A resource for emergency management planning purposes.

3. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster.

4. A resource for situational awareness planning and response for federal government events.

Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes are included due to the fact that the New Mexico Mounted Police work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 08/14/2006 and the newest record dates from 10/23/2009

This data was obtained from https://mappingpoliceviolence.us/.

Mapping Police Violence is a 501(c)(3) organization that publishes the most comprehensive and up-to-date data on police violence in America to support transformative change.

This is a database set on openly sharing information on police violence in America.

Some information on this data according to their website: Our data has been meticulously sourced from official police use of force data collection programs in states like California, Texas and Virginia, combined with nationwide data from The Gun Violence Archive and the Fatal Encounters database, two impartial crowdsourced databases. We've also done extensive original research to further improve the quality and completeness of the data; searching social media, obituaries, criminal records databases, police reports and other sources to identify the race of 90 percent of all victims in the database.

We believe the data represented on this site is the most comprehensive accounting of people killed by police since 2013. Note that the Mapping Police Violence database is more comprehensive than the Washington Post police shootings database: while WaPo only tracks cases where people are fatally shot by on-duty police officers, our database includes additional incidents such as cases where police kill someone through use of a chokehold, baton, taser or other means as well as cases such as killings by off-duty police. A recent report from the Bureau of Justice Statistics estimated approximately 1,200 people were killed by police between June, 2015 and May, 2016. Our database identified 1,100 people killed by police over this time period. While there are undoubtedly police killings that are not included in our database (namely, those that go unreported by the media), these estimates suggest that our database captures 92% of the total number of police killings that have occurred since 2013. We hope these data will be used to provide greater transparency and accountability for police departments as part of the ongoing work to end police violence in America.

Content

Police Residence

This folder contains data behind the story Most Police Don’t Live In The Cities They Serve.

Includes the cities with the 75 largest police forces, with the exception of Honolulu for which data is not available. All calculations are based on data from the U.S. Census.

The Census Bureau numbers are potentially going to differ from other counts for three reasons:

1. The census category for police officers also includes sheriffs, transit police and others who might not be under the same jurisdiction as a city’s police department proper. The census category won’t include private security officers.
2. The census data is estimated from 2006 to 2010; police forces may have changed in size since then.
3. There is always a margin of error in census numbers; they are estimates, not complete counts.

How to read police-locals.csv

Note: When a cell contains ** it means that there are fewer than 100 police officers of that race serving that city.

Context

This is a dataset from FiveThirtyEight hosted on their GitHub. Explore FiveThirtyEight data using Kaggle and all of the data sources available through the FiveThirtyEight organization page!

• Update Frequency: This dataset is updated daily.

Acknowledgements

This dataset is maintained using GitHub's API and Kaggle's API.

This dataset is distributed under the Attribution 4.0 International (CC BY 4.0) license.

Information found in this report follow the Uniformed Crime Reporting guidelines established by the FBI for LEOKA.

Key code for Race:

A- Asian/Pacific Island, Non-Hispanic B- African American, Non-Hispanic C- Hawaiian/Other Pacific Island, Hispanic H- Hawaiian/Other Pacific Island, Non-Hispanic I- Indian/Alaskan Native, Non-Hispanic K- African American, Hispanic L- Caucasian, Hispanic N- Indian/Alaskan Native, Hispanic P- Asian/Pacific Island, Hispanic S- Asian, Non-Hispanic T- Asian, Hispanic U- Unknown W- Caucasian, Non-Hispanic

Key Code for Reading Districts:

Example: LB519

L for Law call or incident B stands for Bloomington 5 is the district or beat where incident occurred All numbers following represents a grid sector.

Disclaimer: The Bloomington Police Department takes great effort in making open data as accurate as possible, but there is no avoiding the introduction of errors in this process, which relies on data provided by many people and that cannot always be verified. Information contained in this dataset may change over a period of time. The Bloomington Police Department is not responsible for any error or omission from this data, or for the use or interpretation of the results of any research conducted.

These data on 19th- and early 20th-century police department and arrest behavior were collected between 1975 and 1978 for a study of police and crime in the United States. Raw and aggregated time-series data are presented in Parts 1 and 3 on 23 American cities for most years during the period 1860-1920. The data were drawn from annual reports of police departments found in the Library of Congress or in newspapers and legislative reports located elsewhere. Variables in Part 1, for which the city is the unit of analysis, include arrests for drunkenness, conditional offenses and homicides, persons dismissed or held, police personnel, and population. Part 3 aggregates the data by year and reports some of these variables on a per capita basis, using a linear interpolation from the last decennial census to estimate population. Part 2 contains data for 267 United States cities for the period 1880-1890 and was generated from the 1880 federal census volume, REPORT ON THE DEFECTIVE, DEPENDENT, AND DELINQUENT CLASSES, published in 1888, and from the 1890 federal census volume, SOCIAL STATISTICS OF CITIES. Information includes police personnel and expenditures, arrests, persons held overnight, trains entering town, and population.

A list of all NYPD officers, as reported to CCRB by NYPD based on NYPD's roster, and a count of any complaints they have received since the year 2000. The dataset is part of a database of all public police misconduct records the Civilian Complaint Review Board (CCRB) maintains on complaints against New York Police Department uniformed members of service received in CCRB's jurisdiction since the year 2000, when CCRB's database was first built. This data is published as four tables: Civilian Complaint Review Board: Police Officers Civilian Complaint Review Board: Complaints Against Police Officers Civilian Complaint Review Board: Allegations Against Police Officers Civilian Complaint Review Board: Penalties A single complaint can include multiple allegations, and those allegations may include multiple subject officers and multiple complainants. Public records exclude complaints and allegations that were closed as Mediated, Mediation Attempted, Administrative Closure, Conciliated (for some complaints prior to the year 2000), or closed as Other Possible Misconduct Noted. This database is inclusive of prior datasets held on Open Data (previously maintained as "Civilian Complaint Review Board (CCRB) - Complaints Received," "Civilian Complaint Review Board (CCRB) - Complaints Closed," and "Civilian Complaint Review Board (CCRB) - Allegations Closed") but includes information and records made public by the June 2020 repeal of New York Civil Rights law 50-a, which precipitated a full revision of what CCRB data could be considered public.

The primary table for all public data on complaints, including dates, locations and the outcomes of closed complaints received since the year 2000. The dataset is part of a database of all public police misconduct records the Civilian Complaint Review Board (CCRB) maintains on complaints against New York Police Department uniformed members of service received in CCRB's jurisdiction since the year 2000, when CCRB's database was first built. This data is published as four tables: Civilian Complaint Review Board: Police Officers Civilian Complaint Review Board: Complaints Against Police Officers Civilian Complaint Review Board: Allegations Against Police Officers Civilian Complaint Review Board: Penalties A single complaint can include multiple allegations, and those allegations may include multiple subject officers and multiple complainants. Public records exclude complaints and allegations that were closed as Mediated, Mediation Attempted, Administrative Closure, Conciliated (for some complaints prior to the year 2000), or closed as Other Possible Misconduct Noted. This database is inclusive of prior datasets held on Open Data (previously maintained as "Civilian Complaint Review Board (CCRB) - Complaints Received," "Civilian Complaint Review Board (CCRB) - Complaints Closed," and "Civilian Complaint Review Board (CCRB) - Allegations Closed") but includes information and records made public by the June 2020 repeal of New York Civil Rights law 50-a, which precipitated a full revision of what CCRB data could be considered public.

Feature layer showing the locations of Sworn Law Enforcement Officer Locations in California.This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. This also applies to mounted police in New Mexico. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection in the United States and its territories. This dataset is comprised completely of license free data. At the request of NGA, FBI entities are intended to be excluded from this dataset, but a few may be included. The HSIP Freedom Law Enforcement dataset and the HSIP Freedom Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. Please see the process description for the breakdown of how the records were merged. With the merge of the Law Enforcement and the Correctional Institutions datasets, the HSIP Themes and NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard HSIP fields that TGS populated. Double spaces were replaced by single spaces in these same fields. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 12/07/2004 and the newest record dates from 09/10/2009.Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.1. An assessment of whether or not the total police capability in a given area is adequate. 2. A list of resources to draw upon in surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can help to determine those entities who are able to respond the quickest. 3. A resource for emergency management planning purposes. 4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster. 5. A resource for situational awareness planning and response for federal government events.

This dataset contains Use of Force (UOF) incidents (formerly referred to as "Response to Resistance" incidents) from January 2018 through February 17, 2025, including demographic information for officers as well as individuals. All incidents included in the UOF dataset have gone through a review process and have been completed and finalized. Incidents still in process are not included in the dataset until marked complete.

Note: Phoenix Police Department released an update to our Use of Force policy on February 18, 2025. We are currently working to build an updated Transparency Dashboard for this new data moving forward.

View Operations Order 1.5

Provide your feedback!

Help us improve this site and complete the Open Data Customer Survey.

This dataset contains Phoenix Police Department officer demographics as of January 1st of each year starting in 2018. All ranks of sworn employees are included.

Provide your feedback!

Help us improve this site and complete the Open Data Customer Survey.

Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 04/26/2006 and the newest record dates from 10/19/2009

Bloomington Police Department cases where officers have fired a gun at an individual. Key code for Race: A- Asian/Pacific Island, Non-Hispanic B- African American, Non-Hispanic C- Hawaiian/Other Pacific Island, Hispanic H- Hawaiian/Other Pacific Island, Non-Hispanic I- Indian/Alaskan Native, Non-Hispanic K- African American, Hispanic L- Caucasian, Hispanic N- Indian/Alaskan Native, Hispanic P- Asian/Pacific Island, Hispanic S- Asian, Non-Hispanic T- Asian, Hispanic U- Unknown W- Caucasian, Non-Hispanic Key Code for Reading Districts: Example: LB519 L for Law call or incident B stands for Bloomington 5 is the district or beat where incident occurred All numbers following represents a grid sector. Disclaimer: The Bloomington Police Department takes great effort in making open data as accurate as possible, but there is no avoiding the introduction of errors in this process, which relies on data provided by many people and that cannot always be verified. Information contained in this dataset may change over a period of time. The Bloomington Police Department is not responsible for any error or omission from this data, or for the use or interpretation of the results of any research conducted.

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.

Context

Introduction: The dataset used for this experiment is real and authentic. The dataset is acquired from UCI machine learning repository website [13]. The title of the dataset is ‘Crime and Communities’. It is prepared using real data from socio-economic data from 1990 US Census, law enforcement data from the 1990 US LEMAS survey, and crimedata from the 1995 FBI UCR [13]. This dataset contains a total number of 147 attributes and 2216 instances.

The per capita crimes variables were calculated using population values included in the 1995 FBI data (which differ from the 1990 Census values).

Content

The variables included in the dataset involve the community, such as the percent of the population considered urban, and the median family income, and involving law enforcement, such as per capita number of police officers, and percent of officers assigned to drug units. The crime attributes (N=18) that could be predicted are the 8 crimes considered 'Index Crimes' by the FBI)(Murders, Rape, Robbery, .... ), per capita (actually per 100,000 population) versions of each, and Per Capita Violent Crimes and Per Capita Nonviolent Crimes)

predictive variables : 125 non-predictive variables : 4 potential goal/response variables : 18

Acknowledgements

http://archive.ics.uci.edu/ml/datasets/Communities%20and%20Crime%20Unnormalized

U. S. Department of Commerce, Bureau of the Census, Census Of Population And Housing 1990 United States: Summary Tape File 1a & 3a (Computer Files),

U.S. Department Of Commerce, Bureau Of The Census Producer, Washington, DC and Inter-university Consortium for Political and Social Research Ann Arbor, Michigan. (1992)

U.S. Department of Justice, Bureau of Justice Statistics, Law Enforcement Management And Administrative Statistics (Computer File) U.S. Department Of Commerce, Bureau Of The Census Producer, Washington, DC and Inter-university Consortium for Political and Social Research Ann Arbor, Michigan. (1992)

U.S. Department of Justice, Federal Bureau of Investigation, Crime in the United States (Computer File) (1995)

Inspiration

Your data will be in front of the world's largest data science community. What questions do you want to see answered?

Data available in the dataset may not act as a complete source of information for identifying factors that contribute to more violent and non-violent crimes as many relevant factors may still be missing.

However, I would like to try and answer the following questions answered.

1. Analyze if number of vacant and occupied houses and the period of time the houses were vacant had contributed to any significant change in violent and non-violent crime rates in communities

2. How has unemployment changed crime rate(violent and non-violent) in the communities?

3. Were people from a particular age group more vulnerable to crime?

4. Does ethnicity play a role in crime rate?

5. Has education played a role in bringing down the crime rate?

Context

This dataset contains information about fatal shooting of civilians by police officers in the US since Jan 1st, 2015. The data about the shootings was collected by the Washington Post in their fatal police shootings dataset. The city locations were geocoded using OpenStreetMap Nominatim.

Content

fatal-police-shootings-data.csv contains information about each shooting. Each row is a shooting, and columns contain information about

• Name of the individual shot
• Date of the shooting
• Manner of death of the individual shot
• If and how the individual shot was armed
• Age of the individual shot
• Gender of the individual shot
• Race of the individual shot
• Whether the individual shot displayed signs of mental illness
• To what level the individual shot was attacking when shot
• If and how the individual shot was fleeing from police
• If an officer present for the shooting was wearing a body camera

CityLocations.csv contains the latitude and longitude for each city present in fatal-police-shootings-data.csv.

Acknowledgements and Licenses

The data in fatal-police-shootings-data.csv was collected by the Washington Post, and is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License.

The data in CityLocations.csv was geocoded using OpenStreetMap Nominatim, and is licensed under the Open Database License.

Cover image by Spenser.

This dataset includes responses to two survey experiments testing the effects of officer diversity, which were conducted with a national sample (N = 1,100). The survey was fielded by YouGov in the spring of 2022 (between April 21 and May 2). For our experiments, YouGov constructed two synthetic sampling frames (SSF) via stratified sampling from the 2019 American Community Survey, which were used to select two matched (on gender, age, and education) samples of opt-in panelists: a general population sample (N = 650) and a large oversample of Black Americans (N = 450). (The general population sample was also matched on race.) Using propensity scoring based on region and the matching variables, both samples were then weighted to their respective SSFs, after which the weights were post-stratified on 2016 and 2020 Presidential vote choice. The purpose of the oversample was to yield (after combining Black respondents in the oversample with those in the general population sample) similarly sized analytic samples of Black and non-Black Americans. Per this sampling design, we estimated the models for the experiments separately for Black and non-Black respondents. For the main analysis, we applied the provided sampling weights. (NOTE: The original files were uploaded in Stata-12 version.)