The killing of Tyre Nichols in January 2023 by Memphis Police Officers has reignited debates about police brutality in the United States. Between 2013 and 2024, over 1,000 people have been killed by police every year. Some of the most infamous examples include the murder of George Floyd in May 2020 and the shooting of Breonna Taylor earlier that year. Within the provided time period, the most people killed by police in the United States was in 2024, at 1,375 people. Police Violence in the U.S. Police violence is defined as any instance where a police officer’s use of force results in a civilian’s death, regardless of whether it is considered justified by the law. While many people killed by police in the U.S. were shot, other causes of death have included tasers, vehicles, and physical restraints or beatings. In the United States, the rate of police shootings is much higher for Black Americans than it is for any other ethnicity, and recent incidents of police killing unarmed Black men and women in the United States have led to widespread protests against police brutality, particularly towards communities of color. America’s Persistent Police Problem Despite increasing visibility surrounding police violence in recent years, police killings have continued to occur in the United States at a consistently high rate. In comparison to other countries, police in the U.S. have killed people at a rate three times higher than police in Canada and 60 times the rate of police in England. While U.S. police have killed people in almost all 50 states, as well as the District of Columbia, New Mexico was reported to have the highest rate of people killed by the police in the United States, with 8.03 people per million inhabitants killed by police.

As of November 17, 277 Black people were killed by the police in the United States in 2024. This compares to 201 Hispanic people and 445 white people. The rate of police shootings of Black Americans is much higher than any other ethnicity, at 6.2 per million people. This rate stands at 2.8 per million for Hispanic people and 2.4 per million for white people.

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.

About Dataset:

Don't Forget to Upvote the dataset.

https://upload.wikimedia.org/wikipedia/commons/thumb/2/2f/Police_killings_in_the_USA_in_2018.svg/220px-Police_killings_in_the_USA_in_2018.svg.png" alt="">

Below are lists of people killed by law enforcement in the United States, both on duty and off duty. Although Congress instructed the Attorney General in 1994 to compile and publish annual statistics on police use of excessive force, this was never carried out, and the Federal Bureau of Investigation does not collect these data.

Deaths by age group in 2015, according to The Counted

Column Details:

COLUMN NAME	INFO
id	SERIAL NO
name	NAME OF VICTIM THAT GOT SHOT OR TASERED BY POLICE
date	DATE IN WHICH HE GOT VICTIMIZED
manner_of_death	TYPE OF MANNER IN WHICH HE DIED
armed	THE VICTIM WAS ARMED OR NOT
age	AGE OF VICTIM
gender	GENDER OF VICTIM
race	RACE,ETHICITY OF VICTIM
city	CITY IN THE USA IN which he/she DIED
state	STATE IN THE USA IN which he/she DIED
signs_of_mental_illness	VICTIM SHOWS SIGN OF ILLNESS
threat_level	LEVEL OF THREAT ON POLICE
flee	VICTIM FLEE OR DIE
body_camera	BODY CAMERA WAS ON POLICE OR NOT
longitude	LONGITUDE OF LOCATION
latitude	LATITUDE OF LOCATION
is_geocoding_exact	LOCATION AVAILABLE EXACT OR NOT

TO KNOW MORE FROM WIKIPEDIA :https://en.wikipedia.org/wiki/Lists_of_killings_by_law_enforcement_officers_in_the_United_States

In 2023/24, the police in England and Wales fatally shot two people, compared with three in the previous reporting year, and six in 2016/17. During the same reporting year, the police used firearms twice, compared with ten times in 2022/23. In general, the police in England and Wales and in the rest of the UK do not have a tradition of carrying firearms, with the country having some of the strictest gun laws in the world. In 2023/24, out of around 147,746 police officers, just 5,861 were licensed to carry firearms in England and Wales. Comparisons with the United States Among developed economies, the United States is something of an outlier when it comes to police shootings. In 2024, it is estimated that the police in the United States fatally shot 1,173 people. There are also significant disparities based on a person's ethnicity. Between 2015 and March 2024, the rate of fatal police shootings among Black Americans was 6.1 per one million people, 2.7 per million people for Hispanic Americans and 2.4 per million people for white Americans. Gun violence overall is also far more prevalent in the United States, with 42 percent of American households owning a firearm as of 2023. Gun homicides rare in England and Wales Of the 583 homicides that took place in England and Wales in 2023/24, just 22 were committed by a person using a firearm. By far the most common method of killing was using a knife or other sharp instrument, at 262 homicides, or around 46 percent of them. Compared with twenty years ago, homicides in England and Wales have declined, falling from 1,047 in 2002/03, to just 533 in 2014/15. After this point, annual homicides rose, and by 2016/17 there were more than 700 homicides recorded in England and Wales. Although there have been some fluctuations, particularly during 2020/21 at the height of COVID-19 lockdowns.

