Beach Topography—Fire Island, New York, Post-Hurricane Sandy, April 2014: Ground Based Lidar (ASCII XYZ Point Data)

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Beach Topography—Fire Island, New York, Post-Hurricane Sandy, April 2014: Ground Based Lidar (ASCII XYZ Point Data)
Abstract:
The U.S. Geological Survey St. Petersburg Coastal and Marine Science Center (USGS-SPCMSC) and the U.S. Army Corps of Engineers Field Research Facility (USACE-FRF) of Duck, NC collaborated to gather alongshore ground-based lidar beach topography at Fire Island, NY. This high-resolution elevation dataset was collected on April 1, 2014, and is part of the USGS's ongoing beach monitoring effort under Hurricane Sandy Supplemental Project GS2-2B. This USGS Data Release includes the resulting processed elevation point data (xyz) and an interpolated digital elevation model (DEM).
  1. How might this data set be cited?
    U.S. Geological Survey, 2015, Beach Topography—Fire Island, New York, Post-Hurricane Sandy, April 2014: Ground Based Lidar (ASCII XYZ Point Data): U.S. Geological Survey Data Release doi:10.5066/F77H1GNN, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

    This is part of the following larger work.

    Brenner, Owen, Hapke, Cheryl J., Spore, Nick J., Brodie, Katherine L., and McNinch, Jesse E., 20150909, Ground-based lidar beach topography of Fire Island, New York, April 2014: U.S. Geological Survey Data Release doi:10.5066/F77H1GNN, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -73.262161363
    East_Bounding_Coordinate: -72.899671378
    North_Bounding_Coordinate: 40.728972747
    South_Bounding_Coordinate: 40.615961807
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 10-Apr-2014
    Currentness_Reference:
    ground elevation
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Tabular digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a point data set. It contains the following vector data types (SDTS terminology):
      • Point (8,304,337)
    2. What coordinate system is used to represent geographic features?
      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 coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 1.000000
      Ordinates (y-coordinates) are specified to the nearest 1.000000
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum 1983.
      The ellipsoid used is Geodectic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222101.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum 1988
      Altitude_Resolution: 0.0001 cm
      Altitude_Distance_Units: meter
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    20140401_CLARIS_xyz.txt
    Comma delimited xyz file (Source: U.S. Geological Survey)
    POINT_X
    UTM x-axis coordinate (Zone 18N) (Source: U.S. Geologocial Survey)
    Range of values
    Minimum:646990.3192
    Maximum:677384.1057
    Units:Meter
    POINT_Y
    UTM y-axis coordinate (Zone 18N) (Source: U.S. Geological Survey)
    Range of values
    Minimum:4498240.2469
    Maximum:4510128.0593
    Units:Meter
    POINT_Z
    z-value (elevation) in NAVD88 (Source: U.S. Geological Survey)
    Range of values
    Minimum:-3.695
    Maximum:15.496
    Units:meters
    Entity_and_Attribute_Overview:
    Comma delimited xyz file containing UTM X, UTM Y locations and corresponding Z elevation value, all in meters.
    Entity_and_Attribute_Detail_Citation:
    Beach topography point data for Fire Island, NY, created from data collected during a ground-based lidar survey conducted on April 1, 2014. After post-processing, the lidar point cloud was reprojected within ArcCatalog 10.1 into NAD83 UTM zone 18N and corresponding vertical value is in NAVD88.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: Cheryl J. Hapke
    600 4th Street South
    St Petersburg, FL
    USA

    727-502-8068 (voice)
    727-502-8001 (FAX)
    chapke@usgs.gov

Why was the data set created?

