The Uniform Crime Reporting Program Data, Police Employee Data, 2015 file contains monthly data on felonious or accidental killings and assaults upon United States law enforcement officers acting in the line of duty. The Federal Bureau of Investigation (FBI) assembled the data and processed them from UCR Master Police Employee (LEOKA) data tapes. Each agency record in the file includes the following summary variables: state code, population group code, geographic division, Metropolitan Statistical Area code, and agency name. These variables afford considerable flexibility in creating subsets or aggregations of the data. Since 1930, the Federal Bureau of Investigation has compiled the Uniform Crime Reports (UCR) to serve as a periodic nationwide assessment of reported crimes not available elsewhere in the criminal justice system. Each year, this information is reported in four types of files: (1) Offenses Known and Clearances by Arrest, (2) Property Stolen and Recovered, (3) Supplementary Homicide Reports (SHR), and (4) Police Employee (LEOKA) Data. The Police Employee (LEOKA) Data provide information about law enforcement officers killed or assaulted (hence the acronym, LEOKA) in the line of duty. The variables created from the LEOKA forms provide in-depth information on the circumstances surrounding killings or assaults, including type of call answered, type of weapon used, and type of patrol the officers were on.

These data on 19th- and early 20th-century police department and arrest behavior were collected between 1975 and 1978 for a study of police and crime in the United States. Raw and aggregated time-series data are presented in Parts 1 and 3 on 23 American cities for most years during the period 1860-1920. The data were drawn from annual reports of police departments found in the Library of Congress or in newspapers and legislative reports located elsewhere. Variables in Part 1, for which the city is the unit of analysis, include arrests for drunkenness, conditional offenses and homicides, persons dismissed or held, police personnel, and population. Part 3 aggregates the data by year and reports some of these variables on a per capita basis, using a linear interpolation from the last decennial census to estimate population. Part 2 contains data for 267 United States cities for the period 1880-1890 and was generated from the 1880 federal census volume, REPORT ON THE DEFECTIVE, DEPENDENT, AND DELINQUENT CLASSES, published in 1888, and from the 1890 federal census volume, SOCIAL STATISTICS OF CITIES. Information includes police personnel and expenditures, arrests, persons held overnight, trains entering town, and population.

The Uniform Crime Reporting Program Data, Police Employee Data, 2019 file contains monthly data on felonious or accidental killings and assaults upon United States law enforcement officers acting in the line of duty. The Federal Bureau of Investigation (FBI) assembled the data and processed them from UCR Master Police Employee (LEOKA) data tapes. Each agency record in the file includes the following summary variables: state code, population group code, geographic division, Metropolitan Statistical Area code, and agency name. These variables afford considerable flexibility in creating subsets or aggregations of the data. Since 1930, the Federal Bureau of Investigation has compiled the Uniform Crime Reports (UCR) to serve as a periodic nationwide assessment of reported crimes not available elsewhere in the criminal justice system. Each year, this information is reported in four types of files: (1) Offenses Known and Clearances by Arrest, (2) Property Stolen and Recovered, (3) Supplementary Homicide Reports (SHR), and (4) Police Employee (LEOKA) Data. The Police Employee (LEOKA) Data provide information about law enforcement officers killed or assaulted (hence the acronym, LEOKA) in the line of duty. The variables created from the LEOKA forms provide in-depth information on the circumstances surrounding killings or assaults, including type of call answered, type of weapon used, and type of patrol the officers were on.

This dataset contains crime reports from the City of Somerville Police Department's records management system from 2017 to present. Each data point represents an incident, which may involve multiple offenses (the most severe offense is provided here). Incidents deemed sensitive by enforcement agencies are included in the data set but are stripped of time or location information to protect the privacy of victims. For these incidents, only the year of the offense is provided. This data set is refreshed daily with data appearing with a one-month delay (for example, crime reports from 1/1 will appear on 2/1). If a daily update does not refresh, please email data@somervillema.gov.

Data on police personnel (police officers by gender, civilian and other personnel), police officers and authorized strength per 100,000 population, authorized police officer strength, population, net gain or loss from hirings and departures, police officers eligible to retire and selected crime statistics. Data is provided for municipal police services, 2000 to 2023.