Since 2013, protests opposing police violence against Black people have occurred across a number of American cities under the banner of “Black Lives Matter.” We develop a new dataset of Black Lives Matter protests that took place in 2014–2015 and explore the contexts in which they emerged. We find that Black Lives Matter protests are more likely to occur in localities where more Black people have previously been killed by police. We discuss the implications of our findings in light of the literature on the development of social movements and recent scholarship on the carceral state’s impact on political engagement.

In the United States, more men than women are shot to death by the police. As of October 22, the U.S. police shot 904 men and 44 women to death in 2024. In 2023, the police shot 1,107 men and 48 women to death.

The rate of fatal police shootings in the United States shows large differences based on ethnicity. Among Black Americans, the rate of fatal police shootings between 2015 and December 2024 stood at 6.1 per million of the population per year, while for white Americans, the rate stood at 2.4 fatal police shootings per million of the population per year. Police brutality in the United States Police brutality is a major issue in the United States, but recently saw a spike in online awareness and protests following the murder of George Floyd, an African American who was killed by a Minneapolis police officer. Just a few months before, Breonna Taylor was fatally shot in her apartment when Louisville police officers forced entry into her apartment. Despite the repeated fatal police shootings across the country, police accountability has not been adequate according to many Americans. A majority of Black Americans thought that police officers were not held accountable for their misconduct, while less than half of White Americans thought the same. Political opinions Not only are there differences in opinion between ethnicities on police brutality, but there are also major differences between political parties. A majority of Democrats in the United States thought that police officers were not held accountable for their misconduct, while a majority of Republicans that they were held accountable. Despite opposing views on police accountability, both Democrats and Republicans agree that police should be required to be trained in nonviolent alternatives to deadly force.

This approximately 9-year dataset of suspects involved in shooting incidents contains suspect demographic information. Between January 1, 2010 and April 10, 2018, the Tucson Police Department experienced 51 Officer-involved shooting incidents. The suspects reported here are those involved in an incident in which an Officer discharged a firearm at a person. This list does not contain accidental discharges or incidents involving animals.This data is related to the Officer Involved Shootings Feature Layer through the Incident ID.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactScott EllisCity of Tucson Police DepartmentScott.Ellis@tucsonaz.govUpdate FrequencyUPDATED Occasionally using ArcMapLast known updated -- April, 2018

