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.

• Total Male Juvenile
• Total Female Juvenile
• Total Male Adult
• Total Female Adult
• Total Ma

This dataset provides information on the number of re-arrests by county and race. Below are a few items to note about the dataset: Re-arrest rates are given for a cohort of releases within a given year. The re-arrest rate is calculated based upon the number of individuals released that had an arrest within a year of their release date. County is based upon county of commitment. Parole violations (& possibly probation violations) are not captured in Indiana State Police (ISP) arrest data and will therefore be underrepresented in the data. Arrest data comes from the Criminal History Repository System (CHRIS). Data feeding into the CHRIS system comes from three main sources. Arrest data comes from the LiveScan system, which is used for fingerprinting and capturing other pertinent information at the time of the arrest. Criminal disposition data are maintained by prosecutors in ProsLink system, and by the courts in the Odyssey system. Arrest data are sent to ISP soon after the arrest occurs, but disposition data have a lag of approximately seven months as the case makes its way through the legal system. Text description of the original offenses are provided by the arresting officer when the offender is arrested. Later, the prosecutor's office or court provides a text description of the filed offenses, along with the Indiana Code title, article, chapter, and section (e.g.35-48-4-6). The filed offense may be amended later. The data refers to the "most recent" offenses (arrest or dispositioned). The date range for the data is 2013 to 2020. The data provides a one-year post-release analysis on the charges of recently released individuals.

This project provided the first large-scale examination of the police response to intimate partner violence and of the practice known as "dual arrest." The objectives of the project were: (1) to describe the prevalence and context of dual arrest in the United States, (2) to explain the variance in dual arrest rates throughout the United States, (3) to describe dual arrest within the full range of the police response to intimate partner violence, (4) to analyze the factors associated with no arrest, single arrest, and dual arrest, (5) to examine the reasons why women are arrested in intimate partner cases, and (6) to describe how the criminal justice system treats women who have been arrested for domestic violence. Data for the project were collected in two phases. In Phase I, researchers examined all assault and intimidation cases in the year 2000 National Incident-Based Reporting System (NIBRS) database (NATIONAL INCIDENT-BASED REPORTING SYSTEM, 2000 [ICPSR 3449]) to investigate the extent to which dual arrest is occurring nationwide, the relationship between incident and offender characteristics, and the effect of state laws on police handling of these cases for all relationship types. Because the NIBRS dataset contained a limited number of incident-specific variables that helped explain divergent arrest practices, in Phase II, researchers collected more detailed information on a subset of NIBRS cases from 25 police departments of varying sizes across four states. This phase of the study was restricted to intimate partner and other domestic violence cases. Additional data were collected for these cases to evaluate court case outcomes and subsequent re-offending. This phase also included an assessment of how closely department policy reflected state law in a larger sample of agencies within five states. The data in Part 1 (Phase I Data) contain 577,862 records from the NIBRS. This includes information related to domestic violence incidents such as the most serious offense against the victim, the most serious victim injury, the assault type, date of incident, and the counts of offenses, offenders, victims, and arrests for the incident. The data also include information related to the parties involved in the incident including demographics for the victim(s) and arrestee(s) and the relationship between victim(s) and arrestee(s). There is also information related to the jurisdiction in which the incident occurred such as population, urban/rural classification, and whether the jurisdiction is located in a metropolitan area. There are also variables pertaining to whether a weapon was used, the date of arrest, and the type of arrest. Also included are variables regarding the police department such as the number of male and female police officers and civilians employed. The data in Part 2 (Phase II Data) contain 4,388 cases and include all of the same variables as those in Part 1. In addition to these variables, there are variables such as whether the offender was on the scene when the police arrived, who reported the incident, the exact nature of injuries suffered by the involved parties, victim and offender substance use, offender demeanor, and presence of children. Also included are variables related to the number of people including police and civilians who were on the scene, the number of people who were questioned, whether there were warrants for the victim(s) or offender(s), whether citations were issued, whether arrests were made, whether any cases were prosecuted, the number of charges filed and against whom, and the sentences for prosecuted cases that resulted in conviction. The data in Part 3 (Police Department Policy Data) contain 282 cases and include variables regarding whether the department had a domestic violence policy, what the department's arrest policy was, whether a police report needed to be made, whether the policy addressed mutual violence, whether the policy instructed how to determine the primary aggressor, and what factors were taken into account in making a decision to arrest. There is also information related to the proportion of arrests involving intimate partners, the proportion of arrests involving other domestics, the proportion of arrests involving acquaintances, and the proportion of arrests involving strangers.

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