This complete version of the dataset contains traffic citations issued in Somerville by Somerville police officers since 2017. Citations include both written warnings and those with a monetary fine. Every citation is composed of one or more violations. Each row in the dataset represents a violation. This data set should be refreshed daily with data appearing with a one-month delay (e.g. citations issued on 1/1 will appear on 2/1). If a daily update does not refresh, please email data@somervillema.gov.

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

Since 1930, the Federal Bureau of Investigation has compiled the Uniform Crime Reports (UCR) to serve as a periodic nationwide assessment of reported crimes not available elsewhere in the criminal justice system. Each year, this information is reported in four types of files: (1) Offenses Known and Clearances by Arrest, (2) Property Stolen and Recovered, (3) Supplementary Homicide Reports (SHR), and (4) Police Employee (LEOKA) Data. The Police Employee (LEOKA) Data provide information about law enforcement officers killed or assaulted (hence the acronym, LEOKA) in the line of duty. The variables created from the LEOKA forms provide in-depth information on the circumstances surrounding killings or assaults, including type of call answered, type of weapon used, and type of patrol the officers were on.

Update Frequency: Daily

Current year to date. The data included in this dataset has been reviewed and approved by a Milwaukee Police Department supervisor and the Milwaukee Police Department’s Records Management Division. This approval process can take a few weeks from the reported date of the crime. For preliminary crime data, please visit the Milwaukee Police Department’s Crime Maps and Statistics dashboard at https://city.milwaukee.gov/police/Information-Services/Crime-Maps-and-Statistics.

Wisconsin Incident Based Report (WIBR) Group A Offenses.

The Crime Data represents incident level data defined by Wisconsin Incident Based Reporting System (WIBRS) codes. WIBRS reporting is a crime reporting standard and can not be compared to any previous UCR report. Therefore, the Crime Data may reflect:

• Information not yet verified by further investigation
• Preliminary crime classifications that may be changed at a later date based upon further investigation
• Information that may include mechanical or human error

Neither the City of Milwaukee nor the Milwaukee Police Department guarantee (either express or implied) the accuracy, completeness, timeliness, or correct sequencing of the Crime Data. The City of Milwaukee and the Milwaukee Police Department shall have no liability for any error or omission, or for the use of, or the results obtained from the use of the Crime Data. In addition, the City of Milwaukee and the Milwaukee Police Department caution against using the Crime Data to make decisions/comparisons regarding the safety of or the amount of crime occurring in a particular area. When reviewing the Crime Data, the site user should consider that:

• The information represents only police services where a report was made and does not include other calls for police service
• The information does not reflect or certify "safe" or "unsafe" areas
• The information will sometimes reflect where the crime was reported versus where the crime occurred

This data is not intended to represent a total number/sum of crimes, rather 1 = True and 0 = False.

The use of the Crime Data indicates the site user's unconditional acceptance of all risks associated with the use of the Crime Data.

To download XML and JSON files, click the CSV option below and click the down arrow next to the Download button in the upper right on its page. XY fields in data is in projection Wisconsin State Plane South NAD27 (WKID 32054).

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that have occurred in the City of Chicago over the past year, minus the most recent seven days of data. 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://bit.ly/rk5Tpc.

This dataset shows the time spent by currently active Pittsburgh Police Officers in professional development training. Officers who are no longer employed in the Police Bureau are not included in this data. The data is presented in two ways: total, cumulative hours spent in training, per year, by category and total number of officers who completed training, per year, by category.

For up to date data starting in 2018, please go to the new dataset at: https://data.sfgov.org/d/wg3w-h783

As of May 2018, the feed from the legacy mainframe CABLE was discontinued. It was extremely prone to issues and caused many delays in data accessibility. The new dataset linked above comes from the Crime Data Warehouse, a more reliable data system maintained by the Police Department.

This data will undergo a minor update to conform more closely to the schema of the new dataset. We will post a change notice when that work is planned. This change will not include adding new fields or backfilling data. It is provided as is. We are keeping data from the two systems separate to make it transparent to data users that there were fundamental changes.

