Edited by MetroSafe. Efforts were made to include/exclude specific Address points from ZIP code regions. As a result, boundary areas not conforming to coincident parcel boundary, road edge, or street centerline features should be seen as interpolated/extrapolated, and not geographically certain beyond a general measure. View detailed metadata.

GIS Feature class polygon of Zip codes in Jefferson County joined with Latest Confirmed Cases by Zip code without Long Term Care and Population of 2019 ACS Demographic Data by Zip code. This feature is used in the Covid-19 Jefferson County Public Hub Site https://covid-19-in-jefferson-county-ky-lojic.hub.arcgis.com/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.

** The data set is no longer being updated.Human Resources provides efficient, high quality, customer-oriented personnel services to Metro Government employees, city agencies and those seeking employment consistent with legal mandates.

Provides weekly account of rate of first doses given to Jefferson County residents by zip code. ACS 2019 demographics are referenced in population counts and calculations. Fieldname Definition Group_type Currently, the group types are based on Age. Group_Type Group Description AG_12to18 Age group 12 to 18 AG_60 Age group 60+ AG_60to69 Age group 60 to 69 AG_70 Age group 70+ TOTAL All ages zipcode zipcode of region where the recipient resides WEEKENDINGDATE Last full Week-ending date a dose was administered to the recipient population_count Estimated total population in the zipcode from the ref.Zip_ACS2019_AgeGroups table AG_12to18 leverages the Bridged-Race Population Estimates to use a factor of 0.70136413 * Zip_ACS2019_AgeGroups estimates to establish current population estimates for this age group. Total_Dose_1 number of recipients, to date, who received the first dose in the zipcode, by Group_type Completed_Series number of recipients, to date, who completed their vaccination series in the zipcode, by Group_type Dose_1_rate_per100k The number of recipients who received the first dose in zipcode per 100k, by Group_type Total_Dose_1100000.0/ population_count Completed_Series_rate_per100k The number of recipients who received the first dose in zipcode per 100k, by Group_type (Total_JSN +Total_Dose_2)100000.0/ population_count 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.

GIS Feature class polygon of Zip codes in Jefferson County joined with Latest Confirmed Cases by Zip code with Long Term Care and Population of 2019 ACS Demographic Data by Zip code. This feature is used in the Covid-19 Jefferson County Public Hub Site https://covid-19-in-jefferson-county-ky-lojic.hub.arcgis.com/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 Public Health and Wellness has a Testing Taskforce (now combined with the Vaccine Taskforce) pulling together labs and healthcare systems in Jefferson County to coordinate COVID-19 testing efforts and response across the country.Data Dictionary Field Name Field Type Field Description ID Integer Unique identifier Date Date Data the tests were reported. Centers Text Center the tests were conducted. No of Tests Integer No of test as the reported date Address Text address of the testing center Council District Integer council district where the testing center belong to Zip Code Text Zip code of the testing center

Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

The purpose of this project is to pay electric and water/sewer expenses for residents who would otherwise have their utilities turned off.Data DictionaryField NameField TypeField DescriptionReference IdTextID for the beneficiaries of the projectsAccountIntegerAccount ID generated for beneficiaries of the project.Agency ApplicationTextThe application source, whether it was directly from the agency or from outside the agency. Relief ProgramTextThe program involves in carrying out the project.DateDateDate application was made.Relief AmountFloatThe amount the beneficiary got from the project.Monthly HouseholdIncomeFloatThe cumulative income of the all the individuals in the household that benefited from the program.Household Sizeintegerthe total number of people in the householdLive In Jefferson CountyTextDoes the beneficiary live in Jefferson town?Financial HardshipTextIs the reason for the application financial hardship?Job LossTextIs the reason for the application Job loss?Reduced HoursTextIs the reason for the application reduction in work hours?Account TypeTextThe type of housing the beneficiary is applying with.ZipTextZip code of the address of the beneficiary CountryTextCountry of the address of the beneficiary StateTextState of the address of the beneficiary LocationTextA concatenation of zip codes, state and countryCouncil DistrictIntegerCouncil district the beneficiary resides.

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates within 30 days of the system migration, on or around April 13th, 2023Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities. The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics. Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred). Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained. Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.com Data Dictionary: INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence rooms DATE_REPORTED - the date the incident was reported to LMPD DATE_OCCURED - the date the incident actually occurred BADGE_ID - UOR_DESC - Uniform Offense Reporting code for the criminal act committed CRIME_TYPE - the crime type category NIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/view UCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime. LMPD_DIVISION - the LMPD division in which the incident actually occurred LMPD_BEAT - the LMPD beat in which the incident actually occurred PREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant) BLOCK_ADDRESS - the location the incident occurred CITY - the city associated to the incident block location ZIP_CODE - the zip code associated to the incident block location ID - Unique identifier for internal database Contact: Crime Information Center CrimeInfoCenterDL@louisvilleky.gov

