AndreaBozzo/ceres-open-data-index huggingface dataset:
Louisville Metro KY - Crime Data 2022

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]
Louisville Metro KY - LMPD Stops Data 2023

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 on or around July 17^{th}, 2024. The data for Vehicle Stops for 2023. 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
Vaccination doses distributed to Jefferson County, KY residents Weekly

This data set is no longer being updated and is historical, last update 10/10/2022. Provides number of doses, by dose number, distributed to Jefferson County residents over 7 day period as defined by CDC. Note: Not all residents Of Jefferson County receive their dose from Jefferson County, KY Agencies. ──────────────┬─────────────────────────────────────────────────────────────────────────── Fieldname │Definition ──────────────┼─────────────────────────────────────────────────────────────────────────── admin_date │Week-Ending date the dose was administered to the recipient ──────────────┼─────────────────────────────────────────────────────────────────────────── dose │Dose sequence ──────────────┼─────────────────────────────────────────────────────────────────────────── last_7days │total number of doses administered on the admin_date including last 7 days ──────────────┼─────────────────────────────────────────────────────────────────────────── rolling_total │total number of doses administered up to and including the admin_date ──────────────┼─────────────────────────────────────────────────────────────────────────── LOADED │date the data was loaded into the system ──────────────┴─────────────────────────────────────────────────────────────────────────── Note: This data is preliminary, routinely updated, and is subject to change For questions about this data please contact Angela Graham (Angela.Graham@louisvilleky.gov) or YuTing Chen (YuTing.Chen@louisvilleky.gov) or call (502) 574-8279.
Louisville Metro KY - Crime Data 2013

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]
Louisville Metro KY - Crime Data 2020

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]
Louisville Metro KY - Crime Data 2004

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]
Louisville Metro KY - Crime Data 2008

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]
Louisville Metro KY - Crime Data 2021

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 on or around July 17^{th}, 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 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]
Louisville Metro KY - LMPD Stops Data 2022

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 on or around July 17^{th}, 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