This 2018 rime data is the list of crimes that the Syracuse Police Department responded to in 2018. These records does not include rape offenses as well as any crimes that have been sealed by the court. These records are derived from the records management system utilized by the SPD. The data is then anonymized by SPD Crime Analysts weekly. After this data is received weekly from the SPD, this data is then mapped to the approximate location of that incident, using the 100 block level and a Geolocator File from Onondaga County GIS Department. This data is then updated on the Open Data Portal. The points should not be construed to be the exact point this incidents were reported to occur, rather the block where these incident is reported to occur.Crimes are reported to the FBI in two major categories under the Uniform Crime Reports specification: Part 1 and Part 2 crimes. Part 1 crimes include criminal homicide, forcible rape, robbery, aggravated assault, burglary, larceny-theft, and motor vehicle theft. In these records, rape offenses have been excluded due to victim privacy concerns.Part 2 crimes include all other offenses. A more detailed guide to Part 1 crimes is listed below. More details about Part 2 Crimes is listed in the Part 2 Crimes Dataset.When using the data, the date and time provided are when the crime was actually reported. This means that though a larceny might be reported at noon, the actual crime could have happened at 8am, but was not realized until someone noticed hours later. Similarly, if a home break-in happens during a holiday weekend when the owners are out of town, the crime report may not come in until they return home and notice the crime took place previously. The address in the dataset is where the crime occurred. The location is also anonymized to the block level, so a crime that occurred at 123 Main St. will appear as occurring on the 100 block of Main St. This is to protect the privacy of all involved. Finally, information about crimes is fluid, and details about the crime could change.Data DictionaryDate End - Date that the crime was reported. It could have happened earlier. This is in the format of DD-MON-YY (Ex. 01-Jan-22).Time start and time end - Listed in military time (2400) - Burglaries and larcenies are often a time frame. Address - Where the crime occurred. All addresses are in the 100’s because the Syracuse Police Department allows privacy for residents and only lists the block number.Code Defined - Offense names are listed as crime categories group for ease of understanding. There may have been other offenses also, but the one displayed is the highest Unified Crime Reporting (UCR) category.Arrest - Means that there was an arrest, but not necessarily for that crime.DisclaimerData derived from the Syracuse Police Department record management system, any data not listed is not currently available.Part I Crime DefinitionsCriminal homicide—a.) Murder and non-negligent manslaughter: the willful (non-negligent) killing of one human being by another. Deaths caused by negligence, attempts to kill, assaults to kill, suicides, and accidental deaths are excluded. The program classifies justifiable homicides separately and limits the definition to: (1) the killing of a felon by a law enforcement officer in the line of duty; or (2) the killing of a felon, during the commission of a felony, by a private citizen. b.) Manslaughter by negligence: the killing of another person through gross negligence. Deaths of persons due to their own negligence, accidental deaths not resulting from gross negligence, and traffic fatalities are not included in the category Manslaughter by Negligence. Robbery—The taking or attempting to take anything of value from the care, custody, or control of a person or persons by force or threat of force or violence and/or by putting the victim in fear. Aggravated assault—An unlawful attack by one person upon another for the purpose of inflicting severe or aggravated bodily injury. This type of assault usually is accompanied by the use of a weapon or by means likely to produce death or great bodily harm. Simple assaults are excluded. Burglary (breaking or entering)—The unlawful entry of a structure to commit a felony or a theft. Attempted forcible entry is included. Larceny-theft (except motor vehicle theft)—The unlawful taking, carrying, leading, or riding away of property from the possession or constructive possession of another. Examples are thefts of bicycles, motor vehicle parts and accessories, shoplifting, pocket picking, or the stealing of any property or article that is not taken by force and violence or by fraud. Attempted larcenies are included. Embezzlement, confidence games, forgery, check fraud, etc., are excluded. Motor vehicle theft—The theft or attempted theft of a motor vehicle. A motor vehicle is self-propelled and runs on land surface and not on rails. Motorboats, construction equipment, airplanes, and farming equipment are specifically excluded from this category. Dataset Contact Information:Organization: Syracuse Police Department (SPD)Position: Data Program ManagerCity: Syracuse, NYE-Mail Address: opendata@syrgov.net

Between 2008/09 and 2018/19, 85 percent of deaths in police custody in England and Wales were white people, who make up 86 percent of the UK population. In the same time period, black people accounted for eight percent of the UK deaths in police custody, while only making up three percent of the total population.

This data set contains Somerville crashes that occurred from May 2018 to present. Crash reports are completed when a motor vehicle crash occurs on a public way and involves at least one of the following: Any person is killed, any person is injured, or damage is in excess of $1,000 to any one vehicle or other property. Data does not include crashes that are under active investigation, nor those that occur on state roads, which are under the jurisdiction of the Massachusetts State Police. State crash data may be accessed on the Massachusetts Department of Transportation’s crash data portal, IMPACT. This data set should be refreshed daily with data appearing with a one-month delay (e.g. crashes that occurred from 1/1 will appear on 2/1). If a daily update does not refresh, please email data@somervillema.gov.

