Number and percentage of homicide victims, by type of firearm used to commit the homicide (total firearms; handgun; rifle or shotgun; fully automatic firearm; sawed-off rifle or shotgun; firearm-like weapons; other firearms, type unknown), Canada, 1974 to 2018.

THIS DATASET WAS LAST UPDATED AT 2:11 AM EASTERN ON JULY 12

OVERVIEW

2019 had the most mass killings since at least the 1970s, according to the Associated Press/USA TODAY/Northeastern University Mass Killings Database.

In all, there were 45 mass killings, defined as when four or more people are killed excluding the perpetrator. Of those, 33 were mass shootings . This summer was especially violent, with three high-profile public mass shootings occurring in the span of just four weeks, leaving 38 killed and 66 injured.

A total of 229 people died in mass killings in 2019.

The AP's analysis found that more than 50% of the incidents were family annihilations, which is similar to prior years. Although they are far less common, the 9 public mass shootings during the year were the most deadly type of mass murder, resulting in 73 people's deaths, not including the assailants.

One-third of the offenders died at the scene of the killing or soon after, half from suicides.

About this Dataset

The Associated Press/USA TODAY/Northeastern University Mass Killings database tracks all U.S. homicides since 2006 involving four or more people killed (not including the offender) over a short period of time (24 hours) regardless of weapon, location, victim-offender relationship or motive. The database includes information on these and other characteristics concerning the incidents, offenders, and victims.

The AP/USA TODAY/Northeastern database represents the most complete tracking of mass murders by the above definition currently available. Other efforts, such as the Gun Violence Archive or Everytown for Gun Safety may include events that do not meet our criteria, but a review of these sites and others indicates that this database contains every event that matches the definition, including some not tracked by other organizations.

This data will be updated periodically and can be used as an ongoing resource to help cover these events.

Using this Dataset

To get basic counts of incidents of mass killings and mass shootings by year nationwide, use these queries:

Mass killings by year

Mass shootings by year

To get these counts just for your state:

Filter killings by state

Definition of "mass murder"

Mass murder is defined as the intentional killing of four or more victims by any means within a 24-hour period, excluding the deaths of unborn children and the offender(s). The standard of four or more dead was initially set by the FBI.

This definition does not exclude cases based on method (e.g., shootings only), type or motivation (e.g., public only), victim-offender relationship (e.g., strangers only), or number of locations (e.g., one). The time frame of 24 hours was chosen to eliminate conflation with spree killers, who kill multiple victims in quick succession in different locations or incidents, and to satisfy the traditional requirement of occurring in a “single incident.”

Offenders who commit mass murder during a spree (before or after committing additional homicides) are included in the database, and all victims within seven days of the mass murder are included in the victim count. Negligent homicides related to driving under the influence or accidental fires are excluded due to the lack of offender intent. Only incidents occurring within the 50 states and Washington D.C. are considered.

Methodology

Project researchers first identified potential incidents using the Federal Bureau of Investigation’s Supplementary Homicide Reports (SHR). Homicide incidents in the SHR were flagged as potential mass murder cases if four or more victims were reported on the same record, and the type of death was murder or non-negligent manslaughter.

Cases were subsequently verified utilizing media accounts, court documents, academic journal articles, books, and local law enforcement records obtained through Freedom of Information Act (FOIA) requests. Each data point was corroborated by multiple sources, which were compiled into a single document to assess the quality of information.

In case(s) of contradiction among sources, official law enforcement or court records were used, when available, followed by the most recent media or academic source.

Case information was subsequently compared with every other known mass murder database to ensure reliability and validity. Incidents listed in the SHR that could not be independently verified were excluded from the database.

Project researchers also conducted extensive searches for incidents not reported in the SHR during the time period, utilizing internet search engines, Lexis-Nexis, and Newspapers.com. Search terms include: [number] dead, [number] killed, [number] slain, [number] murdered, [number] homicide, mass murder, mass shooting, massacre, rampage, family killing, familicide, and arson murder. Offender, victim, and location names were also directly searched when available.

This project started at USA TODAY in 2012.

Contacts

Contact AP Data Editor Justin Myers with questions, suggestions or comments about this dataset at jmyers@ap.org. The Northeastern University researcher working with AP and USA TODAY is Professor James Alan Fox, who can be reached at j.fox@northeastern.edu or 617-416-4400.

Context

The Gun Violence Archive is an online archive of gun violence incidents collected from over 2,000 media, law enforcement, government and commercial sources daily in an effort to provide near-real time data about the results of gun violence. GVA in an independent data collection and research group with no affiliation with any advocacy organization.

Content

This dataset includes files that separate gun violence incidents by category, including deaths and injuries of children and teens, and a collection of mass shootings.

Inspiration

• What has been the trend of gun violence in the past few years?
• What states have the highest incidents per capita per year? How has this metric changed over time?
• Are officer involved shootings on the rise? Where are they most concentrated? Do they correlate with the rates of accidental deaths and mass shootings?

Acknowledgements

