This dataset contains 50-ft contours for the Hot Springs shallowest unit of the Ouachita Mountains aquifer system potentiometric-surface map. The potentiometric-surface shows altitude at which the water level would have risen in tightly-cased wells and represents synoptic conditions during the summer of 2017. Contours were constructed from 59 water-level measurements measured in selected wells (locations in the well point dataset). Major streams and creeks were selected in the study area from the USGS National Hydrography Dataset (U.S. Geological Survey, 2017), and the spring point dataset with 18 spring altitudes calculated from 10-meter digital elevation model (DEM) data (U.S. Geological Survey, 2015; U.S. Geological Survey, 2016). After collecting, processing, and plotting the data, a potentiometric surface was generated using the interpolation method Topo to Raster in ArcMap 10.5 (Esri, 2017a). This tool is specifically designed for the creation of digital elevation models and imposes constraints that ensure a connected drainage structure and a correct representation of the surface from the provided contour data (Esri, 2017a). Once the raster surface was created, 50-ft contour interval were generated using Contour (Spatial Analyst), a spatial analyst tool (available through ArcGIS 3D Analyst toolbox) that creates a line-feature class of contours (isolines) from the raster surface (Esri, 2017b). The Topo to Raster and contouring done by ArcMap 10.5 is a rapid way to interpolate data, but computer programs do not account for hydrologic connections between groundwater and surface water. For this reason, some contours were manually adjusted based on topographical influence, a comparison with the potentiometric surface of Kresse and Hays (2009), and data-point water-level altitudes to more accurately represent the potentiometric surface. Select References: Esri, 2017a, How Topo to Raster works—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/how-topo-to-raster-works.htm. Esri, 2017b, Contour—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro Raster Surface toolset at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/contour.htm. Kresse, T.M., and Hays, P.D., 2009, Geochemistry, Comparative Analysis, and Physical and Chemical Characteristics of the Thermal Waters East of Hot Springs National Park, Arkansas, 2006-09: U.S. Geological Survey 2009–5263, 48 p., accessed November 28, 2017, at https://pubs.usgs.gov/sir/2009/5263/. U.S. Geological Survey, 2015, USGS NED 1 arc-second n35w094 1 x 1 degree ArcGrid 2015, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html. U.S. Geological Survey, 2016, USGS NED 1 arc-second n35w093 1 x 1 degree ArcGrid 2016, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html.

The Terrain 3D layer provides global elevation surface to use in ArcGIS 3D applicationsWhat 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 Coverage To see the coverage and sources of various datasets comprising this elevation layer, view the Elevation Coverage Map. Additionally, this layer uses data from Maxar’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.

Elevation service which can be used in ArcGIS Pro or in an ArcGIS Online Scene Layer.

The TopoBathy 3D layer provides a global seamless topography (land elevation) and bathymetry (water depths) surface to use in ArcGIS 3D applications.What can you do with this layer?This layer is meant to be used as a ground in ArcGIS Online Web Scenes, ArcGIS Earth, and ArcGIS Pro to help visualize your maps and data in 3D.How do I use this layer?In the ArcGIS Online Web Scene Viewer:Sign-in with ArcGIS Online accountOn the Designer toolbar, click Add Layers Click Browse layers and choose Living Atlas.Search for TopoBathy 3DAdd TopoBathy 3D (Elevation Layer)The TopoBathy 3D will get added under Ground. Change basemap to OceansOptionally, add any other operational layers to visualize in 3DIn ArcGIS Pro:Ensure you are logged in with an ArcGIS Online accountOpen a Global SceneOn the Map tab, click Add Data > Elevation Source LayerUnder Portal, click Living Atlas and search for TopoBathy 3DSelect TopoBathy 3D (Elevation Layer) and click OKThe TopoBathy 3D will get added under GroundOptionally, remove other elevation layers from ground and choose the desired basemapDataset Coverage To see the coverage and sources of various datasets comprising this elevation layer, view the Elevation Coverage Map. Additionally, this layer uses data from Maxar’s Precision 3D Digital Terrain Models for parts of the globe.

