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.

Lidar (light detection and ranging) imagery provides valuable information in the field of remote sensing, allowing users to determine elevation, vegetation structure, and terrain with remarkable levels of detail. This manual will lead ArcGIS Pro users through the tools and methods needed to access, process, and analyze lidar data through a series of step-by-step tutorials.

By completing this series of tutorials, you will be able to: •Manipulate data to create maps and map templates in ArcGIS Pro •Obtain and display lidar imagery •Use ArcGIS Pro tools to process and analyze lidar data •Classify lidar points using different classification methods • Process lidar point clouds to create digital elevation models

This World Elevation TopoBathy service combines topography (land elevation) and bathymetry (water depths) from various authoritative sources from across the globe. Heights are orthometric (sea level = 0), and bathymetric values are negative downward from sea level. The source data of land elevation in this service is same as in the Terrain layer. When possible, the water areas are represented by the best available bathymetry. Height/Depth units: MetersUpdate Frequency: QuarterlyCoverage: World/GlobalData Sources: This layer is compiled from a variety of best available sources from several data providers. To see the coverage and extents of various datasets comprising this service in an interactive map, see Elevation Coverage Map.What can you do with this layer?Use for Visualization: This layer is generally not optimal for direct visualization. By default, 32 bit floating point values are returned, resulting in higher bandwidth requirements. Therefore, usage should be limited to applications requiring elevation data values. Alternatively, client applications can select additional functions, applied on the server, that return rendered data. For visualizations such as hillshade or elevation tinted hillshade, consider using the appropriate server-side function defined on this service. Use for Analysis: Yes. This layer provides data as floating point elevation values suitable for use in analysis. There is a limit of 5000 rows x 5000 columns. NOTE: This image services combine data from different sources and resample the data dynamically to the requested projection, extent and pixel size. For analyses using ArcGIS Desktop, it is recommended to filter a dataset, specify the projection, extent and cell size using the Make Image Server Layer geoprocessing tool. The extent is factor of cell size and rows/columns limit. e.g. if cell size is 10 m, the max extent for analysis would be less than 50,000 m x 50,000 m.Server Functions: This layer has server functions defined for the following elevation derivatives. In ArcGIS Pro, server function can be invoked from Layer Properties - Processing Templates.

Slope Degrees Slope Percentage Hillshade Multi-Directional Hillshade Elevation Tinted HillshadeSlope MapMosaic Method: This image service uses a default mosaic method of "By Attribute”, using Field 'Best' and target of 0. Each of the rasters has been attributed with ‘Best’ field value that is generally a function of the pixel size such that higher resolution datasets are displayed at higher priority. Other mosaic methods can be set, but care should be taken as the order of the rasters may change. Where required, queries can also be set to display only specific datasets such as only NED or the lock raster mosaic rule used to lock to a specific dataset.Accuracy: Accuracy will vary as a function of location and data source. Please refer to the metadata available in the layer, and follow the links to the original sources for further details. An estimate of CE90 and LE90 is included as attributes, where available.This layer allows query, identify, and export image requests. The layer is restricted to a 5,000 x 5,000 pixel limit in a single request. This layer is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks. Disclaimer: Bathymetry data sources are not to be used for navigation/safety at sea.

This dynamic World Elevation Terrain layer returns float values representing ground heights in meters and compiles multi-resolution data from many authoritative data providers from across the globe. Heights are orthometric (sea level = 0), and water bodies that are above sea level have approximated nominal water heights.Height units: MetersUpdate Frequency: QuarterlyCoverage: World/GlobalData Sources: This layer is compiled from a variety of best available sources from several data providers. To see the coverage and extents of various datasets comprising this service in an interactive map, see World Elevation Coverage Map.What can you do with this layer?Use for Visualization: This layer is generally not optimal for direct visualization. By default, 32 bit floating point values are returned, resulting in higher bandwidth requirements. Therefore, usage should be limited to applications requiring elevation data values. Alternatively, client applications can select from numerous additional functions, applied on the server, that return rendered data. For visualizations such as multi-directional hillshade, hillshade, elevation tinted hillshade, and slope, consider using the appropriate server-side function defined on this service.Use for Analysis: Yes. This layer provides data as floating point elevation values suitable for use in analysis. There is a limit of 5000 rows x 5000 columns.Note: This layer combine data from different sources and resamples the data dynamically to the requested projection, extent and pixel size. For analyses using ArcGIS Desktop, it is recommended to filter a dataset, specify the projection, extent and cell size using the Make Image Server Layer geoprocessing tool. The extent is factor of cell size and rows/columns limit. e.g. if cell size is 10 m, the extent for analysis would be less than 50,000 m x 50,000 m.Server Functions: This layer has server functions defined for the following elevation derivatives. In ArcGIS Pro, server function can be invoked from Layer Properties - Processing Templates.