This dataset is owned by the Gun Violence Archive, and can be accessed in its original form here.

Number of homicide victims, by method used to commit the homicide (total methods used; shooting; stabbing; beating; strangulation; fire (burns or suffocation); other methods used; methods used unknown), Canada, 1974 to 2023.

The data on mass shootings is from https://www.gunviolencearchive.org/ . This dataset on mass shootings for the period 2014-2023 was provided on Feb 19, 2024 by the Data Manager (Ms. Sharon Williams) at the Gun Violence Archive (https://www.gunviolencearchive.org/) on a data request. Minimal curation was done on this data – the date variable was split into year, month and day. See the codebook for full details.A mass shooting is defined as four or more people injured or killed, because of firearms, excluding the shooter.The curated datasets are included here along with a research question and guiding questions.For information of how this data is collected, go to: https://www.gunviolencearchive.org/explainerDefinition for mass shooting and mass murder from the above website is given verbatim below:Mass Shooting Methodology and Reasoning: Mass Shootings are, for the most part an American phenomenon. While they are generally grouped together as one type of incident they are several different types including public shootings, bar/club incidents, family annihilations, drive-by, workplace and those which defy description but with the established foundation definition being that they have a minimum of four victims shot, either injured or killed, not including any shooter who may also have been killed or injured in the incident. GVA also presents the count of Mass Murder which, like the FBI's definition is four or more victims, killed, not including the shooter. Mass Murder by gun is a subset of the Mass Shooting count.

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.

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

This dataset consists of gun violence within Jefferson county that may fall within LMPDs radar, including non-fatal shootings, homicides, as well as shot-spotter data. The mapping data points where there are victims have been obfuscated to maintain privacy, while still being accurate enough to be placed in its correct boundaries, particularly around, neighborhoods, ZIP Codes, Council districts, and police divisions. The data also excludes any victim information that could be used to identify any individual. this data is used to make the public aware of what is going on in their communities. The data consists of only criminal incidents, excluding any cases that are deemed non-criminal.Field NameField DescriptionCase numberPolice report number. For ShotSpotter detections, it is the ShotSpotter ID.DateTimeDate and time in which the original incident occurred. Time is rounded down.AddressAddress rounded down to the one hundred block of where the initial incident occured. Unless it is an intersection.NeighborhoodNeighborhood in which the original incident occurred.Council DistrictCouncil district in which the original incident occurred.LatitudeLatitude coordinate used to map the incidentLongitudeLongitude coordinate used to map the incidentZIP CodeZIP Code in which the original incident occurred.Crime Typea distinction between incidents, whether it is a non-fatal shooting, homicide, or a ShotSpotter detection.CauseUsed to differentiate on the cause of death for homicide victims.SexGender of the victim of the initial incident.RaceRace/Ethnicity of the victim in a given incident.Age GroupCategorized age groups used to anonymize victim information.Division NamePolice division or department where the initial incident occurred.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities, unless LMPD becomes involved in smaller agency incident.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Contact:Ivan Benitez, Ph.D.Gun Violence Data FellowOffice for Safe and Healthy Neighborhoodsivan.benitez@louisvilleky.gov

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.

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

• Understanding US Police Shootings by Curtis Thompson
• Dataset Questions and Suggestions
• More datasets

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.

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.

Victims of gang-related homicides (total number of homicide victims; number of homicide victims - unknown gang-relation; number of homicide victims - known gang relation; number of gang-related homicide victims; percentage of gang-related homicide victims; rate (per 100,000 population) of gang-related homicide victims), Canada and regions, 1999 to 2023.

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.

Data tables relating to offences involving weapons as recorded by police and hospital episode statistics.