The efficiency of any police action depends on the relative magnitude of its crime reducing benefits and legitimacy costs. Policing strategies that are socially efficient at the city level may be harmful at the local level, because the distribution of direct costs and benefits of police actions that reduce victimization is not the same as the distribution of indirect benefits of feeling safe. In the United States, the local misallocation of police resources is disproportionately borne by Black and Hispanic people. Despite the complexity of this particular problem, we point out that the incentives facing both police departments and police officers tend to be structured as if the goals of policing were simple - to reduce crime by as much as possible. Data collection on the crime reducing benefits of policing, and not the legitimacy costs, produce further incentives to provide more engagement than may be efficient in any specific encounter, at both the officer and departmental level. There is currently little evidence as to what screening, training, or monitoring strategies are most effective at encouraging individual officers to balance the crime reducing benefits and legitimacy costs of their actions.

Crime data from years prior to the current one. The data included in this dataset has been reviewed and approved by a Milwaukee Police Department supervisor and the Milwaukee Police Department’s Records Management Division. This approval process can take a few weeks from the reported date of the crime. For preliminary crime data, please visit the Milwaukee Police Department’s Crime Maps and Statistics dashboard at https://city.milwaukee.gov/police/Information-Services/Crime-Maps-and-Statistics.

Wisconsin Incident Based Report (WIBR) Group A Offenses.

The Crime Data represents incident level data defined by Wisconsin Incident Based Reporting System (WIBRS) codes. WIBRS reporting is a crime reporting standard and can not be compared to any previous UCR report. Therefore, the Crime Data may reflect:

• Information not yet verified by further investigation
• Preliminary crime classifications that may be changed at a later date based upon further investigation
• Information that may include mechanical or human error

Neither the City of Milwaukee nor the Milwaukee Police Department guarantee (either express or implied) the accuracy, completeness, timeliness, or correct sequencing of the Crime Data. The City of Milwaukee and the Milwaukee Police Department shall have no liability for any error or omission, or for the use of, or the results obtained from the use of the Crime Data. In addition, the City of Milwaukee and the Milwaukee Police Department caution against using the Crime Data to make decisions/comparisons regarding the safety of or the amount of crime occurring in a particular area. When reviewing the Crime Data, the site user should consider that:

• The information represents only police services where a report was made and does not include other calls for police service
• The information does not reflect or certify "safe" or "unsafe" areas
• The information will sometimes reflect where the crime was reported versus where the crime occurred

The use of the Crime Data indicates the site user's unconditional acceptance of all risks associated with the use of the Crime Data.

To download XML and JSON files, click the CSV option below and click the down arrow next to the Download button in the upper right on its page. XY fields in data is in projection Wisconsin State Plane South NAD27 (WKID 32054).

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.

To estimate national trends of crime, the FBI collects crime reports from law enforcement agencies across the country. In 2022, Delaware, the District of Columbia, and Oklahoma had perfect participation rates, with 100 percent of law enforcement agencies reporting crime data to the FBI in those states. In contrast, the state of Florida had the lowest share of law enforcement agencies who reported crime data to the FBI in the United States, at 7.7 percent. An unreliable source? Along with being the principal investigative agency of the U.S. federal government, the FBI is also in charge of tracking crimes committed in the United States. In recent years, however, the FBI made significant changes to their crime reporting system, requiring a more detailed input on how agencies report their data. Consequently, less crime data has been reported and the FBI has come under criticism as an unreliable source on crime in the United States. In 2022, the FBI was found to rank low on trustworthiness for Americans when compared to other government agencies, further demonstrating the need for transparent and accurate data. Importance of crime rates As crime and policing data can help to analyze emerging issues and policy responses, the inaccuracy of the FBI’s crime reporting system may lead to misinformation which could be used to impact elections and the beliefs of the American public. In addition, the lack of crime data from Republican states such as Florida may prove problematic as 78 percent of Republicans said that crime was a very important issue for them in midterm elections.

Chicago Police district station locations. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required. To download, right-click the "Download" link above and choose "Save link as."