The combined data will be available by 3/10/2025 at the linke above.

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.

Content

This dataset contains three tables, each as a separate file. Each row corresponds to either

1. an arrest/criminal citation
2. an incident (which may or may not have a corresponding arrest/citation), or
3. a charge that was filed

See the corresponding tables for more information on fields, foreign keys, etc

File Names

Files contain either Arrest data, Incident data, or Charge data. Files with the _All suffix are consolidated files that contain all time periods with consistent column names. The time-specific files are as-is as provided by SJPD and contain some column name inconsistencies

Arrests

The "Arrest" datasets contain entries for SJPD stops ("arrests"). This includes booking, where the subject is placed in jail pending arraignment, and also criminal citations, where the subject is not booked, but rather assigned a court date by the officer and promises to appear. The CURRENT STATUS field distinguishes between these two types of arrests

Due to limitations in their internal Record Management System, not all arrests have the arresting officer listed. This issue is being addressed, and recent arrests are more likely to have this field available

Acknowledgements

This dataset was provided directly from San Jose Police Department via a request under the California Public Records Act

Photo by Alex Young on Unsplash

The bar chart shows the percentage of Indiana’s total arrests by racial category. The arrest percentage is calculated by dividing the number of arrests of people within a specific racial category by the total number of statewide arrests. The baseline of “per 1000” allows for comparison of rates across categories. Selecting the “rate per 1000” view produces a line graph that shows the number of arrests per 1,000 individuals by race. The number of arrests per county and by race are compared to 2010 Census population 2014-2020. Additional facts to note: 1. This dashboard shows data from the Criminal History Records Information System (CHRIS), which comes from three main sources. Arrest data comes from the Live Scan system, which is used for finger printing and capturing other pertinent information at the time of the arrest. Criminal disposition data are maintained by prosecutors in the ProsLink system, and by courts in the Odyssey system. Arrest county is determined by the location of the booking agency. If the booking agency is missing, then the arresting agency is used. The % of IN Population will not equal 100% because we are excluding non-represented racial category "Two or More Races," which accounts for ~1.7% of Indiana's population. Because some arrests are not included in the individual race categories shown here, total counts and percentages from the individual race categories add up to less than the totals for “All” races. While most dashboards in the Data Portal use Census estimates from 2019, this dashboard uses 2010 Census data.

This juvenile arrest report contains all arrests made by MPD and other law enforcement agencies of individuals 17 and under, excluding any arrests that have been expunged. Only the top charge (most serious charge) is reported for each arrest.The "Home PSA" of all arrests for which a valid District of Columbia address was given are provided. For all cases where the home address was outside the District of Columbia, the home address field was manually reviewed and marked as "OUT OF STATE". "UNKNOWN" is provided for cases where no address was reported.The "Crime/Arrest PSA" field contains the PSA associated with the original crime where the arrest record could be matched against the original crime report. For cases where the DC Moultrie Courthouse was indicated as the crime address (e.g., for Juvenile Custody Order, Failure to Appear, Fugitive from Justice, and Booking Order), "COURT" was listed as the crime PSA instead of PSA 102. For cases for which the Juvenile Processing Center (JPC) was indicated as the crime address, or for cases where other processing locations were listed as the crime address (e.g., District station or MPD Headquarters), "DISTRICT/JPC" was listed as the crime PSA . For arrest cases without proper crime incident address, it was assumed that the arrest was made at the site of the crime, and the PSA associated with the arrest location was provided.

The data represents individuals arrested with a marijuana charge, regardless of whether there was a more serious secondary charge. If an arrestee was charged with multiple marijuana charges, the arrest is only counted once under the more serious charge type (Manufacture/Cultivation > Distribution > Possession with Intent to Distribute > Possession > Public Consumption). The category of “Manufacture or Cultivation” was added in the 2019 data and for future years, but is not utilized in prior years.MPD 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).” Data on race and ethnicity prior to November 9, 2018 was based on officer observation; on and after November 9, 2018, the data is based on the arrestee’s response.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. Due to the Department’s redistricting efforts in 2012 and 2019, data may not be comparable in some years.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 or if the arrestee refused to provide it.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 have been coded as “NA” for the following fields:• Arrest Hour• CCN• Age• Offense Location Block GeoX/Y• Defendant Race• Defendant Ethnicity• Defendant Sex• Arrest Location Block Address• Arrest Location Block GeoX/YThis data may not match other marijuana data requests that may have included all law enforcement agencies in the District, or only the most serious charge. Figures are subject to change due to record sealing, expungements, and data quality audits.

