GIS project files and imagery data required to complete the Introduction to Planetary Image Analysis and Geologic Mapping in ArcGIS Pro tutorial. These data cover the area in and around Jezero crater, Mars.
The National Insect and Disease Risk map identifies areas with risk of significant tree mortality due to insects and plant diseases. The layer identifies lands in three classes: areas with risk of tree mortality from insects and disease between 2013 and 2027, areas with lower tree mortality risk, and areas that were formerly at risk but are no longer at risk due to disturbance (human or natural) between 2012 and 2018. Areas with risk of tree mortality are defined as places where at least 25% of standing live basal area greater than one inch in diameter will die over a 15-year time frame (2013 to 2027) due to insects and diseases.The National Insect and Disease Risk map, produced by the US Forest Service FHAAST, is part of a nationwide strategic assessment of potential hazard for tree mortality due to major forest insects and diseases. Dataset Summary Phenomenon Mapped: Risk of tree mortality due to insects and diseaseUnits: MetersCell Size: 30 meters in Hawaii and 240 meters in Alaska and the Contiguous USSource Type: DiscretePixel Type: 2-bit unsigned integerData Coordinate System: NAD 1983 Albers (Contiguous US), WGS 1984 Albers (Alaska), Hawaii Albers (Hawaii)Mosaic Projection: North America Albers Equal Area ConicExtent: Alaska, Hawaii, and the Contiguous United States Source: National Insect Disease Risk MapPublication Date: 2018ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/This layer was created from the 2018 version of the National Insect Disease Risk Map.What can you do with this Layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "insects and disease" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "insects and disease" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use raster functions to create your own custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro. For example, Zonal Statistics as Table tool can be used to summarize risk of tree mortality across several watersheds, counties, or other areas that you may be interested in such as areas near homes.In ArcGIS Online you can change then layer's symbology in the image display control, set the layer's transparency, and control the visible scale range.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.
The Minnesota DNR Toolbox provides a number of convenience geoprocessing tools used regularly by MNDNR staff. Many of these may be useful to the wider public. However, some tools may rely on data that is not available outside of the DNR.
Toolsets included in MNDNR Tools:
- Analysis Tools
- Conversion Tools
- General Tools
- LiDAR and DEM Tools
- Sampling Tools
The application download includes a comprehensive help document, which you can also access separately here: ArcGISPro_MNDNR_Toolbox_Pro_User_Guide.pdf
These toolboxes are provided free of charge and are not warrantied for any specific use. We do not provide support or assistance in downloading or using these tools. We do, however, strive to produce high-quality tools and appreciate comments you have about them.
In this course, you will learn about some common types of data used for GIS mapping and analysis, and practice adding data to a file geodatabase to support a planned project.Goals Create a file geodatabase. Add data to a file geodatabase. Create an empty geodatabase feature class.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Collection of multispectral imagery from an aerial sensor is a means to obtain plot-level vegetation index (VI) values; however, post-capture image processing and analysis remain a challenge for small-plot researchers. An ArcGIS Pro workflow of two task items was developed with established routines and commands to extract plot-level VI values (Normalized Difference VI, Ratio VI, and Chlorophyll Index-Red Edge) from multispectral aerial imagery of small-plot turfgrass experiments. Users can access and download task item(s) from the ArcGIS Online platform for use in ArcGIS Pro. The workflow standardizes the processing of aerial imagery to ensure repeatability between sampling dates and across site locations. A guided workflow saves time with assigned commands, ultimately allowing users to obtain a table with plot descriptions and index values within a .csv file for statistical analysis. The workflow was used to analyze aerial imagery from a small-plot turfgrass research study evaluating herbicide effects on St. Augustinegrass [Stenotaphrum secundatum (Walt.) Kuntze] grow-in. To compare methods, index values were extracted from the same aerial imagery by TurfScout, LLC and were obtained by handheld sensor. Index values from the three methods were correlated with visual percentage cover to determine the sensitivity (i.e., the ability to detect differences) of the different methodologies.
Explore time-discrete statistical climate downscaling using regression tools and a Jupyter notebook with Python to automate temperature predictions and build a time-series mosaic.This is an archived copy of the tutorial data and will no longer be updated. For an up-to-date version, available only in English, please see Regression Analysis: Building a Regression Model Using ArcGIS Pro, Regression Analysis: Performing Random Forest Regression Using ArcGIS Pro, and Downscaling a Prediction Model Using ArcGIS Notebooks and ArcGIS Pro.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Purpose: This is an ArcGIS Pro template that GIS Specialists can use to identify vulnerable populations and special needs infrastructure most at risk to flooding events.How does it work?Determine and understand the Place Vulnerability (based on Cutter et al. 1997) and the Special Needs Infrastructure for an area of interest based on Special Flood Hazard Zones, Social Vulnerability Index, and the distribution of its Population and Housing units. The final product will be charts of the data distribution and a Hosted Feature Layer. See this Story Map example for a more detailed explanation.This uses the FEMA National Flood Hazard Layer as an input (although you can substitute your own flood hazard data), check availability for your County before beginning the Task: FEMA NFHL ViewerThe solution consists of several tasks that allow you to:Select an area of interest for your Place Vulnerability Analysis. Select a Hazard that may occur within your area of interest.Select the Social Vulnerability Index (SVI) features contained within your area of interest using the CDC’s Social Vulnerability Index (SVI) – 2016 overall SVI layer at the census tract level in the map.Determine and understand the Social Vulnerability Index for the hazard zones identified within you area of interest.Identify the Special Needs Infrastructure features located within the hazard zones identified within you area of interest.Share your data to ArcGIS Online as a Hosted Feature Layer.FIRST STEPS:Create a folder C:\GIS\ if you do not already have this folder created. (This is a suggested step as the ArcGIS Pro Tasks does not appear to keep relative paths)Download the ZIP file.Extract the ZIP file and save it to the C:\GIS\ location on your computer. Open the PlaceVulnerabilityAnalysis.aprx file.Once the Project file (.aprx) opens, we suggest the following setup to easily view the Tasks instructions, the Map and its Contents, and the Databases (.gdb) from the Catalog pane.The following public web map is included as a Template in the ArcGIS Pro solution file: Place Vulnerability Template Web MapNote 1:As this is a beta version, please take note of some pain points:Data input and output locations may need to be manually populated from the related workspaces (.gdb) or the tools may fail to run. Make sure to unzip/extract the file to the C:\GIS\ location on your computer to avoid issues.Switching from one step to the next may not be totally seamless yet.If you are experiencing any issues with the Flood Hazard Zones service provided, or if the data is not available for your area of interest, you can also download your Flood Hazard Zones data from the FEMA Flood Map Service Center. In the search, use the FEMA ID. Once downloaded, save the data in your project folder and use it as an input.Note 2:In this task, the default hazard being used are the National Flood Hazard Zones. If you would like to use a different hazard, you will need to add the new hazard layer to the map and update all query expressions accordingly.For questions, bug reports, or new requirements contact pdoherty@publicsafetygis.org
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
scripts.zip
arcgisTools.atbx: terrainDerivatives: make terrain derivatives from digital terrain model (Band 1 = TPI (50 m radius circle), Band 2 = square root of slope, Band 3 = TPI (annulus), Band 4 = hillshade, Band 5 = multidirectional hillshades, Band 6 = slopeshade). rasterizeFeatures: convert vector polygons to raster masks (1 = feature, 0 = background).
makeChips.R: R function to break terrain derivatives and chips into image chips of a defined size. makeTerrainDerivatives.R: R function to generated 6-band terrain derivatives from digital terrain data (same as ArcGIS Pro tool). merge_logs.R: R script to merge training logs into a single file. predictToExtents.ipynb: Python notebook to use trained model to predict to new data. trainExperiments.ipynb: Python notebook used to train semantic segmentation models using PyTorch and the Segmentation Models package. assessmentExperiments.ipynb: Python code to generate assessment metrics using PyTorch and the torchmetrics library. graphs_results.R: R code to make graphs with ggplot2 to summarize results. makeChipsList.R: R code to generate lists of chips in a directory. makeMasks.R: R function to make raster masks from vector data (same as rasterizeFeatures ArcGIS Pro tool).
terraceDL.zip
dems: LiDAR DTM data partitioned into training, testing, and validation datasets based on HUC8 watershed boundaries. Original DTM data were provided by the Iowa BMP mapping project: https://www.gis.iastate.edu/BMPs. extents: extents of the training, testing, and validation areas as defined by HUC 8 watershed boundaries. vectors: vector features representing agricultural terraces and partitioned into separate training, testing, and validation datasets. Original digitized features were provided by the Iowa BMP Mapping Project: https://www.gis.iastate.edu/BMPs.
Explore time-discrete statistical climate downscaling using regression tools and a Jupyter notebook with Python to automate temperature predictions and build a time-series mosaic. This has been created for the Learn ArcGIS lesson Downscale climate data with machine learning.This is an archived copy of the tutorial data and will no longer be updated. For an up-to-date version, available only in English, please see Regression Analysis: Building a Regression Model Using ArcGIS Pro, Regression Analysis: Performing Random Forest Regression Using ArcGIS Pro, and Downscaling a Prediction Model Using ArcGIS Notebooks and ArcGIS Pro.
This packaged data collection contains two sets of two additional model runs that used the same inputs and parameters as our primary model, with the exception being we implemented a "maximum corridor length" constraint that allowed us to identify and visualize the corridors as being well-connected (≤15km) or moderately connected (≤45km). This is based on an assumption that corridors longer than 45km are too long to sufficiently accommodate dispersal. One of these sets is based on a maximum corridor length that uses Euclidean (straight-line) distance, while the other set is based on a maximum corridor length that uses cost-weighted distance. These two sets of corridors can be compared against the full set of corridors from our primary model to identify the remaining corridors, which could be considered poorly connected. This package includes the following data layers: Corridors classified as well connected (≤15km) based on Cost-weighted Distance Corridors classified as moderately connected (≤45km) based on Cost-weighted Distance Corridors classified as well connected (≤15km) based on Euclidean Distance Corridors classified as moderately connected (≤45km) based on Euclidean Distance Please refer to the embedded metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in raster GeoTIFF (.tif) format.
This dataset contains 50-ft contours for the Hot Springs shallowest unit of the Ouachita Mountains aquifer system potentiometric-surface map. The potentiometric-surface shows altitude at which the water level would have risen in tightly-cased wells and represents synoptic conditions during the summer of 2017. Contours were constructed from 59 water-level measurements measured in selected wells (locations in the well point dataset). Major streams and creeks were selected in the study area from the USGS National Hydrography Dataset (U.S. Geological Survey, 2017), and the spring point dataset with 18 spring altitudes calculated from 10-meter digital elevation model (DEM) data (U.S. Geological Survey, 2015; U.S. Geological Survey, 2016). After collecting, processing, and plotting the data, a potentiometric surface was generated using the interpolation method Topo to Raster in ArcMap 10.5 (Esri, 2017a). This tool is specifically designed for the creation of digital elevation models and imposes constraints that ensure a connected drainage structure and a correct representation of the surface from the provided contour data (Esri, 2017a). Once the raster surface was created, 50-ft contour interval were generated using Contour (Spatial Analyst), a spatial analyst tool (available through ArcGIS 3D Analyst toolbox) that creates a line-feature class of contours (isolines) from the raster surface (Esri, 2017b). The Topo to Raster and contouring done by ArcMap 10.5 is a rapid way to interpolate data, but computer programs do not account for hydrologic connections between groundwater and surface water. For this reason, some contours were manually adjusted based on topographical influence, a comparison with the potentiometric surface of Kresse and Hays (2009), and data-point water-level altitudes to more accurately represent the potentiometric surface. Select References: Esri, 2017a, How Topo to Raster works—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/how-topo-to-raster-works.htm. Esri, 2017b, Contour—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro Raster Surface toolset at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/contour.htm. Kresse, T.M., and Hays, P.D., 2009, Geochemistry, Comparative Analysis, and Physical and Chemical Characteristics of the Thermal Waters East of Hot Springs National Park, Arkansas, 2006-09: U.S. Geological Survey 2009–5263, 48 p., accessed November 28, 2017, at https://pubs.usgs.gov/sir/2009/5263/. U.S. Geological Survey, 2015, USGS NED 1 arc-second n35w094 1 x 1 degree ArcGrid 2015, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html. U.S. Geological Survey, 2016, USGS NED 1 arc-second n35w093 1 x 1 degree ArcGrid 2016, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html.
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.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Geostatistics analyzes and predicts the values associated with spatial or spatial-temporal phenomena. It incorporates the spatial (and in some cases temporal) coordinates of the data within the analyses. It is a practical means of describing spatial patterns and interpolating values for locations where samples were not taken (and measures the uncertainty of those values, which is critical to informed decision making). This archive contains results of geostatistical analysis of COVID-19 case counts for all available US counties. Test results were obtained with ArcGIS Pro (ESRI). Sources are state health departments, which are scraped and aggregated by the Johns Hopkins Coronavirus Resource Center and then pre-processed by MappingSupport.com.
This update of the Zenodo dataset (version 6) consists of three compressed archives containing geostatistical analyses of SARS-CoV-2 testing data. This dataset utilizes many of the geostatistical techniques used in previous versions of this Zenodo archive, but has been significantly expanded to include analyses of up-to-date U.S. COVID-19 case data (from March 24th to September 8th, 2020):
Archive #1: “1.Geostat. Space-Time analysis of SARS-CoV-2 in the US (Mar24-Sept6).zip” – results of a geostatistical analysis of COVID-19 cases incorporating spatially-weighted hotspots that are conserved over one-week timespans. Results are reported starting from when U.S. COVID-19 case data first became available (March 24th, 2020) for 25 consecutive 1-week intervals (March 24th through to September 6th, 2020). Hotspots, where found, are reported in each individual state, rather than the entire continental United States.
Archive #2: "2.Geostat. Spatial analysis of SARS-CoV-2 in the US (Mar24-Sept8).zip" – the results from geostatistical spatial analyses only of corrected COVID-19 case data for the continental United States, spanning the period from March 24th through September 8th, 2020. The geostatistical techniques utilized in this archive includes ‘Hot Spot’ analysis and ‘Cluster and Outlier’ analysis.
Archive #3: "3.Kriging and Densification of SARS-CoV-2 in LA and MA.zip" – this dataset provides preliminary kriging and densification analysis of COVID-19 case data for certain dates within the U.S. states of Louisiana and Massachusetts.
These archives consist of map files (as both static images and as animations) and data files (including text files which contain the underlying data of said map files [where applicable]) which were generated when performing the following Geostatistical analyses: Hot Spot analysis (Getis-Ord Gi*) [‘Archive #1’: consecutive weeklong Space-Time Hot Spot analysis; ‘Archive #2’: daily Hot Spot Analysis], Cluster and Outlier analysis (Anselin Local Moran's I) [‘Archive #2’], Spatial Autocorrelation (Global Moran's I) [‘Archive #2’], and point-to-point comparisons with Kriging and Densification analysis [‘Archive #3’].
The Word document provided ("Description-of-Archive.Updated-Geostatistical-Analysis-of-SARS-CoV-2 (version 6).docx") details the contents of each file and folder within these three archives and gives general interpretations of these results.
The ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) Project Package includes all of the layers that are in the NTIA Permitting and Environmental Information Application as well as the APPEIT Tool which will allow users to input a project area and determine what layers from the application overlap with it. An overview of the project package and the APPEIT tool is provided below.
User instructions on how to use the tool are available here. A video explaining how to use the Project Package is also available here.
Project Package Overview
This map package includes all of the layers from the NTIA Permitting and Environmental Information Application. The layers included are all feature services from various Federal and State agencies. The map package was created with ArcGIS Pro 3.4.0. The map package was created to allow users easy access to all feature services including symbology. The map package will allow users to avoid downloading datasets individually and easily incorporate into their own GIS system. The map package includes three maps.
Permitting and Environmental Information Application Layers for GIS Analysis - This map includes all of the map tabs shown in the application, except State Data which is provided in another tab. This map includes feature services that can be used for analysis with other project layers such as a route or project area.
Permitting and Environmental Information Application Layers – For Reference Only - This map includes layers that cannot be used for analysis since they are either imagery or tile layers.
State Data - Reference Only - This map includes all relevant state data that is shown in the application.
The NTIA Permitting and Environmental Information Application was created to help with your permitting planning and environmental review preparation efforts by providing access to multiple maps from publicly available sources, including federal review, permitting, and resource agencies. The application should be used for informational purposes only and is intended solely to assist users with preliminary identification of areas that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. Multiple maps are provided in the application which are created from public sources. This application does not have an exhaustive list of everything you need for permitting or environmental review for a project but is an initial starting point to see what might be required.
APPEIT Tool OverviewThe Department of Commerce’s National Telecommunications and Information Administration (NTIA) is providing the ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) to help federal broadband grant recipients and subgrantees identify permits and environmental factors as they plan routes for their broadband deployments. Identifying permit requirements early, initiating pre-application coordination with permitting agencies, and avoiding environmental impacts help drive successful infrastructure projects. NTIA’s public release of the APPEIT tool supports government-wide efforts to improve permitting and explore how online and digital technologies can promote efficient environmental reviews.
This Esri ArcGIS Pro tool is included in the map package and was created to support permitting, planning, and environmental review preparation efforts by providing access to data layers from publicly available sources, including federal review, permitting, and resource agencies. An SOP on how to use the tool is available here. For the full list of APPEIT layers, see Appendix Table 1 in the SOP. The tool is comprised of an ArcGIS Pro Project containing a custom ArcGIS Toolbox tool, linked web map shared by the NTIA’s National Broadband Map (NBAM), a report template, and a Tasks item to guide users through using the tool. This ArcGIS Pro project and its contents (maps and data) are consolidated into this (.ppkx) project file.
To use APPEIT, users will input a project area boundary or project route line in a shapefile or feature class format. The tool will return as a CSV and PDF report that lists any federal layers from the ArcGIS Pro Permitting and Environmental Information Web Map that intersect the project. Users may only input a single project area or line at a time; multiple projects or project segments will need to be screened separately. For project route lines, users are required to specify a buffer distance. The buffer distance that is used for broadband projects should be determined by the area of anticipated impact and should generally not exceed 500 feet. For example, the State of Maryland recommends a 100-foot buffer for broadband permitting. The tool restricts buffers to two miles to ensure relevant results.
Disclaimer
This document is intended solely to assist federal broadband grant recipients and subgrantees in better understanding Infrastructure Investment and Jobs Act (IIJA) broadband grant programs and the requirements set forth in the Notice of Funding Opportunity (NOFO) for this program. This document does not and is not intended to supersede, modify, or otherwise alter applicable statutory or regulatory requirements, the terms and conditions of the award, or the specific application requirements set forth in the NOFO. In all cases, statutory and regulatory mandates, the terms and conditions of the award, the requirements set forth in the NOFO, and follow-on policies and guidance, shall prevail over any inconsistencies contained in this document.
NTIA’s ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) should be used for informational purposes only and is intended solely to assist users with preliminary identification of broadband deployments that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements.
The tool is not an exhaustive or complete resource and does not and is not intended to substitute for, supersede, modify, or otherwise alter any applicable statutory or regulatory requirements, or the specific application requirements set forth in any NTIA NOFO, Terms and Conditions, or Special Award Condition. In all cases, statutory and regulatory mandates, and the requirements set forth in NTIA grant documents, shall prevail over any inconsistencies contained in these templates.
The tool relies on publicly available data available on the websites of other federal, state, local, and Tribal agencies, and in some instances, private organizations and research institutions. Layers identified with a double asterisk include information relevant to determining if an “extraordinary circumstance” may warrant more detailed environmental review when a categorical exclusion may otherwise apply. While NTIA continues to make amendments to its websites to comply with Section 508, NTIA cannot ensure Section 508 compliance of federal and non-federal websites or resources users may access from links on NTIA websites.
All data is presented “as is,” “as available” for informational purposes. NTIA does not warrant the accuracy, adequacy, or completeness of this information and expressly disclaims liability for any errors or omissions.
Please e-mail NTIAanalytics@ntia.gov with any questions.
This packaged data collection contains additional "small" habitat cores that had a minimum size of 1 female marten home range (300ha), but were too small to meet the minimum size threshold of 5 female home ranges (1500ha) used to define cores in the Primary Model. This package includes the following data layers: Habitat Cores Greater Than 300ha (i.e. small cores and cores from primary model) Habitat Cores 300ha-1500ha (small cores only) Please refer to the embedded spatial metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) format.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Summary statistics for the main variables in our analysis.
The Habitat Suitability Analysis was built using ArcGIS Pro's ModelBuilder tool. This program does not have an option to save the model's inputs as a relative file path. As a result, the model may not run because it's searching for each layer's original file path. If this happens, we have included a file titled Habitat_Suitability_Analysis_Script that outlines the processes we used to build the model. This submission contains three folders and three supplemental files. The folder titled "Data" includes all of the raw data and data input in the Habitat Suitability Analysis. The folder titled "Scripts" describes the steps to build the Habitat Suitability Analysis model in ArcGIS Pro. The Results folder contains the Habitat Suitability Analysis model and the data that was input into the model. The supplemental files are a file titled "Dryad_Folder_Contents" which describes the contents of every folder in this submission, and a file titled "Habitat_Suitability_Analysis_README" which contain...
https://spdx.org/licenses/CC0-1.0.htmlhttps://spdx.org/licenses/CC0-1.0.html
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
*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
This packaged data collection contains all of the outputs from our primary model, including the following data layers: Habitat Cores (vector polygons) Least-cost Paths (vector lines) Least-cost Corridors (raster) Least-cost Corridors (vector polygon interpretation) Modeling Extent (vector polygon) Please refer to the embedded spatial metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) or raster GeoTIFF (.tif) formats.
This layer includes Landsat GLS, Landsat 8, and Landsat 9 imagery for use in visualization and analysis. This layer is time enabled and includes a number band combinations and indices rendered on demand. The Landsat 8 and 9 imagery includes nine multispectral bands from the Operational Land Imager (OLI) and two bands from the Thermal Infrared Sensor (TIRS). It is updated daily with new imagery directly sourced from the USGS Landsat collection on AWS.Geographic CoverageGlobal Land Surface.Polar regions are available in polar-projected Imagery Layers: Landsat Arctic Views and Landsat Antarctic Views.Temporal CoverageThis layer is updated daily with new imagery.Working in tandem, Landsat 8 and 9 revisit each point on Earth's land surface every 8 days.Most images collected from January 2015 to present are included.Approximately 5 images for each path/row from 2013 and 2014 are also included.This layer also includes imagery from the Global Land Survey* (circa 2010, 2005, 2000, 1990, 1975).Product LevelThe Landsat 8 and 9 imagery in this layer is comprised of Collection 2 Level-1 data.The imagery has Top of Atmosphere (TOA) correction applied.TOA is applied using the radiometric rescaling coefficients provided the USGS.The TOA reflectance values (ranging 0 – 1 by default) are scaled using a range of 0 – 10,000.Image Selection/FilteringA number of fields are available for filtering, including Acquisition Date, Estimated Cloud Cover, and Product ID.To isolate and work with specific images, either use the ‘Image Filter’ to create custom layers or add a ‘Layer Filter’ to restrict the default layer display to a specified image or group of images.To isolate a specific mission, use the Layer Filter and the dataset_id or SensorName fields.Visual RenderingThe default rendering in this layer is Agriculture (bands 6,5,2) with Dynamic Range Adjustment (DRA). Brighter green indicates more vigorous vegetation.The DRA version of each layer enables visualization of the full dynamic range of the images.Rendering (or display) of band combinations and calculated indices is done on-the-fly from the source images via Raster Functions.Various pre-defined Raster Functions can be selected or custom functions can be created.Pre-defined functions: Natural Color with DRA, Agriculture with DRA, Geology with DRA, Color Infrared with DRA, Bathymetric with DRA, Short-wave Infrared with DRA, Normalized Difference Moisture Index Colorized, NDVI Raw, NDVI Colorized, NBR Raw15 meter Landsat Imagery Layers are also available: Panchromatic and Pansharpened.Multispectral Bands
Band
Description
Wavelength (µm)
Spatial Resolution (m)
1
Coastal aerosol
0.43 - 0.45
30
2
Blue
0.45 - 0.51
30
3
Green
0.53 - 0.59
30
4
Red
0.64 - 0.67
30
5
Near Infrared (NIR)
0.85 - 0.88
30
6
SWIR 1
1.57 - 1.65
30
7
SWIR 2
2.11 - 2.29
30
8
Cirrus (in OLI this is band 9)
1.36 - 1.38
30
9
QA Band (available with Collection 1)*
NA
30
*More about the Quality Assessment BandTIRS Bands
Band
Description
Wavelength (µm)
Spatial Resolution (m)
10
TIRS1
10.60 - 11.19
100 * (30)
11
TIRS2
11.50 - 12.51
100 * (30)
*TIRS bands are acquired at 100 meter resolution, but are resampled to 30 meter in delivered data product.Additional Usage NotesImage exports are limited to 4,000 columns x 4,000 rows per request.This dynamic imagery layer can be used in Web Maps and ArcGIS Pro as well as web and mobile applications using the ArcGIS REST APIs.WCS and WMS compatibility means this imagery layer can be consumed as WCS or WMS services.The Landsat Explorer App is another way to access and explore the imagery.Data SourceLandsat imagery is sourced from the U.S. Geological Survey (USGS) and the National Aeronautics and Space Administration (NASA). Data is hosted in Amazon Web Services as part of their Public Data Sets program.For information, see Landsat 8 and Landsat 9.*The Global Land Survey includes images from Landsat 1 through Landsat 7. Band numbers and band combinations differ from those of Landsat 8, but have been mapped to the most appropriate band as in the above table. For more information about the Global Land Survey, visit GLS.
GIS project files and imagery data required to complete the Introduction to Planetary Image Analysis and Geologic Mapping in ArcGIS Pro tutorial. These data cover the area in and around Jezero crater, Mars.