데이터셋 상세
미국
Louisville Metro KY - Annual Open Data Report 2021
,On October 15, 2013, Louisville Mayor Greg Fischer announced the signing of an open data policy executive order in conjunction with his compelling talk at the 2013 Code for America Summit. In nonchalant cadence, the mayor announced his support for complete information disclosure by declaring, "It's data, man.",Sunlight Foundation - New Louisville Open Data Policy Insists Open By Default is the Future,Section 5.A. Within one year of the effective Data of this Executive Order, and thereafter no later than September 1 of each year, the Open Data Management Team shall submit to the Mayor an annual Open Data Report.,The Open Data Management team (also known as the Data Governance Team is currently led by the city's Data Officer Andrew McKinney in the Office of Civic Innovation and Technology. Previously (2014-16) it was led by the Director of IT.,
데이터 정보
연관 데이터
Louisville Metro KY - Library Collection Inventory
공공데이터포털
,
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 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 2024
공공데이터포털
,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.com,Data Dictionary:,Contact:,LMPD Open Records,lmpdopenrecords@louisvilleky.gov,
Louisville Metro KY - Crime Data 2023
공공데이터포털
,Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates within 30 days of the system migration, on or around April 13th, 2023,Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.,The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.,Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).,Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.,Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.com,Data Dictionary:,INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence rooms,DATE_REPORTED - the date the incident was reported to LMPD,DATE_OCCURED - the date the incident actually occurred,BADGE_ID -,UOR_DESC - Uniform Offense Reporting code for the criminal act committed,CRIME_TYPE - the crime type category,NIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/view,UCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/,ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.,LMPD_DIVISION - the LMPD division in which the incident actually occurred,LMPD_BEAT - the LMPD beat in which the incident actually occurred,PREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant),BLOCK_ADDRESS - the location the incident occurred,CITY - the city associated to the incident block location,ZIP_CODE - the zip code associated to the incident block location,ID - Unique identifier for internal database,Contact:,Crime Information Center,CrimeInfoCenterDL@louisvilleky.gov,
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 2009
공공데이터포털
,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 - National Emissions Inventory
공공데이터포털
,Emissions inventories: emissions reported by regulated facilities and modeled emissions from vehicles, smaller sources, wildfires, etc. Can select data by pollutant and/or geography, then download the resulting data set.,2014 data: https://www.epa.gov/air-emissions-inventories/2014-national-emissions-in...,2011 data: https://www.epa.gov/air-emissions-inventories/2011-national-emissions-in...,2008 data: https://www.epa.gov/air-emissions-inventories/2008-national-emissions-in...,National Emissions Inventory,
Louisville Metro KY - Crime Data 2021
공공데이터포털
Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates within 30 days of the system migration, on or around April 13th, 2023