This project will expand Wi-Fi across Metro Parks to help close the digital divide, providing hundreds of access points that can be used by residents to connect to the internet.

Field Name

Field Type

Field Description

Name

String

The Park's name

Address

String

Address to locate the park

ZIPCODE

Integer

The zip code of the location

COUNDIST

Integer

The Council District of the location

Status

String

The connection status of the Wi-Fi in the park

This data aligns with WWC Certification requirements, and serves as the basis for our data warehouse and open data roadmap. It's a continual work in progress across all departments.Louisville Metro Technology Services builds data and technology platforms to ready our government for our community’s digital future.Data Dictionary:

Field Name

Description

Dataset Name

The official title of the dataset as listed in the inventory.

Brief Description of Data

A short summary explaining the contents and purpose of the dataset.

Data Source

The origin or system from which the data is collected or generated.

Home Department

The primary department responsible for the dataset.

Home Department Division

The specific division within the department that manages the dataset.

Data Steward (Business) Name

The name of person responsible for the dataset’s accuracy and relevance.

Data Custodian (Technical) Name)

The technical contact responsible for maintaining and managing the dataset infrastructure.

Data Classification

The sensitivity level of the data (e.g., Public, Internal, Confidential)

Data Format

The file format(s) in which the dataset is available (e.g., CSV, JSON, Shapefile).

Frequency of Data Change

How often the dataset is updated (e.g., Daily, Weekly, Monthly, Annually).

Time Spam

The overall time period the dataset covers.

Start Date

The beginning date of the data collection period.

End Date

The end date of the data collection period

Geographic Coverage

The geographic area that the dataset pertains to (e.g., Louisville Metro).

Geographic Granularity

The level of geographic detail (e.g., parcel, neighborhood, ZIP code).

Link to Existing Publication

A URL linking to the dataset’s public-facing page or open data portal entry.

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.comData Dictionary:

Field Name

Field Description

Incident Number

the number associated with either the incident or used as reference to store the items in our evidence rooms

Date Reported

the date the incident was reported to LMPD

Date Occurred

the date the incident actually occurred

Badge ID

Badge ID of responding Officer

Offense Classification

NIBRS Reporting category for the criminal act committed

Offense Code Name

NIBRS Reporting code for the criminal act committed

NIBRS_CODE

the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/view

NIBRS Group

hierarchy that follows the guidelines of the FBI National Incident Based Reporting System

Was Offense Completed

Status indicating whether the incident was an attempted crime or a completed crime.

LMPD Division

the LMPD division in which the incident actually occurred

LMPD Beat

the LMPD beat in which the incident actually occurred

Location Category

the type of location in which the incident occurred (e.g. Restaurant)

Block Address

the location the incident occurred

City

the city associated to the incident block location

Zip Code

the zip code associated to the incident block location

