Calculates zonal statistics on polygons from many categorical rasters for multiple attributes

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.

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

Lesson 1. An Introduction to working with multispectral satellite data in ArcGIS Pro In which we learn: • How to unpack tar and gz files from USGS EROS • The basic map interface in ArcGIS • How to add image files • What each individual band of Landsat spectral data looks like • The difference between: o Analysis-ready data: surface reflectance and surface temperature o Landsat Collection 1 Level 3 data: burned area and dynamic surface water o Sentinel2data o ISRO AWiFS and LISS-3 data Lesson 2. Basic image preprocessing In which we learn: • How to composite using the composite band tool • How to represent composite images • All about band combinations • How to composite using raster functions • How to subset data into a rectangle • How to clip to a polygon Lesson 3. Working with mosaic datasets In which we learn: o How to prepare an empty mosaic dataset o How to add images to a mosaic dataset o How to change symbology in a mosaic dataset o How to add a time attribute o How to add a time dimension to the mosaic dataset o How to view time series data in a mosaic dataset Lesson 4. Working with and creating derived datasets In which we learn: • How to visualize Landsat ARD surface temperature • How to calculate F° from K° using ARD surface temperature • How to generate and apply .lyrx files • How to calculate an NDVI raster using ISRO LISS-3 data • How to visualize burned areas using Landsat Level 3 data • How to visualize dynamic surface water extent using Landsat Level 3 data

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.

This layer shows particulate matter in the air sized 2.5 micrometers of smaller (PM 2.5). The data is aggregated from NASA Socioeconomic Data and Applications Center (SEDAC) gridded data into country boundaries, administrative 1 boundaries, and 50 km hex bins. The unit of measurement is micrograms per cubic meter.The layer shows the annual average PM 2.5 from 1998 to 2016, highlighting if the overall mean for an area meets the World Health Organization guideline of 10 micrograms per cubic meter annually. Areas that don't meet the guideline and are above the threshold are shown in red, and areas that are lower than the guideline are in grey.The data is averaged for each year and over the the 19 years to provide an overall picture of air quality globally. Some of the things we can learn from this layer:What is the average annual PM 2.5 value over 19 years? (1998-2016)What is the annual average PM 2.5 value for each year from 1998 to 2016?What is the statistical trend for PM 2.5 over the 19 years? (downward or upward)Are there hot spots (or cold spots) of PM 2.5 over the 19 years?How many people are impacted by the air quality in an area?What is the death rate caused by the joint effects of air pollution?Choose a different attribute to symbolize in order to reveal any of the patterns above.A space time cube was performed on a multidimensional mosaic version of the data in order to derive an emerging hot spot analysis, trends, and a 19-year average. The country and administrative 1 layers provide a population-weighted PM 2.5 value to emphasize which areas have a higher human impact. Citations:van Donkelaar, A., R. V. Martin, M. Brauer, N. C. Hsu, R. A. Kahn, R. C. Levy, A. Lyapustin, A. M. Sayer, and D. M. Winker. 2018. Global Annual PM2.5 Grids from MODIS, MISR and SeaWiFS Aerosol Optical Depth (AOD) with GWR, 1998-2016. Palisades, NY: NASA Socioeconomic Data and Applications Center (SEDAC). https://doi.org/10.7927/H4ZK5DQS. Accessed 1 April 2020van Donkelaar, A., R. V. Martin, M. Brauer, N. C. Hsu, R. A. Kahn, R. C. Levy, A. Lyapustin, A. M. Sayer, and D. M. Winker. 2016. Global Estimates of Fine Particulate Matter Using a Combined Geophysical-Statistical Method with Information from Satellites. Environmental Science & Technology 50 (7): 3762-3772. https://doi.org/10.1021/acs.est.5b05833.Boundaries and population figures:Antarctica is excluded from all maps because it was not included in the original NASA grids.50km hex bins generated using the Generate Tessellation tool - projected to Behrmann Equal Area projection for analysesPopulation figures generated using Zonal Statistics from the World Population Estimate 2016 layer from ArcGIS Living Atlas.Administrative boundaries from World Administrative Divisions layer from ArcGIS Living Atlas - projected to Behrmann Equal Area projection for analyses and hosted in Web MercatorSources: Garmin, CIA World FactbookPopulation figures generated using Zonal Statistics from the World Population Estimate 2016 layer from ArcGIS Living Atlas.Country boundaries from Esri 2019 10.8 Data and Maps - projected to Behrmann Equal Area projection for analyses and hosted in Web Mercator. Sources: Garmin, Factbook, CIAPopulation figures attached to the country boundaries come from the World Population Estimate 2016 Sources Living Atlas layer Data processing notes:NASA's GeoTIFF files for 19 years (1998-2016) were first brought into ArcGIS Pro 2.5.0 and put into a multidimensional mosaic dataset.For each geography level, the following was performed: Zonal Statistics were run against the mosaic as a multidimensional layer.A Space Time Cube was created to compare the 19 years of PM 2.5 values and detect hot/cold spot patterns. To learn more about Space Time Cubes, visit this page.The Space Time Cube is processed for Emerging Hot Spots where we gain the trends and hot spot results.The layers are hosted in Web Mercator Auxillary Sphere projection, but were processed using an equal area projection: Behrmann. If using this layer for analysis, it is recommended to start by projecting the data back to Behrmann.The country and administrative layer were dissolved and joined with population figures in order to visualize human impact.The dissolve tool ensures that each geographic area is only symbolized once within the map.Country boundaries were generalized post-analysis for visualization purposes. The tolerance used was 700m. If performing analysis with this layer, find detailed country boundaries in ArcGIS Living Atlas. To create the population-weighted attributes on the country and Admin 1 layers, the hex value population values were used to create the weighting. Within each hex bin, the total population figure and average PM 2.5 were multiplied.The hex bins were converted into centroids and the PM2.5 and population figures were summarized within the country and Admin 1 boundaries.The summation of the PM 2.5 values were then divided by the total population of each geography. This population value was determined by summarizing the population values from the hex bins within each geography.Some artifacts in the hex bin layer as a result of the input NASA rasters. Because the gridded surface is created from multiple satellites, there are strips within some areas that are a result of satellite paths. Some areas also have more of a continuous pattern between hex bins as a result of the input rasters.Within the country layer, an air pollution attributable death rate is included. 2016 figures are offered by the World Health Organization (WHO). Values are offered as a mean, upper value, lower value, and also offered as age standardized. Values are for deaths caused by all possible air pollution related diseases, for both sexes, and all age groups. For more information visit this page, and here for methodology. According to WHO, the world average was 95 deaths per 100,000 people.To learn the techniques used in this analysis, visit the Learn ArcGIS lesson Investigate Pollution Patterns with Space-Time Analysis by Esri's Kevin Bulter and Lynne Buie.

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.

