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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2020 Census.Download Link:https://ky.box.com/v/kymartian-zip-code-boundaries

U.S. ZIP Code Boundaries provides ZIP Code, postal district name, population, and area for the ZIP Code areas in the United States. This dataset has been filtered to include only Kentucky data.

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.

** 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_1*100000.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.

A dataset showing the population of 42701 between 2010 and 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.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