When rain falls over land, a portion of it runs off into stream channels and storm water systems while the remainder infiltrates into the soil or returns to the atmosphere directly through evaporation.Physical properties of soil affect the rate that water is absorbed and the amount of runoff produced by a storm. Hydrologic soil group provides an index of the rate that water infiltrates a soil and is an input to rainfall-runoff models that are used to predict potential stream flow.For more information on using hydrologic soil group in hydrologic modeling see the publication Urban Hydrology for Small Watersheds (Natural Resources Conservation Service, United States Department of Agriculture, Technical Release–55).Dataset SummaryPhenomenon Mapped: Soil hydrologic groupUnits: ClassesCell Size: 30 metersSource Type: DiscretePixel Type: Unsigned integerData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American Samoa)Mosaic Projection: Web Mercator Auxiliary SphereExtent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaSource: Natural Resources Conservation ServicePublication Date: December 2021ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/Data from the gNATSGO database was used to create the layer for the contiguous United States, Alaska, Puerto Rico, and the U.S. Virgin Islands. The remaining areas were created with the gSSURGO database (Hawaii, Guam, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American Samoa).This layer is derived from the 30m (contiguous U.S.) and 10m rasters (all other regions) produced by the Natural Resources Conservation Service (NRCS). The value for hydrologic group is derived from the gSSURGO map unit aggregated attribute table field Hydrologic Group - Dominant Conditions (hydgrpdcd).The seven classes of hydrologic soil group followed by definitions:Group A - Group A soils consist of deep, well drained sands or gravelly sands with high infiltration and low runoff rates.Group B - Group B soils consist of deep well drained soils with a moderately fine to moderately coarse texture and a moderate rate of infiltration and runoff.Group C - Group C consists of soils with a layer that impedes the downward movement of water or fine textured soils and a slow rate of infiltration.Group D - Group D consists of soils with a very slow infiltration rate and high runoff potential. This group is composed of clays that have a high shrink-swell potential, soils with a high water table, soils that have a clay pan or clay layer at or near the surface, and soils that are shallow over nearly impervious material.Group A/D - Group A/D soils naturally have a very slow infiltration rate due to a high water table but will have high infiltration and low runoff rates if drained.Group B/D - Group B/D soils naturally have a very slow infiltration rate due to a high water table but will have a moderate rate of infiltration and runoff if drained.Group C/D - Group C/D soils naturally have a very slow infiltration rate due to a high water table but will have a slow rate of infiltration if drained.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 "soil hydrologic group" 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 "soil hydrologic group" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.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 Terrain 3D layer provides global elevation surface to use as a ground in ArcGIS 3D applications.What can you do with this layer? Use this layer to visualize your maps and layers in 3D using applications like the Scene Viewer in ArcGIS Online and ArcGIS Pro.Show me how1) Working with Scenes in ArcGIS Pro or ArcGIS Online Scene Viewer2) Select an appropriate basemap or use your own3) Add your unique 2D and 3D data layers to the scene. Your data are simply added on the elevation. If your data have defined elevation (z coordinates) this information will be honored in the scene4) Share your work as a Web Scene with others in your organization or the publicDataset CoverageTo see the coverage and sources of various datasets comprising this elevation layer, view the World Elevation Coverage Map. Additionally, this layer contains data from Vantor’s Precision 3D Digital Terrain Models for parts of the globe.This layer is part of a larger collection of elevation layers. For more information, see the Elevation Layers group on ArcGIS Online.

