AndreaBozzo/ceres-open-data-index huggingface dataset:
Louisville Metro KY -  Metro 311 Service Requests June 18th 2019 to December 18th 2019

## For over 30 years Metro311 has been the Louisville Metro customer service center. Metro311 is contacted with a question or concern. Questions are answered and denoted into the reporting system as a Non-Service Request (NSR). For concerns, a Service Request (SR) is entered into the system and based on the information provided, routed to the appropriate agency. The responsible agency handling the request will receive the report and inspect or investigate per their protocols. A SR number is generated and can be utilized to track the concern. ## ## ## ## The city o f Louisville adheres to the Open311.org [Data Standards] ## ## Data Dictionary ## ## ──────────────────┬────────────────────────────────────────────────────── ## Field name │Field description ## ──────────────────┼────────────────────────────────────────────────────── ## service_request_id│The unique ID of the concern created by the system. ## ──────────────────┼────────────────────────────────────────────────────── ## requested_datetime│The date and time the SR was made. ## ──────────────────┼────────────────────────────────────────────────────── ## updated_datetime │The date and time the SR was last modified ## ──────────────────┼────────────────────────────────────────────────────── ## source │How the SR was received. ## ──────────────────┼────────────────────────────────────────────────────── ## service_name │The name of the SR type ## ──────────────────┼────────────────────────────────────────────────────── ## description │A description of the SR submitted. ## ──────────────────┼────────────────────────────────────────────────────── ## agency_responsible│The agency responsible for addressing the SR. ## ──────────────────┼────────────────────────────────────────────────────── ## address │The location of the concern. ## ──────────────────┼────────────────────────────────────────────────────── ## council_district │council district of the location ## ──────────────────┼────────────────────────────────────────────────────── ## status_description│An indicator of the current state of the SR. ## ──────────────────┼────────────────────────────────────────────────────── ## lat │Latitude of the location, using the WGS84 projection. ## ──────────────────┼────────────────────────────────────────────────────── ## long │Longitude of the location, using the WGS84 projection. ## ──────────────────┴──────────────────────────────────────────────────────
Vaccination_Dist_dose_7days_booster

The data spans from December 2020 through October 2022, and is no longer being updated as of October 10, 2022. The Louisville Metro Department of Public Health and Wellness (LMPHW) is an independent, academic health department under the leadership of Connie Mendel. The department is organized under four divisions: Administration; Environmental; Health Services and the Center for Health Equity. The Administration division includes human resources, information technology, budget and logistics. Data Dictionary ──────────────┬────────────────────────────────────────────────────────────────────────────────────────────────── Field Name │Description ──────────────┼────────────────────────────────────────────────────────────────────────────────────────────────── WEEKENDINGDATE│The end date of the 7-day reporting period (typically a Friday) ──────────────┼────────────────────────────────────────────────────────────────────────────────────────────────── DOSE_ │Number of individuals who received their first dose of a COVID-19 vaccine during the week ──────────────┼────────────────────────────────────────────────────────────────────────────────────────────────── DOSE_ │Number of individuals who received their second dose (completing a 2-dose series) during the week. ──────────────┼────────────────────────────────────────────────────────────────────────────────────────────────── BOOSTER │Number of individuals who received a booster dose during the week. ──────────────┼────────────────────────────────────────────────────────────────────────────────────────────────── LOADED │The timestamp indicating when the data was loaded into the system. ──────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────
Louisville Metro KY - Russell WiFi Locations

The difference from projected coverage area is due to the built and natural environment near the access points. For example, building and tree downgrade the signal much like walls in your home disrupt you Wi-Fi connection. The data is static. Metro Technology Services (MTS) is the owner and responsible for updating this data. The core purpose of (MTS) is to enable Louisville Metro Government to deliver valued services to the community. This is accomplished by providing quality services that meet the needs of Metro Government agencies. Data Dictionary ───────────┬───────────────────────────── Data Fields│Fields Description ───────────┼───────────────────────────── Name │Location name ───────────┼───────────────────────────── Location │Address of the Wi-Fi Location ───────────┴─────────────────────────────
Louisville Metro KY - Noise Citation Management