Catholic_CO2_Footprint_Beta_Full_NULL_NAmerica2Burhans, Molly A., Cheney, David M., Gerlt, R.. . “Catholic_CO2_Footprint_Beta_Full_NULL_NAmerica2”. Scale not given. Version 1.0. MO and CT, USA: GoodLands Inc., Environmental Systems Research Institute, Inc., 2019.MethodologyThis is the first global Carbon footprint of the Catholic population. We will continue to improve and develop these data with our research partners over the coming years. While it is helpful, it should also be viewed and used as a "beta" prototype that we and our research partners will build from and improve. The years of carbon data are (2010) and (2015 - SHOWN). The year of Catholic data is 2018. The year of population data is 2016. Care should be taken during future developments to harmonize the years used for catholic, population, and CO2 data.1. Zonal Statistics: Esri Population Data and Dioceses --> Population per dioceses, non Vatican based numbers2. Zonal Statistics: FFDAS and Dioceses and Population dataset --> Mean CO2 per Diocese3. Field Calculation: Population per Diocese and Mean CO2 per diocese --> CO2 per Capita4. Field Calculation: CO2 per Capita * Catholic Population --> Catholic Carbon FootprintAssumption: PerCapita CO2Deriving per-capita CO2 from mean CO2 in a geography assumes that people's footprint accounts for their personal lifestyle and involvement in local business and industries that are contribute CO2. Catholic CO2Assumes that Catholics and non-Catholic have similar CO2 footprints from their lifestyles.Derived from:A multiyear, global gridded fossil fuel CO2 emission data product: Evaluation and analysis of resultshttp://ffdas.rc.nau.edu/About.htmlRayner et al., JGR, 2010 - The is the first FFDAS paper describing the version 1.0 methods and results published in the Journal of Geophysical Research.Asefi et al., 2014 - This is the paper describing the methods and results of the FFDAS version 2.0 published in the Journal of Geophysical Research.Readme version 2.2 - A simple readme file to assist in using the 10 km x 10 km, hourly gridded Vulcan version 2.2 results.Liu et al., 2017 - A paper exploring the carbon cycle response to the 2015-2016 El Nino through the use of carbon cycle data assimilation with FFDAS as the boundary condition for FFCO2."S. Asefi‐Najafabady P. J. Rayner K. R. Gurney A. McRobert Y. Song K. Coltin J. Huang C. Elvidge K. BaughFirst published: 10 September 2014 https://doi.org/10.1002/2013JD021296 Cited by: 30Link to FFDAS data retrieval and visualization: http://hpcg.purdue.edu/FFDAS/index.phpAbstractHigh‐resolution, global quantification of fossil fuel CO2 emissions is emerging as a critical need in carbon cycle science and climate policy. We build upon a previously developed fossil fuel data assimilation system (FFDAS) for estimating global high‐resolution fossil fuel CO2 emissions. We have improved the underlying observationally based data sources, expanded the approach through treatment of separate emitting sectors including a new pointwise database of global power plants, and extended the results to cover a 1997 to 2010 time series at a spatial resolution of 0.1°. Long‐term trend analysis of the resulting global emissions shows subnational spatial structure in large active economies such as the United States, China, and India. These three countries, in particular, show different long‐term trends and exploration of the trends in nighttime lights, and population reveal a decoupling of population and emissions at the subnational level. Analysis of shorter‐term variations reveals the impact of the 2008–2009 global financial crisis with widespread negative emission anomalies across the U.S. and Europe. We have used a center of mass (CM) calculation as a compact metric to express the time evolution of spatial patterns in fossil fuel CO2 emissions. The global emission CM has moved toward the east and somewhat south between 1997 and 2010, driven by the increase in emissions in China and South Asia over this time period. Analysis at the level of individual countries reveals per capita CO2 emission migration in both Russia and India. The per capita emission CM holds potential as a way to succinctly analyze subnational shifts in carbon intensity over time. Uncertainties are generally lower than the previous version of FFDAS due mainly to an improved nightlight data set."Global Diocesan Boundaries:Burhans, M., Bell, J., Burhans, D., Carmichael, R., Cheney, D., Deaton, M., Emge, T. Gerlt, B., Grayson, J., Herries, J., Keegan, H., Skinner, A., Smith, M., Sousa, C., Trubetskoy, S. “Diocesean Boundaries of the Catholic Church” [Feature Layer]. Scale not given. Version 1.2. Redlands, CA, USA: GoodLands Inc., Environmental Systems Research Institute, Inc., 2016.Using: ArcGIS. 10.4. Version 10.0. Redlands, CA: Environmental Systems Research Institute, Inc., 2016.Boundary ProvenanceStatistics and Leadership DataCheney, D.M. “Catholic Hierarchy of the World” [Database]. Date Updated: August 2019. Catholic Hierarchy. Using: Paradox. Retrieved from Original Source.Catholic HierarchyAnnuario Pontificio per l’Anno .. Città del Vaticano :Tipografia Poliglotta Vaticana, Multiple Years.The data for these maps was extracted from the gold standard of Church data, the Annuario Pontificio, published yearly by the Vatican. The collection and data development of the Vatican Statistics Office are unknown. GoodLands is not responsible for errors within this data. We encourage people to document and report errant information to us at data@good-lands.org or directly to the Vatican.Additional information about regular changes in bishops and sees comes from a variety of public diocesan and news announcements.GoodLands’ polygon data layers, version 2.0 for global ecclesiastical boundaries of the Roman Catholic Church:Although care has been taken to ensure the accuracy, completeness and reliability of the information provided, due to this being the first developed dataset of global ecclesiastical boundaries curated from many sources it may have a higher margin of error than established geopolitical administrative boundary maps. Boundaries need to be verified with appropriate Ecclesiastical Leadership. The current information is subject to change without notice. No parties involved with the creation of this data are liable for indirect, special or incidental damage resulting from, arising out of or in connection with the use of the information. We referenced 1960 sources to build our global datasets of ecclesiastical jurisdictions. Often, they were isolated images of dioceses, historical documents and information about parishes that were cross checked. These sources can be viewed here:https://docs.google.com/spreadsheets/d/11ANlH1S_aYJOyz4TtG0HHgz0OLxnOvXLHMt4FVOS85Q/edit#gid=0To learn more or contact us please visit: https://good-lands.org/Esri Gridded Population Data 2016DescriptionThis layer is a global estimate of human population for 2016. Esri created this estimate by modeling a footprint of where people live as a dasymetric settlement likelihood surface, and then assigned 2016 population estimates stored on polygons of the finest level of geography available onto the settlement surface. Where people live means where their homes are, as in where people sleep most of the time, and this is opposed to where they work. Another way to think of this estimate is a night-time estimate, as opposed to a day-time estimate.Knowledge of population distribution helps us understand how humans affect the natural world and how natural events such as storms and earthquakes, and other phenomena affect humans. This layer represents the footprint of where people live, and how many people live there.Dataset SummaryEach cell in this layer has an integer value with the estimated number of people likely to live in the geographic region represented by that cell. Esri additionally produced several additional layers World Population Estimate Confidence 2016: the confidence level (1-5) per cell for the probability of people being located and estimated correctly. World Population Density Estimate 2016: this layer is represented as population density in units of persons per square kilometer.World Settlement Score 2016: the dasymetric likelihood surface used to create this layer by apportioning population from census polygons to the settlement score raster.To use this layer in analysis, there are several properties or geoprocessing environment settings that should be used:Coordinate system: WGS_1984. This service and its underlying data are WGS_1984. We do this because projecting population count data actually will change the populations due to resampling and either collapsing or splitting cells to fit into another coordinate system. Cell Size: 0.0013474728 degrees (approximately 150-meters) at the equator. No Data: -1Bit Depth: 32-bit signedThis layer has query, identify, pixel, and export image functions enabled, and is restricted to a maximum analysis size of 30,000 x 30,000 pixels - an area about the size of Africa.Frye, C. et al., (2018). Using Classified and Unclassified Land Cover Data to Estimate the Footprint of Human Settlement. Data Science Journal. 17, p.20. DOI: http://doi.org/10.5334/dsj-2018-020.What can you do with this layer?This layer is unsuitable for mapping or cartographic use, and thus it does not include a convenient legend. Instead, this layer is useful for analysis, particularly for estimating counts of people living within watersheds, coastal areas, and other areas that do not have standard boundaries. Esri recommends using the Zonal Statistics tool or the Zonal Statistics to Table tool where you provide input zones as either polygons, or raster data, and the tool will summarize the count of population within those zones. https://www.esri.com/arcgis-blog/products/arcgis-living-atlas/data-management/2016-world-population-estimate-services-are-now-available/