A. SUMMARY To confirm the completeness of this dataset please contact the Sheriff's Office at sheriff.tech.services@sfgov.org The dataset provides summary information on individuals booked into the San Francisco City and County Jail since 2012, categorized by race. The table provides a breakdown of the total number of bookings by month and race. The unit of measure is the jail booking number. The data is collected by the Sheriff's Office and includes self-report and assigned data. However, some race categories with small sample sizes are grouped together to reduce the risk of re-identification and protect the privacy of individuals booked into jail. The booking process refers to the procedure that occurs after an individual has been arrested and is taken into custody. The process begins with the arrest of an individual by law enforcement officers. The arrest can take place on the scene or at a later time if a warrant is issued. Once the individual has been arrested, and statutory law requires incarceration, they would be transported to the jail for booking. The arresting officer will record the reason for the arrest, along with any other relevant information. The sheriff’s deputies will then book the individual into jail, which involves taking their fingerprints, photograph, and recording personal information. The jail will assign a booking number, which is used to identify the individual throughout their time in custody. Once the booking process is complete, the individual will be incarcerated and will remain in custody until they are released per court order. Disclaimer: The San Francisco Sheriff's Office does not guarantee the accuracy, completeness, or timeliness of the information as the data is subject to change as modifications and updates are completed. B. HOW THE DATASET IS CREATED When an arrest is presented to the Sheriff’s Office, relevant data is manually entered into the Sheriff Office's jail management system. Data reports are pulled from this system on a semi-regular basis, and added to Open Data. C. UPDATE PROCESS This dataset is scheduled to update monthly D. HOW TO USE THIS DATASET This data can be used to identify trends and patterns in the jail population over time. The date in this dataset is based on the date the suspect was booked into county jail for the arresting incident. The unit of measurement for this dataset is the booking number. A jail booking number is a unique identifier assigned to each individual who is booked into a jail facility. It is used to track the individual throughout their time in custody and to link their records to other relevant information, such as court appearances and medical records. Note that this dataset should be used with the Jail Bookings by Ethnicity dataset for an accurate characterization of the Hispanic or Latin populations. E. RELATED DATASETS • Bookings by Age • Bookings by Male/Female • Bookings by Ethnicity

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.

Version 11 release notes:Changes release notes description, does not change data.Version 10 release notes:The data now has the following age categories (which were previously aggregated into larger groups to reduce file size): under 10, 10-12, 13-14, 40-44, 45-49, 50-54, 55-59, 60-64, over 64. These categories are available for female, male, and total (female+male) arrests. The previous aggregated categories (under 15, 40-49, and over 49 have been removed from the data). Version 9 release notes:For each offense, adds a variable indicating the number of months that offense was reported - these variables are labeled as "num_months_[crime]" where [crime] is the offense name. These variables are generated by the number of times one or more arrests were reported per month for that crime. For example, if there was at least one arrest for assault in January, February, March, and August (and no other months), there would be four months reported for assault. Please note that this does not differentiate between an agency not reporting that month and actually having zero arrests. The variable "number_of_months_reported" is still in the data and is the number of months that any offense was reported. So if any agency reports murder arrests every month but no other crimes, the murder number of months variable and the "number_of_months_reported" variable will both be 12 while every other offense number of month variable will be 0. Adds data for 2017 and 2018.Version 8 release notes:Adds annual data in R format.Changes project name to avoid confusing this data for the ones done by NACJD.Fixes bug where bookmaking was excluded as an arrest category. Changed the number of categories to include more offenses per category to have fewer total files. Added a "total_race" file for each category - this file has total arrests by race for each crime and a breakdown of juvenile/adult by race. Version 7 release notes: Adds 1974-1979 dataAdds monthly data (only totals by sex and race, not by age-categories). All data now from FBI, not NACJD. Changes some column names so all columns are <=32 characters to be usable in Stata.Changes how number of months reported is calculated. Now it is the number of unique months with arrest data reported - months of data from the monthly header file (i.e. juvenile disposition data) are not considered in this calculation. Version 6 release notes: Fix bug where juvenile female columns had the same value as juvenile male columns.Version 5 release notes: Removes support for SPSS and Excel data.Changes the crimes that are stored in each file. There are more files now with fewer crimes per file. The files and their included crimes have been updated below.Adds in agencies that report 0 months of the year.Adds a column that indicates the number of months reported. This is generated summing up the number of unique months an agency reports data for. Note that this indicates the number of months an agency reported arrests for ANY crime. They may not necessarily report every crime every month. Agencies that did not report a crime with have a value of NA for every arrest column for that crime.Removes data on runaways.Version 4 release notes: Changes column names from "poss_coke" and "sale_coke" to "poss_heroin_coke" and "sale_heroin_coke" to clearly indicate that these column includes the sale of heroin as well as similar opiates such as morphine, codeine, and opium. Also changes column names for the narcotic columns to indicate that they are only for synthetic narcotics. Version 3 release notes: Add data for 2016.Order rows by year (descending) and ORI.Version 2 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The Arrests by Age, Sex, and Race (ASR) data is an FBI data set that is part of the annual Uniform Crime Reporting (UCR) Program data. This data contains highly granular data on the number of people arrested for a variety of crimes (see below for a full list of included crimes). The data sets here combine data from the years 1974-2018 into a single file for each group of crimes. Each monthly file is only a single year as my laptop can't handle combining all the years together. These files are quite large and may take some time to load. Columns are crime-arrest category units. For example, If you choose the data set that includes murder, you would have rows for each age

