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

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

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

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

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

🇺🇸 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 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

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

Content

Data is a culmination of separate csv files found at https://data.louisvilleky.gov/dataset/crime-data

Each row represents a reported crime

The following description is from https://data.louisvilleky.gov/dataset/crime-data:

DATE_REPORTED - the date the incident was reported to LMPD

DATE_OCCURED - the date the incident actually occurred

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

Acknowledgements

Thank you to Louisville OPEN DATA!

https://data.louisvilleky.gov/dataset/crime-data

Inspiration

Which crimes are most common? In which zip codes is crime more likely to occur? Is there a trend of some crimes increasing and other decreasing in number? Which crimes take longest to report? Which beats handle the most homicides?

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Louisville/Jefferson County, KY-IN Metropolitan Statistical Area (MSA), including incidents, statistics, demographics, and agency information across multiple jurisdictions.

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

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for University of Louisville Police Department (University or College) in Kentucky, including incidents, statistics, demographics, and detailed incident information.

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Louisville Police Department (City) in Kentucky, including incidents, statistics, demographics, and detailed incident information.

Graph and download economic data for Combined Violent and Property Crime Offenses Known to Law Enforcement in Henry County, KY (DISCONTINUED) (FBITC021103) from 2005 to 2021 about Henry County, KY; crime; violent crime; property crime; Louisville; KY; and USA.

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 location

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Louisville Police Department (City) in Mississippi, including incidents, statistics, demographics, and detailed incident information.

FBI National Incident-Based Reporting System (FBI NIBRS) crime data for Louisville Regional Airport Authority (Other) in Kentucky, including incidents, statistics, demographics, and detailed incident information.

Note: Due to a system migration, this data will cease to update on March 14^th, 2023. The current projection is to restart the updates within 30 days of the system migration, on or around April 13^th, 2023

Data is subset of the Incident data provided by the open data portal. This data specifically identifies crimes that meet the elements outlined under the FBI Hate crimes program since 2010. For more information on the FBI hate crime overview please visit
https://www.fbi.gov/about-us/investigate/civilrights/hate_crimes

Data Dictionary:

ID - the row number

INCIDENT_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 other LMPD datasets:
DATE_REPORTED - the date the incident was reported to LMPD

DATE_OCCURED - the date the incident actually occurred

CRIME_TYPE - the crime type category

BIAS_MOTIVATION_GROUP - Victim group that was targeted by the criminal act

BIAS_TARGETED_AGAINST - Criminal act was against a person or property

UOR_DESC - Uniform Offense 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

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

Three crime data sources were collected and merged for this study. All three crime sources were either only reporting on the U.S. state of Kentucky (KOOL and Louisville Open Data), or filtered to only contain results for the U.S. state of Kentucky (FBI). Each data source contains unique features such as crime classifications, and unique challenges in collection and cleaning.

The United States Federal Bureau of Investigation (FBI) issues a variety of query-able crime related data on their website. This data is sourced from law enforcement agencies across the U.S. as part of their National Incident-Based Reporting System (NIBRS) and its standards. The goal of gathering, standardizing, and providing this information is to facilitate research into crime and law enforcement patterns. The information is provided as a collection of CSV files with instructions and code for importing into a SQL database. For the purposes of this research, we utilized the the crime databases for the years 2017, 2018 and 2019, containing a total of 1,939,990 unique incidents. The NIBRS_code property denotes the type of crime as assigned by the reporting agency. The human trafficking codes are 40A (Prostitution), 40B (Assisting or Promoting Prostitution), and 370 (Pornography/Obscene Material). The drug incidents were found using codes 35A (Drug/Narcotic Violations) and 35B (Drug Equipment Violations).

The Kentucky Department of Corrections, as a service to the public, provides an online lookup of people currently in its custody called Kentucky Offender Online Lookup (KOOL). This web application offers users tools to search for sets of inmates based on features such as name, crime date, crime name, race, and gender. The data that KOOL searches contains only people who are currently under supervision of the state of Kentucky (or should be under supervision in the case of escape).

The Louisville Open Data Initiative (LOD) is a program from the city of Louisville, Kentucky, U.S.A. to increase the transparency of the city government and promote technological innovation. As part of LOD, a dataset of crime reports is made available online. The records contained within the LOD dataset represent any call for police service where a police incident report was generated. This does not necessarily mean a crime was committed, as an incident report can be generated before an investigation has taken place.

{{description}}

Graph and download economic data for Combined Violent and Property Crime Offenses Known to Law Enforcement in Spencer County, KY (DISCONTINUED) (FBITC021215) from 2005 to 2021 about Spencer County, KY; crime; violent crime; property crime; Louisville; KY; and USA.