Slope Degrees Slope Percent Aspect Ellipsoidal height Hillshade Multi-Directional Hillshade Dark Multi-Directional Hillshade Elevation Tinted Hillshade Slope Map Aspect Map Mosaic Method: This image service uses a default mosaic method of "By Attribute”, using Field 'Best' and target of 0. Each of the rasters has been attributed with ‘Best’ field value that is generally a function of the pixel size such that higher resolution datasets are displayed at higher priority. Other mosaic methods can be set, but care should be taken as the order of the rasters may change. Where required, queries can also be set to display only specific datasets such as only NED or the lock raster mosaic rule used to lock to a specific dataset.Accuracy: Accuracy will vary as a function of location and data source. Please refer to the metadata available in the layer, and follow the links to the original sources for further details. An estimate of CE90 and LE90 are included as attributes, where available.This layer allows query, identify, and export image requests. The layer is restricted to a 5,000 x 5,000 pixel limit in a single request.This layer is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.

The dataset includes 5 panoramic scans of the buildings, cultural resources, and other features within the National Park Service boundaries at Roger Williams National Memorial. The scans exist as point cloud files in Trimble Business Center. Each scan has at most 24 panoramic photographs associated with it, depending on whether it was a horizontal band or polygon scan. The points have been colorized based off the panoramic photographs and have been categorized into regions, such as buildings, ground, poles, and trees. There is a layer of points selected from the bottom of doorway thresholds to capture the finished floor elevation data. There is also a layer of points representing the elevation of first floor windows and basement windows. Each point in the layer has elevation data and latitude and longitude data associated with it. The layers are exportable into ArcGIS Pro as point layers, and the data associated with each point layer is exportable as a CSV file. The data was collected in NAD83 (2011) meters UTM Zone 19 and NAVD88. The controller used was a Trimble TSC7 data collector. Control points were set using the BOHA NTRIP base station, an R12i GNSS receiver, and a prism. Scans were completed using a Trimble SX12 scanner that was set so that points would be 2 cm apart at 20 m with a scanning distance of 200 m and a scanning radius of 1 m from the scanner. The scans were performed using the coarse resolution, stored in Trimble Access, and exported to Trimble Business Center.

The dataset includes 19 panoramic, scans of the buildings, cultural resources, and other features within the National Park Service boundaries at Roger Williams National Memorial. The scans exist as point cloud files in Trimble Business Center. Each scan has at most 24 panoramic photographs associated with it, depending on whether it was a horizontal band or polygon scan. The points have been colorized based off the panoramic photographs and have been categorized into regions, such as buildings, ground, poles, and trees. There is a layer of points selected from the bottom of doorway thresholds to capture the finished floor elevation data. There is also a layer of points representing the elevation of first floor windows and basement windows. Each point in the layer has elevation data and latitude and longitude data associated with it. The layers are exportable into ArcGIS Pro as point layers, and the data associated with each point layer is exportable as a CSV file. The data was collected in NAD83 (2011) meters UTM Zone 19 and NAVD88. The controller used was a Trimble TSC7 data collector. Control points were set using the BOHA NTRIP base station, an R12i GNSS receiver, and a prism. Scans were completed using a Trimble SX12 scanner that was set so that points would be 2 cm apart at 20 m with a scanning distance of 200 m and a scanning radius of 1 m from the scanner. The scans were performed using the coarse resolution, stored in Trimble Access, and exported to Trimble Business Center.

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 dataset includes 19 panoramic scans of the buildings, cultural resources, and other features within the National Park Service boundaries at Roger Williams National Memorial. The scans exist as point cloud files in Trimble Business Center. Each scan has at most 24 panoramic photographs associated with it, depending on whether it was a horizontal band or polygon scan. The points have been colorized based off the panoramic photographs and have been categorized into regions, such as buildings, ground, poles, and trees. There is a layer of points selected from the bottom of doorway thresholds to capture the finished floor elevation data. There is also a layer of points representing the elevation of first floor windows and basement windows. Each point in the layer has elevation data and latitude and longitude data associated with it. The layers are exportable into ArcGIS Pro as point layers, and the data associated with each point layer is exportable as a CSV file. The data was collected in NAD83 (2011) meters UTM Zone 19 and NAVD88. The controller used was a Trimble TSC7 data collector. Control points were set using the BOHA NTRIP base station, an R12i GNSS receiver, and a prism. Scans were completed using a Trimble SX12 scanner that was set so that points would be 2 cm apart at 20 m with a scanning distance of 200 m and a scanning radius of 1 m from the scanner. The scans were performed using the coarse resolution, stored in Trimble Access, and exported to Trimble Business Center.

