List of cities, zip codes and counties in Missouri

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

This layer shows Population. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the point by Population Density and size of the point by Total Population. The size of the symbol represents the total count of housing units. Population Density was calculated based on the total population and area of land fields, which both came from the U.S. Census Bureau. Formula used for Calculating the Pop Density (B01001_001E/GEO_LAND_AREA_SQ_KM). To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B01001, B09020Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

This layer shows Health Insurance Coverage. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show Percent of Population with No Health Insurance Coverage. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B27010, DP03Data downloaded from: Census Bureau's API for American Community SurveyDate of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

Context

I couldn't find a NJ county-wise demographic data (including population, income, housing, etc.) on Kaggle, so here's my contribution.

Content

This contains data on population estimates, housing/mortgage/rent information, demographics based on education, disability, gender, diversity, veterans, immigrants, sales, income, employer, employment & firms collected between 2010 & 2019 for the state of New Jersey & all 21 NJ counties.

Acknowledgements

I would like to thank the U.S. Census Bureau for collecting this data & making it available at https://www.census.gov/ from which I was able to gather & clean the data.

Inspiration

Feel free to analyze this data across the different NJ counties. Also feel free to use these attributes as dimensions with other datasets to add more color.

Context

There is no story behind this data.

These are just supplementary datasets which I plan on using for plotting county wise data on maps.. (in particular for using with my kernel : https://www.kaggle.com/stansilas/maps-are-beautiful-unemployment-is-not/)
As that data set didn't have the info I needed for plotting an interactive map using highcharter .

Content

Since I noticed that most demographic datasets here on Kaggle, either have state code, state name, or county name + state name but not all of it i.e county name, fips code, state name + state code.

Using these two datasets one can get any combination of state county codes etc.

States.csv has State name + code
US counties.csv has county wise data.

Acknowledgements

Picture : https://unsplash.com/search/usa-states?photo=-RO2DFPl7wE
Counties : https://www.census.gov/geo/reference/codes/cou.html
State :

Inspiration

Not Applicable.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, gis@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

County facilities by location and type of services provided at that location.

Polygon layer representing United States counties with name attributes.About Natural EarthNatural Earth is a convenient resource for creating custom maps. Unlike other map data intended for analysis or detailed government mapping, it is designed to meet the needs of cartographers and designers to make generalized maps. Maximum flexibility is a goal.Natural Earth is a public domain collection of map datasets available at 1:10 million (larger scale/more detailed), 1:50 million (medium scale/moderate detail), and 1:110 million (small scale/coarse detail) scales. It features tightly integrated vector and raster data to create a variety of visually pleasing, well-crafted maps with cartography or GIS software. Natural Earth data is made possible by many volunteers and supported by the North American Cartographic Information Society (NACIS).Convenience – Natural Earth solves a problem: finding suitable data for making small-scale maps. In a time when the web is awash in geospatial data, cartographers are forced to waste time sifting through confusing tangles of poorly attributed data to make clean, legible maps. Because your time is valuable, Natural Earth data comes ready to use.Neatness Counts–The carefully generalized linework maintains consistent, recognizable geographic shapes at 1:10m, 1:50m, and 1:110m scales. Natural Earth was built from the ground up, so you will find that all data layers align precisely with one another. For example, where rivers and country borders are one and the same, the lines are coincident.GIS Attributes – Natural Earth, however, is more than just a collection of pretty lines. The data attributes are equally important for mapmaking. Most data contain embedded feature names, which are ranked by relative importance. Other attributes facilitate faster map production, such as width attributes assigned to river segments for creating tapers. Intelligent dataThe attributes assigned to Natural Earth vectors make for efficient mapmaking. Most lines and areas contain embedded feature names, which are ranked by relative importance. Up to eight rankings per data theme allow easy custom map “mashups” to emphasize your subject while de-emphasizing reference features. Other attributes focus on map design. For example, width attributes assigned to rivers allow you to create tapered drainages. Assigning different colors to contiguous country polygons is another task made easier thanks to data attribution.Other key featuresVector features include name attributes and bounding box extents. Know that the Rocky Mountains are larger than the Ozarks.Large polygons are split for more efficient data handling—such as bathymetric layers.Projection-friendly vectors precisely match at 180 degrees longitude. Lines contain enough data points for smooth bending in conic projections, but not so many that computer processing speed suffers.Raster data includes grayscale-shaded relief and cross-blended hypsometric tints derived from the latest NASA SRTM Plus elevation data and tailored to register with Natural Earth Vector.Optimized for use in web mapping applications, with built-in scale attributes to assist features to be shown at different zoom levels.

This site provides access to download an ArcGIS geodatabase or shapefiles for the 2017 Texas Address Database, compiled by the Center for Water and the Environment (CWE) at the University of Texas at Austin, with guidance and funding from the Texas Division of Emergency Management (TDEM). These addresses are used by TDEM to help anticipate potential impacts of serious weather and flooding events statewide. This is part of the Texas Water Model (TWM), a project to adapt the NOAA National Water Model [1] for use in Texas public safety. This database was compiled over the period from June 2016 to December 2017. A number of gaps remain (towns and cities missing address points), see Address Database Gaps spreadsheet below [4]. Additional datasets include administrative boundaries for Texas counties (including Federal and State disaster-declarations), Councils of Government, and Texas Dept of Public Safety Regions. An Esri ArcGIS Story Map [5] web app provides an interactive map-based portal to explore and access these data layers for download.

The address points in this database include their "height above nearest drainage" (HAND) as attributes in meters and feet. HAND is an elevation model developed through processing by the TauDEM method [2], built on USGS National Elevation Data (NED) with 10m horizontal resolution. The HAND elevation data and 10m NED for the continental United States are available for download from the Texas Advanced Computational Center (TACC) [3].

The complete statewide dataset contains about 9.28 million address points representing a population of about 28 million. The total file size is about 5GB in shapefile format. For better download performance, the shapefile version of this data is divided into 5 regions, based on groupings of major watersheds identified by their hydrologic unit codes (HUC). These are zipped by region, with no zipfile greater than 120mb: - North Tx: HUC1108-1114 (0.52 million address points) - DFW-East Tx: HUC1201-1203 (3.06 million address points) - Houston-SE Tx: HUC1204 (1.84 million address points) - Central Tx: HUC1205-1210 (2.96 million address points) - Rio Grande-SW Tx: HUC2111-1309 (2.96 million address points)

Additional state and county boundaries are included (Louisiana, Mississippi, Arkansas), as well as disaster-declaration status.

Compilation notes: The Texas Commission for State Emergency Communications (CSEC) provided the first 3 million address points received, in a single batch representing 213 of Texas' 254 counties. The remaining 41 counties were primarily urban areas comprising about 6.28 million addresses (totaling about 9.28 million addresses statewide). We reached the GIS data providers for these areas (see Contributors list below) through these emergency communications networks: Texas 9-1-1 Alliance, the Texas Emergency GIS Response Team (EGRT), and the Texas GIS 9-1-1 User Group. The address data was typically organized in groupings of counties called Councils of Governments (COG) or Regional Planning Commissions (RPC) or Development Councils (DC). Every county in Texas belongs to a COG, RPC or DC. We reconciled all counties' addresses to a common, very simple schema, and merged into a single geodatabase.

November 2023 updates: In 2019, TNRIS took over maintenance of the Texas Address Database, which is now a StratMap program updated annually [6]. In 2023, TNRIS also changed its name to the Texas Geographic Information Office (TxGIO). The datasets available for download below are not being updated, but are current as of the time of Hurricane Harvey.

References: [1] NOAA National Water Model [https://water.noaa.gov/map] [2] TauDEM Downloads [https://hydrology.usu.edu/taudem/taudem5/downloads.html] [3] NFIE Continental Flood Inundation Mapping - Data Repository [https://web.corral.tacc.utexas.edu/nfiedata/] [4] Address Database Gaps, Dec 2017 (download spreadsheet below) [5] Texas Address and Base Layers Story Map [https://www.hydroshare.org/resource/6d5c7dbe0762413fbe6d7a39e4ba1986/] [6] TNRIS/TxGIO StratMap Address Points data downloads [https://tnris.org/stratmap/address-points/]

Abstract (en): This data collection contains FIPS codes for state, county, county subdivision, and place, along with the 1990 Census tract number for each side of the street for the urban cores of 550 counties in the United States. Street names, including prefix and/or suffix direction (north, southeast, etc.) and street type (avenue, lane, etc.) are provided, as well as the address range for that portion of the street located within a particular Census tract and the corresponding Census tract number. The FIPS county subdivision and place codes can be used to determine the correct Census tract number when streets with identical names and ranges exist in different parts of the same county. Contiguous block segments that have consecutive address ranges along a street and that have the same geographic codes (state, county, Census tract, county subdivision, and place) have been collapsed together and are represented by a single record with a single address range. 2006-01-12 All files were removed from dataset 551 and flagged as study-level files, so that they will accompany all downloads. (1) Due to the number of files in this collection, parts have been eliminated here. For a complete list of individual part names designated by state and county, consult the ICPSR Website. (2) There are two types of records in this collection, distinguished by the first character of each record. A "0" indicates a street name/address range record that can be used to find the Census tract number and other geographic codes from a street name and address number. A "2" indicates a geographic code/name record that can be used to find the name of the state, county, county subdivision, and/or place from the FIPS code. The "0" records contain 18 variables and the "2" records contain 10 variables.

The Impact of COVID-19 on Veterans in America

County-Level Data on Veteran Cases and Proportion of Population

About this dataset

Welcome to the Kaggle dataset on The Impact of COVID-19 on Veterans in the United States! This dataset contains data on confirmed cases of COVID-19 in counties across the United States, as well as information on the percentage of each county's population that are veterans. With this dataset, you can investigate how the pandemic has impacted veterans specifically, and compare veteran case rates to the general population. How do veteran cases differ across age groups? Are there any geographical patterns? What can we learn about risk factors for COVID-19 among veterans? Download the dataset and explore for yourself today!

How to use the dataset

This dataset includes information on the number of confirmed cases of COVID-19 by county, as well as the percentage of the population in each county that are veterans. This data can be used to examine the relationship between veteran cases and the proportion of population who are veterans.

To do this, simply look at the 'CASES' and 'VET_CASES' columns for each county. The 'CASES' column represents the total number of confirmed cases of COVID-19 in that county, while the 'VET_CASES' column represents the number of confirmed cases among veterans. To compare these two values, simply divide 'VET_CASES' by 'CASES'. This will give you a ratio of veteran cases to total cases for each county.

You can then use this ratio to compare counties and see which ones have a higher proportion of veteran cases. This data can be used to help understand where more outreach may be needed to support veterans during this pandemic

Research Ideas

• Find the correlation between the number of veterans in a county and the number of confirmed cases of COVID-19.
• Find the counties with the highest percentage of veterans and the lowest number of confirmed cases of COVID-19.
• Predict how many veterans in a county will contract COVID-19 based on the percentage of veterans in the population

Columns

File: CountyVACOVID.csv | Column name | Description | |:---------------------------|:-----------------------------------------------------------------------------------------------------------------------| | FIPS | Federal Information Processing Standards code that uniquely identifies counties within the USA. (String) | | COUNTY | County name. (String) | | STATE | State name. (String) | | POP | County population. (Integer) | | VETS | Number of veterans in the county. (Integer) | | VET_PERCENT | Percentage of the population that are veterans. (Float) | | CASES | Number of confirmed cases of COVID-19 in the county. (Integer) | | YESTER_CASES | Number of confirmed cases of COVID-19 in the county from the previous day. (Integer) | | VET_CASES | Number of confirmed cases of COVID-19 in veterans in the county. (Integer) | | VET_YESTER | Number of confirmed cases of COVID-19 in veterans in the county from the previous day. (Integer) | | LOWER_Hospitalizations | Lower bound of the 95% confidence interval for the number of hospitalizations due to COVID-19 in the county. (Integer) | | UPPER_Hospitalizations | Upper bound of the 95% confidence interval for the number of hospitalizations due to COVID-19 in the county. (Integer) | | DATE | Date of data. (Date) |

File: VAChart.csv | Column name | Description | |:------------------------|:----------------------------------------------------------------------------------| | DATE | Date of data. (Date) | | US Cases | The number of confirmed cases of COVID-19 in the United States. (Integer) | | **New US ...

Two datasets provide geographic, land use and population data for US Counties within the contiguous US. Land area, water area, cropland area, farmland area, pastureland area and idle cropland area are given along with latitude and longitude of the county centroid and the county population. Variables in this dataset come from the US Dept. of Agriculture (USDA) Natural Resources Conservation Service (NRCS) and the US Census Bureau.

EOS-WEBSTER provides seven datasets which provide county-level data on agricultural management, crop production, livestock, soil properties, geography and population. These datasets were assembled during the mid-1990's to provide driving variables for an assessment of greenhouse gas production from US agriculture using the DNDC agro-ecosystem model [see, for example, Li et al. (1992), J. Geophys. Res., 97:9759-9776; Li et al. (1996) Global Biogeochem. Cycles, 10:297-306]. The data (except nitrogen fertilizer use) were all derived from publicly available, national databases. Each dataset has a separate DIF.

The US County data has been divided into seven datasets.

US County Data Datasets:

1) Agricultural Management 2) Crop Data (NASS Crop data) 3) Crop Summary (NASS Crop data) 4) Geography and Population 5) Land Use 6) Livestock Populations 7) Soil Properties