A. SUMMARY This table contains all fatalities resulting from a traffic crash in the City of San Francisco. Fatality year-to-date crash data is obtained from the Office of the Chief Medical Examiner (OME) death records, and only includes those cases that meet the San Francisco Vision Zero Fatality Protocol maintained by the San Francisco Department of Public Health (SFDPH), San Francisco Police Department (SFPD), and San Francisco Municipal Transportation Agency (SFMTA). Injury crash data is obtained from SFPD’s Interim Collision System for 2018 to YTD, Crossroads Software Traffic Collision Database (CR) for years 2013-2017 and the Statewide Integrated Transportation Record System (SWITRS) maintained by the California Highway Patrol for all years prior to 2013. Only crashes with valid geographic information are mapped. All geocodable crash data is represented on the simplified San Francisco street centerline model maintained by the Department of Public Works (SFDPW). Collision injury data is queried and aggregated on a quarterly basis. Crashes occurring at complex intersections with multiple roadways are mapped onto a single point and injury and fatality crashes occurring on highways are excluded. The fatality table contains information about each party injured or killed in the collision, including any passengers. B. HOW THE DATASET IS CREATED Traffic crash injury data is collected from the California Highway Patrol 555 Crash Report as submitted by the police officer within 30 days after the crash occurred. All fields that match the SWITRS data schema are programmatically extracted, de-identified, geocoded, and loaded into TransBASE. See Section D below for details regarding TransBASE. This table is filtered for fatal traffic crashes. C. UPDATE PROCESS After review by SFPD and SFDPH staff, the data is made publicly available approximately a month after the end of the previous quarter (May for Q1, August for Q2, November for Q3, and February for Q4). D. HOW TO USE THIS DATASET This data is being provided as public information as defined under San Francisco and California public records laws. SFDPH, SFMTA, and SFPD cannot limit or restrict the use of this data or its interpretation by other parties in any way. Where the data is communicated, distributed, reproduced, mapped, or used in any other way, the user should acknowledge the Vision Zero initiative and the TransBASE database as the source of the data, provide a reference to the original data source where also applicable, include the date the data was pulled, and note any caveats specified in the associated metadata documentation provided. However, users should not attribute their analysis or interpretation of this data to the City of San Francisco. While the data has been collected and/or produced for the use of the City of San Francisco, it cannot guarantee its accuracy or completeness. Accordingly, the City of San Francisco, including SFDPH, SFMTA, and SFPD make no representation as to the accuracy of the information or its suitability for any purpose and disclaim any liability for omissions or errors that may be contained therein. As all data is associated with methodological assumptions and limitations, the City recommends that users review methodological documentation associated with the data prior to its analysis, interpretation, or communication. TransBASE is a geospatially enabled database maintained by SFDPH that currently includes over 200 spatially referenced variables from multiple agencies and across a range of geographic scales, including infrastructure, transportation, zoning, sociodemographic, and collision data, all linked to an intersection or street segment. TransBASE facilitates a data-driven approach to understanding and addressing transportation-related health issues, informed by a large and growing evidence base regarding the importance of transportation system design and land u

Abstract (en): For any questions about this data please email me at jacob@crimedatatool.com. If you use this data, please cite it.Version 7 release notes:Add data from 2018Version 6 release notes:Adds data in the following formats: SPSS and Excel.Changes project name to avoid confusing this data for the ones done by NACJD.Version 5 release notes: Adds data for 1960-1974 and 2017. Note: many columns (including number of female officers) will always have a value of 0 for years prior to 1971.Removes support for .csv and .sav files.Adds a number_of_months_reported variable for each agency-year. A month is considered reported if the month_indicator column for that month has a value of "normal update" or "reported, not data."The formatting of the monthly data has changed from wide to long. This means that each agency-month has a single row. The old data had each agency being a single row with each month-category (e.g. jan_officers_killed_by_felony) being a column. Now there will just be a single column for each category (e.g. officers_killed_by_felony) and the month can be identified in the month column. This also results in most column names changing. As such, be careful when aggregating the monthly data since some variables are the same every month (e.g. number of officers employed is measured annually) so aggregating will be 12 times as high as the real value for those variables. Adds a date column. This date column is always set to the first of the month. It is NOT the date that a crime occurred or was reported. It is only there to make it easier to create time-series graphs that require a date input.All the data in this version was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. Data is the same as from NACJD but using all FBI files makes cleaning easier as all column names are already identical. Version 4 release notes: Add data for 2016.Order rows by year (descending) and ORI.Version 3 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The LEOKA data sets contain highly detailed data about the number of officers/civilians employed by an agency and how many officers were killed or assaulted. All the data was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. About 7% of all agencies in the data report more officers or civilians than population. As such, I removed the officers/civilians per 1,000 population variables. You should exercise caution if deciding to generate and use these variables yourself. Several agency had impossible large (>15) officer deaths in a single month. For those months I changed the value to NA. See the R code for a complete list. For the R code used to clean this data, see here. https://github.com/jacobkap/crime_data.The UCR Handbook (https://ucr.fbi.gov/additional-ucr-publications/ucr_handbook.pdf/view) describes the LEOKA data as follows:"The UCR Program collects data from all contributing agencies ... on officer line-of-duty deaths and assaults. Reporting agencies must submit data on ... their own duly sworn officers feloniously or accidentally killed or assaulted in the line of duty. The purpose of this data collection is to identify situations in which officers are killed or assaulted, describe the incidents statistically, and publish the data to aid agencies in developing policies to improve officer safety."... agencies must record assaults on sworn officers. Reporting agencies must count all assaults that resulted in serious injury or assaults in which a weapon was used that could have caused serious injury or death. They must include other assaults not causing injury if the assault involved more than mere verbal abuse or minor resistance to an arrest. In other words, agencies must include in this section all assaults on officers, whether or not the officers sustained injuries." Law enforcement agencies in the United States.Smallest Geographic Unit: Police agency jurisdiction

