Police fatalities from 2000 to 2016

This dataset aims to provide insight into individuals who were killed during altercations with police. It includes information on their age, race, mental health status, weapons they were armed with, and if they were fleeing.

Content

some of the features are in the original data and the others were added in this updated version. 1. UID, Unique ID of the murdered, In the original data 2. Name, The name of the murdered, In the original data 3. Age, The age of the murdered, In the original data 4. Stages of Life, The age stage of the murdered, Added in this updated version 5. Gender, The Gender of the murdered, In the original data 6. Race, The Race of the murdered, In the original data 7. Date, The date of death, In the original data 8. Year, The year in which the death occurred, Added in this updated version 9. Quarter, The Quarter in which the death occurred, Added in this updated version 10. Month, The month in which the death occurred, Added in this updated version 11. Week, The week in which the death occurred, Added in this updated version 12. Day, The day in which the death occurred, Added in this updated version 13. City, The City in which the death occurred, In the original data 14. State, The State in which the death occurred, In the original data 15. Region, The Region in which the death occurred, Added in this updated version 16. Manner of death In what way was the victim killed?, In the original data 17. Armed, Did the victim have a weapon?, In the original data 18. Mental illness, Was the victim mentally ill?, In the original data 19. Flee, Did the victim try to escape?, In the original data

Acknowledgements

This dataset comes from https://data.world/awram/us-police-involved-fatalities.

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

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

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

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

Refresh Frequency: This data is updated daily.

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

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

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

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

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

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.

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

Chicago Police district station locations and contact information.

Context:

On a typical day in the United States, police officers make more than 50,000 traffic stops. The Stanford Open Policing Project team is gathering, analyzing, and releasing records from millions of traffic stops by law enforcement agencies across the country. Their goal is to help researchers, journalists, and policymakers investigate and improve interactions between police and the public.

If you'd like to see data regarding other states, please go to https://www.kaggle.com/stanford-open-policing.

Content:

This dataset includes over 1 gb of stop data from Ohio. Please see the data readme for the full details of the available fields.

Acknowledgements:

This dataset was kindly made available by the Stanford Open Policing Project. If you use it for a research publication, please cite their working paper: E. Pierson, C. Simoiu, J. Overgoor, S. Corbett-Davies, V. Ramachandran, C. Phillips, S. Goel. (2017) “A large-scale analysis of racial disparities in police stops across the United States”.

Inspiration:

• How predictable are the stop rates? Are there times and places that reliably generate stops?
• Concerns have been raised about jurisdictions using civil forfeiture as a funding mechanism rather than to properly fight drug trafficking. Can you identify any jurisdictions that may be exhibiting this behavior?

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 includes all criminal offenses reported to the Colorado Springs Police Department. Each case report (incident) may have several offenses. Each offense may have multiple suspects and/or victims.

Important: This dataset provided by CSPD does not apply the same counting rules as official data reported to the Colorado Bureau of Investigations and the Federal Bureau of Investigation. This means comparisons to those datasets would be inaccurate.

This dataset contains Crime and Safety data from the Cary Police Department.

This data is extracted by the Town of Cary's Police Department's RMS application. The police incidents will provide data on the Part I crimes of arson, motor vehicle thefts, larcenies, burglaries, aggravated assaults, robberies and homicides. Sexual assaults and crimes involving juveniles will not appear to help protect the identities of victims.

This dataset includes criminal offenses in the Town of Cary for the previous 10 calendar years plus the current year. The data is based on the National Incident Based Reporting System (NIBRS) which includes all victims of person crimes and all crimes within an incident. The data is dynamic, which allows for additions, deletions and/or modifications at any time, resulting in more accurate information in the database. Due to continuous data entry, the number of records in subsequent extractions are subject to change. Crime data is updated daily however, incidents may be up to three days old before they first appear.

About Crime Data

The Cary Police Department strives to make crime data as accurate as possible, but there is no avoiding the introduction of errors into this process, which relies on data furnished by many people and that cannot always be verified. Data on this site are updated daily, adding new incidents and updating existing data with information gathered through the investigative process.

This dynamic nature of crime data means that content provided here today will probably differ from content provided a week from now. Additional, content provided on this site may differ somewhat from crime statistics published elsewhere by other media outlets, even though they draw from the same database.

