Investigator(s): Federal Bureau of Investigation Since 1930, the Federal Bureau of Investigation (FBI) has compiled the Uniform Crime Reports (UCR) to serve as periodic nationwide assessments of reported crimes not available elsewhere in the criminal justice system. With the 1977 data, the title was expanded to Uniform Crime Reporting Program Data. Each year, participating law enforcement agencies contribute reports to the FBI either directly or through their state reporting programs. ICPSR archives the UCR data as five separate components: (1) summary data, (2) county-level data, (3) incident-level data (National Incident-Based Reporting System [NIBRS]), (4) hate crime data, and (5) various, mostly nonrecurring, data collections. Summary data are reported in four types of files: (a) Offenses Known and Clearances by Arrest, (b) Property Stolen and Recovered, (c) Supplementary Homicide Reports (SHR), and (d) Police Employee (LEOKA) Data (Law Enforcement Officers Killed or Assaulted). The county-level data provide counts of arrests and offenses aggregated to the county level. County populations are also reported. In the late 1970s, new ways to look at crime were studied. The UCR program was subsequently expanded to capture incident-level data with the implementation of the National Incident-Based Reporting System. The NIBRS data focus on various aspects of a crime incident. The gathering of hate crime data by the UCR program was begun in 1990. Hate crimes are defined as crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity. In September 1994, disabilities, both physical and mental, were added to the list. The fifth component of ICPSR's UCR holdings is comprised of various collections, many of which are nonrecurring and prepared by individual researchers. These collections go beyond the scope of the standard UCR collections provided by the FBI, either by including data for a range of years or by focusing on other aspects of analysis. NACJD has produced resource guides on UCR and on NIBRS data.

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

description: Updated daily postings on Montgomery County s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by EJustice , a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation. dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect: -Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -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.] Update Frequency: Daily; abstract: Updated daily postings on Montgomery County s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by EJustice , a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation. dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect: -Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -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.] Update Frequency: Daily

In response to a growing concern about hate crimes, the United States Congress enacted the Hate Crime Statistics Act of 1990. The Act requires the attorney general to establish guidelines and collect, as part of the Uniform Crime Reporting (UCR) Program, data "about crimes that manifest evidence of prejudice based on race, religion, sexual orientation, or ethnicity, including where appropriate the crimes of murder and non-negligent manslaughter, forcible rape, aggravated assault, simple assault, intimidation, arson, and destruction, damage or vandalism of property." Hate crime data collection was required by the Act to begin in calendar year 1990 and to continue for four successive years. In September 1994, the Violent Crime Control and Law Enforcement Act amended the Hate Crime Statistics Act to add disabilities, both physical and mental, as factors that could be considered a basis for hate crimes. Although the Act originally mandated data collection for five years, the Church Arson Prevention Act of 1996 amended the collection duration "for each calendar year," making hate crime statistics a permanent addition to the UCR program. As with the other UCR data, law enforcement agencies contribute reports either directly or through their state reporting programs. Information contained in the data includes number of victims and offenders involved in each hate crime incident, type of victims, bias motivation, offense type, and location type.

These data provide information on the number of arrests reported to the Federal Bureau of Investigation's (FBI) Uniform Crime Reporting (UCR) Program each month by police agencies in the United States. Although not as well known as the "Crimes Known to the Police" data drawn from the Uniform Crime Report's Return A form, the arrest reports by age, sex, and race provide valuable data on 44 offenses including violent, drug, gambling, and larceny crimes. The data received by ICPSR were structured as a hierarchical file containing (per reporting police agency) an agency header record, and 1 to 12 monthly header reports, and 1 to 43 detail offense records containing the counts of arrests by age, sex, and race for a particular offense. ICPSR restructured the original data to a rectangular format.

UCR Crime Index reports the number and rate of violent and property crimes, per crime type.

Crime data assembled by census block group for the MSA from the Applied Geographic Solutions' (AGS) 1999 and 2005 'CrimeRisk' databases distributed by the Tetrad Computer Applications Inc. CrimeRisk is the result of an extensive analysis of FBI crime statistics. Based on detailed modeling of the relationships between crime and demographics, CrimeRisk provides an accurate view of the relative risk of specific crime types at the block group level. Data from 1990 - 1996,1999, and 2004-2005 were used to compute the attributes, please refer to the 'Supplemental Information' section of the metadata for more details. Attributes are available for two categories of crimes, personal crimes and property crimes, along with total and personal crime indices. Attributes for personal crimes include murder, rape, robbery, and assault. Attributes for property crimes include burglary, larceny, and mother vehicle theft. 12 block groups have no attribute information. CrimeRisk is a block group and higher level geographic database consisting of a series of standardized indexes for a range of serious crimes against both persons and property. It is derived from an extensive analysis of several years of crime reports from the vast majority of law enforcement jurisdictions nationwide. The crimes included in the database are the "Part I" crimes and include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. These categories are the primary reporting categories used by the FBI in its Uniform Crime Report (UCR), with the exception of Arson, for which data is very inconsistently reported at the jurisdictional level. Part II crimes are not reported in the detail databases and are generally available only for selected areas or at high levels of geography. In accordance with the reporting procedures using in the UCR reports, aggregate indexes have been prepared for personal and property crimes separately, as well as a total index. While this provides a useful measure of the relative "overall" crime rate in an area, it must be recognized that these are unweighted indexes, in that a murder is weighted no more heavily than a purse snatching in the computation. For this reason, caution is advised when using any of the aggregate index values. The block group boundaries used in the dataset come from TeleAtlas's (formerly GDT) Dynamap data, and are consistent with all other block group boundaries in the BES geodatabase.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.


   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

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 contains county-level totals for the years 2002-2014 for eight types of crime: murder, rape, robbery, aggravated assault, burglary, larceny, motor vehicle theft, and arson. These crimes are classed as Part I criminal offenses by the United States Federal Bureau of Investigations (FBI) in their Uniform Crime Reporting (UCR) program. Each record in the dataset represents the total of each type of criminal offense reported in (or, in the case of missing data, attributed to) the county in a given year.

***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. *** **Update 1/18/2024 - LAPD is facing issues with posting the Crime data, but we are taking immediate action to resolve the problem. We understand the importance of providing reliable and up-to-date information and are committed to delivering it. As we work through the issues, we have temporarily reduced our updates from weekly to bi-weekly to ensure that we provide accurate information. Our team is actively working to identify and resolve these issues promptly. We apologize for any inconvenience this may cause and appreciate your understanding. Rest assured, we are doing everything we can to fix the problem and get back to providing weekly updates as soon as possible. ** This dataset reflects incidents of crime in the City of Los Angeles dating back to 2020. This data is transcribed from original crime 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°, 0°). 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

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.

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

The RMS Crime Incidents dataset consists of crime reports from the Detroit Police Department Records Management System (RMS). This data reflects reported criminal offenses that have occurred in the City of Detroit. Incident-based offense data is extracted from the Detroit Police Department's records management system hourly. This data set contains the most recent data available and is updated anytime DPD sends official crime records contributing to the Michigan Incident Crime Reporting (MICR) or the National Incident Based Reporting systems (reflected by the IBR Date field). It should be noted that some incidents involve the commission of multiple offenses, such as a domestic assault where property was also vandalized. In such cases, there is a row in the dataset for each offense, and the related offenses share a common Crime ID and Report Number.

Crime isn't a topic most people want to use mental energy to think about. We want to avoid harm, protect our loved ones, and hold on to what we claim is ours. So how do we remain vigilant without digging too deep into the filth that is crime? Data, of course. The focus of our study is to explore possible trends between crime and communities in the city of Calgary. Our purpose is visualize Calgary criminal behaviour in order to help increase awareness for both citizens and law enforcement. Through the use of our visuals, individuals can make more informed decisions to improve the overall safety of their lives. Some of the main concerns of the study include: how crime rates increase with population, which areas in Calgary have the most crime, and if crime adheres to time-sensative patterns.

In 2023, the violent crime rate in the United States was 363.8 cases per 100,000 of the population. Even though the violent crime rate has been decreasing since 1990, the United States tops the ranking of countries with the most prisoners. In addition, due to the FBI's transition to a new crime reporting system in which law enforcement agencies voluntarily submit crime reports, data may not accurately reflect the total number of crimes committed in recent years. Reported violent crime rate in the United States The United States Federal Bureau of Investigation tracks the rate of reported violent crimes per 100,000 U.S. inhabitants. In the timeline above, rates are shown starting in 1990. The rate of reported violent crime has fallen since a high of 758.20 reported crimes in 1991 to a low of 363.6 reported violent crimes in 2014. In 2023, there were around 1.22 million violent crimes reported to the FBI in the United States. This number can be compared to the total number of property crimes, roughly 6.41 million that year. Of violent crimes in 2023, aggravated assaults were the most common offenses in the United States, while homicide offenses were the least common. Law enforcement officers and crime clearance Though the violent crime rate was down in 2013, the number of law enforcement officers also fell. Between 2005 and 2009, the number of law enforcement officers in the United States rose from around 673,100 to 708,800. However, since 2009, the number of officers fell to a low of 626,900 officers in 2013. The number of law enforcement officers has since grown, reaching 720,652 in 2023. In 2023, the crime clearance rate in the U.S. was highest for murder and non-negligent manslaughter charges, with around 57.8 percent of murders being solved by investigators and a suspect being charged with the crime. Additionally, roughly 46.1 percent of aggravated assaults were cleared in that year. A statistics report on violent crime in the U.S. can be found here.

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates within 30 days of the system migration, on or around April 13th, 2023Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities. The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics. Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred). Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained. Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.com Data Dictionary: INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence rooms DATE_REPORTED - the date the incident was reported to LMPD DATE_OCCURED - the date the incident actually occurred BADGE_ID - UOR_DESC - Uniform Offense Reporting code for the criminal act committed CRIME_TYPE - the crime type category NIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/view UCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime. LMPD_DIVISION - the LMPD division in which the incident actually occurred LMPD_BEAT - the LMPD beat in which the incident actually occurred PREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant) BLOCK_ADDRESS - the location the incident occurred CITY - the city associated to the incident block location ZIP_CODE - the zip code associated to the incident block location ID - Unique identifier for internal database Contact: Crime Information Center CrimeInfoCenterDL@louisvilleky.gov

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.comData Dictionary:

Field Name

Field Description

Incident Number

the number associated with either the incident or used as reference to store the items in our evidence rooms

Date Reported

the date the incident was reported to LMPD

Date Occurred

the date the incident actually occurred

Badge ID

Badge ID of responding Officer

Offense Classification

NIBRS Reporting category for the criminal act committed

Offense Code Name

NIBRS Reporting code for the criminal act committed

NIBRS_CODE

the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/view

NIBRS Group

hierarchy that follows the guidelines of the FBI National Incident Based Reporting System

Was Offense Completed

Status indicating whether the incident was an attempted crime or a completed crime.

LMPD Division

the LMPD division in which the incident actually occurred

LMPD Beat

the LMPD beat in which the incident actually occurred

Location Category

the type of location in which the incident occurred (e.g. Restaurant)

Block Address

the location the incident occurred

City

the city associated to the incident block location

Zip Code

the zip code associated to the incident block location

Contact:LMPD Open Records lmpdopenrecords@louisvilleky.gov

These are the fixed-width ASCII files that the FBI sends you when you request Uniform Crime Reporting (UCR) Program data. All data are .dat or .txt files. I did not make any changes to the data at all. For a small number of files (mostly data within the last few years), I changed the file name to indicate the data category (e.g. arrests, arson) or to add the .dat extension. Also included are the documents that the FBI provides that instructs users on how to make an .sps or .sas setup file to read in the data ("record descriptions".Please note that when unzipped the files may be quite large.The following data are available:Arson, 1979-2017Arrests by Age, Sex, and Race - Monthly Data, 1974-2016Law Enforcement Officers Killed and Assaulted (LEOKA), 1960-2017Offenses Known and Cleared by Arrest (Return A), 1960-2017Property Stolen and Recovered (Supplement to Return A), 1960-2017

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates on or around July 17th, 2023.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

***In January 2020, as part of implementing a new citywide police incident reporting system the City began moving away from reporting crime to the FBI Unified Crime Reporting (UCR) Program and instead to the new National Incident-Based Reporting System (NIBRS) format. For this reason, 2020 UCR data may have inconsistencies and/or inaccuracies. A filtered view of UCR data is available for 2011-2019 at https://citydata.mesaaz.gov/Police/Crime-Reporting-Statistics-Uniform-Crime-Reporting/bfen-qa5d

As of January 1, 2021, the National Incident-Based Reporting System (NIBRS) became the national crime data collection program. NIBRS was implemented to improve the overall quality of crime data collected by law enforcement, by capturing details on each single crime incident, as well as on separate offenses within the same incident. The historic Summary Reporting System (SRS) data collection, which collects more limited information than the more robust NIBRS, was phased out to make Uniform Crime Reporting (UCR) a NIBRS-only data collection.

Coming soon, look for a new dataset based on NIBRS, which will provide more complete and comprehensive data for law enforcement, researchers, and the public.

The Uniform Crime Reporting Program collects statistics on the number of offenses known to City of Mesa Police Department. Address and Location data are not exact location of incidents and have been rounded to nearest hundred block. Lat/Long are approximations only based on rounded hundred block. Part 1 offenses are reported monthly and are chosen by the Federal Bureau of Investigation (FBI) because they are serious crimes, they occur with regularity in all areas of the country, and they are likely to be reported to police. Part I offenses are defined as: Criminal homicide, Forcible Rape, Robbery, Aggravated Assault, Burglary (breaking or entering), Larceny-theft (except motor vehicle theft), Motor vehicle theft and Arson.