Contact:LMPD Open Records lmpdopenrecords@louisvilleky.gov

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.comData Dictionary:Field NameField DescriptionIncident Numberthe number associated with either the incident or used as reference to store the items in our evidence roomsDate Reportedthe date the incident was reported to LMPDDate Occurredthe date the incident actually occurredBadge IDBadge ID of responding OfficerOffense ClassificationNIBRS Reporting category for the criminal act committedOffense Code NameNIBRS Reporting code for the criminal act committedNIBRS_CODEthe 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/viewNIBRS Grouphierarchy that follows the guidelines of the FBI National Incident Based Reporting SystemWas Offense CompletedStatus indicating whether the incident was an attempted crime or a completed crime.LMPD Divisionthe LMPD division in which the incident actually occurredLMPD Beatthe LMPD beat in which the incident actually occurredLocation Categorythe type of location in which the incident occurred (e.g. Restaurant)Block Addressthe location the incident occurredCitythe city associated to the incident block locationZip Codethe zip code associated to the incident block locationContact:LMPD Open Records lmpdopenrecords@louisvilleky.gov

This data aligns with WWC Certification requirements, and serves as the basis for our data warehouse and open data roadmap. It's a continual work in progress across all departments.Louisville Metro Technology Services builds data and technology platforms to ready our government for our community’s digital future.Data Dictionary:Field NameDescriptionDataset NameThe official title of the dataset as listed in the inventory.Brief Description of DataA short summary explaining the contents and purpose of the dataset.Data SourceThe origin or system from which the data is collected or generated.Home DepartmentThe primary department responsible for the dataset.Home Department DivisionThe specific division within the department that manages the dataset.Data Steward (Business) NameThe name of person responsible for the dataset’s accuracy and relevance.Data Custodian (Technical) Name)The technical contact responsible for maintaining and managing the dataset infrastructure.Data ClassificationThe sensitivity level of the data (e.g., Public, Internal, Confidential)Data FormatThe file format(s) in which the dataset is available (e.g., CSV, JSON, Shapefile).Frequency of Data ChangeHow often the dataset is updated (e.g., Daily, Weekly, Monthly, Annually).Time SpamThe overall time period the dataset covers.Start DateThe beginning date of the data collection period.End DateThe end date of the data collection periodGeographic CoverageThe geographic area that the dataset pertains to (e.g., Louisville Metro).Geographic GranularityThe level of geographic detail (e.g., parcel, neighborhood, ZIP code).Link to Existing PublicationA URL linking to the dataset’s public-facing page or open data portal entry.

Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