WorldClim 2.1 provides downscaled estimates of climate variables as monthly means over the period of 1970-2000 based on interpolated station measurements. Here we provide analytical image services of precipitation for each month along with an annual mean. Each time step is accessible from a processing template.Time Extent: Monthly/Annual 1970-2000Units: mm/monthCell Size: 2.5 minutes (~5 km)Source Type: StretchedPixel Type: 16 Bit IntegerData Projection: GCS WGS84Mosaic Projection: GCS WGS84Extent: GlobalSource: WorldClim v2.1Using Processing Templates to Access TimeThere are 13 processing templates applied to this service, each providing access to the 12 monthly and 1 annual mean precipitation layers. To apply these in ArcGIS Online, select the Image Display options on the layer. Then pull down the list of variables from the Renderer options. Click Apply and Close. In ArcGIS Pro, go into the Layer Properties. Select Processing Templates from the left-hand menu. From the Processing Template pull down menu, select the version to display.What can you do with this layer?This layer may be added to maps to visualize and quickly interrogate each pixel value. The pop-up provides a graph of the time series along with the calculated annual mean value.This layer can be used in analysis. For example, the layer may be added to ArcGIS Pro and an area count of precipitation may be produced for a feature dataset using the zonal statistics tool. Statistics may be compared with the statistics from month to month to show seasonal patterns.To calculate precipitation by land area, or any other analysis, be sure to use an equal area projection, such as Albers or Equal Earth.Source Data: The datasets behind this layer were extracted from GeoTIF files produced by WorldClim at 2.5 minutes resolution. The mean of the 12 GeoTIFs was calculated (annual), and the 13 rasters were converted to Cloud Optimized GeoTIFF format and added to a mosaic dataset.Citation: Fick, S.E. and R.J. Hijmans, 2017. WorldClim 2: new 1km spatial resolution climate surfaces for global land areas. International Journal of Climatology 37 (12): 4302-4315.

