EAARL Coastal Topography--Virginia, Post-Nor'Ida, 2009

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

Frequently anticipated questions:


What does this data set describe?

Title: EAARL Coastal Topography--Virginia, Post-Nor'Ida, 2009
Abstract:
A digital elevation model (DEM) of a portion of the Virginia coastline beachface, post-Nor'Ida (November 2009 nor'easter), was produced from remotely sensed, geographically referenced elevation measurements by the U.S. Geological Survey (USGS). Elevation measurements were collected over the area using the Experimental Advanced Airborne Research Lidar (EAARL), a pulsed laser ranging system mounted onboard an aircraft to measure ground elevation, vegetation canopy, and coastal topography. The EAARL sensor suite includes the raster-scanning, water-penetrating full-waveform adaptive lidar, a down-looking red-green-blue (RGB) digital camera, a high-resolution multispectral color-infrared (CIR) camera, two precision dual frequency kinematic carrier-phase GPS receivers, and an integrated miniature digital inertial measurement unit, which provide for sub-meter georeferencing of each laser sample. The system uses high-frequency laser beams directed at the Earth's surface through an opening in the bottom of the aircraft's fuselage. The laser system records the time difference between emission of the laser beam and the reception of the reflected laser signal in the aircraft. The plane travels over the target area at approximately 50 meters per second at an elevation of approximately 300 meters, resulting in a laser swath of approximately 240 meters with an average point spacing of 2-3 meters. The EAARL, developed originally by the National Aeronautics and Space Administration (NASA) at Wallops Flight Facility in Virginia, measures ground elevation with a vertical resolution of +/-15 centimeters. A sampling rate of 3 kilohertz or higher results in an extremely dense spatial elevation dataset. Over 100 kilometers of coastline can be surveyed easily within a 3- to 4-hour mission. When resultant elevation maps for an area are analyzed, they provide a useful tool to make management decisions regarding land development.
Supplemental_Information:
Raw lidar data are not in a format that is generally usable by resource managers and scientists for scientific analysis. Converting dense lidar elevation data into a readily usable format without loss of essential information requires specialized processing. The U.S. Geological Survey's Coastal and Marine Geology Program (CMGP) has developed custom software to convert raw lidar data into a GIS-compatible map product to be provided to GIS specialists, managers, and scientists. The primary tool used in the conversion process is Airborne Lidar Processing System (ALPS), a multi-tiered processing system developed by a USGS-NASA collaborative project. Specialized processing algorithms are used to convert raw waveform lidar data acquired by the EAARL to georeferenced spot (x,y,z) returns for "first surface" and "bare earth" topography. The terms first surface and bare earth refer to the digital elevation data of the terrain, but while the first-surface data include vegetation, buildings, and other manmade structures, the bare-earth data do not. The zero crossing of the second derivative (that is, detection of stationary points) is used to detect the first return, resulting in "first surface" topography, while the trailing edge algorithm (that is, the algorithm searches for the location prior to the last return where direction changes along the trailing edge) is used to detect the range to the last return, or "bare earth" (the first and last returns being the first and last significant measurable portion of the return pulse). Statistical filtering, known as the Random Consensus Filter (RCF), is used to remove false bottom returns and other outliers from the EAARL topography data. The filter uses a grid of non-overlapping square cells (buffer) of user-defined size overlaid onto the original point cloud. The user also defines the vertical tolerance (vertical width) based on the topographic complexity and point-sampling density of the data. The maximum allowable elevation range within a cell is established by this vertical tolerance. An iterative process searches for the maximum concentration of points within the vertical tolerance and removes those points outside of the tolerance (Nayegandhi and others, 2009). These data are then converted to the North American Datum of 1983 and the North American Vertical Datum of 1988 (using the GEOID09 model). Each file contains data located in a 2-kilometer by 2-kilometer tile, where the upper-left bound can be assessed quickly through the filename. The first 3 numbers in the filename represent the left-most UTM easting coordinate (e###000) in meters, the next 4 numbers represent the top-most UTM northing coordinate (n####000) in meters, and the last 2 numbers (##) represent the UTM zone in which the tile is located (for example, fs_e123_n4567_18).The development of custom software for creating these data products has been supported by the U.S. Geological Survey CMGP's Decision Support for Coastal Science and Management project. Processed data products are used by the U.S. Geological Survey CMGP's National Assessments of Coastal Change Hazards project to quantify the vulnerability of shorelines to coastal change hazards such as severe storms, sea-level rise, and shoreline erosion and retreat.
  1. How might this data set be cited?
    U.S. Geological Survey, 2011, EAARL Coastal Topography--Virginia, Post-Nor'Ida, 2009: U.S. Geological Survey Data Series 638, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -76.0331
    East_Bounding_Coordinate: -75.4547
    North_Bounding_Coordinate: 37.8746
    South_Bounding_Coordinate: 36.5382
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 27-Nov-2009
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: remote-sensing image
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference: Tiling Index
      This is a Raster data set. It contains the following raster data types:
      • Dimensions 2001 x 2001 x 1, type Pixel
    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
      False_Easting: 500000.000000
      False_Northing: 0
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 2
      Ordinates (y-coordinates) are specified to the nearest 2
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.25722210100002.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: 0.15
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    Each pixel of the encoded GeoTIFF has an explicit elevation value associated with it. The GeoTIFF grid is encoded with the interpolated elevation value at a 2.5-meter resolution. The input parameters for the random consensus filter (RCF) were grid cell size (buffer) = 6 meters x 6 meters; vertical tolerance (vertical width) = 500 centimeters for first surface and 50 centimeters for bare earth. The GeoTIFFs are created using Delauney triangulation, followed by linear interpolation based on routines in the ITT VIS Interactive Data Language (IDL) code.
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/of/2009/1078/

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?
    Acknowledgment of the U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, as a data source would be appreciated in products developed from these data, and such acknowledgment as is standard for citation and legal practices for data source is expected. Sharing of new data layers developed directly from these data would also be appreciated by the U.S. Geological Survey staff. Users should be aware that comparisons with other datasets for the same area from other time periods may be inaccurate due to inconsistencies resulting from changes in photointerpretation, mapping conventions, and digital processes over time. These data are not legal documents and are not to be used as such.
  3. To whom should users address questions about the data?
    Jamie M. Bonisteel-Cormier
    Jacobs Technology, U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL
    Lidar Analyst
    600 4th Street South
    St. Petersburg, FL
    USA

    727 803-8747 (x3124) (voice)
    727 803-2031 (FAX)
    jcormier@usgs.gov
    Hours_of_Service: M-F, 8:00-4:00 EST