In 2023, the FBI reported that there were 9,284 Black murder victims in the United States and 7,289 white murder victims. In comparison, there were 554 murder victims of unknown race and 586 victims of another race. Victims of inequality? In recent years, the role of racial inequality in violent crimes such as robberies, assaults, and homicides has gained public attention. In particular, the issue of police brutality has led to increasing attention following the murder of George Floyd, an African American who was killed by a Minneapolis police officer. Studies show that the rate of fatal police shootings for Black Americans was more than double the rate reported of other races. Crime reporting National crime data in the United States is based off the Federal Bureau of Investigation’s new crime reporting system, which requires law enforcement agencies to self-report their data in detail. Due to the recent implementation of this system, less crime data has been reported, with some states such as Delaware and Pennsylvania declining to report any data to the FBI at all in the last few years, suggesting that the Bureau's data may not fully reflect accurate information on crime in the United States.

The Motor Vehicle Collisions crash table contains details on the crash event. Each row represents a crash event. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. The police report (MV104-AN) is required to be filled out for collisions where someone is injured or killed, or where there is at least $1000 worth of damage (https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/documents/ny_overlay_mv-104an_rev05_2004.pdf). It should be noted that the data is preliminary and subject to change when the MV-104AN forms are amended based on revised crash details.For the most accurate, up to date statistics on traffic fatalities, please refer to the NYPD Motor Vehicle Collisions page (updated weekly) or Vision Zero View (updated monthly).

Due to success of the CompStat program, NYPD began to ask how to apply the CompStat principles to other problems. Other than homicides, the fatal incidents with which police have the most contact with the public are fatal traffic collisions. Therefore in April 1998, the Department implemented TrafficStat, which uses the CompStat model to work towards improving traffic safety. Police officers complete form MV-104AN for all vehicle collisions. The MV-104AN is a New York State form that has all of the details of a traffic collision. Before implementing Trafficstat, there was no uniform traffic safety data collection procedure for all of the NYPD precincts. Therefore, the Police Department implemented the Traffic Accident Management System (TAMS) in July 1999 in order to collect traffic data in a uniform method across the City. TAMS required the precincts manually enter a few selected MV-104AN fields to collect very basic intersection traffic crash statistics which included the number of accidents, injuries and fatalities. As the years progressed, there grew a need for additional traffic data so that more detailed analyses could be conducted. The Citywide traffic safety initiative, Vision Zero started in the year 2014. Vision Zero further emphasized the need for the collection of more traffic data in order to work towards the Vision Zero goal, which is to eliminate traffic fatalities. Therefore, the Department in March 2016 replaced the TAMS with the new Finest Online Records Management System (FORMS). FORMS enables the police officers to electronically, using a Department cellphone or computer, enter all of the MV-104AN data fields and stores all of the MV-104AN data fields in the Department’s crime data warehouse. Since all of the MV-104AN data fields are now stored for each traffic collision, detailed traffic safety analyses can be conducted as applicable.