This version (V3) fixes a bug in Version 2 where 1993 data did not properly deal with missing values, leading to enormous counts of crime being reported. This is a collection of Offenses Known and Clearances By Arrest data from 1960 to 2016. The monthly zip files contain one data file per year(57 total, 1960-2016) as well as a codebook for each year. These files have been read into R using the ASCII and setup files from ICPSR (or from the FBI for 2016 data) using the package asciiSetupReader. The end of the zip folder's name says what data type (R, SPSS, SAS, Microsoft Excel CSV, feather, Stata) the data is in. Due to file size limits on open ICPSR, not all file types were included for all the data. The files are lightly cleaned. What this means specifically is that column names and value labels are standardized. In the original data column names were different between years (e.g. the December burglaries cleared column is "DEC_TOT_CLR_BRGLRY_TOT" in 1975 and "DEC_TOT_CLR_BURG_TOTAL" in 1977). The data here have standardized columns so you can compare between years and combine years together. The same thing is done for values inside of columns. For example, the state column gave state names in some years, abbreviations in others. For the code uses to clean and read the data, please see my GitHub file here. https://github.com/jacobkap/crime_data/blob/master/R_code/offenses_known.RThe zip files labeled "yearly" contain yearly data rather than monthly. These also contain far fewer descriptive columns about the agencies in an attempt to decrease file size. Each zip folder contains two files: a data file in whatever format you choose and a codebook. The data file is aggregated yearly and has already combined every year 1960-2016. For the code I used to do this, see here https://github.com/jacobkap/crime_data/blob/master/R_code/yearly_offenses_known.R.If you find any mistakes in the data or have any suggestions, please email me at jkkaplan6@gmail.comAs a description of what UCR Offenses Known and Clearances By Arrest data contains, the following is copied from ICPSR's 2015 page for the data.The Uniform Crime Reporting Program Data: Offenses Known and Clearances By Arrest dataset is a compilation of offenses reported to law enforcement agencies in the United States. Due to the vast number of categories of crime committed in the United States, the FBI has limited the type of crimes included in this compilation to those crimes which people are most likely to report to police and those crimes which occur frequently enough to be analyzed across time. Crimes included are criminal homicide, forcible rape, robbery, aggravated assault, burglary, larceny-theft, and motor vehicle theft. Much information about these crimes is provided in this dataset. The number of times an offense has been reported, the number of reported offenses that have been cleared by arrests, and the number of cleared offenses which involved offenders under the age of 18 are the major items of information collected.