To collect, process, and disseminate beach topography along 30 kilometers (km) of Fire Island, NY beach, stretching from Robert Moses State Park to the Wilderness Breach. The USACE-FRF team acquired and performed initial processing of the high-resolution lidar data, which is only one component of a larger dataset collected using the CLARIS platform. To ensure that SPCMSC data management protocols were followed, this survey was retroactively assigned a USGS field activity number (FAN), 14CNT02. Additional survey details are available at http://cmgds.marine.usgs.gov/fan_info.php?fan=14CNT02.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 2014 (process 1 of 9)
    USACE-FRF Processing - Data for the survey extents was collected along with a boresight to resolve subtle differences between the scanner and the Inertial Measurement Unit (IMU). After collection, the data was post-processed using multiple software packages to produce the final digital elevation model product. Person who carried out this activity:
    U.S. Army Corps of Engineers: Engineer Research and Development Center (ERDC) - Coastal Hydraulics Laboratory (CHL) - Coastal Observation and Analysis Branch (COAB)
    Attn: Nick Spore
    Research Civil Engineer
    USACE-CEERD-HF-A, Field Research Facility
    Kitty Hawk, NC
    USA

    252-261-6840 ext: 231 (voice)
    252-261-4432 (FAX)
    nicholas.j.spore@usace.army.mil
    Contact_Instructions: http://www.frf.usace.army.mil
    Date: 2014 (process 2 of 9)
    Terrestrial GPS data was post-processed with National Geodetic Survey's Continuously Operating Reference Stations (CORS) and integrated with post-processed IMU data through Applanix's POSPac GNSS software to derive a smoothed, best estimate of trajectory (SBET). After processing, quantitative quality-metrics were analyzed to ensure the trajectory accuracy met the manufacturer's specified values. Person who carried out this activity:
    U.S. Army Corps of Engineers: Engineer Research and Development Center (ERDC) - Coastal Hydraulics Laboratory (CHL) - Coastal Observation and Analysis Branch (COAB)
    Attn: Nick Spore
    Research Civil Engineer
    USACE-CEERD-HF-A, Field Research Facility
    Kitty Hawk, NC
    USA

    252-261-6840 ext: 231 (voice)
    252-261-4432 (FAX)
    nicholas.j.spore@usace.army.mil
    Contact_Instructions: http://www.frf.usace.army.mil
    Date: 2014 (process 3 of 9)
    The SBET was imported into Riegl's RiProcess lidar software project where the lidar point cloud was rectified and geo-registered to a particular coordinate system, projection, and geoid model as well as applying boresight values for roll, pitch and yaw. Control monuments and previously validated datasets were used for comparison, to determine the accuracy of the survey. These were measured by cutting cross-sections of the current survey overlayed on previously validated data within the software through stable structures such as houses, monuments, and road centerlines. Person who carried out this activity:
    U.S. Army Corps of Engineers: Engineer Research and Development Center (ERDC) - Coastal Hydraulics Laboratory (CHL) - Coastal Observation and Analysis Branch (COAB)
    Attn: Nick Spore
    Research Civil Engineer
    USACE-CEERD-HF-A, Field Research Facility
    Kitty Hawk, NC
    USA

    252-261-6840 ext: 231 (voice)
    252-261-4432 (FAX)
    nicholas.j.spore@usace.army.mil
    Contact_Instructions: http://www.frf.usace.army.mil
    Date: 2014 (process 4 of 9)
    The processed point cloud was manipulated within RiProcess to delineate the shoreline, filter structures and vegetation, and classify points as water, vegetation, structures, and ground. The classified point cloud was exported as a .las (1.1) file. Person who carried out this activity:
    U.S. Army Corps of Engineers: Engineer Research and Development Center (ERDC) - Coastal Hydraulics Laboratory (CHL) - Coastal Observation and Analysis Branch (COAB)
    Attn: Nick Spore
    Research Civil Engineer
    USACE-CEERD-HF-A, Field Research Facility
    Kitty Hawk, NC
    USA

    252-261-6840 ext: 231 (voice)
    252-261-4432 (FAX)
    nicholas.j.spore@usace.army.mil
    Contact_Instructions: http://www.frf.usace.army.mil
    Date: 2014 (process 5 of 9)
    The .las file was imported into Applied Imagery's QTModeler software where a mean-z (elevation) algorithm was applied to the point cloud data to grid the data at 0.5-meter resolution. Anti-aliasing was also applied to increase the precision of the triangulation by subdividing each grid cell into 16 equal segments and recording which segment contained the point that was used to represent the elevation value of the grid cell. When triangulation occurs, this increased level of precision will enhance the accuracy of the triangles and the subsequent sampling that occurs. The sub-grid was not retained after the model was created. During the model triangulation, any grid cells with no data were assigned a value of "null" - i.e., no data exists. Person who carried out this activity:
    U.S. Army Corps of Engineers: Engineer Research and Development Center (ERDC) - Coastal Hydraulics Laboratory (CHL) - Coastal Observation and Analysis Branch (COAB)
    Attn: Nick Spore
    Research Civil Engineer
    USACE-CEERD-HF-A, Field Research Facility
    Kitty Hawk, NC
    USA

    252-261-6840 ext: 231 (voice)
    252-261-4432 (FAX)
    nicholas.j.spore@usace.army.mil
    Contact_Instructions: http://www.frf.usace.army.mil
    Date: 2014 (process 6 of 9)
    After gridding was completed, the raster digital elevation model (surface) was inspected for any remaining noise such as spikes and wells and these were removed prior to final export as an ASCII .xyz file. Person who carried out this activity:
    U.S. Army Corps of Engineers: Engineer Research and Development Center (ERDC) - Coastal Hydraulics Laboratory (CHL) - Coastal Observation and Analysis Branch (COAB)
    Attn: Nick Spore
    Research Civil Engineer
    USACE-CEERD-HF-A, Field Research Facility
    Kitty Hawk, NC
    USA

    252-261-6840 ext: 231 (voice)
    252-261-4432 (FAX)
    nicholas.j.spore@usace.army.mil
    Contact_Instructions: http://www.frf.usace.army.mil
    Date: 2014 (process 7 of 9)
    SPCMSC Processing - The ASCII xyz file was converted to an ArcGIS multipoint feature using the 'ASCII 3D To Feature Class' tool within ArcCatalog 10.1. Output feature class was reprojected from the State Plane Coordinate System (NY, Long Island Zone) to NAD83 UTM Zone 18N. Using the 'Feature Class Z To ASCII' tool the point data was reverted back to ASCII xyz format for publication, in a non-proprietary format. Person who carried out this activity:
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: Owen Brenner
    Geologist
    600 4th Street South
    St. Petersburg, FL
    U.S.

    727-502-8085 (voice)
    727-502-8001 (FAX)
    obrenner@usgs.gov
    Date: 24-Jan-2017 (process 8 of 9)
    Keywords section of metadata optimized for discovery in USGS Coastal and Marine Geology Data Catalog. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Alan O. Allwardt
    Contractor -- Information Specialist
    2885 Mission Street
    Santa Cruz, CA

    831-460-7551 (voice)
    831-427-4748 (FAX)
    aallwardt@usgs.gov
    Date: 13-Oct-2020 (process 9 of 9)
    Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
  3. What similar or related data should the user be aware of?
    Brenner, Owen, Hapke, Cheryl J., Spore, Nick, Brodie, Katherine L., and McNinch, Jesse E., 2015, Ground-based lidar beach topography of Fire Island, New York, April 2013: U.S. Geological Survey Data Series DS 921, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Areas of data overlap were initially compared against each other to measure repeatability. Depending on distance from the base station (Ashtech Z-Xtreme GPS reciever at temporary benchmark at U.S. Coast Guard: Fire Island) the accuracy of the scans varied from 5 to 15 centimeters (cm). The fixed structures (i.e. houses, rooflines, decks) were used to measure repeatability and the base station benchmark was used to measure accuracy. Previous airborne lidar from a 2011-2012 National Ocean and Atmospheric Administration (NOAA)/New York State Department of Environmental Conservation (NYSDEC) survey was also used as an alternative fixed structure comparison. Repeatability: 5-15 cm Accuracy: 5-10 cm
  2. How accurate are the geographic locations?
    10 cm
  3. How accurate are the heights or depths?
    10 cm
  4. Where are the gaps in the data? What is missing?
    This dataset is considered complete for the information presented, as described in the abstract section. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    Lidar beach morphology data were collected by the U.S. Army Corps of Engineers' (USACE) Coastal Lidar and Radar Imaging System (CLARIS) vehicle on April 1, 2014. This survey utilized the same equipment set up and follows the same procedure as an identical survey which occurred on April 10, 2013 (2015 USGS Data Series 921). The survey vehicle traveled approximately 5 kilometers per hour (km/h) along two 30 km shore parallel transits; the first transit surveyed the seaward side of the dune and upper beach while the second transit surveyed the area near the shoreline and lower beach. The survey was designed to provide a significant overlap area of data coverage which is used to verify system accuracy and assess survey precision.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None
Use_Constraints:
Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey, St Petersburg Coastal and Marine Science Center as the originator of these data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey, St Petersburg Coastal and Marine Science Center, St. Petersburg, FL
    Attn: Cheryl J. Hapke
    600 4th Street South
    St. Petersburg, FL
    USA

    727-502-8068 (voice)
    727-502-8001 (FAX)
  2. What's the catalog number I need to order this data set? U.S. Geological Survey DS XXX
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 22-Sep-2021
Metadata author:
U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
Attn: Owen Brenner
Geologist
600 4th Street South
St. Petersburg, Florida
U.S.

727-502-8085 (voice)
727-502-8001 (FAX)
obrenner@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/20140401_CLARIS_metadata_xyz.faq.html>
Generated by mp version 2.9.50 on Wed Sep 22 17:19:07 2021