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

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

,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, 2023,The data for Vehicle Stops for 2021. The data includes vehicle stops. Not included in the data are vehicle collisions, stranded motorists or non-moving vehicles. The Louisville Metro Police Department previously engaged the University of Louisville to conduct an analysis of LMPD’s vehicle stops.,The data includes vehicle stops. Not included in the data are vehicle collisions, stranded motorists or non-moving vehicles.,Data Dictionary:,,ID - the row number,TYPE_OF_STOP - category for the stop,CITATION_CONTROL_NUMBER -,ACTIVITY RESULTS - whether a warning or a citation was issued for the stop,OFFICER_GENDER - gender of the officer who made the stop,OFFICER_RACE - race of the officer who made the stop,OFFICER_AGE_RANGE - age range the officer who made the stop belonged to at the time of the stop,ACTIVITY_DATE - the date when the stop was made,ACTIVITY_TIME - the time when the stop was made,ACTIVITY_LOCATION - the location where the stop was made,ACTIVITY_DIVISION - the LMPD division where the stop was made,ACTIVITY_BEAT - the LMPD beat where the stop was made,DRIVER_GENDER - gender of the driver who was stopped,DRIVER_RACE - race of the driver who was stopped,DRIVER_AGE_RANGE - age range the driver who was stopped belonged to at the time of the stop,NUMBER OF PASSENGERS - number of passengers in the vehicle with the driver (excludes the driver),WAS_VEHCILE_SEARCHED - Yes or No whether the vehicle was searched at the time of the stop,,REASON_FOR_SEARCH - if the vehicle was searched, the reason the search was done, please see codes below,CONSENT - 01 TERRY STOP OR PAT DOWN - 02 INCIDENT TO ARREST - 03 PROBABLE CAUSE - 04 OTHER – 05,

,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, 2023,The data for Vehicle Stops for 2022. The data includes vehicle stops. Not included in the data are vehicle collisions, stranded motorists or non-moving vehicles. The Louisville Metro Police Department previously engaged the University of Louisville to conduct an analysis of LMPD’s vehicle stops.,The data includes vehicle stops. Not included in the data are vehicle collisions, stranded motorists or non-moving vehicles.,Data Dictionary:,,ID - the row number,TYPE_OF_STOP - category for the stop,CITATION_CONTROL_NUMBER -,ACTIVITY RESULTS - whether a warning or a citation was issued for the stop,OFFICER_GENDER - gender of the officer who made the stop,OFFICER_RACE - race of the officer who made the stop,OFFICER_AGE_RANGE - age range the officer who made the stop belonged to at the time of the stop,ACTIVITY_DATE - the date when the stop was made,ACTIVITY_TIME - the time when the stop was made,ACTIVITY_LOCATION - the location where the stop was made,ACTIVITY_DIVISION - the LMPD division where the stop was made,ACTIVITY_BEAT - the LMPD beat where the stop was made,DRIVER_GENDER - gender of the driver who was stopped,DRIVER_RACE - race of the driver who was stopped,DRIVER_AGE_RANGE - age range the driver who was stopped belonged to at the time of the stop,NUMBER OF PASSENGERS - number of passengers in the vehicle with the driver (excludes the driver),WAS_VEHCILE_SEARCHED - Yes or No whether the vehicle was searched at the time of the stop,,REASON_FOR_SEARCH - if the vehicle was searched, the reason the search was done, please see codes below,CONSENT - 01 TERRY STOP OR PAT DOWN - 02 INCIDENT TO ARREST - 03 PROBABLE CAUSE - 04 OTHER – 05,

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

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

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

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

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

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