The accompanying data cover all MPD stops including vehicle, pedestrian, bicycle, and harbor stops for the period from January 1, 2023 – June 30, 2024. A stop may involve a ticket (actual or warning), investigatory stop, protective pat down, search, or arrest.If the final outcome of a stop results in an actual or warning ticket, the ticket serves as the official documentation for the stop. The information provided in the ticket include the subject’s name, race, gender, reason for the stop, and duration. All stops resulting in additional law enforcement actions (e.g., pat down, search, or arrest) are documented in MPD’s Record Management System (RMS). This dataset includes records pulled from both the ticket (District of Columbia Department of Motor Vehicles [DMV]) and RMS sources. Data variables not applicable to a particular stop are indicated as “NULL.” For example, if the stop type (“stop_type” field) is a “ticket stop,” then the fields: “stop_reason_nonticket” and “stop_reason_harbor” will be “NULL.”Each row in the data represents an individual stop of a single person, and that row reveals any and all recorded outcomes of that stop (including information about any actual or warning tickets issued, searches conducted, arrests made, etc.). A single traffic stop may generate multiple tickets, including actual, warning, and/or voided tickets. Additionally, an individual who is stopped and receives a traffic ticket may also be stopped for investigatory purposes, patted down, searched, and/or arrested. If any of these situations occur, the “stop_type” field would be labeled “Ticket and Non-Ticket Stop.” If an individual is searched, MPD differentiates between person and property searches. Please note that the term property in this context refers to a person’s belongings and not a physical building. The “stop_location_block” field represents the block-level location of the stop and/or a street name. The age of the person being stopped is calculated based on the time between the person’s date of birth and the date of the stop.There are certain locations that have a high prevalence of non-ticket stops. These can be attributed to some centralized processing locations. Additionally, there is a time lag for data on some ticket stops as roughly 20 percent of tickets are handwritten. In these instances, the handwritten traffic tickets are delivered by MPD to the DMV, and then entered into data systems by DMV contractors.On August 1, 2021, MPD transitioned to a new version of its current records management system, Mark43 RMS.Beginning January 1, 2023, fields pertaining to the bureau, division, unit, and PSA (if applicable) of the officers involved in events where a stop was conducted were added to the dataset. MPD’s Records Management System (RMS) captures all members associated with the event but cannot isolate which officer (if multiple) conducted the stop itself. Assignments are captured by cross-referencing officers’ CAD ID with MPD’s Timesheet Manager Application. These fields reflect the assignment of the officer issuing the Notice of Infraction (NOIs) and/or the responding officer(s), assisting officer(s), and/or arresting officer(s) (if an investigative stop) as of the end of the two-week pay period for January 1 – June 30, 2023 and as of the date of the stop for July 1, 2023 and forward. The values are comma-separated if multiple officers were listed in the report.For Stop Type = Harbor and Stop Type = Ticket Only, the officer assignment information will be in the NOI_Officer fields. For Stop Type = Ticket and Non-Ticket the officer assignments will be in both NOI Officer (for the officer that issued the NOI) and RMS_Officer fields (for any other officer involved in the event, which may also be the officer who issued the NOI). For Stop Type = Non-Ticket, the officer assignment information will be in the RMS_Officer fields.Null values in officer assignment fields reflect either Reserve Corps members, who’s assignments are not captured in the Timesheet Manager Application, or members who separated from MPD between the time of the stop and the time of the data extraction.Finally, MPD is conducting on-going data audits on all data for thorough and complete information. Figures are subject to change due to delayed reporting, on-going data quality audits, and data improvement processes.

A. SUMMARY Please note that the "Data Last Updated" date on this page denotes the most recent DataSF update and does not reflect the most recent update to this dataset. To confirm the completeness of this dataset please contact the Sheriff's Office at sheriff.tech.services@sfgov.org The dataset provides summary information on individuals booked into the San Francisco City and County Jail since 2012, categorized by ethnicity. The table provides a breakdown of the total number of bookings by month and ethnicity. The unit of measure is the jail booking number. The data is collected by the Sheriff's Office and includes self-report and assigned data. However, some ethnicity categories with small sample sizes are grouped together to reduce the risk of re-identification and protect the privacy of individuals booked into jail. The booking process refers to the procedure that occurs after an individual has been arrested and is taken into custody. The process begins with the arrest of an individual by law enforcement officers. The arrest can take place on the scene or at a later time if a warrant is issued. Once the individual has been arrested, and statutory law requires incarceration, they would be transported to the jail for booking. The arresting officer will record the reason for the arrest, along with any other relevant information. The sheriff’s deputies will then book the individual into jail, which involves taking their fingerprints, photograph, and recording personal information. The jail will assign a booking number, which is used to identify the individual throughout their time in custody. Once the booking process is complete, the individual will be incarcerated and will remain in custody until they are released per court order. Disclaimer: The San Francisco Sheriff's Office does not guarantee the accuracy, completeness, or timeliness of the information as the data is subject to change as modifications and updates are completed. B. HOW THE DATASET IS CREATED When an arrest is presented to the Sheriff’s Office, relevant data is manually entered into the Sheriff Office's jail management system. Data reports are pulled from this system on a semi-regular basis, and added to Open Data. C. UPDATE PROCESS This dataset is scheduled to update monthly. D. HOW TO USE THIS DATASET This data can be used to identify trends and patterns in the jail population over time. The date in this dataset is based on the date the suspect was booked into county jail for the arresting incident. The unit of measurement for this dataset is the booking number. A jail booking number is a unique identifier assigned to each individual who is booked into a jail facility. E. RELATED DATASETS • Booking by Age • Bookings by Race • Booking by Male/Female

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.