A 6-in resolution 8-class land cover dataset derived from the 2017 Light Detection and Ranging (LiDAR) data capture. This dataset was developed as part of an updated urban tree canopy assessment and therefore represents a ''top-down" mapping perspective in which tree canopy overhanging features is assigned to the tree canopy class. The eight land cover classes mapped were: (1) Tree Canopy, (2) Grass\Shrubs, (3) Bare Soil, (4) Water, (5) Buildings, (6) Roads, (7) Other Impervious, and (8) Railroads. The primary sources used to derive this land cover layer were 2017 LiDAR (1-ft post spacing) and 2016 4-band orthoimagery (0.5-ft resolution). Object based image analysis was used to automate land-cover features using LiDAR point clouds and derivatives, orthoimagery, and vector GIS datasets -- City Boundary (2017, NYC DoITT) Buildings (2017, NYC DoITT) Hydrography (2014, NYC DoITT) LiDAR Hydro Breaklines (2017, NYC DoITT) Transportation Structures (2014, NYC DoITT) Roadbed (2014, NYC DoITT) Road Centerlines (2014, NYC DoITT) Railroads (2014, NYC DoITT) Green Roofs (date unknown, NYC Parks) Parking Lots (2014, NYC DoITT) Parks (2016, NYC Parks) Sidewalks (2014, NYC DoITT) Synthetic Turf (2018, NYC Parks) Wetlands (2014, NYC Parks) Shoreline (2014, NYC DoITT) Plazas (2014, NYC DoITT) Utility Poles (2014, ConEdison via NYCEM) Athletic Facilities (2017, NYC Parks) For the purposes of classification, only vegetation > 8 ft were classed as Tree Canopy. Vegetation below 8 ft was classed as Grass/Shrub. To learn more about this dataset, visit the interactive "Understanding the 2017 New York City LiDAR Capture" Story Map -- https://maps.nyc.gov/lidar/2017/ Please see the following link for additional documentation on this dataset -- https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_LandCover.md