The Federal Emergency Management Agency (FEMA) produces Flood Insurance Rate maps and identifies Special Flood Hazard Areas as part of the National Flood Insurance Program's floodplain management. Special Flood Hazard Areas have regulations that include the mandatory purchase of flood insurance for holders of federally regulated mortgages. In addition, this layer can help planners and firms avoid areas of flood risk and also avoid additional cost to carry insurance for certain planned activities. Dataset SummaryPhenomenon Mapped: Flood Hazard AreasGeographic Extent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands and American Samoa.Projection: Web Mercator Auxiliary SphereData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Northern Mariana Islands, and American Samoa)Cell Sizes: 10 meters (default), 30 meters, and 90 metersUnits: NoneSource Type: ThematicPixel Type: Unsigned integerSource: Federal Emergency Management Agency (FEMA)Update Frequency: AnnualPublication Date: May 7, 2025 This layer is derived from the May 7, 2025 version Flood Insurance Rate Map feature class S_FLD_HAZ_AR. The vector data were then flagged with an index of 94 classes, representing a unique combination of values displayed by three renderers. (In three resolutions the three renderers make nine processing templates.) Repair Geometry was run on the set of features, then the features were rasterized using the 94 class index at a resolutions of 10, 30, and 90 meters, using the Polygon to Raster tool and the "MAXIMUM_COMBINED_AREA" option. Not every part of the United States is covered by flood rate maps. This layer compiles all the flood insurance maps available at the time of publication. To make analysis easier, areas that were NOT mapped by FEMA for flood insurance rates no longer are served as NODATA but are filled in with a value of 250, representing any unmapped areas which appear in the US Census boundary of the USA states and territories. The attribute table corresponding to value 250 will indicate that the area was not mapped.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 "flood hazard areas" 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 "flood hazard areas" in the search box, browse to the layer then click OK. In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro. 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. Processing TemplatesCartographic Renderer - The default. These are meaningful classes grouped by FEMA which group its own Flood Zone Type and Subtype fields. This renderer uses FEMA's own cartographic interpretations of its flood zone and zone subtype fields to help you identify and assess risk. Flood Zone Type Renderer - Specifically renders FEMA FLD_ZONE (flood zone) attribute, which distinguishes the original, broadest categories of flood zones. This renderer displays high level categories of flood zones, and is less nuanced than the Cartographic Renderer. For example, a fld_zone value of X can either have moderate or low risk depending on location. This renderer will simply render fld_zone X as its own color without identifying "500 year" flood zones within that category.Flood Insurance Requirement Renderer - Shows Special Flood Hazard Area (SFHA) true-false status. This may be helpful if you want to show just the places where flood insurance is required. A value of True means flood insurance is mandatory in a majority of the area covered by each 10m pixel. Each of these three renderers have templates at three different raster resolutions depending on your analysis needs. To include the layer in web maps to serve maps and queries, the 10 meter renderers are the preferred option. These are served with overviews and render at all resolutions. However, when doing analysis of larger areas, we now offer two coarser resolutions of 30 and 90 meters in processing templates for added convenience and time savings.Data DictionaryMaking a copy of your area of interest using copyraster in arcgis pro will copy the layer's attribute table to your network alongside the local output raster. The raster attribute table in the copied raster will contain the flood zone, zone subtype, and special flood hazard area true/false flag which corresponds to each value in the layer for your area of interest. For your convienence, we also included a table in CSV format in the box below as a data dictionary you can use as an index to every value in the layer. Value,FLD_ZONE,ZONE_SUBTY,SFHA_TF 2,A,, 3,A,,F 4,A,,T 5,A,,T 6,A,,T 7,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 8,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 9,A,ADMINISTRATIVE FLOODWAY,T 10,A,COASTAL FLOODPLAIN,T 11,A,FLOWAGE EASEMENT AREA,T 12,A99,,T 13,A99,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 14,AE,,F 15,AE,,T 16,AE,,T 17,AE,,T 18,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 19,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 20,AE,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",T 21,AE,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",T 22,AE,ADMINISTRATIVE FLOODWAY,T 23,AE,AREA OF SPECIAL CONSIDERATION,T 24,AE,COASTAL FLOODPLAIN,T 25,AE,COLORADO RIVER FLOODWAY,T 26,AE,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 27,AE,COMMUNITY ENCROACHMENT,T 28,AE,COMMUNITY ENCROACHMENT AREA,T 29,AE,DENSITY FRINGE AREA,T 30,AE,FLOODWAY,T 31,AE,FLOODWAY CONTAINED IN CHANNEL,T 32,AE,FLOODWAY CONTAINED IN STRUCTURE,T 33,AE,FLOWAGE EASEMENT AREA,T 34,AE,RIVERINE FLOODWAY IN COMBINED RIVERINE AND COASTAL ZONE,T 35,AE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 36,AE,STATE ENCROACHMENT AREA,T 37,AH,,T 38,AH,,T 39,AH,FLOODWAY,T 40,AO,,T 41,AO,COASTAL FLOODPLAIN,T 42,AO,FLOODWAY,T 43,AREA NOT INCLUDED,,F 44,AREA NOT INCLUDED,,T 45,AREA NOT INCLUDED,,U 46,D,,F 47,D,,T 48,D,AREA WITH FLOOD RISK DUE TO LEVEE,F 49,OPEN WATER,,F 50,OPEN WATER,,T 51,OPEN WATER,,U 52,V,,T 53,V,COASTAL FLOODPLAIN,T 54,VE,,T 55,VE,,T 56,VE,COASTAL FLOODPLAIN,T 57,VE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 58,X,,F 59,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,F 60,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,T 61,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,U 62,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,F 63,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,F 64,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COASTAL ZONE,F 65,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COMBINED RIVERINE AND COASTAL ZONE,F 66,X,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",F 67,X,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",F 68,X,1 PCT DEPTH LESS THAN 1 FOOT,F 69,X,1 PCT DRAINAGE AREA LESS THAN 1 SQUARE MILE,F 70,X,1 PCT FUTURE CONDITIONS,F 71,X,1 PCT FUTURE CONDITIONS CONTAINED IN STRUCTURE,F 72,X,"1 PCT FUTURE CONDITIONS, COMMUNITY ENCROACHMENT",F 73,X,"1 PCT FUTURE CONDITIONS, FLOODWAY",F 74,X,"1 PCT FUTURE IN STRUCTURE, COMMUNITY ENCROACHMENT",F 75,X,"1 PCT FUTURE IN STRUCTURE, FLOODWAY",F 76,X,AREA OF MINIMAL FLOOD HAZARD, 77,X,AREA OF MINIMAL FLOOD HAZARD,F 78,X,AREA OF MINIMAL FLOOD HAZARD,T 79,X,AREA OF MINIMAL FLOOD HAZARD,U 80,X,AREA OF SPECIAL CONSIDERATION,F 81,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,F 82,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 83,X,FLOWAGE EASEMENT AREA,F 84,X,1 PCT FUTURE CONDITIONS,T 85,AH,COASTAL FLOODPLAIN,T 86,AE,,U 87,AE,FLOODWAY,F 88,X,AREA WITH REDUCED FLOOD HAZARD DUE TO ACCREDITED LEVEE SYSTEM,F 89,X,530,F 90,VE,100,T 91,AE,100,T 92,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO LEVEE SYSTEM,T 93,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO NON-ACCREDITED LEVEE SYSTEM,T 94,A,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 250,AREA NOT INCLUDED,Not Mapped by FEMA, Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