This study examined spatial and temporal features of crime guns in Pittsburgh, Pennsylvania, in order to ascertain how gun availability affected criminal behavior among youth, whether the effects differed between young adults and juveniles, and whether that relationship changed over time. Rather than investigating the general prevalence of guns, this study focused only on those firearms used in the commission of crimes. Crime guns were defined specifically as those used in murders, assaults, robberies, weapons offenses, and drug offenses. The emphasis of the project was on the attributes of crime guns and those who possess them, the geographic sources of those guns, the distribution of crime guns over neighborhoods in a city, and the relationship between the prevalence of crime guns and the incidence of homicide. Data for Part 1, Traced Guns Data, came from the City of Pittsburgh Bureau of Police. Gun trace data provided a detailed view of crime guns recovered by police during a two-year period, from 1995 to 1997. These data identified the original source of each crime gun (first sale to a non-FFL, i.e., a person not holding a Federal Firearms License) as well as attributes of the gun and the person possessing the gun at the time of the precipitating crime, and the ZIP-code location where the gun was recovered. For Part 2, Crime Laboratory Data, data were gathered from the local county crime laboratory on guns submitted by Pittsburgh police for forensic testing. These data were from 1993 to 1998 and provided a longer time series for examining changes in crime guns over time than the data in Part 1. In Parts 3 and 4, Stolen Guns by ZIP-Code Data and Stolen Guns by Census Tract Data, data on stolen guns came from the local police. These data included the attributes of the guns and residential neighborhoods of owners. Part 3 contains data from 1987 to 1996 organized by ZIP code, whereas Part 4 contains data from 1993 to 1996 organized by census tract. Part 5, Shots Fired Data, contains the final indicator of crime gun prevalence for this study, which was 911 calls of incidents involving shots fired. These data provided vital information on both the geographic location and timing of these incidents. Shots-fired incidents not only captured varying levels of access to crime guns, but also variations in the willingness to actually use crime guns in a criminal manner. Part 6, Homicide Data, contains homicide data for the city of Pittsburgh from 1990 to 1995. These data were used to examine the relationship between varying levels of crime gun prevalence and levels of homicide, especially youth homicide, in the same city. Part 7, Pilot Mapping Application, is a pilot application illustrating the potential uses of mapping tools in police investigations of crime guns traced back to original point of sale. NTC. It consists of two ArcView 3.1 project files and 90 supporting data and mapping files. Variables in Part 1 include date of manufacture and sale of the crime gun, weapon type, gun model, caliber, firing mechanism, dealer location (ZIP code and state), recovery date and location (ZIP code and state), age and state of residence of purchaser and possessor, and possessor role. Part 2 also contains gun type and model, as well as gun make, precipitating offense, police zone submitting the gun, and year the gun was submitted to the crime lab. Variables in Parts 3 and 4 include month and year the gun was stolen, gun type, make, and caliber, and owner residence. Residence locations are limited to owner ZIP code in Part 3, and 1990 Census tract number and neighborhood name in Part 4. Part 5 contains the date, time, census tract and police zone of 911 calls relating to shots fired. Part 6 contains the date and census tract of the homicide incident, drug involvement, gang involvement, weapon, and victim and offender ages. Data in Part 7 include state, county, and ZIP code of traced guns, population figures, and counts of crime guns recovered at various geographic locations (states, counties, and ZIP codes) where the traced guns first originated in sales by an FFL to a non-FFL individual. Data for individual guns are not provided in Part 7.

This study was undertaken to obtain information on the characteristics of gun ownership, gun-carrying practices, and weapons-related incidents in the United States -- specifically, gun use and other weapons used in self-defense against humans and animals. Data were gathered using a national random-digit-dial telephone survey. The respondents were comprised of 1,905 randomly-selected adults aged 18 and older living in the 50 United States. All interviews were completed between May 28 and July 2, 1996. The sample was designed to be a representative sample of households, not of individuals, so researchers did not interview more than one adult from each household. To start the interview, six qualifying questions were asked, dealing with (1) gun ownership, (2) gun-carrying practices, (3) gun display against the respondent, (4) gun use in self-defense against animals, (5) gun use in self-defense against people, and (6) other weapons used in self-defense. A "yes" response to a qualifying question led to a series of additional questions on the same topic as the qualifying question. Part 1, Survey Data, contains the coded data obtained during the interviews, and Part 2, Open-Ended-Verbatim Responses, consists of the answers to open-ended questions provided by the respondents. Information collected for Part 1 covers how many firearms were owned by household members, types of firearms owned (handguns, revolvers, pistols, fully automatic weapons, and assault weapons), whether the respondent personally owned a gun, reasons for owning a gun, type of gun carried, whether the gun was ever kept loaded, kept concealed, used for personal protection, or used for work, and whether the respondent had a permit to carry the gun. Additional questions focused on incidents in which a gun was displayed in a hostile manner against the respondent, including the number of times such an incident took place, the location of the event in which the gun was displayed against the respondent, whether the police were contacted, whether the individual displaying the gun was known to the respondent, whether the incident was a burglary, robbery, or other planned assault, and the number of shots fired during the incident. Variables concerning gun use by the respondent in self-defense against an animal include the number of times the respondent used a gun in this manner and whether the respondent was hunting at the time of the incident. Other variables in Part 1 deal with gun use in self-defense against people, such as the location of the event, if the other individual knew the respondent had a gun, the type of gun used, any injuries to the respondent or to the individual that required medical attention or hospitalization, whether the incident was reported to the police, whether there were any arrests, whether other weapons were used in self-defense, the type of other weapon used, location of the incident in which the other weapon was used, and whether the respondent was working as a police officer or security guard or was in the military at the time of the event. Demographic variables in Part 1 include the gender, race, age, household income, and type of community (city, suburb, or rural) in which the respondent lived. Open-ended questions asked during the interview comprise the variables in Part 2. Responses include descriptions of where the respondent was when he or she displayed a gun (in self-defense or otherwise), specific reasons why the respondent displayed a gun, how the other individual reacted when the respondent displayed the gun, how the individual knew the respondent had a gun, whether the police were contacted for specific self-defense events, and if not, why not.

Number, rate and percentage changes in rates of homicide victims, Canada, provinces and territories, 1961 to 2023.

Information from Bloomington Police Department regarding guns reported stolen. 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.

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

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.