Elevation service which can be used in ArcGIS Pro or in an ArcGIS Online Scene Layer.

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.

A 2D Hydraulic model (HEC-RAS) for below Tuttle Creek Reservoir at the confluence of the Kansas River and the Big Blue River near Manhattan, KS is presented. Model geometry is based on United States Geological Survey (USGS) 3DEP data (2015), with underwater bathymetry “burned” in using cross-sections sampled in the field in April of 2023. The model was calibrated based on water surface measured during data collection. The hydraulic simulations correspond to streamflows during which fish monitoring data were collected by researchers at Kansas State University (L. Rowley and K. Gido, to be published). Results from the hydraulic model, coupled with a sediment transport model, will be used to study fish and macroinvertabrate ecological response to streamflow. Methods The following is a summary of data utilized for developing a bathymetric terrain for 2D hydraulic modeling using HEC-RAS. Data used for model calibration and validation is also discussed.

Available Data Cross-section elevation data were collected by the United States Army Corps of Engineers (USACE) Kansas City District at approximately 200-foot to 1000-foot increments at the confluence of the Big Blue River and the Kansas River near Manhattan, Kansas. The following equipment was used by two complete surveying teams: • Ohmex SonarMite single beam echo sounder SFX @ 200khz, • Ohmex SonarMite single beam echo sounder DFX @ 28kHz & 200kHZ, • Trimble R12i 0096 & 0098, • Trimble R8 1984 & 6282

The cross-section elevation data were collected by boat and supplemented by hand-carried, pole-mounted Trimbles on April 10 to 14, 2023. The USGS gage on the Big Blue River near Manhattan, KS (06887000) had an average discharge of 425 cfs during the field collection time period (Figure 1). A USGS gage downstream of the confluence, Kansas River at Wamego, KS (06887500) shows an average discharge of 780 cfs at the same time period (Figure 2).

Figure 1 (Refer to supplemental information file). USGS gage Big Blue R NR Manhattan, KS – 06887000 discharge data for the week of April 11, 2023 – April 15, 2023. The average flow was taken as 425 cfs.

Figure 2 (Refer to supplemental information file). USGS gage Kansas River at Wamego, KS (06887500) discharge data for the week of April 11, 2023 – April 15, 2023. The average flow was taken as 780 cfs. Wamego, KS is downstream of the Big Blue River and Kansas River confluence and represents combined flow for both tributaries.

Figure 3 (Refer to supplemental information file). Map of bathymetric cross-sections collected in April 2023 near Manhattan, KS. Arrows show flow direction. Inset is the data collection location relative to the state of Kansas.

Terrain The field data collection featured 56 cross-sections. HEC-RAS 6.3.1 was utilized to create a bathymetric surface by interpolating 1-D cross-sections, while a 1-m resolution USGS 3DEP terrain (2015) was used for the floodplain and surrounding areas. A more recent USGS 3DEP (2018) data was available but featured higher stream flow than the 2015 data collection and therefore, more of the channel was submerged. Overall, the difference between 2015 and 2018 had a mean deviation of ~0.04 feet, with a majority of the differences in the channel ranging between +/-0.5 feet. Islands in this reach are unvegetated and prone to movement, and therefore the exact channel form is uncertain. However, it is assumed that relative island areas are consistent throughout the reach, and 2015 LiDAR was used to delineate the most island area as possible.

To build the bathymetric terrain, a similar process as what was discussed in Harris et al. (2023), field collected data were imported into ArcGIS Pro 3.0 as a point shapefile. To preserve georeferencing, the point shapefile was segmented into groups of 3-4 cross-sections and these cross-sections were interpolated into mini-surfaces using the Inverse Distance Weighted (IDW) spatial analysis tool. These mini-surfaces were brought into HEC-RAS and cross-sections were drawn to intersect with these field surveyed locations. The 1-D cross-sections were then used to create a TIFF for the entire channel area. The 1D interpolation captures the channel centerline between measured cross-sections but meanders and channel widening may not be covered by the interpolated channel. The channel raster was broken into its component objects or “exploded”, in ArcGIS Pro using the Raster to Point tool. The points were then interpolated using the Inverse-Distance-Weighted interpolation tool (IDW). This creates a terrain that covers meanders and channel expansion while maintaining fidelity to the original channel raster.

