Although there are a large number of software products available for calculating landscape metrics (e.g. FRAGSTATS, landscapemetrics package in R) no tools are currently available (to my knowledge) that calculate landscape metrics directly in ArcGIS Pro. Moreover, many, if not most, landscape metrics were designed with vector data in mind, but most software calculates landscape metrics from raster data due to processing time and complexity. Scaling landscape metrics can also be tedious in some instances. This toolbox was designed to calculate attributes of patches that are easily calculated on polygons in ArcGIS (i.e. area, number of patches, Landscape Shape Index, edge density, patch size, distance to the nearest patch) and scales those calculations to coarser resolutions using Block Statistics. The tool also summarizes the relationships among metrics by using Principal Component Analysis and correlation matrices to assess relationships among variables. All variables are output to a single folder.

The Viewshed analysis layer is used to identify visible areas. You specify the places you are interested in, either from a file or interactively, and the Viewshed service combines this with Esri-curated elevation data to create output polygons of visible areas. Some questions you can answer with the Viewshed task include:What areas can I see from this location? What areas can see me?Can I see the proposed wind farm?What areas can be seen from the proposed fire tower?The maximum number of input features is 1000.Viewshed has the following optional parameters:Maximum Distance: The maximum distance to calculate the viewshed.Maximum Distance Units: The units for the Maximum Distance parameter. The default is meters.DEM Resolution: The source elevation data; the default is 90m resolution SRTM. Other options include 30m, 24m, 10m, and Finest.Observer Height: The height above the surface of the observer. The default value of 1.75 meters is an average height of a person. If you are looking from an elevation location such as an observation tower or a tall building, use that height instead.Observer Height Units: The units for the Observer Height parameter. The default is meters.Surface Offset: The height above the surface of the object you are trying to see. The default value is 0. If you are trying to see buildings or wind turbines add their height here.Surface Offset Units: The units for the Surface Offset parameter. The default is meters.Generalize Viewshed Polygons: Determine if the viewshed polygons are to be generalized or not. The viewshed calculation is based upon a raster elevation model which creates a result with stair-stepped edges. To create a more pleasing appearance, and improve performance, the default behavior is to generalize the polygons. This generalization will not change the accuracy of the result for any location more than one half of the DEM's resolution.By default, this tool currently works worldwide between 60 degrees north and 56 degrees south based on the 3 arc-second (approximately 90 meter) resolution SRTM dataset. Depending upon the DEM resolution pick by the user, different data sources will be used by the tool. For 24m, tool will use global dataset WorldDEM4Ortho (excluding the counties of Azerbaijan, DR Congo and Ukraine) 0.8 arc-second (approximately 24 meter) from Airbus Defence and Space GmbH. For 30m, tool will use 1 arc-second resolution data in North America (Canada, United States, and Mexico) from the USGS National Elevation Dataset (NED), SRTM DEM-S dataset from Geoscience Australia in Australia and SRTM data between 60 degrees north and 56 degrees south in the remaining parts of the world (Africa, South America, most of Europe and continental Asia, the East Indies, New Zealand, and islands of the western Pacific). For 10m, tool will use 1/3 arc-second resolution data in the continental United States from USGS National Elevation Dataset (NED) and approximately 10 meter data covering Netherlands, Norway, Finland, Denmark, Austria, Spain, Japan Estonia, Latvia, Lithuania, Slovakia, Italy, Northern Ireland, Switzerland and Liechtenstein from various authoritative sources.To learn more, read the developer documentation for Viewshed or follow the Learn ArcGIS exercise called I Can See for Miles and Miles. To use this Geoprocessing service in ArcGIS Desktop 10.2.1 and higher, you can either connect to the Ready-to-Use Services, or create an ArcGIS Server connection. Connect to the Ready-to-Use Services by first signing in to your ArcGIS Online Organizational Account:Once you are signed in, the Ready-to-Use Services will appear in the Ready-to-Use Services folder or the Catalog window:If you would like to add a direct connection to the Elevation ArcGIS Server in ArcGIS for Desktop or ArcGIS Pro, use this URL to connect: https://elevation.arcgis.com/arcgis/services. You will also need to provide your account credentials. ArcGIS for Desktop:ArcGIS Pro:The ArcGIS help has additional information about how to do this:Learn how to make a ArcGIS Server Connection in ArcGIS Desktop. Learn more about using geoprocessing services in ArcGIS Desktop.This tool is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.