A. SUMMARY To confirm the completeness of this dataset please contact the Sheriff's Office at sheriff.tech.services@sfgov.org The dataset provides summary information on individuals booked into the San Francisco City and County Jail since 2012, categorized by age group. The table provides a breakdown of the total number of bookings by month and age group. The unit of measure is the jail booking number. The data is collected by the Sheriff's Office and includes self-reported and assigned data. The booking process refers to the procedure that occurs after an individual has been arrested and is taken into custody. The process begins with the arrest of an individual by law enforcement officers. The arrest can take place on the scene or at a later time if a warrant is issued. Once the individual has been arrested, and statutory law requires incarceration, they would be transported to the jail for booking. The arresting officer will record the reason for the arrest, along with any other relevant information. The sheriff’s deputies will then book the individual into jail, which involves taking their fingerprints, photograph, and recording personal information. The jail will assign a booking number, which is used to identify the individual throughout their time in custody. Once the booking process is complete, the individual will be incarcerated and will remain in custody until they are released per court order. Disclaimer: The San Francisco Sheriff's Office does not guarantee the accuracy, completeness, or timeliness of the information as the data is subject to change as modifications and updates are completed. B. HOW THE DATASET IS CREATED When an arrest is presented to the Sheriff’s Office, relevant data is manually entered into the Sheriff Office's jail management system. Data reports are pulled from this system on a semi-regular basis, and added to Open Data. C. UPDATE PROCESS This dataset is scheduled to update monthly D. HOW TO USE THIS DATASET This data can be used to identify trends and patterns in the jail population over time. The date in this dataset is based on the date the suspect was booked into county jail for the arresting incident. The unit of measurement for this dataset is the booking number. A jail booking number is a unique identifier assigned to each individual who is booked into a jail facility. It is used to track the individual throughout their time in custody and to link their records to other relevant information, such as court appearances and medical records. E. RELATED DATASETS • Bookings by Race • Bookings by Male/Female • Bookings by Ethnicity

*This data is updated nightly from the Police Reporting Server housed at the ECC every day at 11:59PM.Arrest data contains information on people taken into custody by City of Charlottesville police officers. More serious crimes such as felony offenses are more likely to result in an arrest. However, arrests can occur as a result of other offenses, such as parole violations or a failure to appear for trial.This dataset only contains information reported by City of Charlottesville Police. It does not contain information about incidents that solely involve other police departments operating within the city (for example, University of Virginia police or Albemarle County police).

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 collection focuses on how changes in the legal drinking age affect the number of fatal motor vehicle accidents and crime rates. The principal investigators identified three areas of study. First, they looked at blood alcohol content of drivers involved in fatal accidents in relation to changes in the drinking age. Second, they looked at how arrest rates correlated with changes in the drinking age. Finally, they looked at the relationship between blood alcohol content and arrest rates. In this context, the investigators used the percentage of drivers killed in fatal automobile accidents who had positive blood alcohol content as an indicator of drinking in the population. Arrests were used as a measure of crime, and arrest rates per capita were used to create comparability across states and over time. Arrests for certain crimes as a proportion of all arrests were used for other analyses to compensate for trends that affect the probability of arrests in general. This collection contains three parts. Variables in the Federal Bureau of Investigation Crime Data file (Part 1) include the state and year to which the data apply, the type of crime, and the sex and age category of those arrested for crimes. A single arrest is the unit of analysis for this file. Information in the Population Data file (Part 2) includes population counts for the number of individuals within each of seven age categories, as well as the number in the total population. There is also a figure for the number of individuals covered by the reporting police agencies from which data were gathered. The individual is the unit of analysis. The Fatal Accident Data file (Part 3) includes six variables: the FIPS code for the state, year of accident, and the sex, age group, and blood alcohol content of the individual killed. The final variable in each record is a count of the number of drivers killed in fatal motor vehicle accidents for that state and year who fit into the given sex, age, and blood alcohol content grouping. A driver killed in a fatal accident is the unit of analysis.