Areas where the terrain was inundated at the time of LiDAR data collection are “flat” and referred to as a hydro-flattened surface. The Slope tool in ArcMap was used to delineate these hydro-flattened areas and a shapefile tracing unsubmerged islands was used. The IDW surface was clipped to the hydro-flattened extents and then mosaicked with the original 3DEP terrain to create a seamless bathymetric and topographic surface.

The field data collected in April 2023 (Figure 3) required supplemental information to cover a fish monitoring instance upstream of the bridge at Pillsbury Drive/177. In September 2021, the USACE Kansas City District collected sediment samples with XY-georeference and depth measurements. The LiDAR hydro-flattened surface was used to estimate the energy grade slope from the new cross-section to the recent field monitoring extents. The model scenario or “plan” on the April 2023 extents was run at a similar flow as was occurring in September 2021. The combination of water surface elevation at that flow (780 cfs), the energy grade slope in the 3DEP data and field measured depth in 2021 were used to estimate the elevation at the channel bed.

Land Cover Land cover was delineated using the Multi-Resolution Land Characteristic (MRLC) Consortium’s 2019 National Land Cover Data (NLCD) (MRLC 2016). Fifteen types of landcover were identified for this study area by the NLCD: Hay-Pasture, Shrub-Scrub, Developed Low Intensity, Developed Medium Intensity, Cultivated Crops, Deciduous Forest, Herbaceous, Develop Open Space, Developed High Intensity, Woody Wetlands, Emergent Herbaceous Wetland, Open Water, Mixed Forest, Barren Land, and Evergreen Forest. Manning’s n values were selected based on a range of n values along with a “Suggested Initial n” provided by Krest Engineers (2021) (Table 1). Table 1. A table representing a range of Manning’s n values, a suggested Manning’s n value, and percent imperviousness for each NLCD land cover type. (Krest Engineers, 2021)

Model Settings The 2D HEC-RAS mesh was set to 40-feet square, with breaklines to orient cell edges along areas of steep elevation change or to support model convergence. Boundary conditions were placed at three locations in the 2D flow area: the inflow of the Big Blue River (boundary condition type: flow hydrograph), the upstream end of the Kanas River (flow hydrograph), and the downstream end of the Kanas River (normal depth). An energy grade slope was given as 0.0005 ft/ft for the Big Blue River and 0.0003 ft/ft for the Kansas River. Advanced time step control adjustments were implemented using Courant’s Criterion, with a minimum Courant of 0.75 and a maximum of 3.

Calibration The suggested value from Krest Engineers (2021) was the initial Manning’s n used for each land cover type (Table 1). The hydraulic model was then run, and the Manning’s n was changed to better conform to water surface elevations observed during field data collection. Flows corresponding to the field collection dates were 415 cfs for the Big Blue River and 360 cfs for the Kansas River. These streamflows were determined by cross-referencing the field collection dates (April 10 to 14, 2023) to continuous monitoring data available from USGS at gages Big Blue R NR Manhattan, KS (06887000) and Kansas R at Fort Riley, KS (06879100). The 2D model simulation results were compared to the field-measured water surface elevations at each channel cross-section with the ArcGIS Zonal Statistics as Table tool. Model improvement was determined by calculating the Root Mean Square Error (RMSE) of the simulated water surface elevation to the field observed water surface elevation, and the Manning’s n values resulting in the lowest error were selected. Following calibration, the model has overall RMSE of 0.29 ft for depth. The final Manning’s n values used for all the following simulations are included in Table 2.

Land Cover

Mannings n

Open Water

0.025

Emergent Herbaceous Wetlands

0.05

Woody Wetlands

0.045

Herbaceous

0.025

Mixed Forest

0.08

Evergreen Forest

0.08

Deciduous Forest

0.1

Scrub-Shrub

0.07

Hay-Pasture

0.025