pockmarks are defined as depressions on the seabed and are usually formed by fluid expulsions. recently discovered, pockmarks along the aquitaine slope within the french eez, were manually mapped although two semi-automated methods were tested without convincing results. in order to potentially highlight different groups and possibly discriminate the nature of the fluids involved in their formation and evolution, a morphological study was conducted, mainly based on multibeam data and in particular bathymetry from the marine expedition gazcogne1, 2013. bathymetry and seafloor backscatter data, covering more than 3200 km², were acquired with the kongsberg em302 ship-borne multibeam echosounder of the r/v le suroît at a speed of ~8 knots, operated at a frequency of 30 khz and calibrated with ©sippican shots. precision of seafloor backscatter amplitude is +/- 1 db. multibeam data, processed using caraibes (©ifremer), were gridded at 15x15 m and down to 10x10 m cells, for bathymetry and seafloor backscatter, respectively. the present table includes 11 morphological attributes extracted from a geographical information system project (mercator 44°n conserved latitude in wgs84 datum) and additional parameters related to seafloor backscatter amplitudes. pockmark occurrence with regards to the different morphological domains is derived from a morphological analysis manually performed and based on gazcogne1 and bobgeo2 bathymetric datasets.the pockmark area and its perimeter were calculated with the “calculate geometry” tool of arcmap 10.2 (©esri) (https://desktop.arcgis.com/en/arcmap/10.3/manage-data/tables/calculating-area-length-and-other-geometric-properties.htm). a first method to calculate pockmark internal depth developed by gafeira et al. was tested (gafeira j, long d, diaz-doce d (2012) semi-automated characterisation of seabed pockmarks in the central north sea. near surface geophysics 10 (4):303-315, doi:10.3997/1873-0604.2012018). this method is based on the “fill” function from the hydrology toolset in spatial analyst toolbox arcmap 10.2 (©esri), (https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/fill.htm) which fills the closed depressions. the difference between filled bathymetry and initial bathymetry produces a raster grid only highlighting filled depressions. thus, only the maximum filling values which correspond to the internal depths at the apex of the pockmark were extracted. for the second method, the internal pockmark depth was calculated with the difference between minimum and maximum bathymetry within the pockmark.latitude and longitude of the pockmark centroid, minor and major axis lengths and major axis direction of the pockmarks were calculated inside each depression with the “zonal geometry as table” tool from spatial analyst toolbox in arcgis 10.2 (©esri) (https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/zonal-statistics.htm). pockmark elongation was calculated as the ratio between the major and minor axis length.cell count is the number of cells used inside each pockmark to calculate statistics (https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/zonal-geometry.htm). cell count and minimum, maximum and mean bathymetry, slope and seafloor backscatter values were calculated within each pockmark with “zonal statistics as table” tool from spatial analyst toolbox in arcgis 10.2 (©esri). slope was calculated from bathymetry with “slope” function from spatial analyst toolbox in arcgis 10.2 (©esri) and preserves its 15 m grid size (https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/slope.htm). seafloor backscatter amplitudes (minimum, maximum and mean values) of the surrounding sediments were calculated within a 100 m buffer around the pockmark rim.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer of INDU and immediate environs. At this stage, the map layer has only map attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map class names, physiognomic definitions, link to NVC association and alliance codes), we produced a feature class table along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature class layers produced from this project, including vegetation sample plots, accuracy assessment sites, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

This layer contains wildfire hazard potential (WHP) data for the conterminous United States aggregated from states to block groups and 50 km hex bins then enriched with demographic data. The data is from the USDA Forest Service Fire Modeling Institute providing an index of WHP at a 270 meter resolution. Wildfire hazard potential provides information on the relative potential for wildfire that would be difficult for fire crews to contain. "Areas with higher wildfire potential values represent fuels with a higher likelihood of experiencing high-intensity fire with torching, crowning, and other forms of extreme fire behavior." - Fire Modeling Institute. A score of 5 is very high risk and a score between 0-1 is likely non-burnable area such as water or asphalt. "On its own, WHP is not an explicit map of wildfire threat or risk, but when paired with spatial data depicting highly valued resources and assets such as communities, structures, or powerlines, it can approximate relative wildfire risk to those resources and assets. WHP is also not a forecast or wildfire outlook for any particular season, as it does not include any information on current or forecasted weather or fuel moisture conditions. It is instead intended for long-term strategic planning and fuels management."Each layer has been enriched with 2020 Esri demographic attributes to better approximate wildfire hazard risk relating to the human population. This layer is available in a ready to use web map. A hosted imagery layer of this data is available in ArcGIS Living Atlas for additional analysis.Data notes:Zonal Statistics as Table were run against a local copy of the WHP data using US standard geographies as the feature zone input for the analysis. Geographies included are: State, County, Congressional District, ZIP Code, Tract, and Block Group. Statistical tables were joined to geographies. To learn more about zonal statistics, view the documentation here. 50 km hex bins were created using Generate Tessellation and then joined to zonal statistics as described above (step 1).Data was enriched with 2020 Esri Demographics. Attributes include population, households & housing units, growth rate, and calculated variables such as population change over time. To create the population-weighted attributes on the state, congressional district, and county layers, the hex value population values were used to create the weighting. Within each hex bin, the total population figure and average WHP were multiplied.The hex bins were converted into centroids and summarized within the state, congressional district, and county boundaries.The summation of these values were then divided by the total population of each respective geography.

The Opportunity Zone Program was created in the Tax Cuts and Jobs Act of 2017, Opportunity Zones is a federal program that provides tax incentives for investments in new businesses and commercial projects in low-income communities. On April 20, 2017 Mayor Bowser nominated 25 census tracts to be Opportunity Zones. The U.S. Department of Treasury certified these tracts on May 18, 2018. Opportunity Zones will stay in place for 10 years.

Important Note: This item is in mature support as of February 2023 and will be retired in December 2025. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. This layer displays change in pixels of the Sentinel-2 10m Land Use/Land Cover product developed by Esri, Impact Observatory, and Microsoft. Available years to compare with 2021 are 2018, 2019 and 2020. By default, the layer shows all comparisons together, in effect showing what changed 2018-2021. But the layer may be changed to show one of three specific pairs of years, 2018-2021, 2019-2021, or 2020-2021.Showing just one pair of years in ArcGIS Online Map ViewerTo show just one pair of years in ArcGIS Online Map viewer, create a filter. 1. Click the filter button. 2. Next, click add expression. 3. In the expression dialogue, specify a pair of years with the ProductName attribute. Use the following example in your expression dialogue to show only places that changed between 2020 and 2021:ProductNameis2020-2021By default, places that do not change appear as a transparent symbol in ArcGIS Pro. But in ArcGIS Online Map Viewer, a transparent symbol may need to be set for these places after a filter is chosen. To do this:4. Click the styles button. 5. Under unique values click style options. 6. Click the symbol next to No Change at the bottom of the legend. 7. Click the slider next to "enable fill" to turn the symbol off.Showing just one pair of years in ArcGIS ProTo show just one pair of years in ArcGIS Pro, choose one of the layer's processing templates to single out a particular pair of years. The processing template applies a definition query that works in ArcGIS Pro. 1. To choose a processing template, right click the layer in the table of contents for ArcGIS Pro and choose properties. 2. In the dialogue that comes up, choose the tab that says processing templates. 3. On the right where it says processing template, choose the pair of years you would like to display. The processing template will stay applied for any analysis you may want to perform as well.How the change layer was created, combining LULC classes from two yearsImpact Observatory, Esri, and Microsoft used artificial intelligence to classify the world in 10 Land Use/Land Cover (LULC) classes for the years 2017-2021. Mosaics serve the following sets of change rasters in a single global layer: Change between 2018 and 2021Change between 2019 and 2021Change between 2020 and 2021To make this change layer, Esri used an arithmetic operation combining the cells from a source year and 2021 to make a change index value. ((from year * 16) + to year) In the example of the change between 2020 and 2021, the from year (2020) was multiplied by 16, then added to the to year (2021). Then the combined number is served as an index in an 8 bit unsigned mosaic with an attribute table which describes what changed or did not change in that timeframe. Variable mapped: Change in land cover between 2018, 2019, or 2020 and 2021 Data Projection: Universal Transverse Mercator (UTM)Mosaic Projection: WGS84Extent: GlobalSource imagery: Sentinel-2Cell Size: 10m (0.00008983152098239751 degrees)Type: ThematicSource: Esri Inc.Publication date: January 2022What can you do with this layer?Global LULC maps provide information on conservation planning, food security, and hydrologic modeling, among other things. This dataset can be used to visualize land cover anywhere on Earth. This layer can also be used in analyses that require land cover input. For example, the Zonal Statistics tools allow a user to understand the composition of a specified area by reporting the total estimates for each of the classes. Land Cover processingThis map was produced by a deep learning model trained using over 5 billion hand-labeled Sentinel-2 pixels, sampled from over 20,000 sites distributed across all major biomes of the world. The underlying deep learning model uses 6 bands of Sentinel-2 surface reflectance data: visible blue, green, red, near infrared, and two shortwave infrared bands. To create the final map, the model is run on multiple dates of imagery throughout the year, and the outputs are composited into a final representative map. Processing platformSentinel-2 L2A/B data was accessed via Microsoft’s Planetary Computer and scaled using Microsoft Azure Batch.Class definitions1. WaterAreas where water was predominantly present throughout the year; may not cover areas with sporadic or ephemeral water; contains little to no sparse vegetation, no rock outcrop nor built up features like docks; examples: rivers, ponds, lakes, oceans, flooded salt plains.2. TreesAny significant clustering of tall (~15-m or higher) dense vegetation, typically with a closed or dense canopy; examples: wooded vegetation,
clusters of dense tall vegetation within savannas, plantations, swamp or mangroves (dense/tall vegetation with ephemeral water or canopy too thick to detect water underneath).4. Flooded vegetationAreas of any type of vegetation with obvious intermixing of water throughout a majority of the year; seasonally flooded area that is a mix of grass/shrub/trees/bare ground; examples: flooded mangroves, emergent vegetation, rice paddies and other heavily irrigated and inundated agriculture.5. CropsHuman planted/plotted cereals, grasses, and crops not at tree height; examples: corn, wheat, soy, fallow plots of structured land.7. Built AreaHuman made structures; major road and rail networks; large homogenous impervious surfaces including parking structures, office buildings and residential housing; examples: houses, dense villages / towns / cities, paved roads, asphalt.8. Bare groundAreas of rock or soil with very sparse to no vegetation for the entire year; large areas of sand and deserts with no to little vegetation; examples: exposed rock or soil, desert and sand dunes, dry salt flats/pans, dried lake beds, mines.9. Snow/IceLarge homogenous areas of permanent snow or ice, typically only in mountain areas or highest latitudes; examples: glaciers, permanent snowpack, snow fields. 10. CloudsNo land cover information due to persistent cloud cover.11. Rangeland Open areas covered in homogenous grasses with little to no taller vegetation; wild cereals and grasses with no obvious human plotting (i.e., not a plotted field); examples: natural meadows and fields with sparse to no tree cover, open savanna with few to no trees, parks/golf courses/lawns, pastures. Mix of small clusters of plants or single plants dispersed on a landscape that shows exposed soil or rock; scrub-filled clearings within dense forests that are clearly not taller than trees; examples: moderate to sparse cover of bushes, shrubs and tufts of grass, savannas with very sparse grasses, trees or other plants.CitationKarra, Kontgis, et al. “Global land use/land cover with Sentinel-2 and deep learning.” IGARSS 2021-2021 IEEE International Geoscience and Remote Sensing Symposium. IEEE, 2021.AcknowledgementsTraining data for this project makes use of the National Geographic Society Dynamic World training dataset, produced for the Dynamic World Project by National Geographic Society in partnership with Google and the World Resources Institute.For questions please email environment@esri.com

This layer contains wildfire hazard potential (WHP) data for the conterminous United States aggregated from states to block groups and 50 km hex bins then enriched with demographic data. The data is from the USDA Forest Service Fire Modeling Institute providing an index of WHP at a 270 meter resolution. Wildfire hazard potential provides information on the relative potential for wildfire that would be difficult for fire crews to contain. "Areas with higher wildfire potential values represent fuels with a higher likelihood of experiencing high-intensity fire with torching, crowning, and other forms of extreme fire behavior." - Fire Modeling Institute. A score of 5 is very high risk and a score between 0-1 is likely non-burnable area such as water or asphalt. "On its own, WHP is not an explicit map of wildfire threat or risk, but when paired with spatial data depicting highly valued resources and assets such as communities, structures, or powerlines, it can approximate relative wildfire risk to those resources and assets. WHP is also not a forecast or wildfire outlook for any particular season, as it does not include any information on current or forecasted weather or fuel moisture conditions. It is instead intended for long-term strategic planning and fuels management."Each layer has been enriched with 2020 Esri demographic attributes to better approximate wildfire hazard risk relating to the human population. This layer is available in a ready to use web map. A hosted imagery layer of this data is available in ArcGIS Living Atlas for additional analysis.Data notes:Zonal Statistics as Table were run against a local copy of the WHP data using US standard geographies as the feature zone input for the analysis. Geographies included are: State, County, Congressional District, ZIP Code, Tract, and Block Group. Statistical tables were joined to geographies. To learn more about zonal statistics, view the documentation here. 50 km hex bins were created using Generate Tessellation and then joined to zonal statistics as described above (step 1).Data was enriched with 2020 Esri Demographics. Attributes include population, households & housing units, growth rate, and calculated variables such as population change over time. To create the population-weighted attributes on the state, congressional district, and county layers, the hex value population values were used to create the weighting. Within each hex bin, the total population figure and average WHP were multiplied.The hex bins were converted into centroids and summarized within the state, congressional district, and county boundaries.The summation of these values were then divided by the total population of each respective geography.

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.

This raster represents a continuous surface of sage-grouse habitat suitability index (HSI, created using ArcGIS 10.2.2) values for Nevada during spring, which is a surrogate for habitat conditions during the sage-grouse breeding and nesting period. Summary of steps to create Habitat Categories: HABITAT SUITABILITY INDEX: The HSI was derived from a generalized linear mixed model (specified by binomial distribution) that contrasted data from multiple environmental factors at used sites (telemetry locations) and available sites (random locations). Predictor variables for the model represented vegetation communities at multiple spatial scales, water resources, habitat configuration, urbanization, roads, elevation, ruggedness, and slope. Vegetation data was derived from various mapping products, which included NV SynthMap (Petersen 2008, SageStitch (Comer et al. 2002, LANDFIRE (Landfire 2010), and the CA Fire and Resource Assessment Program (CFRAP 2006). The analysis was updated to include high resolution percent cover within 30 x 30 m pixels for Sagebrush, non-sagebrush, herbaceous vegetation, and bare ground (C. Homer, unpublished; based on the methods of Homer et al. 2014, Xian et al. 2015 ) and conifer (primarily pinyon-juniper, P. Coates, unpublished). The pool of telemetry data included the same data from 1998 - 2013 used by Coates et al. (2014); additional telemetry location data from field sites in 2014 were added to the dataset. The dataset was then split according calendar date into three seasons (spring, summer, winter). Summer included telemetry locations (n = 14,058) from mid-March to June. All age and sex classes of marked grouse were used in the analysis. Sufficient data (i.e., a minimum of 100 locations from at least 20 marked Sage-grouse) for modeling existed in 10 subregions for spring and summer, and seven subregions in winter, using all age and sex classes of marked grouse. It is important to note that although this map is composed of HSI values derived from the seasonal data, it does not explicitly represent habitat suitability for reproductive females (i.e., nesting and with broods). Insufficient data were available to allow for estimation of this habitat type for all seasons throughout the study area extent. A Resource Selection Function (RSF) was calculated using R Software (v 3.13) for each subregion and using generalized linear models to derive model-averaged parameter estimates for each covariate across a set of additive models. Subregional RSFs were transformed into Habitat Suitability Indices, and averaged together to produce an overall statewide HSI whereby a relative probability of occurrence was calculated for each raster cell during the spring. In order to account for discrepancies in HSI values caused by varying ecoregions within Nevada, the HSI was divided into north and south extents using a slightly modified flood region boundary (Mason 1999) that was designed to represent respective mesic and xeric regions of the state. North and south HSI rasters were each relativized according to their maximum value to rescale between zero and one, then mosaicked once more into a state-wide extent. REFERENCES: California Forest and Resource Assessment Program (CFRAP). 2006. Statewide Land Use / Land Cover Mosaic. [Geospatial data.] California Department of Forestry and Fire Protection, http://frap.cdf.ca.gov/data/frapgisdata-sw-rangeland-assessment_data.php Census 2010. TIGER/Line Shapefiles. Urban Areas [Geospatial data.] U.S. Census Bureau, Washington D.C., https://www.census.gov/geo/maps-data/data/tiger-line.html Census 2014. TIGER/Line Shapefiles. Roads [Geospatial data.] U.S. Census Bureau, Washington D.C., https://www.census.gov/geo/maps-data/data/tiger-line.html Census 2015. TIGER/Line Shapefiles. Blocks [Geospatial data.] U.S. Census Bureau, Washington D.C., https://www.census.gov/geo/maps-data/data/tiger-line.html Coates, P.S., Casazza, M.L., Brussee, B.E., Ricca, M.A., Gustafson, K.B., Overton, C.T., Sanchez-Chopitea, E., Kroger, T., Mauch, K., Niell, L., Howe, K., Gardner, S., Espinosa, S., and Delehanty, D.J. 2014, Spatially explicit modeling of greater sage-grouse (Centrocercus urophasianus) habitat in Nevada and northeastern California—A decision-support tool for management: U.S. Geological Survey Open-File Report 2014-1163, 83 p., http://dx.doi.org/10.3133/ofr20141163. ISSN 2331-1258 (online) Comer, P., Kagen, J., Heiner, M., and Tobalske, C. 2002. Current distribution of sagebrush and associated vegetation in the western United States (excluding NM). [Geospatial data.] Interagency Sagebrush Working Group, http://sagemap.wr.usgs.gov Homer, C.G., Aldridge, C.L., Meyer, D.K., and Schell, S.J. 2014. Multi-Scale Remote Sensing Sagebrush Characterization with Regression Trees over Wyoming, USA; Laying a Foundation for Monitoring. International Journal of Applied Earth Observation and Geoinformation 14, Elsevier, US. LANDFIRE. 2010. 1.2.0 Existing Vegetation Type Layer. [Geospatial data.] U.S. Department of the Interior, Geological Survey, http://landfire.cr.usgs.gov/viewer/ Mason, R.R. 1999. The National Flood-Frequency Program—Methods For Estimating Flood Magnitude And Frequency In Rural Areas In Nevada U.S. Geological Survey Fact Sheet 123-98 September, 1999, Prepared by Robert R. Mason, Jr. and Kernell G. Ries III, of the U.S. Geological Survey; and Jeffrey N. King and Wilbert O. Thomas, Jr., of Michael Baker, Jr., Inc. http://pubs.usgs.gov/fs/fs-123-98/ Peterson, E. B. 2008. A Synthesis of Vegetation Maps for Nevada (Initiating a 'Living' Vegetation Map). Documentation and geospatial data, Nevada Natural Heritage Program, Carson City, Nevada, http://www.heritage.nv.gov/gis Xian, G., Homer, C., Rigge, M., Shi, H., and Meyer, D. 2015. Characterization of shrubland ecosystem components as continuous fields in the northwest United States. Remote Sensing of Environment 168:286-300. NOTE: This file does not include habitat areas for the Bi-State management area and the spatial extent is modified in comparison to Coates et al. 2014

Dataset description
This dataset is a recalculation of the Copernicus 2015 high resolution layer (HRL) of imperviousness density data (IMD) at different spatial/territorial scales for the case studies of Barcelona and Milan. The selected spatial/territorial scales are the following:

• a) Barcelona city boundaries
• b) Barcelona metropolitan area, Àrea Metropolitana de Barcelona (AMB)
• c) Barcelona greater city (Urban Atlas)
• d) Barcelona functional urban area (Urban Atlas)
• e) Milan city boundaries
• f) Milan metropolitan area, Piano Intercomunale Milanese (PIM)
• g) Milan greater city (Urban Atlas)
• h) Milan functional urban area (Urban Atlas)
  

In each of the spatial/territorial scales listed above, the number of 20x20mt cells corresponding to each of the 101 values of imperviousness (0-100% soil sealing: 0% means fully non-sealed area; 100% means fully sealed area) is provided, as well as the converted measure into squared kilometres (km2).

Dataset composition
The dataset is provided in .csv format and is composed of:

_IMD15_BCN_MI_Sources.csv_: Information on data sources

_IMD15_BCN.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Barcelona: * a) Barcelona city boundaries (label: bcn_city) * b) Barcelona metropolitan area, Àrea metropolitana de Barcelona (AMB) (label: bcn_amb) * c) Barcelona greater city (Urban Atlas) (label: bcn_grc) * d) Barcelona functional urban area (Urban Atlas) (label: bcn_fua)

_IMD15_MI.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Milan: * e) Milan city boundaries (label: mi_city) * f) Milan metropolitan area, Piano intercomunale milanese (PIM) (label: mi_pim) * g) Milan greater city (Urban Atlas) (label: mi_grc) * h) Milan functional urban area (Urban Atlas) (label: mi_fua)

_IMD15_BCN_MI.mpk_: the shareable project in Esri ArcGIS format including the HRL IMD data in raster format for each of the territorial boundaries as specified in letter a)-h).

Regarding the territorial scale as per letter f), the list of municipalities included in the Milan metropolitan area in 2016 was provided to me in 2016 from a person working at the PIM.

