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

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 2016

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 2015

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 - Firearm data intersections January 1st, 2010-February 22nd, 2017

A subset of parent FIREARM DATA.csv, this file contains only intersections of seized firearms, with limited success in geocoding from Lojic ArcGIS geocoder. This file contains X and Y coordinates in Kentucky State Plane North coordinate system, in addition to converted Latitude and Longitude coordinates. Data Dictionary: 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 the other datasets UCR_CATEGORY - the UCR based highest offense associated with the incident. For more information on UCR standards please visit [https://ucr.fbi.gov/ucr] TYPE_OF_FIREARM - based on the Firearm type, eg “pistol, revolver” or “shotgun, pump action” this field is for general categorization of the Firearm. FIREARMS_MANUFACTURE - the group, or company who manufactured the Firearm FIREARMS_MODEL - secondary information used to identify the Firearm. FIREARMS_CALIBER - the caliber associated with the Firearm, we use federally supplied caliber codes. RECOVERY_DATE - the date the item was identified or taken into custody. RECOVERY_BLOCK_ADRESS - the location the items was identified or taken into custody. RECOVERY_ZIPCODE - the zip code associated to the recovery block location. PERSON_RECOVERED_FROM RACE - the race associated with person who identified the item or was taken into custody from. The person listed may be the person who found the item, not the person associated with the firearm or offense. PERSON_RECOVERED_FROM _SEX - the sex associated with person who identified the item or was taken into custody from. The person listed may be the person who found the item, not the person associated with the firearm or offense. PERSON_RECOVERED_FROM AGE - the age associated with person who identified the item or was taken into custody from. The person listed may be the person who found the item, not the person associated with the firearm or offense. YEAR - the year the incident happened, useful for times the data is masked.
Louisville Metro KY - Crime Data 2018

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 2003

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 Employee Characteristics

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. LMPD employee characteristic data including Race, Gender, Current Age, Date Hired, Education Level, Job Title and Assigned Division. LMPD characteristics CSV file is updated on daily frequency. Data Dictionary: AOC_CODE - the badge number of the employee RANK_TITLE - the sworn rank of the employee OFFICER_SEX - the gender of the employee OFFICER_RACE - the race of the employee OFFICER_AGE_RANGE - the range of ages that the employee's current age falls into OFFICER_DIVISION - the division where the employee is currently assigned OFFICER_ASSIGNMENT - the employee's job assignment in the division OFFICER_YEARS_SWORN - the number of years that the employee has been a sworn employee
Louisville Metro KY - OSS Clients Demographics

For the purpose of our partners and the community to find demographic information on individual member of households that applied for services provided by the Office of Social Services. The data is updated anually based on the previous fiscal year and it includes: * Client Index * Household Index * Race * Gender * Ethnicity * Disability Status * Military Status * Health Insurance (Y/N) * Employment Status * Education Status * Head of Household (Y/N) * Age The focus of the Office of Social Services (OSS) is to provide essential services for Louisville residents, especially for low and moderate income populations, including: preventing homelessness; delivering Meals on Wheels; helping families build financial stability and security; operating LIHEAP to help residents stay safe and warm; making microloans to jumpstart small businesses; and supporting eight Neighborhood Places.
OSS Households Demographics

For the purpose of our partners and the community to find demographic information on household that applied for services with the Office of Social Services. This data is updated Quarterly and it includes: * Household Index * Date Added (to RCS database) * Housing Type * Household Type * Annual Income * ZIP Code The focus of the Office of Social Services (OSS) is to provide essential services for Louisville residents, especially for low and moderate income populations, including: preventing homelessness; delivering Meals on Wheels; helping families build financial stability and security; operating LIHEAP to help residents stay safe and warm; making microloans to jumpstart small businesses; and supporting eight Neighborhood Places.
Jefferson County KY Buildings without Building Heights

The BG theme represents roofline boundaries of manmade structures identifiable from aerial photography. A building is a manmade structure which may be habitable by human beings, animals or which stores materials and is at a minimum 10' x 10' in roof top area. A building may house a variety of activities at one time, or sequentially over its life. A feature classified as building but not having a roof (silo, tank or water tower) will show outline of the features shape. Planimetric and Topographic mapping of Jefferson , Kentucky. The Jefferson County layers use the Horizontal 1983 North American Datum, Kentucky State Plane North Zone. New data was digitized by NV5 in Spring 2025 using recently acquired imagery from Spring 2024.
Louisville Metro KY - Environmental Health Bulk Data - Complaints

Attributes of Public Health related complaints reported by the public and investigated by Louisville Metro Department of Public Health and Wellness. Personal/identifying data has been removed. EstID column can be joined to the EstablishmentID column in the Establishments table to show attributes of the establishment when a regulated establishment is involved. Data Dictionary: RequestComplaintID-System ID Rcode-Code for Type of Complaint or Request RCodeDescription-Text of type of complaint or request EHS-the license number of the technician investigating section-complaint section TakenBy-who took the complaint or service request Method-how the complaint or service request was taken in Duplicate-is this a duplicate request? System notation EstID-Associated permitted facility if applicable oss_id-associated onsite sewage file if applicable RequestDate-date of request or complaint ResolvedDate-date request or complaint was resolved NextInspDate-scheduled next inspection date IsCityorCounty-is this a city or county request? Status-is the request open or resolved? RequestType-request type IsFollowUp-is this a folowo up entry to an already open request OwnerType- Owner or agent? If applicable PersonOrPremiseZip-zip code of subject person ComplaintantZip-zip code of person making the complaint OwnerZip-zip code of the owner of the premises if applicable Health and Wellness Protects and promotes the health, environment and well being of the people of Louisville, providing health-related programs and health office locations community wide. Contact: Gerald Kaforski [gerald.kaforski@louisvilleky.gov]
Louisville Metro KY - Inspection Results School Food Service

A list of permitted school food service establishments and their last three inspection results. Data Dictionary: ScoreRecent - Most recent inspection score GradeRecent - Most recent inspection grade DateRecent - Most recent inspection date Score2 - 2nd most recent inspection score Grade2 - 2nd most recent inspection grade Date2 - 2nd most recent inspection date Score3 - 3rd most recent inspection score Grade3 - 3rd most recent inspection grade Date3 - 3rd most recent inspection date permit_number - facility permit number facility_type - facility type code facility_type_description - text description of facility type subtype - facility subtype code subtype_description - text description of facility subtype premise_name - facility name premise_address - facility address premise_city - facility city premise_state - facility state premise_zip - facility zip code opening_date - date current owner was first permitted Health and Wellness Protects and promotes the health, environment and well being of the people of Louisville, providing health-related programs and health office locations community wide. Contact: Gerald Kaforski [gerald.kaforski@louisvilleky.gov]
Louisville Metro KY - LMPD Stops Data 2020

The data for Vehicle Stops for 2020. 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