The nine-banded Armadillo (Dasypus novemcinctus) is the only species of Armadillo in the United States and alters ecosystems by excavating extensive burrows used by many other wildlife species. Relatively little is known about its habitat use or population densities, particularly in developed areas, which may be key to facilitating its range expansion. We evaluated Armadillo occupancy and density in relation to anthropogenic and landcover variables in the Ozark Mountains of Arkansas along an urban to rural gradient. Armadillo detection probability was best predicted by temperature (positively) and precipitation (negatively). Contrary to expectations, occupancy probability of Armadillos was best predicted by slope (negatively) and elevation (positively) rather than any landcover or anthropogenic variables. Armadillo density varied considerably between sites (ranging from a mean of 4.88 – 46.20 Armadillos per km2) but was not associated with any environmental or anthropogenic variables. Methods Site Selection Our study took place in Northwest Arkansas, USA, in the greater Fayetteville metropolitan area. We deployed trail cameras (Spypoint Force Dark (Spypoint Inc, Victoriaville, Quebec, Canada) and Browning Strikeforce XD cameras (Browning, Morgan, Utah, USA) over the course of two winter seasons, December 2020-March 2021, and November 2021-March 2022. We sampled 10 study sites in year one, and 12 study sites in year two. All study sites were located in the Ozark Mountains ecoregion in Northwest Arkansas. Sites were all Oak Hickory dominated hardwood forests at similar elevation (213.6 – 541 m). Devils Eyebrow and ONSC are public natural areas managed by the Arkansas Natural heritage Commission (ANHC). Devil’s Den and Hobbs are managed by the Arkansas state park system. Markham Woods (Markham), Ninestone Land Trust (Ninestone) and Forbes, are all privately owned, though Markham has a publicly accessible trail system throughout the property. Lake Sequoyah, Mt. Sequoyah Woods, Kessler Mountain, Lake Fayetteville, and Millsaps Mountain are all city parks and managed by the city of Fayetteville. Lastly, both Weddington and White Rock are natural areas within Ozark National Forest and managed by the U.S. Forest Service. We sampled 5 sites in both years of the study including Devils Eyebrow, Markham Hill, Sequoyah Woods, Ozark Natural Science Center (ONSC), and Kessler Mountain. We chose our study sites to represent a gradient of human development, based primarily on Anthropogenic noise values (Buxton et al. 2017, Mennitt and Fristrup 2016). We chose open spaces that were large enough to accommodate camera trap research, as well as representing an array of anthropogenic noise values. Since anthropogenic noise is able to permeate into natural areas within the urban interface, introducing human disturbance that may not be detected by other layers such as impervious surface and housing unit density (Buxton et al. 2017), we used dB values for each site as an indicator of the level of urbanization. Camera Placement We sampled ten study sites in the first winter of the study. At each of the 10 study sites, we deployed anywhere between 5 and 15 cameras. Larger study areas received more cameras than smaller sites because all cameras were deployed a minimum of 150m between one another. We avoided placing cameras on roads, trails, and water sources to artificially bias wildlife detections. We also avoided placing cameras within 15m of trails to avoid detecting humans. At each of the 12 study areas we surveyed in the second winter season, we deployed 12 to 30 cameras. At each study site, we used ArcGIS Pro (Esri Inc, Redlands, CA) to delineate the trail systems and then created a 150m buffer on each side of the trail. We then created random points within these buffered areas to decide where to deploy cameras. Each random point had to occur within the buffered areas and be a minimum of 150m from the next nearest camera point, thus the number of cameras at each site varied based upon site size. We placed all cameras within 50m of the random points to ensure that cameras were deployed on safe topography and with a clear field of view, though cameras were not set in locations that would have increased animal detections (game trails, water sources, burrows etc.). Cameras were rotated between sites after 5 or 10 week intervals to allow us to maximize camera locations with a limited number of trail cameras available to us. Sites with more than 25 cameras were active for 5 consecutive weeks while sites with fewer than 25 cameras were active for 10 consecutive weeks. We placed all cameras on trees or tripods 50cm above ground and at least 15m from trails and roads. We set cameras to take a burst of three photos when triggered. We used Timelapse 2.0 software (Greenberg et al. 2019) to extract metadata (date and time) associated with all animal detections. We manually identified all species occurring in photographs and counted the number of individuals present. Because density estimation requires the calculation of detection rates (number of Armadillo detections divided by the total sampling period), we wanted to reduce double counting individuals. Therefore, we grouped photographs of Armadillos into “episodes” of 5 minutes in length to reduce double counting individuals that repeatedly triggered cameras (DeGregorio et al. 2021, Meek et al. 2014). A 5 min threshold is relatively conservative with evidence that even 1-minute episodes adequately reduces double counting (Meek et al. 2014). Landcover Covariates To evaluate occupancy and density of Armadillos based on environmental and anthropogenic variables, we used ArcGIS Pro to extract variables from 500m buffers placed around each camera (Table 2). This spatial scale has been shown to hold biological meaning for Armadillos and similarly sized species (DeGregorio et al. 2021, Fidino et al. 2016, Gallo et al. 2017, Magle et al. 2016). At each camera, we extracted elevation, slope, and aspect from the base ArcGIS Pro map. We extracted maximum housing unit density (HUD) using the SILVIS housing layer (Radeloff et al. 2018, Table 2). We extracted anthropogenic noise from the layer created by Mennitt and Fristrup (2016, Buxton et al. 2017, Table 2) and used the “L50” anthropogenic sound level estimate, which was calculated by taking the difference between predicted environmental noise and the calculated noise level. Therefore, we assume that higher levels of L50 sound corresponded to higher human presence and activity (i.e. voices, vehicles, and other sources of anthropogenic noise; Mennitt and Fristrup 2016). We derived the area of developed open landcover, forest area, and distance to forest edge from the 2019 National Land Cover Database (NLDC, Dewitz 2021, Table 2). Developed open landcover refers to open spaces with less than 20% impervious surface such as residential lawns, cemeteries, golf courses, and parks and has been shown to be important for medium-sized mammals (Gallo et al. 2017, Poessel et al. 2012). Forest area was calculated by combing all forest types within the NLCD layer (deciduous forest, mixed forest, coniferous forest), and summarizing the total area (km2) within the 500m buffer. Distance to forest edge was derived by creating a 30m buffer on each side of all forest boundaries and calculating the distance from each camera to the nearest forest edge. We calculated distance to water by combining the waterbody and flowline features in the National Hydrogeography Dataset (U.S. Geological Survey) for the state of Arkansas to capture both permanent and ephemeral water sources that may be important to wildlife. We measured the distance to water and distance to forest edge using the geoprocessing tool “near” in ArcGIS Pro which calculates the Euclidean distance between a point and the nearest feature. We extracted Average Daily Traffic (ADT) from the Arkansas Department of Transportation database (Arkansas GIS Office). The maximum value for ADT was calculated using the Summarize Within tool in ArcGIS Pro. We tested for correlation between all covariates using a Spearman correlation matrix and removed any variable with correlation greater than 0.6. Pairwise comparisons between distance to roads and HUD and between distance to forest edge and forest area were both correlated above 0.6; therefore, we dropped distance to roads and distance to forest edge from analyses as we predicted that HUD and forest area would have larger biological impacts on our focal species (Kretser et al. 2008). Occupancy Analysis In order to better understand habitat associations while accounting for imperfect detection of Armadillos, we used occupancy modeling (Mackenzie et al. 2002). We used a single-species, single-season occupancy model (Mackenzie et al. 2002) even though we had two years of survey data at 5 of the study sites. We chose to do this rather than using a multi-season dynamic occupancy model because most sites were not sampled during both years of the study. Even for sites that were sampled in both years, cameras were not placed in the same locations each year. We therefore combined all sampling into one single-season model and created unique site by year combinations as our sampling locations and we used year as a covariate for analysis to explore changes in occupancy associated with the year of study. For each sampling location, we created a detection history with 7 day sampling periods, allowing presence/absence data to be recorded at each site for each week of the study. This allowed for 16 survey periods between 01 December 2020, and 11 March 2021 and 22 survey periods between 01 November 2021 and 24 March 2022. We treated each camera as a unique survey site, resulting in a total of 352 sites. Because not all cameras were deployed at the same time and for the same length of time, we used a staggered entry approach. We used a multi-stage fitting approach in which we

This dataset contains plans of operations for locatable mineral cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Locatable minerals include all minerals locatable under the 1872 General Mining Law. This data set contains cases for locatable minerals under plan level operations with the case disposition of 'Authorized' or 'Pending'.Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores.Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County.Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This dataset contains non-energy leasable cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. This data set contains cases with the dispositions of 'Authorized', 'Pending','Closed', and 'Interim'. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

Many species show range expansions or contractions due to climate-change-induced changes in habitat suitability. In cold climates, many species that are limited by snow are showing range expansions due to reduced winter severity. The European polecat (Mustela putorius) occurs over large parts of Europe with its northern range limit in southern Fennoscandia. However, it is to date unknown what factors limit polecat distribution. We thus investigated whether climate or land-use variables are more important in determining the habitat suitability for polecats in Sweden. We hypothesized that 1) climatic factors, especially the yearly number of snow days, drive habitat suitability for polecats, and that, 2) as the number of snow days is predicted to decline in the near future, habitat suitability in northern Sweden will increase. We used a combination of sightings data and a selection of national maps of environmental factors to test these hypotheses using MaxEnt models. We also used maps of future climate predictions (2021–2050 and 2063–2098) to predict future habitat suitability. The number of snow days was the most important factor, negatively determining habitat suitability for polecats, as expected. Consequently, the predictions showed an increase in suitable habitat both in the current distribution range and in northern Sweden, especially along the coast of the Baltic Sea. Our results suggest that the polecat distribution is limited by snow and that reduced snow cover will likely result in a northward range expansion. However, the exact mechanisms for how snow limits polecats are still poorly understood. Consequently, we expect the Scandinavian polecat population to increase in numbers, in contrast to many populations elsewhere in Europe, where numbers are declining. Due to polecat predation, the expansion of the species might have cascading effects on other wildlife populations. Methods Polecat sightings data To determine the distribution and habitat suitability of polecats in Sweden, we used sightings data of polecats gathered by volunteers and documented to the Swedish Species Information Centre between 1960 and 2020 (Figure 1; Swedish Species Information Centre 2020). We validated data at the edge of the distribution by contacting the person that reported the sighting, and removed data points if there was uncertainty about the sighting, we also removed data that was categorized as roadkill. As a result, we discarded 44 of the 425 sightings before analysis. Due to an increase of popularity of the sightings platform, the majority of sightings (78%) used in the analyses was from the period 2010–2020. Description of covariates We used nine covariates distributed over four different categories to test our hypotheses (Table 1). We included these covariates based on habitat and diet preferences of the polecat found in previous studies All parameters were rasterized and aggregated to 1-km2 grid cells over the whole of Sweden in ArcGis Pro version 2.6.0