Withheld Data

In accordance with legal restrictions against identifying sexual assault and child abuse victims and juvenile perpetrators, victims, and witnesses of certain crimes, this site includes the following precautionary measures: (a) Addresses of sexual assaults are not included. (b) Child abuse cases, and other crimes which by their nature involve juveniles, or which the reports indicate involve juveniles as victims, suspects, or witnesses, are not reported at all.

Certain crimes that are under current investigation may be omitted from the results in avoid comprising the investigative process.

Incidents five days old or newer may not be included until the internal audit process has been completed.

This data is updated daily.

DATASET DESCRIPTION: This Dataset includes the average response time by Call Priority across days of the week and hours of the day. Response Times reflect the same information contained in the APD 911 Calls for Service 2019-2024 dataset.

AUSTIN POLICE DEPARTMENT DATA DISCLAIMER 1. The data provided is for informational use only and may differ from official Austin Police Department data.

1. The Austin Police Department’s databases are continuously updated, and changes can be made due to a variety of investigative factors including but not limited to offense reclassification and dates.

2. Reports run at different times may produce different results. Care should be taken when comparing against other reports as different data collection methods and different systems of record may have been used.

4.The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided.

City of Austin Open Data Terms of Use -https://data.austintexas.gov/stories/s/ranj-cccq

Overview:

This dataset contains detailed information on cases where a hate or bias crime has been reported to the Bloomington Police Department. Hate crimes are criminal offenses motivated by bias against race, religion, ethnicity, sexual orientation, gender identity, or other protected characteristics. This dataset provides insights into the nature and demographics of hate crimes in Bloomington, aiding in understanding and addressing these incidents.

Dataset Details:

The dataset includes the following columns:

Key Features:

• Comprehensive Crime Data: Provides detailed information on hate crimes, including demographics of victims and offenders, types of offenses, and bias motivations.
• Temporal Analysis: Includes timestamps for each incident, allowing for analysis of trends over time.
• Demographic Insights: Offers data on race and gender of both victims and offenders, helping to identify patterns and target interventions.
• Location Information: Contains details about the type of location where the offense occurred, useful for spatial analysis and preventive measures.

Usage:

This dataset can be used for:

• Crime Analysis: Analyzing trends and patterns in hate crimes to inform law enforcement strategies and policies.
• Community Safety: Identifying high-risk areas and times to improve community policing and preventive measures.
• Research and Advocacy: Supporting academic research and advocacy efforts focused on combating hate crimes and promoting social justice.
• Policy Development: Assisting policymakers in developing targeted initiatives to reduce hate crimes and support affected communities.

Data Maintenance:

• Last Updated: July 7, 2024
• Source: Bloomington Police Department Data Portal
• Revisions: The dataset is annually updated to ensure the inclusion of the latest incidents and to maintain data accuracy. Historical data is preserved to support long-term analyses.

Additional Notes

• Data Accuracy: The Bloomington Police Department strives for accuracy in open data; however, errors may occur due to the nature of data collection from multiple sources.
• Data Interpretation: Users should be aware that the dataset may change over time as new information becomes available or corrections are made.
• Race and District Codes: The dataset uses specific codes for race and reading districts, which are detailed in the accompanying documentation to ensure proper interpretation.
• License: Open Data Commons Public Domain Dedication and License

