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.

Please click here to view the Data Dictionary, a description of the fields in this table.The police arrest report generates from the police department (Record Management System (RMS)) and includes one rolling year of data. Information automatically updates Sunday night. The most recent data available will begin one week prior from the updated date to allow for report approvals, ensuring the most accurate information available. Incidents included may not directly correlate to information found in other data sets nor should this data be considered for official Uniform Crime Reporting. For all official crime statistics please refer to the FBI and Arizona Department of Public Safety.Some information has been excluded and addresses shortened to the hundred block to protect privacy of victims and juveniles.

This dataset documents Group B arrests for crimes reported by the City of Clarkston Police Department to NIBRS (National Incident-Based Reporting System).

The Metropolitan Police Department collects race and ethnicity data according to the United States Census Bureau standards (https://www.census.gov/topics/population/race/about.html). Hispanic, which was previously categorized under the Race field prior to August 2015, is now captured under Ethnicity. All records prior to August 2015 have been updated to “Unknown (Race), Hispanic (Ethnicity)”. Race, ethnicity and gender data are based on officer observation, which may or may not be accurate.MPD cannot release exact addresses to the general public unless proof of ownership or subpoena is submitted. The GeoX and GeoY values represent the block location (approximately 232 ft. radius) as of the date of the arrest and offense. Arrest and offense addresses that could not be geocoded are included as an “unknown” value.Arrestee age is calculated based on the number of days between the self-reported or verified date of birth (DOB) of the arrestee and the date of the arrest; DOB data may not be accurate if self-reported, and an arrestee may refuse to provide his or her date of birth. Due to the sensitive nature of juvenile data and to protect the arrestee’s confidentiality, any arrest records for defendants under the age of 18 or with missing age are excluded in this dataset.The Criminal Complaint Number (CCN) and arrest number have also been anonymized.This data may not match other arrest data requests that may have included all law enforcement agencies in the District or all arrest charges. Arrest totals are subject to change and may be different than MPD Annual Report totals or other publications due to inclusion of juvenile arrest summary, expungements, investigation updates, data quality audits, etc.

Under the current business process, every seizure (4th Amendment of the US Constitution) conducted under the evidentiary standard of Probable Cause (PC) is documented in the RMS (Mark43). In addition to physical arrests made by officers, the system is configured to capture warrants, and summons arrests (where the officer is affecting a PC seizure on the authority of someone else (the court) and administrative arrest types that document updates to the identity of the subject who was arrested and additional charges. In total, 12 types of arrest are captured in the source.

Note: This data set includes counts of arrest reports written which are distinct from physical, in-custody events. All counts herein reflect either total counts of arrest reports by the selected filter parameters, and/or the total number of reports written per subject.

This dataset shows crime statistics for the City of Clarkston, WA Police Department.

DATASET DESCRIPTION: When an officer finds it necessary to arrest an individual, such as upon witnessing a crime, having probable cause, or acting on a judge-issued arrest warrant, they are required to write an arrest report. The arrest report details the conditions of the arrest and directly pertains to the individual in question. Additionally, it includes specific details of the charges associated with the arrest. GENERAL ORDERS RELATED TO ARRESTS Austin Police Department General Order 319 states, "This order outlines the guidelines for warrant and warrantless arrests. The following order cannot address every situation that an officer might encounter; however, in exercising arrest authority, officers should be guided by what is contained in this document. Nothing in this order should be interpreted as authorizing or restricting an officer's arrest authority as defined by the Code of Criminal Procedure." AUSTIN POLICE DEPARTMENT DATA DISCLAIMER 1. The data provided is for informational use only and may differ from official Austin Police Department data. 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. 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

This dataset represents arrests made by the Baltimore Police Department. Data are updated weekly. To leave feedback or ask a question about this dataset, please fill out the following form: BPD Arrests feedback form.

This dataset represents all arrests that occurred in the last 24 hours as recorded by the Norfolk Police Department. This dataset is updated daily.

This dataset provides the public with arrest information from the Montgomery County Central Processing Unit (CPU) systems. The data presented is derived from every booking; criminal, civil and motor vehicle entered through CPU. The data is compiled by “CRIMS”, a respected jail records-management system used by the Montgomery County Corrections and many other law enforcement agencies. To protect arrestee’s privacy, personal information is redacted. Residential addresses are rounded to the nearest hundred block. All data is refreshed on 2 hour basis to reflect any additions or changes. -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law - Records will be removed after 30 days. Update Frequency - every 2 hours

This dataset reflects arrest incidents in the City of Los Angeles from 2010 to 2019. This data is transcribed from original arrest reports that are typed on paper and therefore there may be some inaccuracies within the data. Some location fields with missing data are noted as (0.0000°, 0.0000°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.

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.

This data ceased updating with the transition to a new records management system on 11/14/2023. Access to the updated data set has been added as of April 11, 2025 here: Crime Data Guide.

This dataset has been published by the Virginia Beach Police Department and data.virginiabeach.gov. The mission of data.virginiabeach.gov is to provide timely and accurate City information to increase government transparency and access to useful and well organized data by the general public, non-governmental organizations, and City of Virginia Beach employees.This dataset excludes incidents assigned to 14 of the 152 Incident Based Reporting Codes. The specific IBR codes excluded are outlined below: 1. Runaway2. Death Investigation3. Death, Accidental4. Death, Drowning5. Death, Suicide6. Death, Auto Fatality7. Attempted Suicide8. Officer Involved Shooting, Death9. Officer Involved Shooting, No Death10. Missing Person11. Lost Property12. Habitual Offender13. Other Non-Reportable Offenses14. SVU Information Only

***Starting on March 7th, 2024, the Los Angeles Police Department (LAPD) will adopt a new Records Management System for reporting crimes and arrests. This new system is being implemented to comply with the FBI's mandate to collect NIBRS-only data (NIBRS — FBI - https://www.fbi.gov/how-we-can-help-you/more-fbi-services-and-information/ucr/nibrs). During this transition, users will temporarily see only incidents reported in the retiring system. However, the LAPD is actively working on generating new NIBRS datasets to ensure a smoother and more efficient reporting system. *** This dataset reflects arrest incidents in the City of Los Angeles from 2020 to present. This data is transcribed from original arrest reports that are typed on paper and therefore there may be some inaccuracies within the data. Some _location fields with missing data are noted as (0.0000°, 0.0000°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.

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

Dataset highlighting arrests by Albany PD Officers for the past year to date GeoCoded by Patrol Zone. It is the same data as Arrests by Neighborhood

For purposes of crime statistics, the FBI Uniform Crime Report Hierarchy Rule requires when more than one offense occurs in an incident the highest priority crime is selected as the primary offense.

This dataset reflects arrests in the City of Gainesville since 2011. Arrest data is provided by the Gainesville Police Department (GPD) and derived from Police reports.

Disclaimer: Crime Responses is provided by the Gainesville Police Department (GPD) to document initial details surrounding an incident to which GPD officers respond. This dataset contains crime incidents from 2011 to present and includes a reduced set of fields focused on capturing the type of incident as well when and where an incident occurred. The Incident location addresses have been rounded off and are not the exact location due to the constitutional amendment known as "Marsy's Law".

In 2021, Florida reporting of crime data began a transition from Summary Reporting System (SRS) to National Incident-Based Reporting System (NIBRS), causing an effect on crime statistics reported by Law Enforcement Agencies such as the Gainesville Police Department who made this transition on November 16, 2021. The effect would be an increase in crime due to the elimination of the SRS Hierarchy Rule which collected only the most serious offense in an incident while NIBRS will now capture up to 10 offenses per incident and specifies more offense categories than SRS. The inclusion of these crimes, particularly property crimes, will reflect an increase in crime when switching from SRS reporting to NIBRS' reporting. The apparent increase (usually not greater than 2.7%) is simply due to the difference between how crimes are counted in NIBRS versus the SRS and its application of the Hierarchy Rule. More information regarding NIBRS effect on crime statistics can be found on the following link: https://ucr.fbi.gov/nibrs/2014/resource-pages/effects_of_nibrs_on_crime_statistics_final.pdf.

This publication can be accessed here