Metadata: Identification_Information: Citation: Citation_Information: Originator: Jennifer M. Cramer Originator: Sandra M. Brosnahan Originator: Seth D. Ackerman Originator: Jin-Si R. Over Originator: Amit Millo Originator: David J. Kelley Publication_Date: 20250710 Title: Lidar point clouds (LPC), elevation models, GPS data, image mosaics, and aerial images from thermal infra-red (TIR), natural color (RGB), and multispectral cameras collected during UAS operations at Lower Darby Creek, Darby Township, Pennsylvania, August 14, 2024 Edition: 1.0 Geospatial_Data_Presentation_Form: digital image, point cloud, raster, and tabular digital data Series_Information: Series_Name: data release Issue_Identification: DOI:10.5066/P134HU3Y Publication_Information: Publication_Place: Woods Hole Coastal and Marine Science Center, Woods Hole, MA Publisher: U.S. Geological Survey, Coastal and Marine Hazards and Resources Program Online_Linkage: https://doi.org/10.5066/P134HU3Y Online_Linkage: https://www.sciencebase.gov/catalog/item/67644a60d34e5335adadf390 Larger_Work_Citation: Citation_Information: Originator: Jennifer M. Cramer Originator: Sandra M. Brosnahan Originator: Seth D. Ackerman Originator: Jin-Si R. Over Originator: Amit Millo Originator: Christopher L. Gazoorian Originator: David J. Kelley Publication_Date: 2025 Title: Topographic data, aerial imagery, and GPS data collected during uncrewed aircraft system (UAS) operations at Lower Darby Creek, Darby Township, Pennsylvania, March to August 2024 Edition: 1.0 Geospatial_Data_Presentation_Form: digital data Series_Information: Series_Name: data release Issue_Identification: DOI:10.5066/P134HU3Y Publication_Information: Publication_Place: Reston, VA Publisher: U.S. Geological Survey Other_Citation_Details: Cramer, J.M., Brosnahan, S.M., Ackerman, S.D., Over, J.R., Millo, A., Gazoorian, C.L., and Kelley, D.J., 2025, Topographic data, aerial imagery, and GPS data collected during uncrewed aircraft system (UAS) operations at Lower Darby Creek, Darby Township, Pennsylvania, March to August 2024: U.S. Geological Survey data release, https://doi.org/10.5066/P134HU3Y Online_Linkage: https://doi.org/10.5066/P134HU3Y Online_Linkage: https://www.sciencebase.gov/catalog/item/668ed0a6d34e537145a789b7 Description: Abstract: The U.S. Geological Survey deployed small uncrewed aircraft systems (sUAS) to collect aerial remote sensing data across sites within the Lower Darby Creek Superfund Site and the adjacent John Heinz National Wildlife Refuge (JHNWR) ~5 miles outside of Philadelphia, PA in March and August of 2024. March datasets include aerial images from natural color (RGB) and thermal infra-red (TIR) sensors across the JHNWR and adjacent tributaries as well as the nearby Clearview Landfill within the superfund site. August datasets include aerial images from natural color (RGB), thermal-infrared (TIR), multispectral sensors, and raw lidar over the Clearview Landfill only. These datasets were processed to produce high resolution digital elevation models (DEM), image mosaics, and lidar point clouds (LPC). Black and white cross-coded ground control points (GCPs) were surveyed using Real Time Kinematic (RTK) GPS and RTK-GPS enabled AeroPoints to georeference the model and orthomosaics during post-processing. The elevation and imagery products were produced to help partners at the Environmental Protection Agency (EPA) and U.S. Fish and Wildlife Service (USFWS) acquire accurate elevation data for target sites during the winter "leaf-off" period (March) and monitor changes in vegetation cover during peak growing season (August) building a baseline conditions dataset starting in August 2023. The March field collection included more baseline lidar data for additional large swaths of the National Wildlife Refuge as well as the thermal imagery dataset, which is the only planned thermal survey, and as a result took several days to complete. Although lidar was collecting during the August field effort, the focus was for vegetation at the Clearview Landfill and so only required one day of surveying. Future data collections are planned to support long-term monitoring of landscape change resulting from remediation efforts and potential storm impacts. Purpose: Lidar data were collected to penetrate vegetation canopy and provide accurate digital terrain models (DTMs) and digital surface models (DSMs) especially during the winter to understand canopy height. Aerial imagery was collected with appropriate resolution and overlap to permit high-quality photogrammetry and generation of digital surface models (DSM) and orthoimagery. Multispectral imagery was collected to aid in vegetation classification workflows, and TIR imagery was collected over a pond within Clearview Landfill to understand groundwater movement. Supplemental_Information: These data were collected by the USGS Coastal and Marine Hazards and Resources Program under USGS field activity number 2024-020-FA. The field activity webpage (https://cmgds.marine.usgs.gov/services/activity.php?fan=2024-020-FA) contains additional information regarding the field activity. Time_Period_of_Content: Time_Period_Information: Single_Date/Time: Calendar_Date: 20240814 Currentness_Reference: Ground condition Status: Progress: Complete Maintenance_and_Update_Frequency: Not planned Spatial_Domain: Bounding_Coordinates: West_Bounding_Coordinate: -75.26206 East_Bounding_Coordinate: -75.24639 North_Bounding_Coordinate: 39.91166 South_Bounding_Coordinate: 39.89540 Keywords: Theme: Theme_Keyword_Thesaurus: None Theme_Keyword: U.S. Geological Survey Theme_Keyword: USGS Theme_Keyword: Coastal and Marine Hazards and Resources Program Theme_Keyword: CMHRP Theme_Keyword: Woods Hole Coastal and Marine Science Center Theme_Keyword: WHCMSC Theme_Keyword: YellowScan Mapper Plus Theme_Keyword: DJI Matrice 600 Theme_Keyword: Point Cloud Theme_Keyword: UAS Theme_Keyword: MicaSense Altum-PT Theme_Keyword: Multispectral Theme_Keyword: surface reflectance Theme_Keyword: Rededge Theme_Keyword: near-infrared (NIR) Theme_Keyword: Panchromatic Theme_Keyword: Skydio X10 VT300-L Theme_Keyword: Thermal Infra-red (TIR) Theme_Keyword: Aerial Images Theme_Keyword: JPEG Theme_Keyword: TIFF Theme_Keyword: Digital Terrain Model (DTM) Theme_Keyword: Digital Surface Model (DSM) Theme_Keyword: orthomosaics Theme_Keyword: Spectra Precision SP80 Theme_Keyword: RTK GPS Theme_Keyword: AeroPoints Theme_Keyword: Aerial Imaging and Mapping Group Theme: Theme_Keyword_Thesaurus: USGS Thesaurus Theme_Keyword: remote sensing Theme_Keyword: lidar Theme_Keyword: thermal imaging Theme_Keyword: multispectral imaging Theme_Keyword: visible light imaging Theme_Keyword: digital elevation models Theme_Keyword: structure from motion Theme_Keyword: image mosaics Theme_Keyword: geospatial datasets Theme_Keyword: image collections Theme_Keyword: GPS measurement Theme_Keyword: navigational data Theme: Theme_Keyword_Thesaurus: ISO 19115 Topic Category Theme_Keyword: geoscientificInformation Theme_Keyword: elevation Theme_Keyword: environment Theme_Keyword: imageryBaseMapsEarthCover Theme: Theme_Keyword_Thesaurus: USGS Metadata Identifier Theme_Keyword: USGS:67644a60d34e5335adadf390 Place: Place_Keyword_Thesaurus: Geographic Names Information System (GNIS) Place_Keyword: Commonwealth of Pennsylvania (1779798) Place_Keyword: Philadelphia County (1209187) Place_Keyword: Township of Darby (1216381) Place_Keyword: Darby Creek(1172928) Place: Place_Keyword_Thesaurus: None Place_Keyword: North America Place_Keyword: United States Place_Keyword: Pennsylvania (PA) Place_Keyword: Darby Township Place_Keyword: Lower Darby Creek Access_Constraints: None Use_Constraints: Public domain (CC0-1.0) data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey (USGS) as the source of this information. These data are not intended for navigational use. Point_of_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jennifer M. Cramer Contact_Organization: U.S. Geological Survey, Northeast Region, Woods Hole Coastal and Marine Science Center Contact_Position: Geographer Contact_Address: Address_Type: mailing and physical address Address: 384 Woods Hole Rd. City: Woods Hole State_or_Province: MA Postal_Code: 02543-1598 Contact_Voice_Telephone: 508-548-8700 x2314 Contact_Electronic_Mail_Address: jcramer@usgs.gov Browse_Graphic: Browse_Graphic_File_Name: https://www.sciencebase.gov/catalog/file/get/67644a60d34e5335adadf390?name=2024020FA_Aug_browse.JPG&allowOpen=true Browse_Graphic_File_Description: Landscape view of the Clearview Landfill in the Darby Creek Superfund Site in March 2024. Browse_Graphic_File_Type: JPEG Native_Data_Set_Environment: Agisoft Metashape Pro v. 2.1.3, Trimble PosPac UAV v. 9.0, YellowScan CloudStation v. 2405.0.0, Global Mapper Pro v. 26.0 Cross_Reference: Citation_Information: Originator: Jin-Si R. Over Originator: Andrew C. Ritchie Originator: Christine J. Kranenburg Originator: Jenna A. Brown Originator: Daniel D. Buscombe Originator: Tom Noble Originator: Christopher R. Sherwood Originator: Jonathan A. Warrick Originator: Phillipe A. Wernette Publication_Date: 2021 Title: Processing coastal imagery with Agisoft Metashape Professional Edition, version 1.6-Structure from motion workflow documentation Series_Information: Series_Name: Open-File Report Issue_Identification: 2021-1039 Publication_Information: Publication_Place: Reston, VA Publisher: U.S. Geological Survey Other_Citation_Details: This publication includes the general methodology for processing imagery in Metashape to produce digital surface models and ortho products. Online_Linkage: https://doi.org/10.3133/ofr20211039 Data_Quality_Information: Attribute_Accuracy: Attribute_Accuracy_Report: Lidar point clouds: A YellowScan Mapper Plus (YSMP) high-density LiDAR system, containing a Livox Avia LiDAR sensor, Applanix inertial measurement unit (IMU) and GPS/GNSS antenna, and natural color RGB SONY UMC-10RC camera module, was mounted to a DJI Matrice 600 uncrewed aircraft system (UAS) to collect low-altitude aerial LiDAR point cloud (LPC) data and simultaneous overlapping natural color color images. GPS/GNSS data from real-time kinematic (RTK) base station collecting positions on a known point at 1-hz for the duration of the lidar surveys is used for post-processing kinematic (PPK) corrections of the lidar system trajectory positions. Accuracy of the point clouds can be influenced by the flight altitude, velocity, positions of satellites, terrain, overlap, and atmospheric conditions. Returns are scattered or lost over water, resulting in large bands of no data. This does not impact the goal of the data collection, which is focused on the elevation of the land. Positional accuracy of the processed point cloud can be assessed using RTK-surveyed ground control points and checkpoints (see ground control and checkpoints section below). Horizontal accuracy can be difficult to assess due to difficulty visualizing the cross-checkered pattern of the ground control targets in the point cloud. Ground control and checkpoints: Ground control points (GCPs) are highly visible, typically square and cross-checkered black and white (or light grey), targets designed to be easily identifiable in aerial remote sensing data. RTK-GPS embedded, Wi-Fi enabled grey and black foam Propeller AeroPoints were used to collect continuous location and elevation data as GCPs. To improve visibility in the lidar point cloud, 2x2 meter square vinyl targets, with the same cross-checkered pattern as the AeroPoints were placed underneath the AeroPoints, with grey and black areas aligned. RTK-GPS: GPS point accuracy is assessed based on occupations of a known reference mark and GPS point precision is based on a positioning solution within 1-3 cm or “FIX” for each point and root mean square values of the position. Elevation products: The positional accuracy of elevation and image mosaic rasters are typically determined from RTK-surveyed GCPs and check points. GCPs are surveyed targets visible in aerial imagery that are used to georeference the model, while check points are independent of the model and can be used for post-validation. GCPs and checkpoints were surveyed at the Clearview Landfill survey location. Accuracy degrades toward the edges of the raster products due to the absence of GCPs as well as the lack of overlap along the perimeter of the flight plan and angle of the images where the UAS is turning. Logical_Consistency_Report: UAS data collection: Most missions require multiple flights to complete due to battery limitations. Between individual flights, the camera/sensor settings and mission plan specifications are not changed to ensure consistent data/imagery collection. Following each flight, data is downloaded to a field computer, copied to an external storage device, and later uploaded to a data server. For lidar data, the RGB photos are verified, and the scanner data is plotted in an offline version of YellowScan CloudStation between each flight to verify the scanner was operating as expected and that there are no areas of missing data. Images are also plotted in a photogrammetry software to verify no missing sections of the flight plan before continuing with the mission. GPS data: All RTK-GPS rover data were exported as a single tabular comma-separated values (CSV) file using Microsoft Excel v. 2208. AeroPoint data are uploaded via a WiFi connection to a user defined account on propelleraero.com. The raw data are processed by Propeller and exported to a CSV file. Image Data Management: Aerial images were organized into directories labeled by flight number and then transferred to an external drive and later uploaded to the AIMG server. Images were renamed to include the field activity number (FAN), flight number, camera ID, date and time (UTC), and original filename. Gaps in consecutive flight numbers may be due to a variety of reasons, including no photos being collected during a particular flight, failure to initiate camera, or issues with the imagery during a particular flight. Metadata contained in image file headers were modified for all photos to include standard USGS tags. The natural color images from the YellowScan camera module were manually geotagged using a script that accesses the UAS telemetry logs (tlogs). MicaSense Altum-PT images are internally geotagged by a downwelling light sensor (DLS 2) with integrated u-blox NEO-M8 GNSS module, which also writes illumination information to the image exif. The natural color and thermal-IR images from the Skydio X10 are geotagged by an onboard GNSS/GPS. See the processing steps in Lineage for more information. All processing was done by members of the Aerial Imaging and Mapping Group (AIMG). Completeness_Report: Lidar data: Data was collected in one flight over the Clearview Landfill with the YellowScan Mapper Plus (YSMP) system. The resulting data included one each of .ys, .lvx, and .T04 scanner data files. These files were used in the creation of the .laz point cloud file, but are not included in this data release. One LPC was produced for the survey area over the Clearview Landfill totaling 844.72 MB. A digital surface model (DSM) and digital terrain model (DTM) were generated for the Clearview Landfill, totaling 934 MB. Aerial Imagery: Gaps in sequential 2-second photo intervals exist where photos were removed from the collection. Photos can be removed for reasons including, collected outside flight plan bounds, poor photo quality, overexposure, or redundancy. The final image count for the YSMP natural color imagery in this data release is 428 images totaling 3620 megabytes (MB). The final image count for the MicaSense Altum-PT is 8580 totaling 77,303 MB. The final image count for the Skydio X10 natural color and thermal imagery in this data release is 1,407 images totaling 7574 MB in size. The final image count for vegetation survey photos is 97, totaling 423 MB. Images were geotagged either manually or by an integrated GPS in the sensor. Image location information is provided in the CSV files titled "2024020FA_Clearview_Aug2024_SX10_ImageLocs.csv", "2024020FA_Clearview_Aug2024_YSMP_ImageLocs.csv", "2024020FA_Clearview_Aug2024_aPT_ImageLocs.csv" and "2024020FA_ClearviewVegSurvey_Aug2024_ImageLocs.csv." Structure-from-motion (SfM) processing: Images that were collected outside the bounds of the flight plan, whose photo quality was poor, overexposed, or redundant were disabled and excluded from the photogrammetric model processing. Only enabled images that were used in the photogrammetric model were included in this data release. Additional Altum-PT calibration photos for radiometric calibration of the reflectance image were included in the data release and are appended with "_cal" at the end of the file name. GPS data: The following GPS data was collected within the boundary of the Clearview Landfill. From the SP80 RTK-GPS, a total of 33 surveyed vegetation sample points are included in the "2024020FA_ClearviewVegSurvey_Aug2024.csv" dataset and a total of 111 checkpoint and transect surveyed points are included in "2024006FA_Darby_Mar2024_SP80.csv" dataset. 10 AeroPoints were deployed and are included in the "2024020FA_Aug2024_Clearview_AeroPoint.csv" dataset. Positional_Accuracy: Horizontal_Positional_Accuracy: Horizontal_Positional_Accuracy_Report: Lidar data: Determining horizontal positional accuracy using ground control is difficult due to poor visualization of the center location of ground control targets in the LPC. Considering the GNSS reference accuracy of ~5 cm, a conservative horizontal positional error estimate could be considered up to 10 cm. Aerial Imagery: YellowScan Mapper+ camera module images were manually geotagged using the drone telemetry logs (tlogs). The DJI M600 is equipped with a DJI A3 GPS, which receives signals from GPS and GLONASS satellites in WGS84 (EPSG::4326), but is otherwise uncorrected. The Skydio X10 has an integrated GNSS/GPS receiving signals from GPS + Galileo + GLONASS + BeiDou in WGS84 (EPSG::4326). The Altum-PT contains a u-blox NEO-M8 GNSS module within the DLS sensor, which receives signals from GPS and GLONASS in WGS84/EGM96. Horizontal locations are considered accurate to approximately 0.5 meters, but may be greater than 10 meters due to UAS flight path uncertainty. It is recommended to use the ground control points in the CSV files "2024020FA_Aug2024_Clearview_AeroPoint.csv" for georeferencing. Structure-from-motion (SfM) processing: The RGB/TIR orthomosaic and multispectral reflectance orthomosaic have no elevation data associated with them. The horizontal X/Y RMSE of the orthomosaic from the Altum-PT multispectral imagery is 1.71 cm. The horizontal X/Y RMSE of the orthomosaic from the Skydio X10 RGB and TIR imagery is 2.82 cm. GPS Data: Horizontal positions for the AeroPoint targets are determined from the embedded RTK-GPS. The internal theoretical horizontal accuracy is 10 mm. The global horizontal accuracy is calculated using the following equation: global horizontal accuracy (mm) = internal horizontal accuracy (mm) + longest baseline distance (km) * 2. The resultant global horizontal accuracy of AeroPoint positions is 0.018 m. The SP80 RTK-GPS has a theoretical horizontal accuracy of 2 cm. Vertical_Positional_Accuracy: Vertical_Positional_Accuracy_Report: Lidar data: Using the SP80 RTK-surveyed checkpoints and AeroPoint targets, the LiDAR QC tool in Global Mapper v. 26.0 was used to determine the root mean square error (RMSE) of point cloud compared to the checkpoints. The point spacing was set to 3 (~12 cm), which averages the elevation value of points falling within a 3 point buffer from the checkpoint position. The vertical RMSE determined from the checkpoint positions for the Clearview Landfill LPC was 11.7 cm. The higher RMSE compared to the March survey is likely due to the denser vegetation in August allowing fewer lidar returns to penetrate the canopy. Aerial Imagery: YellowScan Mapper+ camera module images were manually geotagged using the drone telemetry logs (tlogs). The DJI M600 is equipped with a DJI A3 GPS, which receives signals from GPS and GLONASS satellites in WGS84 (EPSG::4326), but is otherwise uncorrected. The Skydio X10 has an integrated GNSS/GPS receiving signals from GPS + Galileo + GLONASS + BeiDou in WGS84 (EPSG::4326). The Altum-PT contains a u-blox NEO-M8 GNSS module within the DLS sensor, which receives signals from GPS and GLONASS in WGS84/EGM96. Vertical locations are considered accurate to approximately 0.5 meters, but may be greater than 10 meters due to UAS flight path uncertainty. It is recommended to use the ground control points in the CSV files "2024020FA_Aug2024_Clearview_AeroPoint.csv" for georeferencing. GPS Data: Vertical positions for the AeroPoint targets are determined from the embedded RTK-GPS. The internal theoretical vertical accuracy is 20 mm. The global vertical accuracy is calculated using the following equation: global vertical accuracy (mm) = internal vertical accuracy (mm) + longest baseline distance (km) * 2. The resultant global vertical accuracy of AeroPoint positions is 0.028 m. The SP80 RTK-GPS has a theoretical vertical accuracy of 2 cm. Lineage: Process_Step: Process_Description: RTK-GPS Base Station and Rover: A Spectra Precision model SP80 GNSS base station receiving real-time differential corrections from the satellites was set up to collect positions in RINEX format at 1 hz on a known point prior to and for the duration of lidar data surveys. A SP80 rover receiving real-time differential corrections from the Pennsylvania CORS network was used to survey points across the field area, including ground position validation points and vegetation sample points. The RTK receivers for both the base and rover are linked via Bluetooth to a handheld data collector (Carlson CHC LT30 Handheld Terminal running Carlson SurvCE v. 4.06 software under Windows Mobile v. 6.1 Professional operating system). Rover antennas were mounted on 2 m survey rods with bubble levels and 5 cm (2 inch) sand feet. Conversions from satellite coordinates to NAD83(2011) UTM zone 18N (EPSG::6347) and NAVD88 (EPSG::5703) were made by Carlson SurvCE software in the data collector. Process_Date: 20240814 Process_Step: Process_Description: Ground control: AeroPoint targets were emplaced on flat, stable surfaces, with clear view of the sky and left undisturbed, collecting data for at least 2 hours. AeroPoint data was uploaded via a WiFi connection to a user defined account on propelleraero.com. The raw data are processed by Propeller and exported to a CSV file in NAD83(2011) UTM zone 18N (EPSG::6347) for horizontal and NAVD88 (geoid 18) (EPSG::5703) for vertical. Process_Date: 20240814 Process_Step: Process_Description: LiDAR System: A YellowScan Mapper Plus (YSMP) high-density LiDAR system containing a LiDAR sensor and natural color RGB camera module was mounted to a DJI Matrice 600 (M600) uncrewed aircraft system (UAS) to collect low-altitude aerial LiDAR point cloud (LPC) data and simultaneous overlapping natural color (RGB) images. A configuration text file (CONFIG.TXT) is pre-loaded onto the lidar USB thumb drive and was edited to control LiDAR and camera module settings, including the camera triggering height, the camera triggering interval, and the LiDAR scan pattern. For this field area over marsh and forested terrain, a point density of ~300 ppsqm was targeted with a non-repetitive (spirograph) scan pattern. The flight plans for this project targeted a swath overlap of 50% with the following flight parameters: altitude of 61 m, flight line spacing at 45 m, a velocity of 10 m/s, and a 2-second camera triggering interval. At these parameters, the natural color RGB camera module was set to trigger every 3 seconds to achieve 50% sidelap and forelap for colorization of the LPC in post-processing. For every lidar UAS flight, the following steps were followed to properly operate the system and collect data: After powering on the UAS and LiDAR system, the GPS, scanner, and camera module all must initialize. After takeoff, an additional initialization pattern must be manually flown by the pilot to signal to the IMU to begin collecting LiDAR data. This pattern consists of a forward, back, and forward flight path ending with a hook-shaped coordinated turn on the last forward maneuver. It is best practice that this is flown below the camera triggering altitude. Once the maneuver is completed, the UAS is ascended to the camera triggering altitude where the RGB camera module sets the ISO for the entire flight. It is recommended to make this altitude close to the flight plan altitude. The mission is uploaded to the UAS and it begins the automated flight plan. When the data collection is finished or batteries require swapping, the same initialization pattern flown at the beginning is flown again to de-initialize the scanner. The LiDAR data is saved to a 256 GB USB thumb drive in three different files: (1) the IMU+GPS data, decimated for quick post-processing, in binary *.ys format, (2) the scanner data in *.lvx format (~600 MB per minute of data collection), (3) and the complete IMU+GPS data in Applanix (Trimble) binary *.t04 format. The RGB images are saved to a 64 GB micro SD card as *.jpeg files. The camera triggering time-interval was determined and set based on the focal length and ground sampling distance (GSD) of the camera as well as the altitude and speed of the UAS in order to achieve ~50% forelap between adjacent photos for colorizing the LiDAR point cloud. The camera triggering interval as well as the altitude at which the camera automatically sets the ISO for the scene is written into a configuration file located on a USB stick that is plugged into the YellowScan Mapper Plus system. Process_Date: 20240814 Process_Step: Process_Description: Skydio X10: Thermal infra-red (TIR) and natural color (RGB) aerial images were collected using the Skydio X10 LZ300 UAS with narrow FOV camera. Two types of TIR images were collected, a "normal" TIR jpeg and a radiometric-TIR JPEG, so three images are stored for each camera trigger. The flight plan settings included a flight altitude of 70 m, a velocity of 5 m/s, a transect spacing of 35 meters and a camera trigger interval of 2 seconds. The skydio ground control system automatically builds the flight plan around the target transect spacing of 75%. The TIR and RGB images are saved to a micro SD card as *.JPG files. Process_Date: 20240814 Process_Step: Process_Description: MicaSense Altum-PT: Multispectral aerial images were collected using a MicaSense Altum-PT mounted to a DJI M600 UAS. The Altum-PT contains 7 sensors: 5 multispectral bands, blue (443-507 nanometers (nm)), green (533-587 nm), red (652-684 nm), red edge (705-729 nm), and near-infrared (NIR) (785-899 nm), 1 panchromatic band (171.5 nm - 1098 nm), and 1 long-wave infrared (LWIR) thermal band (4.5 - 16.5 microns). The LWIR band images were not used in any processing workflows and were excluded from this data release. The flight plan settings included a flight altitude of 61 m, a velocity of 7 m/s, a transect spacing of 20 meters and a camera trigger interval of 3 seconds. Immediately prior to and following each flight, a MicaSense reflectance calibration panel is photographed on the ground in order to perform a reflectance calibration of the imagery in post-processing to account illumination conditions over the course of the survey. The images are saved to a CF Express type B SD card in TIFF format as they are collected. Process_Date: 20240814 Process_Step: Process_Description: Lidar data processing: After each data collection, the three data files are stored on the USB thumb drive in a folder following a naming scheme of "YS-YYYYMMDD-HHMMSS" where YS is the acronym for YellowScan, YYYYMMDD is the date stamp, and HHMMSS is the time stamp in UTC time (e.g. YS-20230830-171402). Within this folder are the three files containing the IMU+GPS data in .ys and .t04 format and the scanner data in *.lvx format, which follow the same naming scheme as the parent folder. The RGB images are stored on the SD card following a naming scheme of DSC#####.JPG (e.g. DSC00001.JPG). Upon import of the raw scanner data (.ys file) for each flight to YellowScan CloudStation v. 2210.0.0, the sensor's Lidar (.profile) and Camera (.camera) profiles, provided by the vendor, are selected for the project and the project coordinate reference system is defined. CloudStation auto-identifies sensor position trajectories that are to be included in the model based on their length and linearity, but adjustments are usually required as the software will sometimes misidentify trajectories that should not be included, such as the path the UAS took to reach the first waypoint of the mission, or leave out paths that are considered too short. If there is a slight waiver in a flight path, the software will sometimes cut off the ends of the flight paths. The .T04 file and base station GNSS RINEX file were used to correct and optimize the sensor position trajectories using th GNSS Inertial Processor and produce a Smoothed Best Estimate of Trajectory (SBET) file in .txt ASCII format, which represents the Post Processing Kinematic (PPK) Solution. The lever arm offsets and boresight angle corrections were applied to the LPC, along with a strip adjustment between transect swaths using CloudStation's "robust" setting. The LPC was then colorized using the images. The Cut Overlap function was applied to remove redundant points based on the closest parallel flight trajectory. The unclassified LPC model was then exported from CloudStation as a 1.4 LAZ file. The LPCs were brought into Global Mapper (v. 26.0) and manually cleaned by reclassifying or removing points interpreted to be noise, points that were either not classified or incorrectly classified as ground, or are above a reasonable elevation threshold based on the surrounding features. The LPCs were exported as a 1.4 LAZ files. To produce the DSMs, the LPCs are gridded in Global Mapper using maximum values and exported to geotiff format. To produce DTMs, only the ground points are gridded using maximum values and exported to geotiff format. All files were exported in EPSG:6347 NAD83(2011)/UTM zone 18N and the vertical datum in EPSG:5703 NAVD88 using Geoid 18. Process_Date: 20240814 Process_Step: Process_Description: Imagery processing: Telemetry navigation logs for each flight are exported from the Ignis app in GPX format. These telemetry logs are used to manually geotag the imagery from the YellowScan Mapper Plus camera modules in preparation for photogrammetric processing. Image timestamps must be adjusted to UTC time depending on timezone and daylight saving. These corrections were done using the program ExifTool. ExifTool uses linear interpolation to determine the position of the device at the time recorded in the image. This creates values for tags GPSLatitude, GPS LatitudeRef, GPSLongitude, GPSLongitudeRef, GPSAltitude, GPSTimeStamp, GPSDateStamp. A sample of code used to geotag images: exiftool -v2 -geotag ../../telemetry/Nav_FlightLogs/Flight\ Logs\ GPX/flight_log_2022_10_10_14_02_42_AGL.gpx -geosync=+16 '-geotime<${DateTimeOriginal}-04:00' -P f05XT2c/*.JPG. All images were renamed to ensure unique filenames following the USGS Coastal and Marine Hazards and Resources Program's best practices for image naming convention: "FieldActivityNumber_f##sensorID_YYYYMMDDTHHMMSS_OriginalFilename.tif" (e.g. "2024020FA_f07SX10c_20240814T194608Z_S1004236.JPG") Field activity number is a unique identifier assigned to the field effort under which the data was collected (e.g. 2024020FA), f## denotes the flight in which the photos were taken (e.g. f07), sensor ID is the sensor or camera used to collect the imagery (e.g. SX10c = Skydio X10 LZ300 natural color RGB camera; SX10n = Skydio X10 LZ300 thermal infra-red TIR normal image, and SX10r = Skydio X10 LZ300 radiometric TIR image), 'YYYYMMDD' is the UTC date, 'HHMMSS' is UTC time and the 'T' is used to separate the UTC date from UTC time, and the original filename is appended to the end. To ensure compliance with USGS Coastal and Marine Hazards and Resources Program's best practices for image exif, exif tags were added using a CSV containing header information for each photo. A sample of the code used to edit the image tags using ExifTool version 12.52: 'exiftool -csv="C:\directory\name\EXIF.csv" C:\directory\name\of\photos *.[ext] The following tags were added to the image exif: -IPTC:Credit="U.S. Geological Survey" -IPTC:Contact="WHSC_data_contact@usgs.gov" -EXIF:Copyright="Public Domain" -XMP:UsageTerms="Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty." -EXIF:ImageDescription="https://cmgds.marine.usgs.gov/fan_info.php?fan=2024-020-FA; Low-altitude aerial photograph of the Lower Darby Creek Superfund, Darby Township, Pennsylvania, taken with the normal thermal module of the Skydio X10 UAS during USGS field activity 2024-020-FA" -XMP:AttributionURL="https://doi.org/10.5066/P134HU3Y" -EXIF:GPSAreaInformation="camera-integrated GPS" -EXIF:GPSMapDatum="EPSG:4326 (WGS 84)" -IPTC:keywords="UAS Aerial Imagery, John Heinz National Wildlife Refuge, Lower Darby Creek Superfund, Darby Township, Pennsylvania, 2023-020-FA, USGS, Skydio X10" -EXIF:Artist="WHCMSC AIM Group" -XMP:PreservedFilename>Filename. The images for this data release have been uploaded to the Imagery Data System (IDS), which renames the images to safeguard from accidental overwriting. A user can restore the preserved filename with ExifTool. It is recommended to test on a single image before running on all images. To test on a single image: exiftool "-XMP:PreservedFilename 2024020FA_Clearview_Aug2024_YSMP_ImageLocs.csv Process_Date: 20240814 Process_Step: Process_Description: Structure-from-motion processing: The SfM products were created in Agisoft Metashape v. 2.0.1 using the following general steps (see Over and others, 2021 for a more detailed methodology explanation), which applies to the imagery collected by each sensor: 1. A project was created in Metashape and imagery specific to each sensor and flight area were imported. 2. Photos were aligned at a low accuracy and then GCPs were automatically detected in the point cloud. GCP positions (2024020FA_Clearview_Aug2024_AeroPoint.csv) were added to the project in the reference systems NAD83(2011)/UTM Zone 18N and NAVD88 (geoid 18). The horizontal and vertical accuracies for the GCPs were set to 0.018/0.028 m, respectively, and the camera positions for the images were turned off. The photos were then re-aligned with high accuracy (the pixels were not subsampled) using a keypoint limit of 60,000 and unlimited tie points. 3. The alignment process matched pixels between images to create point clouds and put the imagery into a relative spatial context using the GCPs. The resultant point clouds were filtered using one iteration of the 'Reconstruction uncertainty' filter at a level of 10, one iteration of the 'Projection accuracy' filter at a level of 3, and eight iterations of the 'Reprojection accuracy' filter to get to a level of 0.3. With each filter, iteration points are selected, deleted, and then the camera model was optimized to refine the focal length, cx, cy, k1, k2, k3, p1, and p2 camera model coefficients. 4. At this point, multiple ‘chunks’ were created so that a high-quality dense cloud with a low-frequency filtering algorithm could be made from the images. The dense point cloud was then edited by visual inspection and Metashape’s confidence filter to remove points with a low confidence near the edges and near water bodies. 5. A DSM is built from the dense point cloud and then an orthomosaic is built from the DSM with refined seamlines. The DSM and orthomosaic are exported in EPSG:6347 NAD83(2011)/UTM18N, the DSM has a vertical reference system in EPSG:5703 NAVD88 (Geoid 18). Process_Date: 20240814 Process_Step: Process_Description: CLOUD OPTIMIZATION: All geoTIFF products were DEFLATE compressed and turned into a cloud-optimized GeoTIFFs (COG) using either the export tool in Global Mapper or gdal_translate with the following command: for %i in (.\*.tif) do gdal_translate %i .\cog\%~ni_cog.tif -of COG -stats -co BLOCKSIZE=256 -co COMPRESS=DEFLATE -co PREDICTOR=YES -co NUM_THREADS=ALL_CPUS -co BIGTIFF=YES (v. 3.1.4 accessed October 20, 2020 https://gdal.org/). Where i is the name of each geoTIFF section. Process_Date: 20241206 Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jennifer M. Cramer Contact_Organization: U.S. Geological Survey, Woods Hole Coastal and Marine Science Center Contact_Position: Geographer Contact_Address: Address_Type: mailing and physical address Address: U.S. Geological Survey Address: 384 Woods Hole Rd. City: Woods Hole State_or_Province: MA Postal_Code: 02543-1598 Contact_Voice_Telephone: 508-548-8700 x2314 Contact_Electronic_Mail_Address: jcramer@usgs.gov Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Planar: Grid_Coordinate_System: Grid_Coordinate_System_Name: Universal Transverse Mercator Universal_Transverse_Mercator: UTM_Zone_Number: 18 Transverse_Mercator: Scale_Factor_at_Central_Meridian: 0.999600 Longitude_of_Central_Meridian: -75.000000 Latitude_of_Projection_Origin: 0.000000 False_Easting: 500000.000000 False_Northing: 0.000000 Planar_Coordinate_Information: Planar_Coordinate_Encoding_Method: row and column Coordinate_Representation: Abscissa_Resolution: 0.001 Ordinate_Resolution: 0.001 Planar_Distance_Units: meters Geodetic_Model: Horizontal_Datum_Name: North American Datum of 1983 (National Spatial Reference System 2011) Ellipsoid_Name: GRS_1980 Semi-major_Axis: 6378137.0 Denominator_of_Flattening_Ratio: 298.257222101 Vertical_Coordinate_System_Definition: Altitude_System_Definition: Altitude_Datum_Name: North American Vertical Datum of 1988 Altitude_Resolution: 0.001 Altitude_Distance_Units: meters Altitude_Encoding_Method: Explicit elevation coordinate included with horizontal coordinates Entity_and_Attribute_Information: Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_ClearviewVegSurvey_Aug2024.csv Entity_Type_Definition: The CSV file contains information and measurements from a ground reference vegetation survey at Clearview Landfill. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: POINT ID Attribute_Definition: The number assigned to the coordinate pair by the RTK GPS in the field. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 2 Range_Domain_Maximum: 35 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Reference Photo ID Attribute_Definition: The reference number used to match the row data to the corresponding field photos based on the image number in the image filename. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1 Range_Domain_Maximum: 33 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Surface Class Attribute_Definition: Description of the surface type based on the following classes: bare ground/soil, grass/low veg, deciduous forest, impervious, and wetland. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Notes Attribute_Definition: Additional details describing surface types, such as whether the ground is dirt or gravel or specific vegetation types if applicable. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: % Veg Cover Attribute_Definition: The percentage of the chosen surface type present at the immediate vicinity of the surveyed point. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 100 Attribute_Units_of_Measure: percent Attribute: Attribute_Label: Veg Height (mm) Attribute_Definition: Global hemisphere the latitude coordinates are referenced to. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 800 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Northing Attribute_Definition: NAD83(2011) / UTM Zone 18N Northing coordinate of the survey site. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4416611.260 Range_Domain_Maximum: 4417356.115 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Easting Attribute_Definition: NAD83(2011) / UTM Zone 18N Easting coordinate of the survey site. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 478092.559 Range_Domain_Maximum: 478475.300 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Elevation (m) Attribute_Definition: Elevation of the survey point referenced to geoid 18. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4.1588 Range_Domain_Maximum: 31.317 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: HSDV Attribute_Definition: Standard deviation of horizontal location values Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.008 Range_Domain_Maximum: 0.297 Attribute_Units_of_Measure: centimeters Attribute: Attribute_Label: VSDV Attribute_Definition: Standard deviation of vertical location values. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.011 Range_Domain_Maximum: 0.432 Attribute_Units_of_Measure: centimeters Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_ClearviewVegSurvey_Aug2024_ImageLocs.csv Entity_Type_Definition: The CSV file contains the approximate position of the cell phone images at the moment of each capture based on camera-integrated GPS. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: SourceFile Attribute_Definition: File names of individual images, see the Process Description for file naming convention. Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: PreservedFileName Attribute_Definition: File names copied from the SourceFile tag to preserve the original file name once image is uploaded to the Imagery Data System (IDS). Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSMapDatum Attribute_Definition: The EPSG code for the coordinate system of the images. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSLatitude Attribute_Definition: Latitude (x) of camera based on time of each image capture. Positive values represent north coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 39.89928889 Range_Domain_Maximum: 39.90630833 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: GPSLongitude Attribute_Definition: Longitude (y) of camera based on time of each image capture. Negative values represent west coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -75.25632500 Range_Domain_Maximum: -75.25031944 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Map Datum (UTM) Attribute_Definition: The geographic coordinate system of the image locations transformed to NAD83(2011) UTM coordinates. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Easting Attribute_Definition: Easting coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 478089.1852 Range_Domain_Maximum: 478603.7698 Attribute_Units_of_Measure: meter Attribute: Attribute_Label: Northing Attribute_Definition: Northing coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4416609.4500 Range_Domain_Maximum: 4417387.5300 Attribute_Units_of_Measure: meter Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_aPT_ImageLocs.csv Entity_Type_Definition: The CSV file contains the approximate position of the Altum-PT images at the moment of each capture based on camera-integrated GPS. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: SourceFile Attribute_Definition: File names of individual images, see the Process Description for file naming convention. Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: PreservedFileName Attribute_Definition: File names copied from the SourceFile tag to preserve the original file name once image is uploaded to the Imagery Data System (IDS). Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSMapDatum Attribute_Definition: The EPSG code for the coordinate system of the images. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSLatitude Attribute_Definition: Latitude (x) of camera based on time of each image capture. Positive values represent north coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 39.8983683 Range_Domain_Maximum: 39.9078061 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: GPSLongitude Attribute_Definition: Longitude (y) of camera based on time of each image capture. Negative values represent west coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -75.2578264 Range_Domain_Maximum: -75.2500729 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Map Datum (UTM) Attribute_Definition: The geographic coordinate system of the image locations transformed to NAD83(2011) UTM coordinates. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Easting Attribute_Definition: Easting coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 477960.8621 Range_Domain_Maximum: 478625.2810 Attribute_Units_of_Measure: meter Attribute: Attribute_Label: Northing Attribute_Definition: Northing coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4435236.0640 Range_Domain_Maximum: 4436267.2080 Attribute_Units_of_Measure: meter Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_SX10_ImageLocs.csv Entity_Type_Definition: The CSV file contains the approximate position of the Skydio X10 images at the moment of each capture based on the drone GPS telemetry logs. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: SourceFile Attribute_Definition: File names of individual images, see the Process Description for file naming convention. Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: PreservedFileName Attribute_Definition: File names copied from the SourceFile tag to preserve the original file name once image is uploaded to the Imagery Data System (IDS). Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSMapDatum Attribute_Definition: The EPSG code for the coordinate system of the images. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSLatitude Attribute_Definition: Latitude (x) of camera based on time of each image capture. Positive values represent north coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 39.89905007 Range_Domain_Maximum: 39.90664923 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: GPSLongitude Attribute_Definition: Longitude (y) of camera based on time of each image capture. Negative values represent west coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -75.25730842 Range_Domain_Maximum: -75.25116145 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Map Datum (UTM) Attribute_Definition: The geographic coordinate system of the image locations transformed to NAD83(2011) UTM coordinates. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Easting Attribute_Definition: Easting coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 478005.0953 Range_Domain_Maximum: 478531.1143 Attribute_Units_of_Measure: meter Attribute: Attribute_Label: Northing Attribute_Definition: Northing coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4416582.9910 Range_Domain_Maximum: 4417425.9530 Attribute_Units_of_Measure: meter Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_YSMP_ImageLocs.csv Entity_Type_Definition: The CSV file contains the approximate position of the YSMP images at the moment of each capture based on the drone GPS telemetry logs. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: SourceFile Attribute_Definition: File names of individual images, see the Process Description for file naming convention. Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: PreservedFileName Attribute_Definition: File names copied from the SourceFile tag to preserve the original file name once image is uploaded to the Imagery Data System (IDS). Attribute_Definition_Source: USGS Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSMapDatum Attribute_Definition: The EPSG code for the coordinate system of the images. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: GPSLatitude Attribute_Definition: Latitude (x) of camera based on time of each image capture. Positive values represent north coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 39.89853843 Range_Domain_Maximum: 39.90763517 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: GPSLongitude Attribute_Definition: Longitude (y) of camera based on time of each image capture. Negative values represent west coordinates. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -75.25772801 Range_Domain_Maximum: -75.25039888 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Map Datum (UTM) Attribute_Definition: The geographic coordinate system of the image locations transformed to NAD83(2011) UTM coordinates. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Easting Attribute_Definition: Easting coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 477969.1308 Range_Domain_Maximum: 478597.2597 Attribute_Units_of_Measure: meter Attribute: Attribute_Label: Northing Attribute_Definition: Northing coordinate of the image in meters. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4416526.0990 Range_Domain_Maximum: 4417534.8490 Attribute_Units_of_Measure: meter Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Aug2024_Clearview_AeroPoints.csv Entity_Type_Definition: Ground control point positions, elevations, and attributes Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: FAN Attribute_Definition: USGS Field Activity Number Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 2024-020-FA Enumerated_Domain_Value_Definition: Year, USGS ID, and Field Activity Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Date Attribute_Definition: Calendar date of collection Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 20240814 Enumerated_Domain_Value_Definition: YYYYMMDD Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Point ID Attribute_Definition: Unique point identification number. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1 Range_Domain_Maximum: 10 Attribute: Attribute_Label: Attributes Attribute_Definition: Unique identifier for individual AeroPoints. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Latitude NAD83[2011] Attribute_Definition: Post-processed latitude of AeroPoint position (NAD83[2011]). Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 39.8995406 Range_Domain_Maximum: 39.90608257 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Longitude NAD83[2011] Attribute_Definition: Post-processed longitude of AeroPoint position (NAD83[2011]). Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -75.25613815 Range_Domain_Maximum: -75.25247364 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Ellipsoid NAD83[2011] Attribute_Definition: Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid. Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -28.292 Range_Domain_Maximum: -1.318 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Northing 18N Attribute_Definition: Post-processed interpolated Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 18N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4416638.346 Range_Domain_Maximum: 4417363.944 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Easting 18N Attribute_Definition: Post-processed interpolated X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 18N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 478105.281 Range_Domain_Maximum: 478418.884 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Orthometric NAVD88 Attribute_Definition: Post-processed Z-coordinate of AeroPoint using NAVD88 with Geoid 18 applied. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4.674 Range_Domain_Maximum: 31.647 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Xvar mm Attribute_Definition: Internal variance in the X-coordinate from post-processing. No data value is NaN. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 1.8 Range_Domain_Maximum: 5.3 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Yvar mm Attribute_Definition: Internal variance in the Y-coordinate from post-processing. No data value is NaN. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 3 Range_Domain_Maximum: 9.6 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Zvar mm Attribute_Definition: Internal variance in the Z-coordinate from post-processing. No data value is NaN. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4.6 Range_Domain_Maximum: 10 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Baseline distance km Attribute_Definition: Distance to from the AeroPoint to the correcting base. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.16 Range_Domain_Maximum: 4.14 Attribute_Units_of_Measure: kilometers Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Aug2024_Darby_SP80.csv Entity_Type_Definition: SP80 RTK-GPS check point positions, elevations, and attributes. Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: FAN Attribute_Definition: USGS Field Activity Number Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 2024-020-FA Enumerated_Domain_Value_Definition: Year, USGS ID, and Field Activity Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Date Attribute_Definition: Calendar date of collection Attribute_Definition_Source: USGS Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: 20240814 Enumerated_Domain_Value_Definition: YYYYMMDD Enumerated_Domain_Value_Definition_Source: USGS Attribute: Attribute_Label: Point ID Attribute_Definition: Unique point identification number. Attribute_Definition_Source: Processor defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 36 Range_Domain_Maximum: 146 Attribute: Attribute_Label: Attributes Attribute_Definition: Identifies the point type (e.g. "transect" or "check point") Attribute_Definition_Source: producer defined Attribute_Domain_Values: Unrepresentable_Domain: Character string. Attribute: Attribute_Label: Latitude NAD83[2011] Attribute_Definition: Real-time Kinematic latitude of GPS point (NAD83[2011]). Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 39.8991458 Range_Domain_Maximum: 39.90601088 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Longitude NAD83[2011] Attribute_Definition: Real-time Kinematic longitude of GPS point (NAD83[2011]). Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -75.25628347 Range_Domain_Maximum: -75.25181287 Attribute_Units_of_Measure: decimal degrees Attribute: Attribute_Label: Ellipsoid NAD83[2011] Attribute_Definition: Real-time Kinematic vertical position of GPS point in relation to the NAD83(2011) reference ellipsoid. Attribute_Definition_Source: None Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -28.805 Range_Domain_Maximum: -1.465 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Northing 18N Attribute_Definition: Real-time kinematic Y-coordinate of GPS point in NAD83(2011)/UTM Zone 18N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4416594.497 Range_Domain_Maximum: 4417356.115 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Easting 18N Attribute_Definition: Real-time kinematic X-coordinate of GPS point in NAD83(2011)/UTM Zone 18N. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 478092.5589 Range_Domain_Maximum: 478475.3003 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Orthometric NAVD88 Attribute_Definition: Real-time kinematic Z-coordinate of GPS point relative to NAVD88 with Geoid 18 applied. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4.1588 Range_Domain_Maximum: 31.5008 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: XYvar m Attribute_Definition: Internal variance in the XY-coordinate from post-processing. No data value is NaN. Attribute_Definition_Source: USGS Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.006 Range_Domain_Maximum: 0.297 Attribute_Units_of_Measure: millimeters Attribute: Attribute_Label: Zvar m Attribute_Definition: Internal variance in the Z-coordinate from post-processing. No data value is NaN. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.011 Range_Domain_Maximum: 0.432 Attribute_Units_of_Measure: millimeters Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_YSMP_LPC.laz Entity_Type_Definition: YSMP lidar point cloud in .laz file format from flights over the Clearview Landfill. This georeferenced point cloud was colorized using the natural color RGB orthomosaic and has classified ground points. Total point count is 107,844,173. The point density is 321.06 points per square meter, and point spacing is 0.056 m. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: Elevation Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using Geoid 18 in NAD83(2011)/UTM Zone 18N. Attribute_Definition_Source: YellowScan CloudStation Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.296 Range_Domain_Maximum: 32.182 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Intensity Attribute_Definition: Lidar intensity is recorded as the return strength of a laser beam during data collection. Attribute_Definition_Source: YellowScan CloudStation Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 65,025 Detailed_Description: Entity_Type: Entity_Type_Label: 2024006FA_Heinz_Henderson_Mar2024_YSMP_LPC.laz Entity_Type_Definition: YSMP lidar point cloud in .laz file format from the westernmost area of the John Heinz National Wildlife Refuge. This georeferenced point cloud was colorized using using the natural color RGB orthomosaic and has classified ground points. Total point count is 530,030,997. The point density is 490.68 points per square meter, and point spacing is 0.045 m. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: Elevation Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using Geoid 18 in NAD83(2011)/UTM Zone 18N. Attribute_Definition_Source: YellowScan CloudStation Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -1.332 Range_Domain_Maximum: 32.345 Attribute_Units_of_Measure: meters Attribute: Attribute_Label: Intensity Attribute_Definition: Lidar intensity is recorded as the return strength of a laser beam during data collection. Attribute_Definition_Source: YellowScan CloudStation Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 65,025 Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_aPT_Ortho_5cm_cog.tif Entity_Type_Definition: A cloud-optimized 5-band multispectral reflectance orthomosaic. Values can be greater than 1 due to oversaturation. Pixel resolution is 5 cm. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: Band_1 Attribute_Definition: Blue wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 1.382 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_2 Attribute_Definition: Green wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 2.150 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_3 Attribute_Definition: Red wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 1.790 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_4 Attribute_Definition: Rededge wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 2.893 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_5 Attribute_Definition: Near infra-red wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 3.387 Attribute_Units_of_Measure: none Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_SX10_Ortho_5cm_cog.tif Entity_Type_Definition: A cloud-optimized 4-band natural color and thermal infra-red orthomosaic. Values can be greater than 1 due to oversaturation. Pixel resolution is 5 cm. Entity_Type_Definition_Source: producer defined Attribute: Attribute_Label: Band_1 Attribute_Definition: Red wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_2 Attribute_Definition: Green wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_3 Attribute_Definition: Blue wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Attribute_Units_of_Measure: none Attribute: Attribute_Label: Band_4 Attribute_Definition: Thermal infra-red wavelength band Attribute_Definition_Source: Agisoft Metashape Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0 Range_Domain_Maximum: 255 Attribute_Units_of_Measure: none Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_YSMP_DSM_5cm_cog.tif Entity_Type_Definition: A cloud-optimized digital surface model gridded from the "2024020FA_Clearview_Aug2024_YSMP_LPC" lidar point cloud with encoded elevation values. Pixel resolution is 5 cm. Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: Value Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 18N. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.281 Range_Domain_Maximum: 34.997 Attribute_Units_of_Measure: meters Detailed_Description: Entity_Type: Entity_Type_Label: 2024020FA_Clearview_Aug2024_YSMP_DTM_5cm_cog.tif Entity_Type_Definition: A cloud-optimized digital surface model gridded from the "2024020FA_Clearview_Aug2024_YSMP_LPC" lidar point cloud ground classified points with encoded elevation values. Pixel resolution is 5 cm. Entity_Type_Definition_Source: USGS Attribute: Attribute_Label: Value Attribute_Definition: Surface elevation orthometric height NAVD88 (m) using Geoid 2018 in NAD83(2011) UTM Zone 18N. Attribute_Definition_Source: producer defined Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 0.296 Range_Domain_Maximum: 32.182 Attribute_Units_of_Measure: meters Overview_Description: Entity_and_Attribute_Overview: The filenames are formatted as "FAN_Location_MonthYear_Sensor_Product_Resolution_cog.*", where FAN is the USGS field activity number, location is the specific location the data represents; sensor includes the YellowScan Mapper Plus (YSMP), the DJI Zenmuse XT2 (XT2), the Spectra-Precision 80 RTK-GPS (SP80), and AeroPoints; products include structure from motion (SfM) orthomosaics (ortho), digital surface models (DSM), and lidar point cloud (LPC). The horizontal coordinate reference system for all products is NAD83(2011)/UTM18N, the vertical coordinate reference system (VCRS) is NAVD88 using Geoid 18. Image location coordinate reference systems are specific to the sensor and can be viewed in the image locations CSV files. Entity_and_Attribute_Detail_Citation: USGS Field Activity 2024-020-FA Distribution_Information: Distributor: Contact_Information: Contact_Organization_Primary: Contact_Organization: U.S. Geological Survey - ScienceBase Contact_Address: Address_Type: mailing and physical address Address: Denver Federal Center, Building 810, Mail Stop 302 City: Denver State_or_Province: CO Postal_Code: 80225 Contact_Voice_Telephone: 1-888-275-8747 Contact_Electronic_Mail_Address: sciencebase@usgs.gov Resource_Description: Aerial imaging and mapping of the Clearview Landfill within the Darby Creek Superfund Site includes one lidar point cloud, two elevation models, one natural color orthomosaics, one thermal infra-red orthomosaic, one multispectral reflectance orthomosaic, associated imagery, vegetation survey data, ground control and check points. Distribution_Liability: Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. Standard_Order_Process: Digital_Form: Digital_Transfer_Information: Format_Name: GeoTIFF Format_Version_Number: 1.0.0 Format_Specification: Cloud optimized GeoTIFF format Adobe deflate compressed Format_Information_Content: 2024020FA_Clearview_Aug2024_YSMP_DSM_5cm_cog.tif, and 2024020FA_Clearview_Aug2024_YSMP_DTM_5cm_cog.tif have encoded surface elevations. 2024020FA_Clearview_Aug2024_aPT_Ortho_5cm_cog.tif, and 2024020FA_Clearview_Aug2024_SX10_Ortho_5cm_cog.tif are orthomosaics. Transfer_Size: 5065 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67644a60d34e5335adadf390 Network_Resource_Name: https://doi.org/10.5066/P134HU3Y Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67644a60d34e5335adadf390 Access_Instructions: The first link in the list above is to the landing page where files can be downloaded individually and the second link is the doi redirect link to the data release landing page. The third link directly downloads all the data hosted on the ScienceBase page; however, due to the large total file size, this link does not currently work and is included in case it works in the future. Digital_Form: Digital_Transfer_Information: Format_Name: CSV Format_Version_Number: Exported from Excel Office 365 16.01 Format_Information_Content: 2024020FA_Clearview_Aug2024_AeroPoints.csv and 2024020FA_Clearview_Aug2024_SP80.csv contains ground control data and checkpoint data respectively. 2024020FA_ClearviewVegSurvey_Aug2024.csv contains data for the ground reference vegetation survey. 2024020FA_Clearview_Aug2024_aPT_ImageLocs.csv, 2024020FA_Clearview_Aug2024_SX10_ImageLocs.csv, 2024020FA_Clearview_Aug2024_YSMP_ImageLocs.csv, and 2024020FA_ClearviewVegSurvey_Aug2024_ImageLocs.csv contain a list of the Altum-PT, Skydio X10, YellowScan Mapper Plus and vegetation survey images and their positions. Transfer_Size: 1.46 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67644a60d34e5335adadf390 Network_Resource_Name: https://doi.org/10.5066/P134HU3Y Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67644a60d34e5335adadf390 Access_Instructions: The first link in the list above is to the landing page where files can be downloaded individually and the second link is the doi redirect link to the data release landing page. The third link directly downloads all the data hosted on the ScienceBase page; however, due to the large total file size, this link does not currently work and is included in case it works in the future. Digital_Form: Digital_Transfer_Information: Format_Name: JPEG Format_Version_Number: 1.0.0 Format_Information_Content: The natural color (RGB) and thermal infra-red (TIR) images from the YSMP camera module and Skydio X10, and the vegetation survey photos. Transfer_Size: 11617 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67644a60d34e5335adadf390 Network_Resource_Name: https://doi.org/10.5066/P13SHGV3 Network_Resource_Name: https://doi.org/10.5066/P134HU3Y Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67644a60d34e5335adadf390 Access_Instructions: The first link in the list above is to the child page where a link to the Imagery Data System landing page can be found, the second link is to the Imagery Data System landing page where the photos can be viewed and downloaded individually, the third link is the doi redirect link to the data release landing page. The fourth link directly downloads all the data hosted on the ScienceBase page; however, due to the large total file size, this link does not currently work and is included in case it works in the future. Transfer size refers to the total size of all images if downloaded from the IDS, images are not hosted on sciencebase. Digital_Form: Digital_Transfer_Information: Format_Name: LAZ Format_Version_Number: 1.4 Format_Information_Content: 2024020FA_Clearview_Aug2024_YSMP.laz is a LAZ (LAserZipped) files, an open file format intended for point data records. File_Decompression_Technique: Use laszip to decompress Transfer_Size: 1339 Digital_Transfer_Option: Online_Option: Computer_Contact_Information: Network_Address: Network_Resource_Name: https://www.sciencebase.gov/catalog/item/67644a60d34e5335adadf390 Network_Resource_Name: https://doi.org/10.5066/P134HU3Y Network_Resource_Name: https://www.sciencebase.gov/catalog/file/get/67644a60d34e5335adadf390 Access_Instructions: The first link in the list above is to the landing page where files can be downloaded individually and the second link is the doi redirect link to the data release landing page. The third link directly downloads all the data hosted on the ScienceBase page; however, due to the large total file size, this link does not currently work and is included in case it works in the future. Fees: None. Metadata_Reference_Information: Metadata_Date: 20250710 Metadata_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jennifer M. Cramer Contact_Organization: U.S. Geological Survey, Northeast Region Contact_Position: Geographer Contact_Address: Address_Type: mailing and physical Address: U.S. Geological Survey Address: 384 Woods Hole Rd. City: Woods Hole State_or_Province: MA Postal_Code: 02543-1598 Contact_Voice_Telephone: 508-548-8700 x2314 Contact_Electronic_Mail_Address: whsc_data_contact@usgs.gov Contact_Instructions: The metadata contact email address is a generic address in the event the person is no longer with USGS. Metadata_Standard_Name: Content Standard for Digital Geospatial Metadata Metadata_Standard_Version: FGDC-STD-001-1998 Metadata_Access_Constraints: None Metadata_Use_Constraints: None