Coastal Topography—Assateague Island, Maryland and Virginia, Post-Hurricane Joaquin, 26 November 2015

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

Frequently anticipated questions:


What does this data set describe?

Title:
Coastal Topography—Assateague Island, Maryland and Virginia, Post-Hurricane Joaquin, 26 November 2015
Abstract:
Binary point-cloud data were produced for Assateague Island, Maryland and Virginia, post-Hurricane Joaquin, from remotely sensed, geographically referenced elevation measurements collected by Quantum Spatial using a Leica ALS70 (1064-nm wavelength) lidar sensor.
Supplemental_Information:
Processed data products are used by the U.S. Geological Survey (USGS) CMGP's National Assessment 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, 20160506, Coastal Topography—Assateague Island, Maryland and Virginia, Post-Hurricane Joaquin, 26 November 2015: U.S. Geological Survey Data Release doi:10.5066/F70P0X4G, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -75.42950193
    East_Bounding_Coordinate: -75.07387345
    North_Bounding_Coordinate: 38.33961735
    South_Bounding_Coordinate: 37.83866023
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 26-Nov-2015
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: binary point cloud
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference: Tile
      This is a Point data set.
    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 coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.01
      Ordinates (y-coordinates) are specified to the nearest 0.01
      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 (GEOID12B)
      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?

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 periods may be inaccurate because of 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?
    Xan Fredericks
    Cherokee Nation Technologies, U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL
    Lidar Validation and Processing Analyst
    600 4th Street South
    St. Petersburg, FL
    USA

    727 502-8086 (voice)
    727 502-8182 (FAX)
    afredericks@usgs.gov
    Hours_of_Service: M-F, 8:00-4:00 ET

Why was the data set created?

The purpose of this project was to produce a highly detailed and accurate digital elevation map for Assateague Island, Maryland and Virginia for use as a management tool and to make these data available to natural-resource managers and research scientists. To ensure that SPCMSC data management protocols were followed, this survey was assigned a USGS field activity number (FAN), 2015-344-FA. Additional survey and data details are available at http://cmgds.marine.usgs.gov/fan_info.php?fan=2015-344-FA. USGS Contract: G10PC00026 Task Order Number: G16PD00038

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: 2015 (process 1 of 2)
    Classified LAS Creation: The bare-earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the lake/pond and double-line drain hydro-flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to ignored ground (ASPRS Class 10). All lake/pond island and double-line drain island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All bridge decks were classified to Class 17. All overlap data were processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data were identified using the Overlap Flag, per LAS 1.4 specifications. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the unclassified point-cloud data and the bare-earth data. Quantum Spatial proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per-tile level to verify final classification metrics and full LAS header information. Person who carried out this activity:
    Quantum Spatial
    523 Wellington Way
    Lexington, KY
    USA

    859-277-8700 (voice)
    859-277-8901 (FAX)
    Hours_of_Service: Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)
    Data sources produced in this process:
    • Classified LAS
    Date: 04-Jan-2017 (process 2 of 2)
    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
  3. What similar or related data should the user be aware of?

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

  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
    Quantum Spatial reports that the contract specifications required that only Nonvegetated Vertical Accuracy (NVA) were computed for raw lidar point cloud swath files. The vertical accuracy was tested with 13 independent surveys located in open terrain. These check points were not used in the calibration or post-processing of the lidar point cloud data. The survey check points were distributed throughout the project area. The independent check points were surveyed using the closed level loop technique. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.042. AccuracyZ has been tested as 0.082 meters AccuracyZ at 95 percent Confidence Interval, meeting 19.6 cm NVA at 95 percent confidence level using (RMSEz * 1.9600) as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/American Society of Photogrammetry and Remote Sensing (ASPRS) Guidelines.
  4. Where are the gaps in the data? What is missing?
    Quantum Spatial reports that these raw LAS data files include all data points collected and that no points have been removed or excluded. Quantum Spatial performed a visual qualitative assessment to ensure data completeness and reported no void areas or missing data exist. Quantum Spatial reports that the raw point cloud is of good quality and data passes Nonvegetated Vertical Accuracy specifications.
  5. How consistent are the relationships among the observations, including topology?
    Quantum Spatial reports that data cover the entire area specified for this project.

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. The U.S. Geological Survey requests to be acknowledged as 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: Xan Fredericks
    Lidar Validation and Processing Analyst, Cherokee Nation Technologies
    600 4th Street South
    St. Petersburg, FL
    USA

    727 502-8086 (voice)
    Hours_of_Service: M-F, 8:00-4:00 ET
  2. What's the catalog number I need to order this data set? ASIS2015_HRJQ_BE_z18_n88g12B_classified.laz
  3. What legal disclaimers am I supposed to read?
    Although these data have been processed successfully on a computer system at the USGS, 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 USGS shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product 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?
  5. Is there some other way to get the data?
    Contact U.S. Geological Survey for details.

Who wrote the metadata?

Dates:
Last modified: 27-Jul-2017
Metadata author:
Xan Fredericks
Cherokee Nation Technology Solutions, U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL
Lidar Validation and Processing Analyst
600 4th Street South
St. Petersburg, FL
USA

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

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/ASIS2015_HRJQ_BE_z18_n88g12B_classified_metadata.faq.html>
Generated by mp version 2.9.49 on Fri Sep 13 15:01:25 2019