See the NZ Elevation Layer for more information on the NZ Elevation layerThe NZ Elevation - Metadata layer provides information about the data used for the NZ Elevation layer. You can identify what areas use 1m or 2m DEM's derived from LiDAR and what areas use the 8m DEM provided by LINZ. You can also find information, whenever available, about capture dates, point cloud density and links to the layer's in the LINZ Data Service.The NZ Elevation layer is an elevation surface for use in 3D applications in the NZTM projection. By adding this layer to a Scene in ArcGIS Pro or in the Scene Viewer it will be define the base height in your application.NZTM Basemaps can be used on top of this service, providing it shares the same tiling scheme. When combining it with the NZ Basemaps provided by Eagle Technolgy, make sure to use the raster basemaps with the updated tiling scheme or one of the vector basemaps. All the compatible basemaps can be found in this group. When creating your own basemap or tiled layer make sure to use the tiling scheme provided here.The elevation service is made up of the available publicly-owned 1m and 2m dems. For areas where 1m/2m elevation data is not available the 8m dem provided by LINZ is being used. Outside of the coverage of the 8m dem, a 0m dem is used for visual purposes.This service is offered by Eagle Technology (Official Esri Distributor). Eagle Technology offers layers and maps that can be used in the ArcGIS platform. The Content team at Eagle Technology updates the layers on a regular basis and regularly adds new content to the Living Atlas. By using this content and combining it with other data you can create new information products quickly and easily.If you have any questions or remarks about the content, please let us now at livingatlas@eagle.co.nz

