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

As part of the basemap data layers, the ZIP code boundary map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output).

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.

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.

Our Cayman Islands zip code Database offers comprehensive postal code data for spatial analysis, including postal and administrative areas. This dataset contains accurate and up-to-date information on all administrative divisions, cities, and zip codes, making it an invaluable resource for various applications such as address capture and validation, map and visualization, reporting and business intelligence (BI), master data management, logistics and supply chain management, and sales and marketing. Our location data packages are available in various formats, including CSV, optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more. Product features include fully and accurately geocoded data, multi-language support with address names in local and foreign languages, comprehensive city definitions, and the option to combine map data with UNLOCODE and IATA codes, time zones, and daylight saving times. Companies choose our location databases for their enterprise-grade service, reduction in integration time and cost by 30%, and weekly updates to ensure the highest quality.

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.

This dataset is part of the Geographical repository maintained by Opendatasoft.This dataset contains data for zip codes 5 digits in United States of America.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.Processors and tools are using this data.EnhancementsAdd ISO 3166-3 codes.Simplify geometries to provide better performance across the services.Add administrative hierarchy.

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

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

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.

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

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.

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

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