Cultivated Crops

0.02

Baren Land

0.023

Developed, Open Space

0.03

Developed, Low Intensity

0.06

Developed, Medium Intensity

0.08

Developed, High Intensity

0.12

Table 2. The selected Manning’s n per Landcover classification after calibration

Simulations Apart from the calibration simulations, further simulations were conducted to match additional fish data collection from July 17 – 21, 2023 and October 2- 6, 2023. USGS gages, Big Blue R NR Manhattan, KS (06887000) and Kansas R at Fort Riley, KS (06879100), were used to find the discharge rates (in cfs) during those fish sampling periods. While discharge was consistent throughout the weeks for some gages (Figures 4 and 7), others showed differences greater than 10% or 100 cfs (Figures 5 and 6). The gages that showed significant differences were divided into two sub-simulations for the lower and higher flows during that week.

USGS Streamflow Data for July 17 - 21, 2023

HEC RAS Scenario Description River Simulation Flow (cfs)

July_KS_LF July lower flow Big

The TopoBathy 3D layer provides a global seamless topography (land elevation) and bathymetry (water depths) surface to use in ArcGIS 3D applications.What can you do with this layer?This layer is meant to be used as a ground in ArcGIS Online Web Scenes, ArcGIS Earth, and ArcGIS Pro to help visualize your maps and data in 3D.How do I use this layer?In the ArcGIS Online Web Scene Viewer:Sign-in with ArcGIS Online accountOn the Designer toolbar, click Add Layers Click Browse layers and choose Living Atlas.Search for TopoBathy 3DAdd TopoBathy 3D (Elevation Layer)The TopoBathy 3D will get added under Ground. Change basemap to OceansOptionally, add any other operational layers to visualize in 3DIn ArcGIS Pro:Ensure you are logged in with an ArcGIS Online accountOpen a Global SceneOn the Map tab, click Add Data > Elevation Source LayerUnder Portal, click Living Atlas and search for TopoBathy 3DSelect TopoBathy 3D (Elevation Layer) and click OKThe TopoBathy 3D will get added under GroundOptionally, remove other elevation layers from ground and choose the desired basemapDataset Coverage To see the coverage and sources of various datasets comprising this elevation layer, view the Elevation Coverage Map. Additionally, this layer uses data from Maxar’s Precision 3D Digital Terrain Models for parts of the globe.

The High Resolution Digital Elevation Model (HRDEM) product is derived from airborne LiDAR data (mainly in the south) and satellite images in the north. The complete coverage of the Canadian territory is gradually being established. It includes a Digital Terrain Model (DTM), a Digital Surface Model (DSM) and other derived data. For DTM datasets, derived data available are slope, aspect, shaded relief, color relief and color shaded relief maps and for DSM datasets, derived data available are shaded relief, color relief and color shaded relief maps. The productive forest line is used to separate the northern and the southern parts of the country. This line is approximate and may change based on requirements. In the southern part of the country (south of the productive forest line), DTM and DSM datasets are generated from airborne LiDAR data. They are offered at a 1 m or 2 m resolution and projected to the UTM NAD83 (CSRS) coordinate system and the corresponding zones. The datasets at a 1 m resolution cover an area of 10 km x 10 km while datasets at a 2 m resolution cover an area of 20 km by 20 km. In the northern part of the country (north of the productive forest line), due to the low density of vegetation and infrastructure, only DSM datasets are generally generated. Most of these datasets have optical digital images as their source data. They are generated at a 2 m resolution using the Polar Stereographic North coordinate system referenced to WGS84 horizontal datum or UTM NAD83 (CSRS) coordinate system. Each dataset covers an area of 50 km by 50 km. For some locations in the north, DSM and DTM datasets can also be generated from airborne LiDAR data. In this case, these products will be generated with the same specifications as those generated from airborne LiDAR in the southern part of the country. The HRDEM product is referenced to the Canadian Geodetic Vertical Datum of 2013 (CGVD2013), which is now the reference standard for heights across Canada. Source data for HRDEM datasets is acquired through multiple projects with different partners. Since data is being acquired by project, there is no integration or edgematching done between projects. The tiles are aligned within each project. The product High Resolution Digital Elevation Model (HRDEM) is part of the CanElevation Series created in support to the National Elevation Data Strategy implemented by NRCan. Collaboration is a key factor to the success of the National Elevation Data Strategy. Refer to the “Supporting Document” section to access the list of the different partners including links to their respective data.