Methods:This lidar derivative provides information about the bare surface of the earth. The 2-foot resolution hillshade raster was produced from the 2020 Digital Terrain Model using the hillshade geoprocessing tool in ArcGIS Pro.QL1 airborne lidar point cloud collected countywide (Sanborn)Point cloud classification to assign ground points (Sanborn)Ground points were used to create over 8,000 1-foot resolution hydro-flattened Raster DSM tiles. Using automated scripting routines within LP360, a GeoTIFF file was created for each tile. Each 2,500 x 2,500 foot tile was reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. (Sanborn)1-foot hydroflattened DTM tiles mosaicked together into a 1-foot resolution mosaiced hydroflattened DTM geotiff (Tukman Geospatial)1-foot hydroflattened DTM (geotiff) resampled to 2-foot hydro-flattened DTM using Bilinear interpolation and clipped to county boundary with 250-meter buffer (Tukman Geospatial)2-foot hillshade derived from DTM using the ESRI Spatial Analyst ‘hillshade’ function The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane, Feet and vertical datum of NAVD88 (GEOID18), Feet. Lidar was collected in early 2020, while no snow was on the ground and rivers were at or below normal levels. To postprocess the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc., utilized a total of 25 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 125 independent accuracy checkpoints, 70 in Bare Earth and Urban landcovers (70 NVA points), 55 in Tall Grass and Brushland/Low Trees categories (55 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data.Uses and Limitations: The hillshade provides a raster depiction of the ground returns for each 2x2 foot raster cell across Santa Clara County. The layer is useful for hydrologic and terrain-focused analysis and is a helpful basemap when analyzing spatial data in relief.Related Datasets: This dataset is part of a suite of lidar of derivatives for Santa Clara County. See table 1 for a list of all the derivatives. Table 1. lidar derivatives for Santa Clara CountyDatasetDescriptionLink to DataLink to DatasheetCanopy Height ModelPixel values represent the aboveground height of vegetation and trees.https://vegmap.press/clara_chmhttps://vegmap.press/clara_chm_datasheetCanopy Height Model – Veg Returns OnlySame as canopy height model, but does not include lidar returns labelled as ‘unclassified’ (uses only returns classified as vegetation)https://vegmap.press/clara_chm_veg_returnshttps://vegmap.press/clara_chm_veg_returns_datasheetCanopy CoverPixel values represent the presence or absence of tree canopy or vegetation greater than or equal to 15 feet tall.https://vegmap.press/clara_coverhttps://vegmap.press/clara_cover_datasheetCanopy Cover – Veg Returns OnlySame as canopy height model, but does not include lidar returns labelled as ‘unclassified’ (uses only returns classified as vegetation)https://vegmap.press/clara_cover_veg_returnshttps://vegmap.press/clara_cover_veg_returns_datasheet HillshadeThis depicts shaded relief based on the Hillshade. Hillshades are useful for visual reference when mapping features such as roads and drainages and for visualizing physical geography. https://vegmap.press/clara_hillshadehttps://vegmap.press/clara_hillshade_datasheetDigital Terrain ModelPixel values represent the elevation above sea level of the bare earth, with all above-ground features, such as trees and buildings, removed. The vertical datum is NAVD88 (GEOID18).https://vegmap.press/clara_dtmhttps://vegmap.press/clara_dtm_datasheetDigital Surface ModelPixel values represent the elevation above sea level of the highest surface, whether that surface for a given pixel is the bare earth, the top of vegetation, or the top of a building.https://vegmap.press/clara_dsmhttps://vegmap.press/clara_dsm_datasheet

The Merced Vernal Pools and Grassland Reserve is 6,500 acres of protected habitat adjacent to the University of California Merced containing rare and endangered species and a unique seasonal wetland habitat. These data were gathered to be used for hydrological modelling on the Reserve for potential restoration projects and to be made public for other researchers who may find very high resolution topographical information useful for their work. This dataset contains a Digital Elevation Model created from 8 field survey days of Aerial LiDAR Scanning (ALS) with a small Unmanned Aerial System (sUAS).

Methods Work Completed by Researchers at University of California, Merced under the direction of Dean/Director/Professor Joshua H. Viers | Vicelab and CITRIS Aviation

Spatial Reference: WGS 1984 UTM Zone 10N / WGS84 Geoid

Units: Meters

Equipment: DJI M600 Pro with Phoenix Aerial Systems AL3-32 LiDAR

Software: Phoenix LiDAR Systems SpatialSuite 4.0.3, LasTools, ArcGIS Pro 2.4, Litchi, ArduPilot Mission Planner

Field Crew/Processing: Michael Kalua (sUAS Pilot/Mission Planning/Sensor Operator/Data Processing), Andreas Anderson (sUAS Pilot/Mission Planning/Sensor Operator), Daniel Gomez (Sensor Operator), Hayden Namgostar (Sensor Operator)

Field Methods: An RTK reference station was set up before each field day over a previously-surveyed benchmark near the entrance of the Reserve, which would continuously send RTK corrections to the LiDAR system over an internet connection service. Before flight the LiDAR system was allowed at least 15 minutes to reach thermal equilibrium and for the onboard Intertial Measurement Unit (IMU) to get a fix on the sensor's position and attitude. At the beginning of each set of flights the Pilot in Command (PIC) would perform a manual takeoff and IMU calibration maneuvers (straight-and-level flight and figure-eights) as per Phoenix LiDAR System's recommended procedures. Once the manuevers were completed and the Sensor Operator determined IMU attitude and position uncertainties were below threshold (0.003- typical values ranged an order of magnitude lower) the PIC would begin the automated waypoint mission via Litchi. During flight, the Sensor Operator would ensure the scanner was operational, that the IMU uncertainties were below margin, and address any potential error messages. In the event of errors, the PIC would bring the sUAS back and the section would be re-surveyed after the issues were addressed.

Processing Methods: The raw flightlines were fused using Phoenix SpatialExplorer 4.0.3 to include only the straight-and-level flightlines over the region of interest. The output were individual flightline .las point clouds conforming to LAS 1.4 format. These flightlines were then passed through a noise filter using LasNoise to remove any "birds" or unwanted noise. Using LasTools these noise-removed flightlines were then tiled, classified into ground/non-ground points, and rasterized into 0.25-meter Digital Surface Models (DSM) containing all points and Bare-Earth Digital Elevation Models (DEM) containing only ground-classified points. These tiled raster outputs were then mosiaced together in ArcGIS Pro.

Please reach out to Michael Kalua (mkalua@ucmerced.edu) for any questions about this dataset.

This layer was created in ArcGIS pro using a point layer and the Geodesic Viewshed tool. To generate this map the Old Rag Peak point was placed on the peak indicated by the basemap and Esri provided elevation model. This point was then used to generate a viewshed using the Geodesic Viewshed too, with a 1.7m offset to account for the height of the average viewer and a presumed focal angle of 120 degrees. The yellow highlighted area is the visible surface from the peak of Old Rag. This viewshed was generated in June of 2024.

This shapefile displays the watershed boundaries for NEON's aquatic wadeable and non-wadeable stream and lake sites. The watershed boundary defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The pour point was selected nearest the downstream most sensor set, primarily NEON’s S2 sensor in wadeable streams, S1 or stream gauge in non-wadeable rivers, and the outlet sensor in lakes. For most of the sites NEON's 1 meter Elevation-LiDAR Digital Terrain Model (DTM) was used to derive the watersheds. In cases where NEON data did not provide complete watershed coverage, a 1/3 arc-second (10 meter) resolution Digital Elevation Model (DEM) raster, available from the U.S. Geological Survey (USGS) website, was utilized to provide full coverage of the watershed extent. A mosaic dataset was created to combine individual DTM or DEM tiles, and a local projection defined for the dataset. ArcGIS Pro software with the ArcHydro Tools [for] Pro were used to model and delineate the watershed. Attribute Table Information:DomainNum:NEON ecoclimatic domain number. DomainName: NEON ecoclimatic domain name.SiteName: NEON aquatic site name.SiteID: NEON four character site ID for the aquatic site.SiteType:Type of NEON site (e.g. core aquatic or relocatable aquatic).Science: Identifies the primary science theme as they relate to the NEON Grand Challenges (AD[01]) and if the aquatic site is a wadeable or non-wadeable stream, or lake.StateID: The 2 letter abbreviation for the state where the watershed is located.UTM_Zone: The local projected coordinate system for the aquatic site and model processing.WSAreaKm2: Watershed area in kilometers squared for watersheds derived from NEON’s 1 meter Elevation-LiDAR dataset.Source: States if the watershed was not derived from NEON data, these sites are supplemented with the 10 meter National Elevation Dataset.Area_NED: Watershed area in kilometers squared for sites where the watershed was derived from the 10 meter National Elevation Dataset.AOPLiDAR: Name of the Elevation-LiDAR DTM tile from the NEON data portal, includes site ID, year, and month the data was collected.AOP_Flight: Identifies the NEON AOP Flight Boundaries layer showing the extent and priority of airborne acquisition. AOPCoverag: Identifies percent coverage of the NEON AOP flight box over the aquatic watershed.TIS_Dist: Distance in kilometers from the aquatic site pour point to the corresponding terrestrial tower site.TIS_Bear: Bearing in degrees from the aquatic site pour point to the corresponding terrestrial tower site.TIS_WS: States if the corresponding terrestrial tower is within the aquatic watershed.HUC12Name: Name of the Hydrologic Unit Code with twelve digits based on the prominent water or physical feature(s) within the unit. Naming follows the conventions and rules outlined by the Geographic Names Information System (GNIS) order of priority and if the dominant feature is named in the HU10, the HU12 retains the twelve digit code as the name. HUC12: Hydrologic Unit Code with twelve digits based on the sixth-level (subwatershed) classification designated by the United States Geological Survey. NLCD_(number): Percentage of land cover classifications within the watershed from the National Land Cover Dataset (NLCD) (Table 2). NRCS_(Soil abbreviations): Percentage of soil classifications within the watershed from the Natural Resources Conservation Service (NRCS) (Table 3).

This map represents a research effort focused upon collecting data on the age, height, and history of each lighthouse that shines upon the Atlantic Ocean. Data were manually collected from local, national, and international libraries including Lighthouse Friends, the United States National Park Service, and Wikipedia. The map was produced in ArcGIS Pro for construction of the lighthouse dataset and initial layout, then exported to Blender (3D rendering and animation software). The 2D terrain was then extruded to become a 3D elevation model, and the Atlantic Ocean created as a simulated water surface. Each lighthouse point was transformed into a 3D light source and a true light simulation performed on the scene to render the partially-illuminated terrain and water based on the presence of lighthouses, forming a heatmap (or lightmap!) to underlay the data itself. Lighthouses are shown by height, age, and whether they still serve as a navigational aid.Other Information:The lighthouses dataset was manually assembled by the authors for a variety of sources, including Wikipedia, the National Park Service, Lighthouse Friends, travel and tourism guides, and more. Shuttle Radar Topography Mission (SRTM) 30-meter Digital Elevation Model (DEM) was used to generate the 3D elevation model and enable light and shadow simulation in Blender. Software used: QGIS, Blender, Adobe Photoshop, Adobe InDesign. Map created by Michael Huff, GISP, and Ryan Huff, 2025.