This study was undertaken to assess the connections between administratively controllable sources of fatigue among police patrol officers and problems such as diminished performance, accidents, and illness. The study sought to answer: (1) What is the prevalence of officer fatigue, and what are officers' attitudes toward it? (2) What are the causes or correlates of officer fatigue? (3) How does fatigue affect officer safety, health, and job performance? and (4) Can officer fatigue be measured objectively? The final sample was comprised of all sworn, nonsupervisory police officers assigned full-time to patrol and/or community policing functions on the day that data collection began at each of four selected sites: Lowell, Massachusetts, Polk County, Florida, Portland, Oregon, and Arlington County, Virginia. Part 1, Fatigue Survey Data, includes demographic data and officers' responses from the initial self-report survey. Variables include the extent to which the respondent felt hot or cold, experienced uncomfortable breathing, bad dreams, or pain while sleeping, the time the respondent usually went to bed, number of hours slept each night, quality of sleep, whether medicine was taken as a sleep aid, estimated hours worked in a one-, two-, seven-, and thirty-day period, how overtime affected income, family relationships, and social activities, and reasons for feeling tired. Part 2, Demographic and Fatigue Survey Data, is comprised of data obtained from administrative records and demographic data forms. Several measures from the initial self-report survey are also included in Part 2. Variables focus on respondents' age, sex, race, marital status, global score on the Pittsburgh Sleep Quality Index scale, total years as a police officer assigned to any agency and current agency, and total years worked in current shift. Data for Part 3, FIT and Administrative Data, were obtained from administrative records and from the fitness-for-duty (FIT) workplace screener test. Variables include a pupilometry index score and the dates, time, and particular shift (days, evenings, or midnight) the officer started working when the pupilometry test was administered. Part 3 also includes the number of hours worked by the officer in a regular shift or in association with overtime, the number of sick leave hours taken by the officer, and whether the officer was involved in an on-duty accident, injured on duty, or commended by his/her department during a particular shift.

Police recorded crime figures by Police Force Area and Community Safety Partnership areas (which equate in the majority of instances, to local authorities).

Each record in this dataset shows information about an arrest executed by the Chicago Police Department (CPD). Source data comes from the CPD Automated Arrest application. This electronic application is part of the CPD CLEAR (Citizen Law Enforcement Analysis and Reporting) system, and is used to process arrests Department-wide.

A more-detailed version of this dataset is available to media by request. To make a request, please email dataportal@cityofchicago.org with the subject line: Arrests Access Request. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup. New data fields may be added to this public dataset in the future. Requests for individual arrest reports or any other related data other than access to the more-detailed dataset should be directed to CPD, through contact information on that site or a Freedom of Information Act (FOIA) request.

The data is limited to adult arrests, defined as any arrest where the arrestee was 18 years of age or older on the date of arrest. The data excludes arrest records expunged by CPD pursuant to the Illinois Criminal Identification Act (20 ILCS 2630/5.2).

Department members use charges that appear in Illinois Compiled Statutes or Municipal Code of Chicago. Arrestees may be charged with multiple offenses from these sources. Each record in the dataset includes up to four charges, ordered by severity and with CHARGE1 as the most severe charge. Severity is defined based on charge class and charge type, criteria that are routinely used by Illinois court systems to determine penalties for conviction. In case of a tie, charges are presented in the order that the arresting officer listed the charges on the arrest report. By policy, Department members are provided general instructions to emphasize seriousness of the offense when ordering charges on an arrest report.

Each record has an additional set of columns where a charge characteristic (statute, description, type, or class) for all four charges, or fewer if there were not four charges, is concatenated with the | character. These columns can be used with the Filter function's "Contains" operator to find all records where a value appears, without having to search four separate columns.