For a comprehensive guide to this data and other UCR data, please see my book at ucrbook.comVersion 12 release notes:Adds 2021 data.Version 11 release notes:Adds 2020 data. Please note that the FBI has retired UCR data ending in 2020 data so this will (probably, I haven't seen confirmation either way) be the last LEOKA data they release. Changes .rda file to .rds.Version 10 release notes:Changes release notes description, does not change data.Version 9 release notes:Adds data for 2019.Version 8 release notes:Fix bug for years 1960-1971 where the number of months reported variable was incorrectly down by 1 month. I recommend caution when using these years as they only report either 0 or 12 months of the year, which differs from every other year in the data. Added the variable officers_killed_total which is the sum of officers_killed_by_felony and officers_killed_by_accident.Version 7 release notes:Adds data from 2018Version 6 release notes:Adds data in the following formats: SPSS and Excel.Changes project name to avoid confusing this data for the ones done by NACJD.Version 5 release notes: Adds data for 1960-1974 and 2017. Note: many columns (including number of female officers) will always have a value of 0 for years prior to 1971. This is because those variables weren't collected prior to 1971. These should be NA, not 0 but I'm keeping it as 0 to be consistent with the raw data. Removes support for .csv and .sav files.Adds a number_of_months_reported variable for each agency-year. A month is considered reported if the month_indicator column for that month has a value of "normal update" or "reported, not data."The formatting of the monthly data has changed from wide to long. This means that each agency-month has a single row. The old data had each agency being a single row with each month-category (e.g. jan_officers_killed_by_felony) being a column. Now there will just be a single column for each category (e.g. officers_killed_by_felony) and the month can be identified in the month column. This also results in most column names changing. As such, be careful when aggregating the monthly data since some variables are the same every month (e.g. number of officers employed is measured annually) so aggregating will be 12 times as high as the real value for those variables. Adds a date column. This date column is always set to the first of the month. It is NOT the date that a crime occurred or was reported. It is only there to make it easier to create time-series graphs that require a date input.All the data in this version was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. Data is the same as from NACJD but using all FBI files makes cleaning easier as all column names are already identical. Version 4 release notes: Add data for 2016.Order rows by year (descending) and ORI.Version 3 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The LEOKA data sets contain highly detailed data about the number of officers/civilians employed by an agency and how many officers were killed or assaulted. All the data was acquired from the FBI as text/DAT files and read into R using the package asciiSetupReader. The FBI also provided a PDF file explaining how to create the setup file to read the data. Both the FBI's PDF and the setup file I made are included in the zip files. About 7% of all agencies in the data report more officers or civilians than population. As such, I removed the officers/civilians per 1,000 population variables. You should exercise caution if deciding to generate and use these variables yourself. Several agency had impossible large (>15) officer deaths in a single month. For those months I changed the value to NA. The UCR Handbook (https://ucr.fbi.gov/additional-ucr-publications/ucr_handbook.pdf/view) describes the LEOKA data as follows:"The UCR Program collects data from all contributing agencies ... on officer line-of-duty deaths and assaults. Reporting agencies must submit data on ... their own duly sworn officers feloniously or accidentally killed or assaulted in the line of duty. The purpose of this data collection is to identify situations in which

Find violent death data in Massachusetts, inluding homicide and suicide.

Content

• Cases of deaths by police action per race, age, state and other variables.
• This data are from DATASUS, the public health system of Brazil

Acknowledgements

part of the cleaning of the data was done with microdatasus package: SALDANHA, Raphael de Freitas. Pacote para o R 'microdatasus', 2018. Disponível em https://github.com/rfsaldanha

The most recent report of the Italian Ministry of the Interior reveals that between January and July 2025, 184 homicides were committed in Italy. The number of homicides has recorded a decreasing trend since 2011. Overall, about 2.3 million criminal acts were reported in Italy in 2023. Femicide Femicide, a homicide in which a woman is killed for gender-based reasons, poses a serious problem around the world. In 2018, roughly one in six Italians believed that femicide was on the rise. Women, victims of homicide, are often related to the culprit; in 2022, 74 women in Italy were killed by their partner. Crime in Italy In 2023, the most common crime in Italy was theft. Law enforcement corps reported one million cases of this delinquency to the juridical authority, with the highest theft rate in the metropolitan city of Milan.