Land cover and soil moisture

We selected several land-cover types and an index of soil moisture from the ungeneralised version of the National Land Cover Database (NMD) Sweden. This project provides a land cover map for the whole of Sweden divided into 24 different land-cover types, as well as a measure of soil moisture as a spectrum from dry to wet soil. We reclassified 17 of the 24 land-cover types into three different groups: coniferous forest, deciduous forest and open landscapes (Table S1.1). We selected these three groups for ease of analysis and due to previous studies showing that polecats selected or avoided these land-cover types at small spatial scales. Polecats were found to avoid coniferous forest (Baghli and Verhagen 2005, Zabala et al. 2005), select for deciduous forest (Jedrzejewski et al. 1993, Baghli et al. 2005), and use landscapes that were characterised by a variety of open habitat and forest (Blandford 1987, Lodé 1993, 2000a, Baghli et al. 2005). Furthermore, we used soil moisture as a variable that could further distinguish areas that would be wet during part of the year, which could result in increased amphibian populations, which are an important part of the polecat’s diet (Lodé 1993, 1997, 2000b, Hammershøj et al. 2004, Malecha and Antczak 2013). After reclassification, we determined the proportion of surface covered by each land-cover group, as well as the average soil moisture index, for each 1-km2 grid cell. Table S1.1: The landcover type clusters and which variables are merged from the original landcover data.

