This layer shows median household income by race and by age of householder. This is shown by tract, county, and state boundaries. This service is updated annually to contain 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. Median income and income source is based on income in past 12 months of survey. This layer is symbolized to show median household income. 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: 2019-2023ACS Table(s): B19013B, B19013C, B19013D, B19013E, B19013F, B19013G, B19013H, B19013I, B19049, B19053Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 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. For more information about ACS layers, visit the FAQ. 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:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).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 file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

This layer shows poverty status by age group. This is shown by tract, county, and state boundaries. This service is updated annually to contain 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. Poverty status is based on income in past 12 months of survey. This layer is symbolized to show the percentage of the population whose income falls below the Federal poverty line. 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: 2019-2023ACS Table(s): B17020, C17002Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 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. For more information about ACS layers, visit the FAQ. 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:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. 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 RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).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 file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

Table from the American Community Survey (ACS) 5-year series on poverty and employment status related topics for City of Seattle Council Districts, Comprehensive Plan Growth Areas and Community Reporting Areas. Table includes B23025 Employment Status for the Population 16 years and over, B23024 Poverty Status by Disability Status by Employment Status for the Population 20 to 64 years, B17010 Poverty Status of Families by Family Type by Presence of Related Children under 18 years, C17002 Ratio of Income to Poverty Level in the Past 12 Months. Data is pulled from block group tables for the most recent ACS vintage and summarized to the neighborhoods based on block group assignment.Table created for and used in the Neighborhood Profiles application.Vintages: 2023ACS Table(s): B23025, B23024, B17010, C17002Data downloaded from: Census Bureau's Explore Census Data The 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.<d