The U.S. Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC) conducted research to identify areas of seafloor elevation stability and instability based on elevation changes between the years of 2016 and 2019 along the Florida Reef Tract (FRT) from Miami to Key West within a 939.4 square-kilometer area. USGS SPCMSC staff used seafloor elevation-change data from Fehr and others (2021) derived from an elevation-change analysis between two elevation datasets acquired in 2016/2017 and 2019 using the methods of Yates and others (2017). Most of the elevation data from the 2016/2017 time period were collected during 2016, so as an abbreviated naming convention, we refer to this time period as 2016. Due to file size limitations, the elevation-change data was divided into five blocks. A seafloor stability threshold was determined for the 2016-2019 FRT elevation-change datasets based on the vertical uncertainty of the 2016 and 2019 digital elevation models (DEMs). Five stability categories (which include, Stable: 0.0 meters (m) to ±0.24 m or 0.0 m to ±0.49 m; Moderately stable: ±0.25 m to ±0.49 m; Moderately unstable: ±0.50 m to ±0.74 m; Mostly unstable: ±0.75 m to ±0.99 m; and Unstable: ±1.00 m to Max/Min elevation change) were created and used to define levels of stability and instability for each elevation-change value (total of 235,153,117 data points at 2-m horizontal resolution) based on the amount of erosion and accretion during the 2016 to 2019 time period. Seafloor-stability point and triangulated irregular network (TIN) surface models were created for each block at five different elevation-change data resolutions (1st order through 5th order) with each resolution becoming increasingly more detailed. The stability models were used to determine the level of seafloor stability at potential areas of interest for coral restoration and 14 habitat types found along the FRT. Stability surface (TIN) models were used for areas defined by specific XY geographic points, while stability point models were used for areas defined by bounding box coordinate locations. This data release includes ArcGIS Pro map packages containing the binned and color-coded stability point and surface (TIN) models, potential coral restoration locations, and habitat files for each block; maps of each stability model; and data tables containing stability and elevation-change data for the potential coral restoration locations and habitat types. Data were collected under Florida Keys National Marine Sanctuary permit FKNMS-2016-068. Coral restoration locations were provided by Mote Marine Laboratory under Special Activity License SAL-18-1724-SCRP.

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.

Our Co-design team is from the University of Texas, working on a Department of Energy-funded project focused on the Beaumont-Port Arthur area. As part of this project, we will be developing climate-resilient design solutions for areas of the region. More on www.caee.utexas.edu. We captured aerial photos in the Port Arthur Coastal Neighborhood Community and the Golf Course on Pleasure Island, Texas, in June 2024. Aerial photos taken were through DroneDeploy autonomous flight, and models were processed through the DroneDeploy engine as well. All aerial photos are in .JPG format and contained in zipped files for each area. The processed data package includes 3D models, geospatial data, mappings, and point clouds. Please be aware that DTM, Elevation toolbox, Point cloud, and Orthomosaic use EPSG: 6588. And 3D Model uses EPSG: 3857. For using these data: - The Adobe Suite gives you great software to open .Tif files. - You can use LASUtility (Windows), ESRI ArcGIS Pro (Windows), or Blaze3D (Windows, Linux) to open a LAS file and view the data it contains. - Open an .OBJ file with a large number of free and commercial applications. Some examples include Microsoft 3D Builder, Apple Preview, Blender, and Autodesk. - You may use ArcGIS, Merkaartor, Blender (with the Google Earth Importer plug-in), Global Mapper, and Marble to open .KML files. - The .tfw world file is a text file used to georeference the GeoTIFF raster images, like the orthomosaic and the DSM. You need suitable software like ArcView to open a .TFW file. This dataset provides researchers with sufficient geometric data and the status quo of the land surface at the locations mentioned above. This dataset could streamline researchers' decision-making processes and enhance the design as well.

The hachure cartographic technique sketches downhill lines along bands of equal elevation to create a topographic effect. This is a rather vintage technique, giving way in the digital age to hillshading. But, shoot, there is just something wonderful about a hachured map. It has a wonderful textural quality and effectively and efficiently conveys topographic aspect and slope. This style is in a manner in keeping with that retro hand-drawn aesthetic, with inky colors, wavy-hand linework, and grainy sketchy downhill strokes.The hachures themselves are available in a few flavors ranging from simple sketched contour lines to densely packed hachures for an almost fur-like surface. Eh, why not? Also available are a handful of tuft-like point features and a few vintage polygon fills like parchment and foxed atlas paper.Let your inner cARRRRRRtographer run wild.Thanks to cartographer Jared Fischer, of the Dept. of the Interior, for his collaboration and inspiration along the way.Find more, larger, examples here.Happy Hachure Mapping! John Nelson

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS and bare earth DEM data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm NVA.This metadata record describes the hydro-flattened bare earth digital elevation model (DEM) derived from the classified LiDAR data for the 2017 Michigan LiDAR project covering approximately 907 square miles, in which its extents cover Oakland County.This data is for planning purposes only and should not be used for legal or cadastral purposes. Any conclusions drawn from analysis of this information are not the responsibility of Sanborn Map Company. Users should be aware that temporal changes may have occurred since this dataset was collected and some parts of this dataset may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Contact: State of MichiganDue to the large size of the data, downloading the entire county may not be possible. It is recommended to use the live service directly within ArcMap or ArcGIS Pro. For further questions, contact the Oakland County Service Center at 248-858-8812, servicecenter@oakgov.com.

Images were acquired from approximately 80 m above ground surface on the 12th of February 2021, using a Phantom 4 Advanced drone with an FC330 camera. The images are in file input_images.zip.

The mission planning software DJI GS Pro was used to automatically acquire images at suitable locations across the survey area to enable the reconstruction of a three dimensional model.

Images 422 to 531 were imported to the photogrammetry software Pix4D (version 4.6.4). The created Pix4D project is Station12Feb2021_limited.p4d, and the processing report is Station12Feb2021_limited_report.pdf.

Four three-dimensional ground control points were used to improve the positioning of the model. No two dimensional control points or check points were used.

These points were in ITRF 2000@2000 datum (UTM Zone 49S), with co-ordinates as per the table below:

Label, Type, X(m), Y(m), Z(m), Accuracy Horz(m), Accuracy Vert(M) BM05, 3D GCP, 478814.460, 2648561.910, 38.558, 0.050, 0.100 EW-05, 3D GCP, 478635.540, 2648617.260, 27.260, 0.050, 0.100 FuelFlange, 3D GCP, 478970.810, 2648642.250, 21.920, 0.050, 0.100 MeltbellFootingA, 3D GCP, 478680.270, 2648466.547, 35.850, 0.050, 0.100

BM-05 is a survey benchmark near the Casey flagpoles, see https://data.aad.gov.au/aadc/survey/display_station.cfm?station_id=600 EW-05 is a 44 gallon drum used as a groundwater extraction well by the remediation project Fuel Flange is the last fuel flange located on the elevated fuel line prior to the fuel line “dipping” under the wharf road. Meltbell footing A is a concrete footing for the Casey melt bell (surveyed in 2019/20).

No point cloud processing (e.g. removal of errant points) was done prior to orthomosaic and model generation.

The resulting orthomosaic (Station12Feb2021_limited_transparent_mosaic_group1.tif) has an average ground sampling distance of 2.9 cm, and covers an area of approximately 15.8 hectares, encompassing the majority of buildings along “main street” at Casey. The quarry, biopiles, helipad, and upper fuel farm area are all visible.

Contour lines were generated in Pix4D at 0.5 m intervals.

Due to the limited number of ground control points, and their imprecision, the estimated residual mean squared error across three dimensions is 0.17 m (17cm), and will be worse on the periphery of the imaged area.

The orthomosaic was exported from ArcGIS to a Google Earth file (CaseyStation Orthomosaic Feb 12 2021.kmz) using XTools Pro Version 17.2.

A map was created in ArcGIS showing the orthomosaic with a background showing contour lines obtained from the AADC data product windmill_is.mdb.

The map was exported in .jpg and .pdf format at 250 dpi. Casey Station Orthomosaic Feb 12 2021.pdf Casey Station Orthomosaic Feb 12 2021.jpg

The Pix4D folder structure has been copied across (with the exception of the temp folder) and is included in this dataset.

Pix4D Folder Structure:

Station12Feb2021_limited.zip 1_intitial • Contains Pix4D files created during the project • Contains the final processing report (as .pdf) 2_densification • Contains the 3D mesh as an .obj file • Contains the point cloud as a .LAS and .PLY file • Contains the point cloud as a .p4b file 3_dsm_ortho • Contains the digital surface model as a georeferenced .tif file • Contains the orthomosaic as a georeferenced .tif file

A text readable log file from the project processing is in the file Station12Feb2021_limited.log

The TopoBathy 3D layer provides a global seamless topography (land elevation) and bathymetry (water depths) surface to use in ArcGIS 3D applications.What can you do with this layer?This layer is meant to be used as a ground in ArcGIS Online Web Scenes, ArcGIS Earth, and ArcGIS Pro to help visualize your maps and data in 3D.How do I use this layer?In the ArcGIS Online Web Scene Viewer:Sign-in with ArcGIS Online accountOn the Designer toolbar, click Add Layers Click Browse layers and choose Living Atlas.Search for TopoBathy 3DAdd TopoBathy 3D (Elevation Layer)The TopoBathy 3D will get added under Ground. Change basemap to OceansOptionally, add any other operational layers to visualize in 3DIn ArcGIS Pro:Ensure you are logged in with an ArcGIS Online accountOpen a Global SceneOn the Map tab, click Add Data > Elevation Source LayerUnder Portal, click Living Atlas and search for TopoBathy 3DSelect TopoBathy 3D (Elevation Layer) and click OKThe TopoBathy 3D will get added under GroundOptionally, remove other elevation layers from ground and choose the desired basemapDataset Coverage To see the coverage and sources of various datasets comprising this elevation layer, view the Elevation Coverage Map. Additionally, this layer uses data from Maxar’s Precision 3D Digital Terrain Models for parts of the globe.

The U.S. Geological Survey (USGS) St. Petersburg Coastal and Marine Science Center (SPCMSC) conducted research to identify areas of seafloor elevation stability and instability based on elevation changes between the years of 2002 and 2016 in the Upper Florida Keys (UFK) from Triumph Reef to Pickles Reef within a 242.4 square-kilometer area. USGS SPCMSC staff used seafloor elevation-change data from Murphy and others (2021) derived from an elevation-change analysis between two elevation datasets acquired in 2001/2002 and 2016/2017 using the methods of Yates and others (2017). Most of the elevation data from these two time periods were collected during 2002 and 2016, so as an abbreviated naming convention, we refer to this study time period as 2002-2016. A seafloor stability threshold was determined for the 2002-2016 UFK elevation-change dataset based on the vertical uncertainty of the 2002 and 2016 digital elevation models (DEMs). Five stability categories (which include, Stable: 0.0 meters (m) to ±0.24 m or 0.0 m to ±0.49 m; Moderately stable: ±0.25 m to ±0.49 m; Moderately unstable: ±0.50 m to ±0.74 m; Mostly unstable: ±0.75 m to ±0.99 m; and Unstable: ±1.00 m to Max/Min elevation change) were created and used to define levels of stability and instability for each elevation-change value (60,585,610 data points at 2-m horizontal resolution) based on the amount of erosion and accretion during the 2002 to 2016 time period. Seafloor-stability point and triangulated irregular network (TIN) surface models were created at five different elevation-change data resolutions (1st order through 5th order) with each resolution becoming increasingly more detailed. The stability models were used to determine the level of seafloor stability at potential areas of interest for coral restoration and 13 habitat types found in the UFK. Stability surface (TIN) models were used for areas defined by specific XY geographic points, while stability point models were used for areas defined by bounding box coordinate locations. This data release includes ArcGIS Pro map packages containing the binned and color-coded stability point and surface (TIN) models, potential coral restoration locations, and habitat files; maps of each stability model; and data tables containing stability and elevation-change data for the potential coral restoration locations and habitat types. Data were collected under Florida Keys National Marine Sanctuary permit FKNMS-2016-068.

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

The Portland Basin is a prime _location to assess the feasibility of DDU-TES because natural geologic conditions provide thermal and hydraulic separation from overlying aquifers that would otherwise sweep away stored heat. Under the Portland Basin, the lower Columbia River Basalt Group (CRBG) aquifers contain brackish water (1,000-10,000 mg/L TDS), indicating low groundwater flow rates and poor connection with the overlying regional aquifer. Further, CRBG lavas tend to have comparatively low thermal conductivity, indicating that the 400-1,000 ft thick CRBG may be an effective thermal barrier to the overlying aquifer. A temporally and spatially limited previous study of a Portland Basin CRBG aquifer demonstrated that the injection of waste heat resulted in an increase in temperature by more than a factor of two, indicating a high potential for storing heat. This data submission includes ASCII grid surfaces for the Portland and Tualatin Basins including a DEM of modern topography, the top of Columbia River Basalt (CRB), the base of CRB, and basement. It also includes three isochore (thickness) maps between these intervals. In addition, there is an ArcGIS attribute table for associated data points, a map of data types used to constrain the top of CRB, and cross-sections, all made using IHS Kingdom Suite, Petrosys PRO, ESRI ArcGIS, and Adobe Illustrator software.

New to 3D GIS with @esri and @ArcGISPro?I’ve put together a printable 2-page cheat-sheet of the concepts and terms you need to get started! 😊First, take a quick anatomy lesson to learn about the elements that make up a 3D scene. Not every scene has every element, but you need to know your options.Perhaps most importantly, think about HOW you intend to share your 3D map BEFORE you spend hours (or days) making it. - Tip: If it’s an image or a video, you can spend more time on areas you know the camera will visit, and less on the rest. 3D also has this nasty habit of showing continuous scales (aka levels-of-detail / LODs) throughout the view… You WILL need to think about how scales change off into the distance, as well as choosing the “just-right” LOD for the features you’re showing.Got data with no Z’s? No problem – give them a place to draw by creating an elevation surface. While ‘Ground’ is the most famous, you can also model surfaces: underground; in the air; and based on thematic values.“Paint” your surfaces by draping them with imagery and cartographic content… but don’t forget about the whole continuous-scale thing.Vector content are the “pretty boys” of your 3D map. They give the scene depth and things for people to click on. They can also be high maintenance, both in creation time and performance impact. Use them wisely, and consistently, to avoid a scene that tries to do too much.Vector objects come in all shapes and sizes. Think about how even a simple shape – rotated and resized into place – can communicate information to the user. Everything does NOT* have to look “real”!* (Full Disclosure: sometimes it does).Much like the Ground surface, the exterior shell of vector objects can also be “painted”. The source could be oblique imagery… or procedurally-placed windows and bricks… or even “material” properties that can make a surface appear to be iron or glass or wood. Text in a 3D view can label locations and reinforce the direction a feature is oriented. Make it 3D (where you can) and only drape it on the ground as a last resort… or when you have full camera control (eg: video).Once you’ve symbolized all your layers, you still have more to do – you must also think about the scene as a whole! A scene’s light direction can change the mood, exaggeration can make flat land interesting, and the background color might be critical for the intended use of an exported image.And, finally, if you’re sharing an interactive 3D view, please have a little EMPATHY for your audience. Some of them will be new to 3D and – let’s be honest - navigating around can be hard.If you give them ‘safe places’ (bookmarks / slides) to zoom to if they get lost, they will love your work even more.Hope this helps – good luck with your 3D!-Nathan.