Cluster of land-cover types

Land-cover type number as presented in the NMD

Coniferous forest

111 (Pine forest not on wetland), 112 (Spruce forest not on wetland), 113 (Mixed coniferous not on wetland), 121 (Pine forest on wetland), 122 (Spruce forest on wetland), 123 (Mixed coniferous on wetland)

Deciduous forest

115 (Deciduous forest not on wetland), 116 (Deciduous hardwood forest not on wetland), 117 (Deciduous forest with deciduous hardwood forest not on wetland), 125 (Deciduous forest on wetland), 126 (Deciduous hardwood forest on wetland), 127 (Deciduous with deciduous hardwood forest on wetland)

Open landscapes

2 (Open wetland), 3 (Arable land), 41 (Non-vegetated other open land), 42 (Vegetated other open land), 118 (Temporarily non-forest not on wetland), 128 (Temporarily non-forest on wetland)

Snow cover and Minimum winter temperature The Swedish Meteorological and Hydrological Institute provides snow cover data for Sweden as the average number of days with snow with a depth above 20mm. The data is provided in 4 time periods, including two future projections (P1=1961–1990, P2 = 1991–2013, P3 = 2021–2050, P4= 2069–2098; Swedish Meteorological and Hydrological Institute 2021). The future projections we included are based on the 4.5 RCP scenario(Thomson et al. 2011). We included these data as a previous study showed that polecats had more difficulty catching prey when there is snow on the ground (Weber 1989). The data consists of interpolated data from 200 weather stations with an average given per municipality. We have rasterized the data giving average values for cells crossing municipality boundaries. We used data averages per cell of P2 for model building, while we used averages of P3 and P4 per cell for model projections of future scenarios.

Human pressure