In the IMD15_BCN.csv and IMD15_MI.csv, the following columns are included:

• Level: the territorial level as defined above (a)-d) for Barcelona and e)-h) for Milan);
• Value: the 101 values of imperviousness density expressed as a percentage of soil sealing (0-100%: 0% means fully non-sealed area; 100% means fully sealed area);
• Count: the number of 20x20mt cells corresponding to a certain percentage of soil sealing or imperviousness;
• Km2: the conversion of the 20x20mt cells into squared kilometres (km2) to facilitate the use of the dataset.
  
  

Further information on the Dataset
This dataset is the result of a combination between different databases of different types and that have been downloaded from different sources. Below, I describe the main steps in data management that resulted in the production of the dataset in an Esri ArcGIS (ArcMap, Version 10.7) project.

1. The high resolution layer (HRL) of the imperviousness density data (IMD) for 2015 has been downloaded from the official website of Copernicus. At the time of producing the dataset (April/May 2021), the 2018 version of the IMD HRL database was not yet validated, so the 2015 version was chosen instead. The type of this dataset is raster.

2. For both Barcelona and Milan, shapefiles of their administrative boundaries have been downloaded from official sources, i.e. the ISTAT (Italian National Statistical Institute) and the ICGC (Catalan Institute for Cartography and Geology). These files have been reprojected to match the IMD HRL projection, i.e. ETRS 1989 LAEA.