This data is no longer being actively updated. The dataset is deprecated and will be removed from the Portal within the next three months. If you have any questions, please reach out to the Open Data team by filling out the following Contact Us form: [https://louisvilleky.wufoo.com/forms/open-data-contact-form/ ."] Noise Citation Management, for Noise Citation data since June 2019 please visit [This Link] and in the enforcement section under general search in the Record Type search field select “Noise Citation Management Case” enter any other parameters you want to limit your search by and click search to view current data. Codes and Regulations issues and inspects Development Permits (building, electrical, HVAC), enforces Property Maintenance Code (housing) and Land Development Code (zoning), issues ABC, taxi cab, vendor and other licenses and administers the Code Enforcement Board.
Louisville Metro KY - Permitted Body Ear Pierce and Tattoo Studios

A list of permitted studios. Data Dictionary: facility_type - Code for facility type facility_type_description - Code translation for facility type subtype - Code for facility subtype subtype_description - Code translation for facility subtype permit_number - permit number premise_name - name of facility premise_address - address of facility premise_city - city of facility premise_state - state of facility premise_zip - zip of facility opening_date - date facility was permitted by current owner 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 - Animal License Historical

Animal Services provides for the care and control of animals in the Louisville Metro area, including pet licensing and pet adoption. Louisville pets owners must license all dogs, cats and ferrets with LMAS. Pet licensing is a requirement of the [Louisville Animal Ordinance]. You can purchase a renewable pet license in one-year or three-year increments. Owners must show proof your pet's Rabies vaccination is up-to-date, to obtain a pet license. Being reunited with your pet is just a phone call away: 365 days a year, employees are on duty to help with the process. For those who find a lost licensed pet, it's your assurance that the pet has its updated rabies shots. If Animal Services finds your lost pet, we will escort it home. Data Dictionary: ──────────────────────┬─────────────────────────────────────────────────────────── Field name │Field description ──────────────────────┼─────────────────────────────────────────────────────────── Year │The year that the license was sold ──────────────────────┼─────────────────────────────────────────────────────────── Month │The month that the license was sold ──────────────────────┼─────────────────────────────────────────────────────────── Number of Tags Issued │The number of tags sold for each month and year by zip code ──────────────────────┼─────────────────────────────────────────────────────────── Animal Type │The type of animal licensed ──────────────────────┼─────────────────────────────────────────────────────────── Zip Code │ The zip code of the owner who purchased the license ──────────────────────┴───────────────────────────────────────────────────────────
Jefferson County KY - Midblock Crossings

Mid-block crossings offer pedestrians and bicyclists approved locations to legally cross a street other than a fully controlled intersection, such as an all-way stop or traffic signal. Mid-block crossings are typically installed in areas with high pedestrian activity and along pedestrian or bicyclist desire lines. The U.S. Department of Transportation’s Federal Highway Administration encourages mid-block crossings be equipped with adequate lighting, signs and markings, a Pedestrian Hybrid Beacon or Rectangular Rapid Flashing Beacon (RRFB), and curb extensions or a pedestrian refuge island, as appropriate. This list can be used by the public, researchers, and roadway owners, such as Louisville Metro Government or the state, to prioritize safety improvements at existing midblock crossing locations and help standardize criteria for considering requests for new crossings or evaluate existing locations. Contact Information: Claire Yates, Louisville Metro Public Works and Assets, Transportation Planner II, [claire.yates@louisvilleky.gov], (502) 574-3197.
Louisville Metro KY - Short Term Rental Conditional Use Permits

Location of Louisville Metro KY - Short-Term Rental Conditional Use Permits Addresses of Approved Short-Term Rentals with Conditional Use Permits Parcels affected by the 600 foot buffer around a Short-Term Rental with a Conditional Use Permit A short term rental of dwelling unit that is not the primary residence of the host or the short term rental of a condominium unit that is the primary residence of the host in a R-R, R-E, R-1, R-2, R3, R-4, R-5, U-N, R-5A, R-5B, R-6, R-7, or R-8A district and a short term rental of any dwelling unit in a TNZD district may be allowed upon the granting of a Conditional Use Permit.
Louisville Metro KY - Crime Data 2005

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 2010

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 2019

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 2017

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]