We used the human footprint index as published by NASA in 2018 as a measure of human pressure. We did this as previous studies have shown that polecats tend to select for areas with extensive human use (Sidorovich et al. 1996, Rondinini et al. 2006) while avoiding urban centres (Zabala et al. 2005). The dataset is based on the global human footprint between 1995 and 2004. The human footprint is an index based on population density, land-use, infrastructure (buildings, lights, land use/cover) and human access (roads, railways; Venter et al. 2018). This raster dataset is publicly available and has a resolution of 1 km2. We only clipped the dataset to the borders of Sweden. Water availability We used the Water & Wetness geo data from Copernicus (CLMS 2018) as a measure of water availability. We did this as previous studies showed that polecats select for riparian habitat (Baghli et al. 2005) as amphibians are an important part of their diet (Lodé 1993, 1997, 2000b, Hammershøj et al. 2004, Malecha and Antczak 2013). This dataset includes all waterways and waterbodies with a resolution of 10 m. We have outlined all waterbodies and then made a buffer of 30 meters around all waterlines to represent near-water (riparian) habitat. We then calculated the proportion of near-water habitat in each 1-km2 grid cell. Elevation We used elevation data from the Copernicus Land Monitoring Service - EU-DEM project. We did this as previous studies showed that polecats avoid high-elevation areas. The dataset is provided as a raster with a spatial resolution of 25 meters. We calculated the average elevation for each 1-km2 grid cell. Bias correction for sampling intensity Due to the nature of citizen science data, it is prone to come with a bias. This bias manifests itself mostly in a discrepancy in spatial sampling effort. To account for this bias, we created a density kernel (as recommended by Kramer-Schadt et al. 2013 and Morelle and Lejeune 2015 and in line with Rutten et al. 2019) based on all mustelid sightings (n = 25686) reported to the Swedish Species Information Centre between 1972 and 2021 (Swedish Species Information Centre 2020), except for the Eurasian badger (Meles meles), the wolverine (Gulo gulo) and the polecat. We excluded the badger and wolverine as we expect this species to be much easier to identify and see compared to the polecat and other mustelids. Furthermore, badger and wolverine have a limited distribution in Sweden, while all other species – Eurasian otter (Lutra lutra), pine marten (Martes martes), American mink (Neovison vison), stoat (Mustela erminea), and weasel (Mustela nivalis) – have a distribution that covers the whole of Sweden (Swedish Species Information Centre 2020). We created the kernel with the ‘Kernel Density’ function in ArcGIS Pro (Esri 2021) with the mustelid sighting coordinates and the 1 km2 raster grid used for the covariates. The use of this density kernel is based on the assumption that people reporting other mustelids would also report a polecat if they saw one, and thus that the distribution of mustelid sightings is representative of the distribution of potential polecat reporters.

This dataset contains land use authorization leases, permits and easement cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. The minimum data entry requirement for legal description for linear authorizations is to the nearest 40 acre aliquot level (e.g.,NENW). Legal descriptions for non-linear authorizations are as described on the authorizing document. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. This data set contains cases with the dispositions of 'Authorized', 'Pending','Closed', and 'Interim'.Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This layer shows health insurance coverage by type and by age group. This is shown by tract, county, and state centroids. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the count and percent uninsured. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B27010 (Not all lines of this ACS table are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

This dataset contains mining claim cases with the case disposition (status) of anything other than closed from US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS). The BLM only requires that mining claims be identified down to the affected quarter section(s)—as such, that is what the MLRS research map and public reports will reflect, most commonly. Claim boundaries, as staked and monumented, are found in the accepted Notice/Certificate of Location as part of the official case file, managed by the BLM State Office having jurisdiction over the claim.The geometries are created in multiple ways but are primarily derived from Legal Land Descriptions (LLD) for the case and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This New Zealand Point Cloud Classification Deep Learning Package will classify point clouds into tree and background classes. This model is optimized to work with New Zealand aerial LiDAR data.The classification of point cloud datasets to identify Trees is useful in applications such as high-quality 3D basemap creation, urban planning, forestry workflows, and planning climate change response.Trees could have a complex irregular geometrical structure that is hard to capture using traditional means. Deep learning models are highly capable of learning these complex structures and giving superior results.This model is designed to extract Tree in both urban and rural area in New Zealand.The Training/Testing/Validation dataset are taken within New Zealand resulting of a high reliability to recognize the pattern of NZ common building architecture.Licensing requirementsArcGIS Desktop - ArcGIS 3D Analyst extension for ArcGIS ProUsing the modelThe model can be used in ArcGIS Pro's Classify Point Cloud Using Trained Model tool. Before using this model, ensure that the supported deep learning frameworks libraries are installed. For more details, check Deep Learning Libraries Installer for ArcGIS.Note: Deep learning is computationally intensive, and a powerful GPU is recommended to process large datasets.InputThe model is trained with classified LiDAR that follows the LINZ base specification. The input data should be similar to this specification.Note: The model is dependent on additional attributes such as Intensity, Number of Returns, etc, similar to the LINZ base specification. This model is trained to work on classified and unclassified point clouds that are in a projected coordinate system, in which the units of X, Y and Z are based on the metric system of measurement. If the dataset is in degrees or feet, it needs to be re-projected accordingly. The model was trained using a training dataset with the full set of points. Therefore, it is important to make the full set of points available to the neural network while predicting - allowing it to better discriminate points of 'class of interest' versus background points. It is recommended to use 'selective/target classification' and 'class preservation' functionalities during prediction to have better control over the classification and scenarios with false positives.The model was trained on airborne lidar datasets and is expected to perform best with similar datasets. Classification of terrestrial point cloud datasets may work but has not been validated. For such cases, this pre-trained model may be fine-tuned to save on cost, time, and compute resources while improving accuracy. Another example where fine-tuning this model can be useful is when the object of interest is tram wires, railway wires, etc. which are geometrically similar to electricity wires. When fine-tuning this model, the target training data characteristics such as class structure, maximum number of points per block and extra attributes should match those of the data originally used for training this model (see Training data section below).OutputThe model will classify the point cloud into the following classes with their meaning as defined by the American Society for Photogrammetry and Remote Sensing (ASPRS) described below: 0 Background 5 Trees / High-vegetationApplicable geographiesThe model is expected to work well in the New Zealand. It's seen to produce favorable results as shown in many regions. However, results can vary for datasets that are statistically dissimilar to training data.Training dataset - Wellington CityTesting dataset - Tawa CityValidation/Evaluation dataset - Christchurch City Dataset City Training Wellington Testing Tawa Validating ChristchurchModel architectureThis model uses the PointCNN model architecture implemented in ArcGIS API for Python.Accuracy metricsThe table below summarizes the accuracy of the predictions on the validation dataset. - Precision Recall F1-score Never Classified 0.991200 0.975404 0.983239 High Vegetation 0.933569 0.975559 0.954102Training dataThis model is trained on classified dataset originally provided by Open TopoGraphy with < 1% of manual labelling and correction.Train-Test split percentage {Train: 80%, Test: 20%} Chosen this ratio based on the analysis from previous epoch statistics which appears to have a descent improvementThe training data used has the following characteristics: X, Y, and Z linear unitMeter Z range-121.69 m to 26.84 m Number of Returns1 to 5 Intensity16 to 65520 Point spacing0.2 ± 0.1 Scan angle-15 to +15 Maximum points per block8192 Block Size20 Meters Class structure[0, 5]Sample resultsModel to classify a dataset with 5pts/m density Christchurch city dataset. The model's performance are directly proportional to the dataset point density and noise exlcuded point clouds.To learn how to use this model, see this story