Predator-prey interactions can be profoundly influenced by vegetation conditions, particularly when predator and prey prefer different habitats. Although such interactions have proven challenging to study for small and cryptic predators, recent methodological advances substantially improve opportunities for understanding how vegetation influences prey acquisition and strengthen conservation planning for this group. The California Spotted Owl (Strix occidentalis occidentalis) is well-known as an old-forest species of conservation concern, but whose primary prey in many regions – woodrats (Neotoma spp.) – occurs in a broad range of vegetation conditions. Here, we used high-resolution GPS tracking coupled with nest video monitoring to test the hypothesis that prey capture rates vary as a function of vegetation structure and heterogeneity, with emergent, reproductive consequences for Spotted Owls in Southern California. Foraging owls were more successful capturing prey, including woodrats, in taller multilayered forests, in areas with higher heterogeneity in vegetation types, and near forest-chaparral edges. Consistent with these findings, Spotted Owls delivered prey items more frequently to nests in territories with greater heterogeneity in vegetation types and delivered prey biomass at a higher rate in territories with more forest-chaparral edge. Spotted Owls had higher reproductive success in territories with higher mean canopy cover, taller trees, and more shrubby vegetation. Collectively, our results provide additional and compelling evidence that a mosaic of large tree forests with complex canopy and shrubby vegetation increases access to prey with potential reproductive benefits to Spotted Owls in landscapes where woodrats are a primary prey item. We suggest that forest management activities that enhance forest structure and vegetation heterogeneity could help curb declining Spotted Owl populations while promoting resilient ecosystems in some regions. Methods See README DOCUMENT Naming conventions *RSF or prey refers to prey capture analysis *delivery in a file name refers to delivery rate analysis *repro in a filename means that file is for the delivery rate analysis

Setup *files with vegetation data should work with minimal alteration(will need to specify working directory) with associated R code for each analysis *Shapefiles were made in ArcGIS pro but they can be opened with any GIS software such as QGIS.

Locational data files

NOTE LOCATIONAL DATA IS SHIFTED AND ROTATED FROM THE ORIGINAL -due to the sensitive nature of this species. The locational_data includes: * All_2021_owls_shifted * Point file showing all GPS tag locations for prey capture analysis * Attributes include: * TERRITORY ID: Numerical identifier for each bird * Year: year GPS tag was recorded * Month: month GPS tag was recorded * Day: Day GPS tag was recorded * Hour: Hour GPS tag was recorded * Minute: minute GPS tag was recorded * All_linked_polygons_shifted * Polygon file showing capture polygons for prey capture analysis * Attributes include * Territory ID: numerical identifier for each bird * Polygon id: numerical identifier for each capture polygon for each bird * Shape area: area of each polygon * SBNF_camera_nests_shifted * Point file showing spotted owl nests for prey capture analysis * Attributes include * Territory id: numerical identifier for each bird * C95_KDE_2021_socal_shifted * Polygon file of owls 95% kernel density estimate for prey delivery rate analysis * Attributes include * Id: numerical identifier for each territory(bird) * Area: area of each polygon * San_bernardino_territory_centers * Point file showing Territory centers for historical SBNF territories – shifted for repro success analysis * Attributes include * Repro Territory id: unique identifier for each territory in broader set of territories

Besides the sifted locational data we have included - For the Resource selection function vegetation data, for the delivery analysis we have included an overview of prey deliveries by territory and vegetation data used, and for the reproductive analysis we have again included vegetation data as well as an overview of reproductive success. these are labled as follows:

Files for the prey capture analysis

Socal_RSF_data.txt

*description: Text file with vegetation data paired with capture locations both buffered polygons used in prey capture analysis and the unbuffered ones which were not used.(Pair with Socal_rsf_code R script) *format: .txt *Dimensions: 2641 X 35