These data were developed by the Research & Analytics Department at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable.For a deep dive into the data model including every specific metric, see the ACS 2019-2023. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e23Estimate from 2019-23 ACS_m23Margin of Error from 2019-23 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_23Change, 2010-23 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLineStatistical (buffer)BeltLineStatisticalSub (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)County (statewide)CCDIST = County Commission Districts (statewide where applicable)CCSUPERDIST = County Commission Superdistricts (DeKalb)Georgia House (statewide)Georgia Senate (statewide)HSSA = High School Statistical Area (11 county region)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)State of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2019-2023). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2019-2023Open Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://opendata.atlantaregional.com/documents/182e6fcf8201449086b95adf39471831/about

This layer shows data related to Grandparents. This is shown by state and county boundaries. This service contains the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show 'Total grandchildren in care of Grandparents.' To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): DP02Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.

This map shows three things: which counties are experiencing high unemployment (indicated by the sad faces)whether unemployment is worsening or getting better since a year ago (indicated by color)the number of unemployed people in the most recent month (indicated by size)The map always represents the most current figures offered by BLS, and updates automatically twice a month. To see the most current month offered by BLS, find the CurrentMonth attribute in the data table, or visit the metadata for the Living Atlas layer used in this map.Click on any county to see full details on the percent unemployed and count of unemployed people over the past 14 months. The pop-up's Arcade expressions compare the most recent month's data to that from 12 months prior. This helps with any seasonal variation that might occur within a year.Bureau of Labor Statistics (BLS):https://www.bls.gov/Local Area Unemployment Statistics (LAUS):https://www.bls.gov/lau/

The US Family Budget Dataset provides insights into the cost of living in different US counties based on the Family Budget Calculator by the Economic Policy Institute (EPI).

This dataset offers community-specific estimates for ten family types, including one or two adults with zero to four children, in all 1877 counties and metro areas across the United States.

Interesting Task Ideas:

1. See how family budgets compare to the federal poverty line and the Supplemental Poverty Measure in different counties.
2. Look into the money challenges faced by different types of families using the budgets provided.
3. Find out which counties have the most affordable places to live, food, transportation, healthcare, childcare, and other things people need.
4. Explore how the average income of families relates to the overall cost of living in different counties.
5. Investigate how family size affects the estimated budget and find counties where bigger families have higher costs.
6. Create visuals showing how the cost of living varies across different states and big cities.
7. Check whether specific counties are affordable for families of different sizes and types.
8. Use the dataset to compare living standards and economic security in different US counties.

If you find this dataset valuable, don't forget to hit the upvote button! 😊💝

Checkout my other datasets

Employment-to-Population Ratio for USA

Productivity and Hourly Compensation

130K Kindle Books

900K TMDb Movies

USA Unemployment Rates by Demographics & Race

Photo by Alev Takil on Unsplash

This dataset was created by the Transportation Planning and Programming (TPP) Division of the Texas Department of Transportation (TxDOT) for planning and asset inventory purposes, as well as for visualization and general mapping. County boundaries were digitized by TxDOT using USGS quad maps, and converted to line features using the Feature to Line tool. This dataset depicts a generalized coastline.Update Frequency: As NeededSource: Texas General Land OfficeSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]

This layer shows Households by Type. This is shown by state and county boundaries. This service contains the 2018-2022 release of data from the American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show Average Household Size and the Total Households in a bi-variate map. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2018-2022ACS Table(s): B11001, B25010, B25044, DP02, DP04Data downloaded from: Census Bureau's API for American Community Survey Date of API call: January 18, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the Cartographic Boundaries via US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates, and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico. The Counties (and equivalent) layer contains 3221 records - all counties and equivalent, Washington D.C., and Puerto Rico municipios. See Areas Published. Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells.Margin of error (MOE) values of -555555555 in the API (or "*****" (five asterisks) on data.census.gov) are displayed as 0 in this dataset. The estimates associated with these MOEs have been controlled to independent counts in the ACS weighting and have zero sampling error. So, the MOEs are effectively zeroes, and are treated as zeroes in MOE calculations. Other negative values on the API, such as -222222222, -666666666, -888888888, and -999999999, all represent estimates or MOEs that can't be calculated or can't be published, usually due to small sample sizes. All of these are rendered in this dataset as null (blank) values.