This dataset contains geothermal leases cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores.Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS.Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSSGroup 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field).Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not.Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data.Group 6 – Mapped to County. Scores of “25” map to the County.Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This dataset contains coal cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. This data set contains cases with the dispositions of 'Authorized', 'Pending','Closed', and 'Interim'.Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This dataset contains oil and gas leases cases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores.Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data.Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This layer includes Landsat 8 and 9 imagery for use in visualization and analysis. This layer is time enabled and includes the panchromatic band from the Operational Land Imager (OLI). It is updated daily with new imagery directly sourced from the USGS Landsat collection on AWS.Geographic CoverageGlobal Land SurfacePolar 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.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 ‘Query Filter’ to restrict the default layer display to a specified image or group of images.Visual RenderingDefault rendering is Panchromatic (0.5-0.68 µm).Raster Functions enable on-the-fly rendering of band combinations and calculated indices from the source imagery.The DRA version of each layer enables visualization of the full dynamic range of the images.Other pre-defined Raster Functions can be selected via the renderer drop-down or custom functions can be created.This layer is part of a larger collection of Landsat Imagery Layers that you can use to perform a variety of mapping analysis tasks.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.

This layer includes Landsat 8 and 9 imagery for use in visualization and analysis. This layer is time enabled and includes a number of pansharpened renderings on demand. The layer includes 15m imagery rendered on-the-fly as Natural Color with DRA. 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.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 ‘Query Filter’ to restrict the default layer display to a specified image or group of images.Visual RenderingDefault rendering is PanSharpened Natural Color images.Raster Functions enable on-the-fly rendering of band combinations and calculated indices from the source imagery.The DRA version of each layer enables visualization of the full dynamic range of the images.Other pre-defined Raster Functions can be selected via the renderer drop-down or custom functions can be created.This layer is part of a larger collection of Landsat Imagery Layers that you can use to perform a variety of mapping analysis tasks.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.

This layer shows total population counts by sex, age, and race groups data from the 2020 Census Demographic and Housing Characteristics. This is shown by Nation, State, County, Census Tract, Block Group boundaries. Each geography layer contains a common set of Census counts based on available attributes from the U.S. Census Bureau. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.   To see the full list of attributes available in this service, go to the "Data" tab above, and then choose "Fields" at the top right. Each attribute contains definitions, additional details, and the formula for calculated fields in the field description. Vintage of boundaries and attributes: 2020 Demographic and Housing Characteristics Table(s): P1, H1, H3, P2, P3, P5, P12, P13, P17, PCT12 (Not all lines of these DHC tables are available in this feature layer.)Data downloaded from: U.S. Census Bureau’s data.census.gov siteDate the Data was Downloaded: May 25, 2023Geography Levels included: Nation, State, County, Census Tract, Block GroupNational Figures: included in Nation layer The United States Census Bureau Demographic and Housing Characteristics: 2020 Census Results 2020 Census Data Quality Geography & 2020 Census Technical Documentation Data Table Guide: includes the final list of tables, lowest level of geography by table and table shells for the Demographic Profile and Demographic and Housing Characteristics.News & Updates This layer is ready to be used in ArcGIS Pro, ArcGIS Online and its configurable apps, Story Maps, dashboards, Notebooks, Python, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the U.S. Census Bureau when using this data. Data Processing Notes: These 2020 Census boundaries come from the US Census TIGER geodatabases. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For Census tracts and block groups, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract and block group boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are unchanged and available as attributes within the data table (units are square meters).  The layer contains all US states, Washington D.C., and Puerto Rico. Census tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99). Block groups that fall within the same criteria (Block Group denoted as 0 with no area land) have also been removed.Percentages and derived counts, are calculated values (that can be identified by the "_calc_" stub in the field name). Field alias names were created based on the Table Shells file available from the Data Table Guide for the Demographic Profile and Demographic and Housing Characteristics. Not all lines of all tables listed above are included in this layer. Duplicative counts were dropped. For example, P0030001 was dropped, as it is duplicative of P0010001.To protect the privacy and confidentiality of respondents, their data has been protected using differential privacy techniques by the U.S. Census Bureau.