3. Urban Atlas (UA) boundaries for the Greater Cities (GRC) and Functional Urban Areas (FUA) of Barcelona and Milan have been checked and reconstructed in Esri ArcGIS from the administrative boundaries files by using a Eurostat correspondence table. This is because at the time of the dataset creation (April/May 2021), the 2018 Urban Atlas shapefiles for these two cities were not fully updated or validated on the Copernicus Urban Atlas website. Therefore, I had to re-create the GRC and FUA boundaries by using the Eurostat correspondence table as an alternative (but still official) data source. The use of the Eurostat correspondence table with the codes and names of municipalities was also useful to detect discrepancies, basically stemming from changes in municipality names and codes and that created inconsistent spatial features. When detected, these discrepancies have been checked with the ISTAT and ICGC offices in charge of producing Urban Atlas data before the final GRC and FUA boundaries were defined.
   

Steps 2) and 3) were the most time consuming, because they required other tools to be used in Esri ArcGIS, like spatial joins and geoprocessing tools for shapefiles (in particular dissolve and area re-calculator in editing sessions) for each of the spatial/territorial scales as indicated in letters a)-h).

Once the databases for both Barcelona and Milan as described in points 2) and 3) were ready (uploaded in Esri ArcGIS, reprojected and their correctness checked), they have been ‘crossed’ (i.e. clipped) with the IMD HRL as described in point 1) and a specific raster for each territorial level has been calculated. The procedure in Esri ArcGIS was the following:

• Clipping: Arctoolbox > Data management tools > Raster > Raster Processing > Clip. The ‘input’ file is the HRL IMD raster file as described in point 1) and the ‘output’ file is each of the spatial/territorial files. The option "Use Input Features for Clipping Geometry (optional)” was selected for each of the clipping.
• Delete and create raster attribute table: Once the clipping has been done, the raster has to be recalculated first through Arctoolbox > Data management tools > Raster > Raster properties > Delete Raster Attribute Table and then through Arctoolbox > Data management tools > Raster > Raster properties > Build Raster Attribute Table; the "overwrite" option has been selected.
  

Other tools used for the raster files in Esri ArcGIS have been the spatial analyst tools (in particular, Zonal > Zonal Statistics). As an additional check, the colour scheme of each of the newly created raster for each of the spatial/territorial attributes as per letters a)-h) above has been changed to check the consistency of its overlay with the original HRL IMD file. However, a perfect match between the shapefiles as per letters a)-h) and the raster files could not be achieved since the raster files are composed of 20x20mt cells.

The newly created attribute tables of each of the raster files have been exported and saved as .txt files. These .txt files have then been copied in the excel corresponding to the final published dataset.