Users interested in learning more about CPD arrest processes can review current directives, using the CPD Automated Directives system (http://directives.chicagopolice.org/directives/). Relevant directives include:

• Special Order S06-01-11 – CLEAR Automated Arrest System: describes the application used by Department members to enter arrest data. • Special Order S06-01-04 – Arrestee Identification Process: describes processes related to obtaining and using CB numbers. • Special Order S09-03-04 – Assignment and Processing of Records Division Numbers: describes processes related to obtaining and using RD numbers. • Special Order 06-01 – Processing Persons Under Department Control: describes required tasks associated with arrestee processing, include the requirement that Department members order charges based on severity.

Context

Approximately 10 people are shot on an average day in Chicago.

http://www.chicagotribune.com/news/data/ct-shooting-victims-map-charts-htmlstory.html http://www.chicagotribune.com/news/local/breaking/ct-chicago-homicides-data-tracker-htmlstory.html http://www.chicagotribune.com/news/local/breaking/ct-homicide-victims-2017-htmlstory.html

Content

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. This data includes unverified reports supplied to the Police Department. 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.

Update Frequency: Daily

Fork this kernel to get started.

Acknowledgements

https://bigquery.cloud.google.com/dataset/bigquery-public-data:chicago_crime

https://cloud.google.com/bigquery/public-data/chicago-crime-data

Dataset Source: City of Chicago

This dataset is publicly available for anyone to use under the following terms provided by the Dataset Source —https://data.cityofchicago.org — and is provided "AS IS" without any warranty, express or implied, from Google. Google disclaims all liability for any damages, direct or indirect, resulting from the use of the dataset.

Banner Photo by Ferdinand Stohr from Unplash.

Inspiration

What categories of crime exhibited the greatest year-over-year increase between 2015 and 2016?

Which month generally has the greatest number of motor vehicle thefts?

How does temperature affect the incident rate of violent crime (assault or battery)?

https://cloud.google.com/bigquery/images/chicago-scatter.png" alt=""> https://cloud.google.com/bigquery/images/chicago-scatter.png

This dataset contains incident reports recorded by the Norfolk Police Department that occurred over the last five years. Incidents can be searched by type, location, date and time of occurrence. This dataset is updated daily.

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 312.745.6071 or RandD@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 is updated daily Tuesday through Sunday. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. 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

Please note that you cannot see the date fields on this page due to a technical issue. To see the Report Date and Date Closed, please access the via ArcGIS Online, or download the dataset from this page.

This dataset reflects all citizen complaints received by the Detroit Police Department (DPD) and the Board of Police Commissioners from January 1, 2012 to the present. There is a 28-day delay between when a new complaint is filed and when it is posted to the Open Data Portal. The data are provided by the Office of the Chief Investigator (OCI), under the direction of the Board of Police Commissioners (BOPC). The OCI receives, investigates, and resolves complaints regarding non-criminal allegations of misconduct against the DPD and its personnel. Each case is allotted 90 days to complete an investigation. If OCI finds that a complaint is criminal in nature, it is transferred to DPD for further investigated.

This dataset contains information about the nature of individual complaints, demographics for both the citizen filing the complaint and the officer against which the complaint is filed, and the resulting finding from the OCI investigation. In order to protect the privacy of both the officer and the citizen filing the complaint, no personally identifiable information is displayed. Each row in the dataset represents an allegation. A single complaint may have one or more allegations and is therefore represented by one or more rows. Allegations associated with the same complaint share same BPC Case Numbers and Citizen Complaint Report Numbers.

Allegation Type Definitions:

Arrest - Complaint associated with an improper or unjustified restraint of a person's liberty. Includes formal arrests and other types of detention.

Demeanor - The bearing, gesture, language, or other action of a DPD staff member alleged to be offensive, of doubtful social propriety, or giving the appearance of conflict of interest, misuse of influence, or lack of jurisdiction or authority.

Entry - Entry into a building or onto property improper and/or excessive force used against property to gain entry.

Force - Use or threatened use of force against a person.

Harassment - When an officer misuses their authority to threaten, intimidate, or coerce a person based on a factor such as race, attire, sex, or age.

Procedure - Complaint regarding other actions in violation of DPD rules, regulations, procedures or policies, or the Law Enforcement Code of Ethics.

Property - Complaint of property lost or damaged while in police custody or confiscated through police action.

Search - Search of a person or a person's property was improper, violated established police procedure, or was unjustified.

Service - Complaint regarding the lack, tardiness or inadequacy of police service.

Findings Definitions:

Unfounded - The investigation revealed no evidence to support that the incident complained of actually occurred.

Sustained - A preponderance of the evidence shows that the alleged conduct did occur and the actions of the officer violated DPD policies, procedures, or training.

Exonerated - A preponderance of the evidence shows that the alleged conduct did occur but did not violate DPD policies, procedures or training.

Administrative Closure - Dispositions for complaints that: duplicates, referred to an outside agency, made against an officer or employee who is no longer employed by DPD, the alleged conduct does not violate the law or DPD policy, and lack sufficient detail of the officers involved or insufficient details within the complaint.

No Charge - When evidence concludes that the allegation did not meet the threshold to dispense disciplinary action.

Inconclusive - When there is insufficient evidence to decide whether the alleged misconduct occurred.

Void - When the investigation is halted due to but not limited to a retracted complaint, duplicate submission, or a submission in error.

Should you have questions about this dataset, you may contact the Office of the Chief Investigator at (313) 596-2499 or go to their website.

A visualization of DPD Citizen Complaints is available from the open data Analytics Hub.