The Census of Agriculture, produced by the United States Department of Agriculture (USDA), provides a complete count of America's farms, ranches and the people who grow our food. The census is conducted every five years, most recently in 2022, and provides an in-depth look at the agricultural industry. This layer was produced from data obtained from the USDA National Agriculture Statistics Service (NASS) Large Datasets download page. The data were transformed and prepared for publishing using the Pivot Table geoprocessing tool in ArcGIS Pro and joined to county boundaries. The county boundaries are 2022 vintage and come from Living Atlas ACS 2022 feature layers.Dataset SummaryPhenomenon Mapped: Grain productionGeographic Extent: 48 contiguous United States, Alaska, Hawaii, and Puerto RicoProjection: Web Mercator Auxiliary SphereSource: USDA National Agricultural Statistics ServiceUpdate Frequency: 5 yearsData Vintage: 2022Publication Date: April 2024AttributesNote that some values are suppressed as "Withheld to avoid disclosing data for individual operations", "Not applicable", or "Less than half the rounding unit". These have been coded in the data as -999, -888, and -777 respectively. You should account for these values when symbolizing or doing any calculations.Commodities included in this layer:Grain - Operations with SalesGrain - Sales, Measured in US Dollars ($)Grain, Other - Operations with SalesGrain, Other - Sales, Measured in US Dollars ($) Geography NoteIn Alaska, one or more county-equivalent entities (borough, census area, city, municipality) are included in an agriculture census area.What can you do with this layer?This layer is designed for data visualization. Identify features by clicking on the map to reveal the pre-configured pop-up. You may change the field(s) being symbolized. When symbolizing other fields, you will need to update the popup accordingly. Simple summary statistics are supported by this data.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Measure and Map Access to Grocery StoresFrom the perspective of the people living in each neighborhood How do people in your city get to the grocery store? The answer to that question depends on the person and where they live. This collection of layers, maps and apps help answer the question.Some live in cities and stop by a grocery store within a short walk or bike ride of home or work. Others live in areas where car ownership is more prevalent, and so they drive to a store. Some do not own a vehicle, and rely on a friend or public transit. Others rely on grocery delivery for their needs. And, many live in rural areas far from town, so a trip to a grocery store is an infrequent event involving a long drive.This map from Esri shows which areas are within a ten minute walk (in green) or ten minute drive (in blue) of a grocery store in the United States and Puerto Rico. Darker color indicates access to more stores. Summarizing this data shows that 20% of U.S. population live within a 10 minute walk of a grocery store, and 90% of the population live within a 10 minute drive of a grocery store. Click on the map to see a summary for each state.Every census block is scored with a count of walkable and drivable stores nearby, making this a map suitable for a dashboard for any city, or any of the 50 states, DC and Puerto Rico. Two colorful layers visualize this definition of access, one for walkable access (suitable for looking at a city neighborhood by neighborhood) and one for drivable access (suitable for looking across a city, county, region or state).On the walkable layer, shades of green define areas within a ten minute walk of one or more grocery stores. The colors become more intense and trend to a blue-green color for the busiest neighborhoods, such as downtown San Francisco. As you zoom in, a layer of Census block points visualizes the local population with or without walkable access. As you zoom out to see the entire city, the map adds a light blue - to dark blue layer, showing which parts of the region fall within ten minutes' drive of one or more grocery stores. As a result, the map is useful at all scales, from national to regional, state and local levels. It becomes easier to spot grocery stores that sit within a highly populated area, and grocery stores that sit in a shopping center far away from populated areas. This view of a city begins to hint at the question: how many people have each type of access to grocery stores? And, what if they are unable to walk a mile regularly, or don't own a car? How to Use This MapUse this map to introduce the concepts of access to grocery stores in your city or town. This is the kind of map where people will want to look up their home or work address to validate what the map is saying against their own experiences. The map was built with that use in mind. Many maps of access use straight-line, as-the-crow-flies distance, which ignores real-world barriers to walkability like rivers, lakes, interstates and other characteristics of the built environment. Block analysis using a network data set and Origin-Destination analysis factors these barriers in, resulting in a more realistic depiction of access. There is data behind the map, which can be summarized to show how many people have walkable access to local grocery stores. The map includes a feature layer of population in Census block points, which are visible when you zoom in far enough. This feature layer of Census block centroids can be plugged into an app like this one that summarizes the population with/without walkable or drivable access. Lastly, this map can serve as backdrop to other community resources, like food banks, farmers markets (example), and transit (example). Add a transit layer to immediately gauge its impact on the population's grocery access. You can also use this map to see how it relates to communities of concern. Add a layer of any block group or tract demographics, such as Percent Senior Population (examples), or Percent of Households with Access to 0 Vehicles (examples). The map is a useful visual and analytic resource for helping community leaders, business and government leaders see their town from the perspective of its residents, and begin asking questions about how their community could be improved. Data sourcesPopulation data is from the 2020 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer. Grocery store locations are from SafeGraph, reflecting what was in the data as of September 2024. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters. The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis. The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer's block figures can be summarized further, to tract, county and state levels. The SafeGraph grocery store locations were provided by SafeGraph. The source data included NAICS code 445110 and 452311 as an initial screening. The CSV file was imported using the Data Interoperability geoprocessing tools in ArcGIS Pro, where a definition query was applied to the layer to exclude any records that were not grocery stores. The final layer used in the analysis had approximately 63,000 records. In this map, this layer is included as a vector tile layer. MethodologyEvery census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway. A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle's access to all types of roads was factored in. The results for each analysis were captured in a Lines layer, which shows which origins are within the 10 minute cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle). The Lines layer is not published but is used to count how many stores each origin has access to over the road network. The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step. Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool used a 100 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect. Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person's commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle.

Three feature layers of Unites States internal state boundaries at different scales: 1:500K, 1:5M, and 1:20M. These layers are intended for use as a cartographic product. It is up to the user to determine which layer is most appropriate for their map.Derived from 2019 US Census Bureau Cartographic Boundary Files for state boundaries using ArcGIS Pro 2.4.3. Process:Original files were downloaded from US Census for the three different scales.Polygons were then converted to lines using the Polygon-to-Line tool.To remove the coastlines, all rows not having a LEFT_FID or RIGHT_FID attribute equal to -1 were then exported to a new geodatabase feature class.The geodatabase was zipped and uploaded to ArcGIS Online.For more information on Cartographic Boundary Files visit https://www.census.gov/programs-surveys/geography/technical-documentation/naming-convention/cartographic-boundary-file.html and https://www.census.gov/geographies/mapping-files/time-series/geo/cartographic-boundary.html.Created by Ryan Davis (RDavis9@cdc.gov) on behalf of CDC/ATSDR/DTHHS/GRASP.