Why was the data set created?

The purpose of this project was to produce highly detailed and accurate digital elevation maps of a portion of the coastline beachface in Virginia, post-Nor'Ida (November 2009 nor'easter), for use as a management tool and to make these data available to natural-resource managers and research scientists.

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: 26-Oct-2010 (process 1 of 4)
    The data were collected using a Pilatus PC-6 aircraft. The Experimental Advanced Airborne Research Lidar (EAARL) laser scanner collects the data using a green-wavelength (532-nanometer) raster scanning laser, while a digital camera acquires a visual record of the flight. The data are stored on hard drives and archived at the U.S. Geological Survey office in St. Petersburg, Florida. The navigational data are processed and, along with the raw data, are then downloaded into ALPS, or the Airborne Lidar Processing System (20091128 - 20101026). Data are converted from units of time to x,y,z points for elevation and formatted into .las and .xyz files. The derived surface data can then also be converted into raster data (GeoTIFFs). Person who carried out this activity:
    Jamie M. Bonisteel-Cormier
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL
    Lidar Analyst
    600 4th Street South
    St. Petersburg, FL
    USA

    727 803-8747 (x3124) (voice)
    jcormier@usgs.gov
    Hours_of_Service: M-F, 8:00-4:00 EST
    Date: 27-Jun-2011 (process 2 of 4)
    Metadata imported into ArcCatalog from XML file. Person who carried out this activity:
    Emily Klipp
    Jacobs Technology, U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL
    Data Analyst
    600 4th Street South
    St. Petersburg, FL
    USA

    727 803-8747 (x3089) (voice)
    eklipp@usgs.gov
    Hours_of_Service: M-F, 8:00-4:00 EST
    Date: 24-Jan-2017 (process 3 of 4)
    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 4 of 4)
    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?
    Nayegandhi, A., Brock, J.C., and Wright, C.W., 2009, Small footprint, waveform-resolving lidar estimation of submerged and subcanopy topography in coastal environments: International Journal of Remote Sensing 30(4), p. 861-878.


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

  1. How well have the observations been checked?
    The expected accuracy of the measured variables is as follows: attitude within 0.07 degree, 3 centimeters nominal ranging accuracy, and vertical elevation accuracy of +/-15 centimeters for the topographic surface. Quality checks are built into the data-processing software.
  2. How accurate are the geographic locations?
    Raw elevation measurements have been determined to be within 1 meter in horizontal accuracy.
  3. How accurate are the heights or depths?
    Typical vertical elevation accuracies for these data are consistent with the point elevation data, +/-15 centimeters. However, a ground-control survey is not conducted simultaneously with every lidar survey. Vertical accuracies may vary based on the type of terrain and the accuracy of the GPS and aircraft-attitude measurements.
  4. Where are the gaps in the data? What is missing?
    Several regions of the dataset are labeled as "No Data," which corresponds to a cell value of -32767 meters in the GeoTIFF file. These "No Data" areas are a result of the survey not covering a particular region, optical water depth of greater than 1.5 Secchi disc depths, or the manual removal of lidar processing artifacts. This metadata file is generalized; each data file on this DVD has its own corresponding metadata file.
  5. How consistent are the relationships among the observations, including topology?
    Each file contains data located in a 2-kilometer by 2-kilometer tile where the upper-left bound can be assessed quickly through the filename. The first 3 numbers in the filename represent the left-most UTM easting coordinate (e###000) in meters, the next 4 numbers represent the top-most UTM northing coordinate (n####000) in meters, and the last 2 numbers (##) represent the UTM zone in which the tile is located (for example, fs_e123_n4567_18).

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:
The U.S. Geological Survey requests to be acknowledged 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
    Attn: Jamie M. Bonisteel-Cormier
    Lidar Analyst
    600 4th Street South
    St. Petersburg, FL
    USA

    727 803-8747 (x3124) (voice)
    Hours_of_Service: M-F, 8:00-4:00 EST
  2. What's the catalog number I need to order this data set? DS 638
  3. What legal disclaimers am I supposed to read?
    This DVD publication was prepared by an agency of the United States Government. Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the display or utility of the data on any other system, or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and (or) contained herein. Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, expressed 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.
  4. How can I download or order the data?
  5. Is there some other way to get the data?
    Contact U.S. Geological Survey for details.

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2020
Metadata author:
Emily Klipp
Jacobs Technology, U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL
Data Analyst
600 4th Street South
St. Petersburg, FL
USA

727 803-8747 (x3089) (voice)
eklipp@usgs.gov
Hours_of_Service: M-F, 8:00-4:00 EST
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/ds-638metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:54 2021