5 datasets found
  1. Grocery Access Map Gallery

    • supply-chain-data-hub-nmcdc.hub.arcgis.com
    Updated Apr 19, 2021
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Urban Observatory by Esri (2021). Grocery Access Map Gallery [Dataset]. https://supply-chain-data-hub-nmcdc.hub.arcgis.com/datasets/UrbanObservatory::grocery-access-map-gallery
    Explore at:
    Dataset updated
    Apr 19, 2021
    Dataset provided by
    Esrihttp://esri.com/
    Authors
    Urban Observatory by Esri
    Area covered
    Description

    This is a collection of maps, layers, apps and dashboards that show population access to essential retail locations, such as grocery stores. Data sourcesPopulation data is from the 2010 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 October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already 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. Alternative versions of these layers are available. These pairs use different colors but are otherwise identical in content.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 created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 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 the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle).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 uses a 200 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. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point.Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes

  2. M

    DNR Travel Time Toolbox v2.0

    • gisdata.mn.gov
    esri_toolbox
    Updated Jul 1, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Natural Resources Department (2023). DNR Travel Time Toolbox v2.0 [Dataset]. https://gisdata.mn.gov/dataset/dnr-travel-time-tool
    Explore at:
    esri_toolboxAvailable download formats
    Dataset updated
    Jul 1, 2023
    Dataset provided by
    Natural Resources Department
    Description

    The Travel Time Tool was created by the MN DNR to use GIS analysis for calculation of hydraulic travel time from gridded surfaces and develop a downstream travel time raster for each cell in a watershed. This hydraulic travel time process, known as Time of Concentration, is a concept from the science of hydrology that measures watershed response to a precipitation event. The analysis uses watershed characteristics such as land-use, geology, channel shape, surface roughness, and topography to measure time of travel for water. Described as Travel Time, it calculates the elapsed time for a simulated drop of water to migrate from its source along a hydraulic path across different surfaces of the replicated watershed landscape, ultimately reaching the watershed outlet. The Travel Time Tool creates a raster whereas each cell is a measure of the length of time (in seconds) that it takes water to flow across it, and then accumulates the time (in hours) from the cell to the outlet of the watershed.

    The Travel Time Tool creates an impedance raster from Manning's Equation that determines the velocity of water flowing across the cell as a measure of time (in feet per second). The Flow Length Tool uses the travel time Grid for the impedance factor and determines the downstream flow time from each cell to the outlet of the watershed.

    The toolbox works with ArcMap 10.6.1 and newer and ArcGIS Pro.

    For step-by-step instructions on how to use the tool, please view MN DNR Travel Time Guidance.pdf

  3. h

    Heat Severity - USA 2021

    • heat.gov
    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • +1more
    Updated Jan 6, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Heat Severity - USA 2021 [Dataset]. https://www.heat.gov/datasets/cdd2ffd5a2fc414ca1a5e676f5fce3e3
    Explore at:
    Dataset updated
    Jan 6, 2022
    Dataset authored and provided by
    The Trust for Public Land
    Area covered
    United States,
    Description

    Notice: this is not the latest Heat Island Severity image service. For 2023 data, visit https://tpl.maps.arcgis.com/home/item.html?id=db5bdb0f0c8c4b85b8270ec67448a0b6. This layer contains the relative heat severity for every pixel for every city in the contiguous United States. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2021, patched with data from 2020 where necessary.Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter than the average temperature for that same city as a whole. Severity is measured on a scale of 1 to 5, with 1 being a relatively mild heat area (slightly above the mean for the city), and 5 being a severe heat area (significantly above the mean for the city). The absolute heat above mean values are classified into these 5 classes using the Jenks Natural Breaks classification method, which seeks to reduce the variance within classes and maximize the variance between classes. Knowing where areas of high heat are located can help a city government plan for mitigation strategies.This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.

  4. Terrain Ruggedness Index (TRI)

    • hub.arcgis.com
    • cacgeoportal.com
    • +1more
    Updated Sep 27, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2020). Terrain Ruggedness Index (TRI) [Dataset]. https://hub.arcgis.com/content/28360713391948af9303c0aeabb45afd
    Explore at:
    Dataset updated
    Sep 27, 2020
    Dataset authored and provided by
    Esrihttp://esri.com/
    Description

    The Terrain Ruggedness Index (TRI) is used to express the amount of elevation difference between adjacent cells of a DEM. This raster function template is used to generate a visual representation of the TRI with your elevation data. The results are interpreted as follows:0-80m is considered to represent a level terrain surface81-116m represents a nearly level surface117-161m represents a slightly rugged surface162-239m represents an intermediately rugged surface240-497m represents a moderately rugged surface498-958m represents a highly rugged surface959-4367m represents an extremely rugged surfaceWhen to use this raster function templateThe main value of this measurement is that it gives a relatively accurate view of the vertical change taking place in the terrain model from cell to cell. The TRI provides data on the relative change in height of the hillslope (rise), such as the side of a canyon.How to use this raster function templateIn ArcGIS Pro, search ArcGIS Living Atlas for raster function templates to apply them to your imagery layer. You can also download the raster function template, attach it to a mosaic dataset, and publish it as an image service. The output is a visual TRI representation of your imagery. This index supports elevation data.References:Raster functionsApplicable geographiesThe index is a standard index which is designed to work globally.

  5. n

    Interactions of wood accumulations, channel dynamics, and geomorphic...

    • data.niaid.nih.gov
    • search.dataone.org
    • +2more
    zip
    Updated May 3, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Anna Marshall; Ellen Wohl; Emily Iskin; Lucas Zeller (2024). Interactions of wood accumulations, channel dynamics, and geomorphic heterogeneity within a river corridor [Dataset]. http://doi.org/10.5061/dryad.k0p2ngff3
    Explore at:
    zipAvailable download formats
    Dataset updated
    May 3, 2024
    Dataset provided by
    Colorado State University
    Authors
    Anna Marshall; Ellen Wohl; Emily Iskin; Lucas Zeller
    License

    https://spdx.org/licenses/CC0-1.0.htmlhttps://spdx.org/licenses/CC0-1.0.html

    Description

    Natural rivers are inherently dynamic. Spatial and temporal variations in water, sediment, and wood fluxes both cause and respond to an increase in geomorphic heterogeneity within the river corridor. We analyze 16 two-kilometer river corridor segments of the Swan River in Montana, USA to examine relationships between wood accumulations (wood accumulation distribution density, count, and persistence), channel dynamism (total sinuosity and average channel migration), and geomorphic heterogeneity (density, aggregation, interspersion, and evenness of patches in the river corridor). We hypothesize that i) more dynamic river segments correlate with a greater presence, persistence, and distribution of wood accumulations; ii) years with higher peak discharge correspond with greater channel dynamism and wood accumulations; and iii) all river corridor variables analyzed play a role in explaining river corridor spatial heterogeneity. Our results suggest that decadal-scale channel dynamism, as reflected in total sinuosity, corresponds to greater numbers of wood accumulations per surface area and greater persistence of these wood accumulations through time. Second, higher peak discharges correspond to greater values of wood distribution density, but not to greater channel dynamism. Third, persistent values of geomorphic heterogeneity, as reflected in the heterogeneity metrics of aggregation, interspersion, patch density, and evenness, are explained by potential predictor variables analyzed here. Our results reflect the complex interactions of water, sediment, and large wood in river corridors; the difficulties of interpreting causal relationships among these variables through time; and the importance of spatial and temporal analyses of past and present river processes to understand future river conditions Methods This data was collected using field and remote sensing methods. To provide spatial context for the measurements of wood distributions, geomorphic heterogeneity, and channel dynamism along our 32-km study reach, we segmented the study reach at uniform 2-km intervals prior to data collection. The downstream-most 8 segments were selected based on the naturalness of the river corridor and the presence of abundant large wood accumulations in the active channel(s). We focused on these segments for ground-based measurements. We subsequently expanded analyses to include an additional eight upstream segments. These segments were included because of anecdotal evidence of at least localized timber harvest in the river corridor, bank stabilization, and large wood removal from the active channel. We included these sites to provide a greater range of values within some of the variables analyzed and thus potentially increase the power of our statistical analyses. Wood accumulations and beaver modifications We conducted aerial wood accumulation surveys using available Google Earth imagery between 2013 and 2022 (four years of available imagery: 2013, 2016, 2020, 2022). We mapped all logjams that could be detected via the aerial imagery. Wood accumulations that were under canopy, too small for the spatial resolution of imagery, not interacting with base flows, or containing less than three visible wood pieces were not included. We recorded the number of wood accumulations per 2-km segment for each available imagery year as a minimum wood-accumulations count and divided the wood count by floodplain area for each segment to get the wood distribution density. We also noted the occurrence of persistent wood accumulations that were continually present in the Google Earth imagery, in what we refer to as “sticky sites”. GPS coordinates of wood accumulations were collected in the field during August 2022 to verify imagery identification. We also manually identified active and remnant beaver meadows using Google Earth. Similar to large wood, American beaver (Castor canadensis) both respond to spatial heterogeneity in the river corridor (e.g., preferentially damming secondary channels) and create spatial heterogeneity through their ecosystem modifications. Beaver-modified portions of the river corridor (beaver meadows) were identified based on presence of standing water in ponds with a visible berm (beaver dam); different vegetation (wetland vegetation including rushes, sedges, and willow carrs that appear as a lighter green color in imagery) than adjacent floodplain areas; and detectable active or relict beaver dams (linear berms with different vegetation than adjacent areas). Several of the sites identified in imagery were also visited in the field to verify identification. Channel dynamism and annual peak discharge Channel dynamism was quantified using metrics of active channel migration and total sinuosity over time. To measure active channel migration, we developed a semi-automated approach to map surface water extent and planimetric centerline movement, which are commonly used to understand morphological evolution in rivers. We followed existing methodologies using base flow conditions as a conservative delineation of planimetric change given our goal of looking at relative channel change over time to understand which segments of our study area were the most dynamic. Surface water extent was delineated for 2013, 2016, 2020, and 2022 to keep the timestep consistent with our wood surveys. Imagery collected for the National Agriculture Imagery Program (NAIP) was used when available (2013 and 2016). For 2020 and 2022, cloud-free multispectral composite images were created in Google Earth Engine (GEE) from Sentinel-2 imagery from average baseflow months (August-October). Surface water was classified using the normalized difference water index (NDWI) (Gao, 1996) for NAIP imagery, and modified normalized difference water index (MNDWI) in Sentinel-2 imagery. A unique threshold was empirically determined for each year to optimize the identification of the river surface while minimizing false-positive water identification, resulting in binary water and non-water masks for each year. Gaps and voids in the Sentinel-2 derived water masks (from shadow-covered areas, thin river segments, or mixed pixels along the river edge) were filled by sequentially buffering the water areas outwards by 30 meters (three pixels) and then inwards by 15 m. Similarly, gaps and voids in NAIP-derived water masks were filled using a sequential 20 m outwards then inwards buffer. The resulting binary water masks were imported into ArcGIS Pro and vectorized. Manual adjustments were made to remove any remaining misclassified areas and join disconnected segments. We delineated centerlines of our channel masks using the ArcGIS Pro Polygon to Centerline tool. When multiple channels were present, the dominant channel branch was chosen for the channel centerline. Consequently, our analysis represents a minimum value of channel migration during each time step because it does not include secondary channel movements. The Feature to Polygon tool was used to extract area differences between two centerlines at each segment. Areas between the centerlines for each segment were divided by centerline length to get a horizontal change distance. We measured total sinuosity in each 2-km segment for 2013, 2016, 2020, and 2022 using Google Earth imagery and the built-in Measure tool in Google Earth. We measured total sinuosity as the ratio of total channel length of all active channels/valley length. We obtained annual peak discharge from the nearest US Geological Survey gauge (12370000, Swan River near Bigfork, MT). This site is below Swan Lake, a natural lake, into which the Swan River in our study area flows. Consequently, the gauge records reflect relative inter-annual fluctuations in peak discharge, but not actual discharge at the study site. We used annual peak discharge for the same time intervals used for analyzing channel position. Geomorphic heterogeneity We performed an unsupervised remote sensing classification on a stack of data containing a 2022 Sentinel-2 imagery mosaic prepared in GEE, and normalized difference vegetation index (NDVI) and normalized difference moisture index (NDMI) rasters calculated from the Sentinel-2 mosaic in ArcGIS Pro. The Sentinel mosaic was prepared for the approximate growing season in Montana, USA, (June 1 to October 31) based on annual phenology activity curves (2018-2022) of the existence of leaves or needles on flowering plants. The unsupervised classification was completed on the floodplain extent of the Swan, delineated manually in ArcGIS Pro using the 10-m 3DEP DEM, hillshade prepared from the DEM, Sentinel-2 imagery, and ArcGIS Pro Imagery basemap as visual references. Although the classification is unsupervised, the classes were intended to represent distinct types of habitats within the river corridor that blend geomorphic features and vegetation communities as observed in the field, including, but not limited to: active channels, secondary channels, accretionary bars, backswamps, natural levees, old-growth forest, wetlands, and beaver meadows. The ISO Cluster Unsupervised Classification ArcGIS Pro tool was used to perform the classification. Inputs to the tool were a maximum of 10 classes, a minimum class size of 20 pixels (tool default), and a sample interval of 10 pixels (tool default). The entire reach was classified once, and then clipped into individual 2-km segments. The classified Swan raster was brought into R for statistical analysis of heterogeneity metrics. Data were visualized using the tidyverse and terra packages. All heterogeneity metrics were calculated using the landscapemetrics package using the Queen’s case. Statistical analyses Statistical analyses were conducted in R. The data we collected span different time intervals, and we conduct our statistical analyses to match the temporal and spatial scales of data we have for each of our hypotheses. We used an alpha (probability of rejecting the null hypothesis when

  6. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Urban Observatory by Esri (2021). Grocery Access Map Gallery [Dataset]. https://supply-chain-data-hub-nmcdc.hub.arcgis.com/datasets/UrbanObservatory::grocery-access-map-gallery
Organization logo

Grocery Access Map Gallery

Explore at:
Dataset updated
Apr 19, 2021
Dataset provided by
Esrihttp://esri.com/
Authors
Urban Observatory by Esri
Area covered
Description

This is a collection of maps, layers, apps and dashboards that show population access to essential retail locations, such as grocery stores. Data sourcesPopulation data is from the 2010 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 October 2020. Access to the layer was obtained from the SafeGraph offering in ArcGIS Marketplace. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it already 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. Alternative versions of these layers are available. These pairs use different colors but are otherwise identical in content.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 created by querying the SafeGraph source layer based on primary NAICS code. After connecting to the layer in ArcGIS Pro, a definition query was set to only show records with NAICS code 445110 as an initial screening. The layer was exported to a local disk drive for further definition query refinement, to eliminate any records that were obviously not grocery stores. The final layer used in the analysis had approximately 53,600 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 the Lines layer, which shows which origins are within the cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle).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 uses a 200 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. Thank you to Melinda Morang on the Network Analyst team for guidance and suggestions at key moments along the way; to Emily Meriam for reviewing the previous version of this map and creating new color palettes and marker symbols specific to this project. Additional ReadingThe methods by which access to food is measured and reported have improved in the past decade or so, as has the uses of such measurements. Some relevant papers and articles are provided below as a starting point.Measuring Food Insecurity Using the Food Abundance Index: Implications for Economic, Health and Social Well-BeingHow to Identify Food Deserts: Measuring Physical and Economic Access to Supermarkets in King County, WashingtonAccess to Affordable and Nutritious Food: Measuring and Understanding Food Deserts and Their ConsequencesDifferent Measures of Food Access Inform Different SolutionsThe time cost of access to food – Distance to the grocery store as measured in minutes

Search
Clear search
Close search
Google apps
Main menu