This dataset contains oil shale leases derived from Legal Land Descriptions (LLD) contained in the US Bureau of Land Management's, BLM, Mineral and Land Record System(MLRS) and geocoded (mapped) using the Public Land Survey System (PLSS) derived from the most accurate survey data available through BLM Cadastral Survey workforce. Geospatial representations might be missing for some cases that can not be geocoded using the MLRS algorithm. This data set contains cases with the dispositions of 'Authorized', 'Pending','Closed', and 'Interim'. Each case is given a data quality score based on how well it mapped. These can be lumped into seven groups to provide a simplified way to understand the scores. Group 1: Direct PLSS Match. Scores “0”, “1”, “2”, “3” should all have a match to the PLSS data. There are slight differences, but the primary expectation is that these match the PLSS. Group 2: Calculated PLSS Match. Scores “4”, “4.1”, “5”, “6”, “7” and “8” were generated through a process of creating the geometry that is not a direct capture from the PLSS. They represent a best guess based on the underlining PLSS Group 3 – Mapped to Section. Score of “8.1”, “8.2”, “8.3”, “9” and “10” are mapped to the Section for various reasons (refer to log information in data quality field). Group 4- Combination of mapped and unmapped areas. Score of 15 represents a case that has some portions that would map and others that do not. Group 5 – No NLSDB Geometry, Only Attributes. Scores “11”, “12”, “20”, “21” and “22” do not have a match to the PLSS and no geometry is in the NLSDB, and only attributes exist in the data. Group 6 – Mapped to County. Scores of “25” map to the County. Group 7 – Improved Geometry. Scores of “100” are cases that have had their geometry edited by BLM staff using ArcGIS Pro or MLRS bulk upload tool.

This submission is from a master's group thesis project at The Bren School of Environmental Science & Management at the University of California, Santa Barbara, and contains the final written report and associated datasets. The graduate student researchers who completed this project include: Meghan Fletcher, Alyssa Kibbe, Grace Kumaishi, Anna Talken, and Nikole Vannest.

The California landscape has been fragmented by urban development, infrastructure, and agriculture. Maintaining connectivity between areas of wildlife habitat is important for the viability of many long-ranging species, such as the mountain lion (Puma concolor). Mountain lion populations are highly susceptible to habitat fragmentation, and face reduced access to resources and decreased genetic diversity. This study explores the habitat connectivity between the Jack and Laura Dangermond Preserve (JLDP), a 24,460 acre protected property owned by The Nature Conservancy (TNC), and neighboring protected areas to identify potential pathways of movement for mountain lions along the Central and Southern California coast. In this project, we: 1) determine regional connectivity and least cost paths between core habitats by modeling suitable mountain lion habitat, 2) estimate mountain lion habitat use and movement on JLDP by performing a site-level suitability and corridor analysis and 3) create a short film focused on highlighting our research, the role that JLDP plays in conservation, and the importance of habitat connectivity. The results of our project show that JLDP contains suitable habitat for mountain lions and may play a positive role in coastal connectivity. When considering the connectivity between JLDP and other regional protected areas, our analyses indicate that urbanized coastal regions act as barriers to mountain lions and contain pinch points that channelize movement. These results can guide TNC in developing management strategies for protecting mountain lions on JLDP and in the surrounding region.

Analyses were conducted using ArcGIS, Google Earth Engine, MaxENT, Circuitscape, and Omniscape. The project began in April 2021 and ended in June 2022. Methods Data was collected from open source data acquired using Google Earth Engine and Esri ArcOnline from the following sources: NASA, USGS, JPL-CalTech, Conservation Science Partners, CalFish, US Census and CalFire. It was processed using Esri ArcMap, ArcGIS Pro, Maxent, Omniscape via Jupyter Notebook and the Linkage Mapper Toolkit within ArcMap.

Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals. Data from the gSSURGO databasewas used to create this layer. To download ready-to-use project packages of useful soil data derived from the SSURGO dataset, please visit the USA SSURGO Downloader app. Dataset SummaryPhenomenon Mapped: Soils of the United States and associated territoriesGeographic Extent: The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaCoordinate System: Web Mercator Auxiliary SphereVisible Scale: 1:144,000 to 1:1,000Source: USDA Natural Resources Conservation ServiceUpdate Frequency: AnnualPublication Date: December 2024 What can you do with this layer?ArcGIS OnlineFeature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro.Below are just a few of the things you can do with a feature service in Online and Pro.Add this layer to a map in the map viewer. The layer is limited to scales of approximately 1:144,000 or larger but avector tile layercreated from the same data can be used at smaller scales to produce awebmapthat displays across the full scale range. The layer or a map containing it can be used in an application.Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections and apply filters. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Change the layer’s style and filter the data. For example, you could set a filter forFarmland Class= "All areas are prime farmland" to create a map of only prime farmland.Add labels and set their propertiesCustomize the pop-up ArcGIS ProAdd this layer to a 2d or 3d map. The same scale limit as Online applies in ProUse as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of theLiving Atlas of the Worldthat provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Data DictionaryAttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them. Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units.Area SymbolSpatial VersionMap Unit Symbol Map Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field.Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability Rating Legend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project Scale Survey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields.Survey Area VersionTabular Version Map Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field. Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted Average Component Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected. Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent Key Component Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r).Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence -