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

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

The following datasets contain the crime rate for cities in the United States. The four datasets are separated based on population ranges.

FILE DESCRIPTION

File names: - 'crime_40 _60.csv': dataset for population ranging from 40,000 to 60,000. - 'crime_60 _100.csv': dataset for population ranging from 60,000 to 100,000. - 'crime_100 _250.csv': dataset for population ranging from 100,000 to 250,000. - 'crime_250 _plus.csv': dataset for population greater than 250,000.

COLUMN DESCRIPTION

For file: crime_40 _60.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ The following datasets contain the crime rate for cities in the United States. The four datasets are separated based on population ranges.

FILE DESCRIPTION

File names: - 'crime_40 _60.csv': dataset for population ranging from 40,000 to 60,000. - 'crime_60 _100.csv': dataset for population ranging from 60,000 to 100,000. - 'crime_100 _250.csv': dataset for population ranging from 100,000 to 250,000. - 'crime_250 _plus.csv': dataset for population greater than 250,000.

COLUMN DESCRIPTION

For file: crime_40 _60.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft

crime_60 _100.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft

crime_100 _250.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft

crime_250 _plus.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'total_crime': total crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'total_violent _crime': total violent crime - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft - 'tot_prop _crime': total property crime - 'arson': arson

Photo by David von Diemar on Unsplash

Los Angeles Crime Data (2020 - Present)

📌 Updated: February 7, 2025

Overview

This dataset contains reported crime incidents in the City of Los Angeles from 2020 to the present, provided by the Los Angeles Police Department (LAPD). It includes key details such as crime type, location (anonymized), and date. The dataset is derived from official LAPD records and is regularly updated.

⚠️ Note: LAPD transitioned to a new Records Management System (RMS) on March 7, 2024, to comply with the FBI’s NIBRS (National Incident-Based Reporting System). During this transition, some crime data may still reflect the older system.

Dataset Highlights

✔ Crime Incidents: Reported cases from 2020 onwards ✔ Location Details: Anonymized to the nearest hundred block ✔ Reporting System: Transition to FBI's NIBRS compliance ✔ Data Accuracy: Transcribed from original LAPD reports

Important Notes

🔹 Temporary Reporting Delays – LAPD is experiencing technical issues affecting data updates. Until resolved, updates will be bi-weekly instead of weekly. 🔹 Data Limitations – Some missing location fields are recorded as (0°, 0°) due to privacy constraints. 🔹 Possible Inaccuracies – Crime reports are transcribed manually, leading to potential data errors.

Usage & Applications

✅ Crime trend analysis over time ✅ Crime hotspot detection & mapping ✅ Law enforcement and policy research ✅ Machine learning applications (predictive modeling)

Column Descriptions for Los Angeles Crime Data (2020 - Present)

Column Name and Description

DR_NO: Unique crime report number assigned by LAPD. Date Rptd: Date when the crime was reported to the LAPD (MM/DD/YYYY HH:MM:SS AM/PM). DATE OCC: Date when the crime occurred (MM/DD/YYYY HH:MM:SS AM/PM). TIME OCC: Time when the crime occurred, in 24-hour format (e.g., 2130 = 9:30 PM). AREA: Numerical code representing the LAPD division where the crime occurred. AREA NAME: Name of the LAPD division (e.g., Wilshire, Central, Southwest, etc.). Rpt Dist No: Reporting district number used internally by LAPD. Part 1-2: Crime category: 1 = Serious (violent/property crimes), 2 = Less serious crimes. Crm Cd: Crime classification code assigned by LAPD. Crm Cd Desc: Description of the crime, such as "Vehicle - Stolen" or "Burglary from Vehicle". Mocodes: Modus Operandi (MO) codes, which indicate methods used by criminals. Vict Age: Age of the victim (0 may indicate missing data). Vict Sex: Gender of the victim (M = Male, F = Female, X = Unknown). Vict Descent: Ethnicity of the victim, encoded as: W (White), B (Black), H (Hispanic), A (Asian), O (Other), etc. Premis Cd: Numerical code representing the type of location where the crime occurred. Premis Desc: Description of the location, such as "Street," "Bus Stop," "Apartment," etc. Weapon Used Cd: Weapon code, if a weapon was used in the crime (NaN if no weapon was involved). Weapon Desc: Description of the weapon (e.g., "Handgun", "Knife", "None"). Status: Case status, such as IC (Investigation Continued) or AA (Adult Arrest). Status Desc: Description of the case status, e.g., "Investigation Continued" or "Adult Arrest". Crm Cd 1 - Crm Cd 4: Additional crime codes, if multiple offenses occurred in the same incident. LOCATION: Nearest street address where the crime occurred. Cross Street: Cross street (if available) for additional location context. LAT Latitude: of the crime location. LON Longitude: of the crime location.

License & Attribution

Source: Los Angeles Police Department (LAPD) Terms of Use: This dataset follows specific non-federal licensing rules different from Data.gov. Attribution: If you use this dataset, please credit LAPD & Data.gov.

💬 Feedback & Discussion

If you notice any inconsistencies or have questions, please leave a comment below. Let's collaborate to improve crime data transparency! 🚀

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

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

This is the most current information as of the date of upload. This provides the user the ability to view the most current crime information within Kansas City, Missouri. The displayed information is the most current information from the data source as of the date of upload. The data source is dynamic and therefore constantly changing. Changes to the information may occur, as incident information is refined. While the Board of Police Commissioners of Kansas City, Missouri (Board) makes every effort to maintain and distribute accurate information, no warranties and/or representations of any kind are made regarding information, data or services provided. The Board is not responsible for misinterpretation of this information and makes no inference or judgment as to the relative safety to any particular area or neighborhood. In no event shall the Board be liable in any way to the users of this data. Users of this data shall hold the Board harmless in all matters and accounts arising from the use and/or accuracy of this data.

This table contains data on the rate of violent crime (crimes per 1,000 population) for California, its regions, counties, cities and towns. Crime and population data are from the Federal Bureau of Investigations, Uniform Crime Reports. Rates above the city/town level include data from city, university and college, county, state, tribal, and federal law enforcement agencies. The table is part of a series of indicators in the Healthy Communities Data and Indicators Project of the Office of Health Equity. Ten percent of all deaths in young California adults aged 15-44 years are related to assault and homicide. In 2010, California law enforcement agencies reported 1,809 murders, 8,331 rapes, and over 95,000 aggravated assaults. African Americans in California are 11 times more likely to die of assault and homicide than Whites. More information about the data table and a data dictionary can be found in the About/Attachments section.

🇺🇸 United States English 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

This dataset represents the Dallas Police Public Data - RMS Incidents beginning June 1, 2014 to current-date. The Dallas Police Department strives to collect and disseminate police report information in a timely, accurate manner. This information reflects crimes as reported to the Dallas Police Department as of the current date. Crime classifications are based upon preliminary information supplied to the Dallas Police Department by the reporting parties and the preliminary classifications may be changed at a later date based upon additional investigation. Therefore, the Dallas Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information contained herein and the information should not be used for comparison purposes over time. The Dallas 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.

This online site is an attempt to make it easier for citizens to access offense reports. In disseminating this crime information, we must also comply with current laws that regulate the release of potentially sensitive and confidential information. To ensure that privacy concerns are protected and legal standards are met, report data is "filtered" prior to being made available to the public. Among the exclusions are:

1.) Sexually oriented offenses 2.) Offenses where juveniles or children (individuals under 17 years of age) are the victim or suspect 3.) Listing of property items that are considered evidence 4.) Social Service Referral offenses 5.) Identifying vehicle information in certain offenses

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

https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F15666745%2F92a4d2a363485867bda0dc4dd6699c13%2FDesign.png?generation=1723995740709789&alt=media" alt="">

Well, Now that you’ve bravely crossed the virtual crime scene tape, find more details below👇

Description:

This dataset provides a detailed account of crime incidents reported in the City of Los Angeles from 2020 to the present day. The data is compiled from the Los Angeles Police Department (LAPD) and includes various features like the type of crime, date and time of occurrence, location, and demographic information of victims. With over four years of data, this dataset is invaluable for researchers, data scientists, and analysts who are interested in studying crime trends, identifying patterns, and developing predictive models to enhance public safety.

This dataset reflects incidents of crime in the City of Los Angeles dating back to 2020. The data is transcribed from original crime reports that are typed on paper, which may introduce some inaccuracies. Location fields with missing data are noted as (0°, 0°), and address fields are provided only to the nearest hundred block to maintain privacy. This data is as accurate as the data in the database.

Features:

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

The 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.com

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

Report Volume Data The report counts in this data set are broken down by activity sector, report type, the year and month of receipt, and reporting entity location. The reporting entity location is represented by the forward sortation area (FSA) component of the Canadian postal code (i.e. the first three characters of the Canadian postal code, e.g. “K1P”) that designates the postal district where the reporting entity is located. ##Modernization of Reporting Forms The Financial Transactions and Reports Analysis Centre of Canada (FINTRAC) is engaged in a multi-year initiative to implement important changes to its reporting forms. Part of this modernization now allows reporting entities to submit reports containing transactions from multiple locations, increasing efficiency and reducing burden. This will change how FINTRAC publishes statistics for reports that have been modernized. FINTRAC implemented the new Large Cash Transaction Report in October 2023. As such, reporting volume statistics for the Large Cash Transaction Report will be published at a national level for quarters 3 and 4 of 2023-2024 (from October to December, and January to March, respectively). The publication of this dataset has been temporarily paused to accommodate the transition to new reporting forms. This transition is part of our ongoing efforts to enhance the quality and consistency of the data we collect. ##Protecting the Identity of Reporting Entities By law, FINTRAC must protect the identity of the persons and entities that are required to submit financial transaction reports to the Centre under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act. In keeping with this responsibility to protect information, FINTRAC cannot provide more specific geographic data than is contained in this data set. Whenever possible, the data set includes the full FSA to identify the location of reporting entities submitting reports to FINTRAC. However, in any case where a certain location contains fewer than five reporting entities, or fewer than five reports submitted, only partial characters of the FSA are shown. This means that certain FSAs may contain only one or two characters (e.g., K or K1) instead of the standard three characters (e.g., K1P). In rare cases, it was not possible to provide a reporting entity location or report count without risking revealing the identity of reporting entities in a given activity sector or identifying a specific report, and so the data is provided at a national level only. All FSA levels are hierarchically inclusive. This means, for example, that the total number of report counts for K1 includes all reports submitted within all FSAs that start with K1 (i.e. K1A, K1B, K1C), including those that may not be visible because they include fewer than five reporting entities in a given activity sector. E&OE

This dataset consists of gun violence within Jefferson county that may fall within LMPDs radar, including non-fatal shootings, homicides, as well as shot-spotter data. The mapping data points where there are victims have been obfuscated to maintain privacy, while still being accurate enough to be placed in its correct boundaries, particularly around, neighborhoods, ZIP Codes, Council districts, and police divisions. The data also excludes any victim information that could be used to identify any individual. this data is used to make the public aware of what is going on in their communities. The data consists of only criminal incidents, excluding any cases that are deemed non-criminal.Field NameField DescriptionCase numberPolice report number. For ShotSpotter detections, it is the ShotSpotter ID.DateTimeDate and time in which the original incident occurred. Time is rounded down.AddressAddress rounded down to the one hundred block of where the initial incident occured. Unless it is an intersection.NeighborhoodNeighborhood in which the original incident occurred.Council DistrictCouncil district in which the original incident occurred.LatitudeLatitude coordinate used to map the incidentLongitudeLongitude coordinate used to map the incidentZIP CodeZIP Code in which the original incident occurred.Crime Typea distinction between incidents, whether it is a non-fatal shooting, homicide, or a ShotSpotter detection.CauseUsed to differentiate on the cause of death for homicide victims.SexGender of the victim of the initial incident.RaceRace/Ethnicity of the victim in a given incident.Age GroupCategorized age groups used to anonymize victim information.Division NamePolice division or department where the initial incident occurred.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities, unless LMPD becomes involved in smaller agency incident.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.Contact:Ivan Benitez, Ph.D.Gun Violence Data FellowOffice for Safe and Healthy Neighborhoodsivan.benitez@louisvilleky.gov

Introduction

Chicago is one of America's most iconic cities. It has a colorful history, which rich histories such. Recently, Chicago was also a setting for one of Netflix's popular series : Ozark. The story has it that Chicago is the center for drug distribution for the Navarro cartel.

So, how true is the series? A quick search on the internet reveals a recently released DEA report on the. The report shows that drug crime exists in Chicago, although they are distributed by the Cartel de Jalisco Nueva Generacion, the Sinaloa Cartel and the Guerros Unidos, to name a few.

Content

The government of the City of Chicago has provided a publicly available crime database accessible via Google BigQuery. I have downloaded a subset of the data with crime_type narcotics and year > 2015. The data contains records between 1 Jan 2016 UTC until 23 Jul 2020 UTC.

The dataset contains these columns : - case_number : ID of the record - date : Date of incident - iucr : Category of the crime, per Illinois Unified Crime Reporting (IUCR) code. [more](https://data.cityofchicago.org/widgets/c7ck-438e) -description: More detailed description of the crime -location_description: Location of the crime -arrest: Whether an arrest was made -domestic: Was the crime domestic? -district: Which district code where the crime happened. [more](https://data.cityofchicago.org/Public-Safety/Boundaries-Police-Districts-current-/fthy-xz3r) -ward: The ward code where the crime happened. [more](https://data.cityofchicago.org/Facilities-Geographic-Boundaries/Boundaries-Wards-2015-/sp34-6z76) -community_area` : The community area code where the crime happened. more

Acknowledgements

The data is owned and kindly provided by the City of Chicago.

Inspiration

Some questions to get you started:

1. Is there a trend? Is the crime increasing? or decreasing?
2. Is there seasonality? Are dealers more like to be out and about in summer? Do they deal inside in winter?
3. Are some activities more like to happen at certain locations?
4. We tend to think that more deals happen at night, especially as people wind down, and the surroundings get dark. Does the data reflect that?
5. Are the incidents clustered to a certain district? Certain type of location?

Lastly, if you are : - a newly recruited analyst at the DEA / police, what would you recommend? - asked by el jefe del cartel (boss of the cartel) on how to expand operation / operate better, what would you say?

Happy wrangling!

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

A list of all uniform citations from the Louisville Metro Police Department, the CSV file is updated daily, including case number, date, location, division, beat, offender demographics, statutes and charges, and UCR codes can be found in this Link.INCIDENT_NUMBER or CASE_NUMBER links these data sets together:Crime DataUniform Citation DataFirearm intakeLMPD hate crimesAssaulted OfficersCITATION_CONTROL_NUMBER links these data sets together:Uniform Citation DataLMPD Stops DataNote: When examining this data, make sure to read the LMPDCrime Data section in our Terms of Use.AGENCY_DESC - the name of the department that issued the citation CASE_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence rooms and can be used to connect the dataset to the following other datasets INCIDENT_NUMBER: 1. Crime Data 2. Firearms intake 3. LMPD hate crimes 4. Assaulted Officers NOTE: CASE_NUMBER is not formatted the same as the INCIDENT_NUMBER in the other datasets. For example: in the Uniform Citation Data you have CASE_NUMBER 8018013155 (no dashes) which matches up with INCIDENT_NUMBER 80-18-013155 in the other 4 datasets. CITATION_YEAR - the year the citation was issued CITATION_CONTROL_NUMBER - links this LMPD stops data CITATION_TYPE_DESC - the type of citation issued (citations include: general citations, summons, warrants, arrests, and juvenile) CITATION_DATE - the date the citation was issued CITATION_LOCATION - the location the citation was issued DIVISION - the LMPD division in which the citation was issued BEAT - the LMPD beat in which the citation was issued PERSONS_SEX - the gender of the person who received the citation PERSONS_RACE - the race of the person who received the citation (W-White, B-Black, H-Hispanic, A-Asian/Pacific Islander, I-American Indian, U-Undeclared, IB-Indian/India/Burmese, M-Middle Eastern Descent, AN-Alaskan Native) PERSONS_ETHNICITY - the ethnicity of the person who received the citation (N-Not Hispanic, H=Hispanic, U=Undeclared) PERSONS_AGE - the age of the person who received the citation PERSONS_HOME_CITY - the city in which the person who received the citation lives PERSONS_HOME_STATE - the state in which the person who received the citation lives PERSONS_HOME_ZIP - the zip code in which the person who received the citation lives VIOLATION_CODE - multiple alpha/numeric code assigned by the Kentucky State Police to link to a Kentucky Revised Statute. For a full list of codes visit: https://kentuckystatepolice.org/crime-traffic-data/ ASCF_CODE - the code that follows the guidelines of the American Security Council Foundation. For more details visit https://www.ascfusa.org/ STATUTE - multiple alpha/numeric code representing a Kentucky Revised Statute. For a full list of Kentucky Revised Statute information visit: https://apps.legislature.ky.gov/law/statutes/ CHARGE_DESC - the description of the type of charge for the citation UCR_CODE - the code that follows the guidelines of the Uniform Crime Report. For more details visit https://ucr.fbi.gov/ UCR_DESC - the description of the UCR_CODE. For more details visit https://ucr.fbi.gov/