This dataset consists of gun violence within Jefferson county that may fall within LMPDs radar, including non-fatal shootings, homicides, as well as shot-spotter data. The mapping data points where there are victims have been obfuscated to maintain privacy, while still being accurate enough to be placed in its correct boundaries, particularly around, neighborhoods, ZIP Codes, Council districts, and police divisions. The data also excludes any victim information that could be used to identify any individual. this data is used to make the public aware of what is going on in their communities. The data consists of only criminal incidents, excluding any cases that are deemed non-criminal.Field NameField DescriptionCase numberPolice report number. For ShotSpotter detections, it is the ShotSpotter ID.DateTimeDate and time in which the original incident occurred. Time is rounded down.AddressAddress rounded down to the one hundred block of where the initial incident occured. Unless it is an intersection.NeighborhoodNeighborhood in which the original incident occurred.Council DistrictCouncil district in which the original incident occurred.LatitudeLatitude coordinate used to map the incidentLongitudeLongitude coordinate used to map the incidentZIP CodeZIP Code in which the original incident occurred.Crime Typea distinction between incidents, whether it is a non-fatal shooting, homicide, or a ShotSpotter detection.CauseUsed to differentiate on the cause of death for homicide victims.SexGender of the victim of the initial incident.RaceRace/Ethnicity of the victim in a given incident.Age GroupCategorized age groups used to anonymize victim information.Division NamePolice division or department where the initial incident occurred.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities, unless LMPD becomes involved in smaller agency incident.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Contact:Ivan Benitez, Ph.D.Gun Violence Data FellowOffice for Safe and Healthy Neighborhoodsivan.benitez@louisvilleky.gov

Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates on or around July 17th, 2023.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates on or around July 17th, 2024.Incidents of Officers assaulted by individuals since 2010.Data Dictionary:ID - the row numberDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredCRIME_TYPE - the crime type category (assault or homicide)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/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedLEOKA_APPLIES - whether or not the incident is reported to the Center for the Study of Law Enforcement Officers Killed and Assaulted (LEOKA). For more information visit https://leoka.org/OFFICER_KILLED - whether or not an officer was killed due to the incidentTYPE_OF_ASSIGNMENT - how the officer was assigned at the time of the incident (e.g. ONE-MAN VEHICLE ALONE (UNIFORMED OFFICER))TYPE_OF_ACTIVITY - the type of activity the officer was doing at the time of the incident (e.g. RESPONDING TO DISTURBANCE CALLS)OFFENSE_CITY - the city associated to the incident block locationOFFENSE_ZIP - 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 on or around July 17th, 2024.A list of all uniform citations from the Louisville Metro Police Department, the CSV file is updated daily, including case number, date, location, division, beat, offender demographics, statutes and charges, and UCR codes can be found in this Link.INCIDENT_NUMBER or CASE_NUMBER links these data sets together:Crime DataUniform Citation DataFirearm intakeLMPD hate crimesAssaulted OfficersCITATION_CONTROL_NUMBER links these data sets together:Uniform Citation DataLMPD Stops DataNote: When examining this data, make sure to read the LMPDCrime Data section in our Terms of Use.AGENCY_DESC - the name of the department that issued the citationCASE_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 following other datasets INCIDENT_NUMBER:1. Crime Data2. Firearms intake3. LMPD hate crimes4. Assaulted OfficersNOTE: CASE_NUMBER is not formatted the same as the INCIDENT_NUMBER in the other datasets. For example: in the Uniform Citation Data you have CASE_NUMBER 8018013155 (no dashes) which matches up with INCIDENT_NUMBER 80-18-013155 in the other 4 datasets.CITATION_YEAR - the year the citation was issuedCITATION_CONTROL_NUMBER - links this LMPD stops dataCITATION_TYPE_DESC - the type of citation issued (citations include: general citations, summons, warrants, arrests, and juvenile)CITATION_DATE - the date the citation was issuedCITATION_LOCATION - the location the citation was issuedDIVISION - the LMPD division in which the citation was issuedBEAT - the LMPD beat in which the citation was issuedPERSONS_SEX - the gender of the person who received the citationPERSONS_RACE - the race of the person who received the citation (W-White, B-Black, H-Hispanic, A-Asian/Pacific Islander, I-American Indian, U-Undeclared, IB-Indian/India/Burmese, M-Middle Eastern Descent, AN-Alaskan Native)PERSONS_ETHNICITY - the ethnicity of the person who received the citation (N-Not Hispanic, H=Hispanic, U=Undeclared)PERSONS_AGE - the age of the person who received the citationPERSONS_HOME_CITY - the city in which the person who received the citation livesPERSONS_HOME_STATE - the state in which the person who received the citation livesPERSONS_HOME_ZIP - the zip code in which the person who received the citation livesVIOLATION_CODE - multiple alpha/numeric code assigned by the Kentucky State Police to link to a Kentucky Revised Statute. For a full list of codes visit: https://kentuckystatepolice.org/crime-traffic-data/ASCF_CODE - the code that follows the guidelines of the American Security Council Foundation. For more details visit https://www.ascfusa.org/STATUTE - multiple alpha/numeric code representing a Kentucky Revised Statute. For a full list of Kentucky Revised Statute information visit: https://apps.legislature.ky.gov/law/statutes/CHARGE_DESC - the description of the type of charge for the citationUCR_CODE - the code that follows the guidelines of the Uniform Crime Report. For more details visit https://ucr.fbi.gov/UCR_DESC - the description of the UCR_CODE. For more details visit https://ucr.fbi.gov/