*Variables: *ORIG_fid: completely unique identifier for each row *unique_id: unique identifier for each capture polygon(shared between a buffered capture location and its unbuffered pair) *territory_id: unique numerical idenifier of territory *Polygon_id: within territory unique prey capture polygon id *buff: bianary buffered or unbuffered (1=buffered, 0=unbuffered) *used: bianary used=1 available=0 *prey_type: prey species associated with polygon unkn:unknown, flsq:flying squirel, wora:woodrat, umou:mouse, pogo:pocketgopher, grsq: grey squirel, ubrd: unknown bird, umol:unknown mole, uvol, unknown vole. *area_sqm: area of polygon in square meters *CanCov_2020_buff: average canopy cover in polygon *CanHeight_2020_buff: average canopy height in polygon *Canlayer_2020_buff: average number of canopy layers in polygon *Understory_density_2020_buff: average brushy vegetation density in polygon *pix_COUNT: count of pixels in polygon (not needed for analysis) *p_chaparral: percent of polygon comprised of chaparral habitat
*p_conifer: percent of polygon comprised of conifer habitat *p_hardwood: percent of polygon comprised of hardwood habitat *p_other: percent of polygon comprised of other habitat types *Calveg_cap_CHt_gt10_CC_30to70_intersect_buff: percent of polygon comprised of trees taller than 10m with 30-70percent canopy cover (used to check data) *Calveg_cap_CHt_gt10_CCgt70_intersect_buff: percent of polygon comprised of trees taller than 10m with greater than 70percent canopy cover (used to check data) *Calveg_cap_CHt_lt10_intersect_buff:percent of polygon comprised of trees less than 10m (used to check data)
*p_sm_conifer: percent of polygon comprised of conifer trees less than 10m (used to calculate diversity)
*p_lrg_conifer_sc: percent of polygon comprised of conifer forests >10m tall with sparse canopy(used to calculate diversity) *p_large_conifer_dc: percent of polygon comprised of conifer forests greater than 10m tall with dense canopy (used to calculate diversity) *p_sm_hard: percent of polygon comprised of hardwood trees less than 10m (used to calculate diversity) *p_lrg_hard_sc: percent of polygon comprised of hardwood forests greater than 10m with sparse canopy(used to calculate diversity)
*p_lrg_hard_dc: percent of polygon comprised of hardwood forests greater than 10m dense canopy (used to calculate diversity) *p_forests_gt10_verysparse_CC: percent of polygon comprised of trees less than 10m with very sparse canopies (used to calculate diversity) *primary_edge: total distance in meters of primary edge in a polygon
*normalized_by_area_primary_edge: total distance in m of primary edge in a polygon divided by the area of the polygon
*secondary_edge: total distance in meters of secondary edge in a polygon *normalized_by_area_secondary_edge:total distance in m of secondary edge in a polygon divided by the area of the polygon *coarse_diversity: shannon diversity in each polygon (see methods below) *fine_diversity: shannon diversity in each polygon (see methods below) *nest_distance: distance from polygon center to nest for each polygon in meters

For the Delivery analysis

note: For information on determining average prey biomass see methods as well as zulla et al 2022 for flying squirels and woodrat masses Zulla CJ, Jones GM, Kramer HA, Keane JJ, Roberts KN, Dotters BP, Sawyer SC, Whitmore SA, Berigan WJ, Kelly KG, Gutiérrez RJ, Peery MZ. Forest heterogeneity outweighs movement costs by enhancing hunting success and fitness in spotted owls. doi:10.21203/rs.3.rs-1370884/v1. PPR:PPR470028.

prey_deliveries_byterritory.csv *Description: overview file of prey delivered to each nest *format: .csv *dimensions:332 x 8

*Variables: *SITE: Unique numerical identifier for each territory *DATE: date prey was delivered (in UTC) *CAMERA TIME: time in UTC prey was delivered *VIDEO TIME: time on video prey was delivered - unrelated to real time just original file
*PREY ITEM: prey species delivered to nest unkn:unknown, uncr: unknown if delivery(removed from eventual analysis due to

Dataset for the textbook Computational Methods and GIS Applications in Social Science (3rd Edition), 2023 Fahui Wang, Lingbo Liu Main Book Citation: Wang, F., & Liu, L. (2023). Computational Methods and GIS Applications in Social Science (3rd ed.). CRC Press. https://doi.org/10.1201/9781003292302 KNIME Lab Manual Citation: Liu, L., & Wang, F. (2023). Computational Methods and GIS Applications in Social Science - Lab Manual. CRC Press. https://doi.org/10.1201/9781003304357 KNIME Hub Dataset and Workflow for Computational Methods and GIS Applications in Social Science-Lab Manual Update Log If Python package not found in Package Management, use ArcGIS Pro's Python Command Prompt to install them, e.g., conda install -c conda-forge python-igraph leidenalg NetworkCommDetPro in CMGIS-V3-Tools was updated on July 10,2024 Add spatial adjacency table into Florida on June 29,2024 The dataset and tool for ABM Crime Simulation were updated on August 3, 2023, The toolkits in CMGIS-V3-Tools was updated on August 3rd,2023. Report Issues on GitHub https://github.com/UrbanGISer/Computational-Methods-and-GIS-Applications-in-Social-Science Following the website of Fahui Wang : http://faculty.lsu.edu/fahui Contents Chapter 1. Getting Started with ArcGIS: Data Management and Basic Spatial Analysis Tools Case Study 1: Mapping and Analyzing Population Density Pattern in Baton Rouge, Louisiana Chapter 2. Measuring Distance and Travel Time and Analyzing Distance Decay Behavior Case Study 2A: Estimating Drive Time and Transit Time in Baton Rouge, Louisiana Case Study 2B: Analyzing Distance Decay Behavior for Hospitalization in Florida Chapter 3. Spatial Smoothing and Spatial Interpolation Case Study 3A: Mapping Place Names in Guangxi, China Case Study 3B: Area-Based Interpolations of Population in Baton Rouge, Louisiana Case Study 3C: Detecting Spatiotemporal Crime Hotspots in Baton Rouge, Louisiana Chapter 4. Delineating Functional Regions and Applications in Health Geography Case Study 4A: Defining Service Areas of Acute Hospitals in Baton Rouge, Louisiana Case Study 4B: Automated Delineation of Hospital Service Areas in Florida Chapter 5. GIS-Based Measures of Spatial Accessibility and Application in Examining Healthcare Disparity Case Study 5: Measuring Accessibility of Primary Care Physicians in Baton Rouge Chapter 6. Function Fittings by Regressions and Application in Analyzing Urban Density Patterns Case Study 6: Analyzing Population Density Patterns in Chicago Urban Area >Chapter 7. Principal Components, Factor and Cluster Analyses and Application in Social Area Analysis Case Study 7: Social Area Analysis in Beijing Chapter 8. Spatial Statistics and Applications in Cultural and Crime Geography Case Study 8A: Spatial Distribution and Clusters of Place Names in Yunnan, China Case Study 8B: Detecting Colocation Between Crime Incidents and Facilities Case Study 8C: Spatial Cluster and Regression Analyses of Homicide Patterns in Chicago Chapter 9. Regionalization Methods and Application in Analysis of Cancer Data Case Study 9: Constructing Geographical Areas for Mapping Cancer Rates in Louisiana Chapter 10. System of Linear Equations and Application of Garin-Lowry in Simulating Urban Population and Employment Patterns Case Study 10: Simulating Population and Service Employment Distributions in a Hypothetical City Chapter 11. Linear and Quadratic Programming and Applications in Examining Wasteful Commuting and Allocating Healthcare Providers Case Study 11A: Measuring Wasteful Commuting in Columbus, Ohio Case Study 11B: Location-Allocation Analysis of Hospitals in Rural China Chapter 12. Monte Carlo Method and Applications in Urban Population and Traffic Simulations Case Study 12A. Examining Zonal Effect on Urban Population Density Functions in Chicago by Monte Carlo Simulation Case Study 12B: Monte Carlo-Based Traffic Simulation in Baton Rouge, Louisiana Chapter 13. Agent-Based Model and Application in Crime Simulation Case Study 13: Agent-Based Crime Simulation in Baton Rouge, Louisiana Chapter 14. Spatiotemporal Big Data Analytics and Application in Urban Studies Case Study 14A: Exploring Taxi Trajectory in ArcGIS Case Study 14B: Identifying High Traffic Corridors and Destinations in Shanghai Dataset File Structure 1 BatonRouge Census.gdb BR.gdb 2A BatonRouge BR_Road.gdb Hosp_Address.csv TransitNetworkTemplate.xml BR_GTFS Google API Pro.tbx 2B Florida FL_HSA.gdb R_ArcGIS_Tools.tbx (RegressionR) 3A China_GX GX.gdb 3B BatonRouge BR.gdb 3C BatonRouge BRcrime R_ArcGIS_Tools.tbx (STKDE) 4A BatonRouge BRRoad.gdb 4B Florida FL_HSA.gdb HSA Delineation Pro.tbx Huff Model Pro.tbx FLplgnAdjAppend.csv 5 BRMSA BRMSA.gdb Accessibility Pro.tbx 6 Chicago ChiUrArea.gdb R_ArcGIS_Tools.tbx (RegressionR) 7 Beijing BJSA.gdb bjattr.csv R_ArcGIS_Tools.tbx (PCAandFA, BasicClustering) 8A Yunnan YN.gdb R_ArcGIS_Tools.tbx (SaTScanR) 8B Jiangsu JS.gdb 8C Chicago ChiCity.gdb cityattr.csv ...

Location and elevation data were collected along with peat auger cores during six U.S. Geological Survey (USGS) field activities from 2013-2018 in and around Grand Bay, Mississippi (MS) and Alabama (AL) and used in models described by Smith and others (2024). Peat auger cores were described, photographed, and the thickness of the peat unit was measured with a measuring tape. Following collection, the distance from the core _location to various geomorphic boundaries (e.g., upland, marsh shoreline, water edge, etc.) and other metrics (angle and width of marsh) were determined using geoprocessing tools from the Data Management and Analysis Toolboxes in ArcGIS Pro (version 3.1) using 2015 shorelines from Terrano and others (2018). This dataset includes all the aforementioned metrics along with the angle from the shoreline and upland boundary to the core locations. The cores used in this data release were collected during the following six field activities identified by the following USGS assigned field activity numbers (FANs): 13BIM01, 2014-323-FA (alternate FAN 14CCT01), 2016-331-FA (16CCT03), 2016-358-FA (16CCT07), 2017-315-FA (17CCT02), and 2018-332-FA (18CCT01). Additional marsh and estuarine data from these six field activities (sediment characteristics, loss-on-ignition (LOI), foraminiferal census data, radiochemistry, and site _location information) are available in previously published data releases, which are cross-referenced in the metadata of this data release. Downloadable data are available as a comma-separated values text file (.csv) and Federal Geographic Data Committee (FGDC) metadata (.txt and .xml).

This is dataset is an ArcGIS Pro project was used to calculate walking distance from buildings to Urban Green Spaces (UGS) within the municipality of Amsterdam. This was made as part of an MSc Earth Sciences thesis aimed at assessing UGS and heat exposure in Amsterdam. The thesis is based on the idea that UGS function as cool spaces within the urban heat island of the city, and thus provides lower temperatures to urban residents, specifically during hot summer months, therefore reducing the risk of heat stress and heat-related illnesses and morbidity.

This layer shows which parts of the United States and Puerto Rico fall within ten minutes" walk of one or more grocery stores. It is estimated that 20% of U.S. population live within a 10 minute walk of a grocery store, and 92% of the population live within a 10 minute drive of a grocery store. The layer is suitable for looking at access at a neighborhood scale. When you add this layer to your web map, along with the drivable access layer and the SafeGraph grocery store layer, 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. Add the Census block points layer to show a popup with the count of stores within 10 minutes" walk and drive. 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 Layer in a Web MapUse this layer in a web 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. See this example web map which you can use in your projects, storymaps, apps and dashboards. The layer 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. Lastly, this layer 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 layer is a useful visual 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 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. 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. Methodology Every 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

This layer shows which parts of the United States and Puerto Rico fall within ten minutes" walk of one or more grocery stores. It is estimated that 20% of U.S. population live within a 10 minute walk of a grocery store, and 92% of the population live within a 10 minute drive of a grocery store. The layer is suitable for looking at access at a neighborhood scale. When you add this layer to your web map, along with the drivable access layer and the SafeGraph grocery store layer, 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. Add the Census block points layer to show a popup with the count of stores within 10 minutes" walk and drive. 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 Layer in a Web MapUse this layer in a web 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. See this example web map which you can use in your projects, storymaps, apps and dashboards. The layer 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. Lastly, this layer 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 layer is a useful visual 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 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. 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. Methodology Every 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

Basemap natural color RGB image.Produced from ESA’s Sentinel-2 A/B imagery, 10 meter resolution Satellite Derive Bathymetry (SDB) is a highly accurate, extremely cost effective bathymetry product that can be produced in clear shallow water regions. The surface in this web scene was calibrated and validated using nautical charts as a survey planning surface to demonstrate shoal points and "no-go" areas.TCarta is a leading global provider of innovative hydrospatial products and Earth observation analysis services. TCarta GIS professionals, hydrographers, and developers provide solutions for onshore and offshore geospatial applications from engineering to environmental monitoring and beyond.TCarta’s primary focus is on providing affordability and accessibility of data and analytics utilizing cutting edge technology and approaches to best serve our clients where traditional methods fail with proven integrity of services and professional practices in a changing and dynamic world.USES: Satellite Derived Bathymetry (SDB) is a lower cost alternative to marine surveys and much higher resolution than ETOPO and GEBCO datasets. Coastal Engineering: Floating Solar Facilities: Suitability Analysis - Location siting using modern and accurate bathymetryWave modeling for construction planningMooring design & Cable routing to shore Offshore Wind Farms:Planning and AppraisalEnvironmental Impact assessmentsMooring design & Cable routingSite characterization Fiber Optic Cable Route Planning:Protecting marine life sanctuariesDecrease distance Aquaculture:Site selectionMonitoringFlow prediction Dredging:Measuring materialMonitoring Water Quality Monitoring:Chlorophyll IndexSediment flowNatural Disasters:Inundation modellingEnvironmental Compliance monitoring.TOOLS: ArcGIS PRO add-in and toolboxDELIVERABLES: GIS ready raster and vector formats, typically as GeoTiff, ASCII data with xyzu(where u represents Uncertainty of Z value) files in map projection coordinates (WGS84) with metadata. Other formats are available upon request like geodatabases, KML/KMZ, HDF, NetCDF

Produced from ESA’s Sentinel-2 A/B imagery, 10 meter resolution Satellite Derive Bathymetry (SDB) is a highly accurate, extremely cost effective bathymetry product that can be produced in clear shallow water regions. The surface in this web scene was calibrated and validated using nautical charts as a survey planning surface to demonstrate shoal points and "no-go" areas.TCarta is a leading global provider of innovative hydrospatial products and Earth observation analysis services. TCarta GIS professionals, hydrographers, and developers provide solutions for onshore and offshore geospatial applications from engineering to environmental monitoring and beyond.TCarta’s primary focus is on providing affordability and accessibility of data and analytics utilizing cutting edge technology and approaches to best serve our clients where traditional methods fail with proven integrity of services and professional practices in a changing and dynamic world.USES: Satellite Derived Bathymetry (SDB) is a lower cost alternative to marine surveys and much higher resolution than ETOPO and GEBCO datasets. Coastal Engineering: Floating Solar Facilities: Suitability Analysis - Location siting using modern and accurate bathymetryWave modeling for construction planningMooring design & Cable routing to shore Offshore Wind Farms:Planning and AppraisalEnvironmental Impact assessmentsMooring design & Cable routingSite characterization Fiber Optic Cable Route Planning:Protecting marine life sanctuariesDecrease distance Aquaculture:Site selectionMonitoringFlow prediction Dredging:Measuring materialMonitoring Water Quality Monitoring:Chlorophyll IndexSediment flowNatural Disasters:Inundation modellingEnvironmental Compliance monitoring.TOOLS: ArcGIS PRO add-in and toolboxDELIVERABLES: GIS ready raster and vector formats, typically as GeoTiff, ASCII data with xyzu(where u represents Uncertainty of Z value) files in map projection coordinates (WGS84) with metadata. Other formats are available upon request like geodatabases, KML/KMZ, HDF, NetCDFContact Sales@tcarta.com..