EAARL Topography-Cape Cod National Seashore

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

Frequently anticipated questions:


What does this data set describe?

Title: EAARL Topography-Cape Cod National Seashore
Abstract:
Elevation maps (also known as Digital Elevation Models or DEMs) of Cape Cod National Seashore were produced from remotely-sensed, geographically-referenced elevation measurements in cooperation with NASA and NPS. Point data in ascii text files were interpolated in a GIS to create a grid or digital elevation model (DEM) of each beach surface. Elevation measurements were collected in Massachusetts, over Cape Cod National Seashore using the NASA Experimental Advanced Airborne Research LiDAR (EAARL), a pulsed laser ranging system mounted onboard an aircraft to measure ground elevation and coastal topography. 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 beach at approximately 60 meters per second while surveying from the low-water line to the landward base of the sand dunes. The EAARL, developed by the National Aeronautics and Space Administration (NASA) located at Wallops Flight Facility in Virginia, measures ground elevation with a vertical resolution of 15 centimeters. A sampling rate of 3 kHz or higher results in an extremely dense spatial elevation data set. Over 100 kilometers of coastline can be easily surveyed within a 3- to 4-hour mission time period. The ability to sample large areas rapidly and accurately is especially useful in morphologically dynamic areas such as barrier beaches. Quick assessment of topographic change can be made following storms comparing measurements against baseline data. When subsequent elevation maps for an area are analyzed, they provide a useful tool to make management decisions regarding coastal development.
For more information on Lidar science and the Experimental Advanced Airborne Research Lidar (EAARL) system and surveys, see http://ngom.usgs.gov/dsp/overview/index.php and http://ngom.usgs.gov/dsp/tech/eaarl/index.php .
Supplemental_Information:
Raw Lidar data is not in a format that is generally usable by National Park Service 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 USGS converts raw Lidar data into a GIS-compatible map product to be provided to Park Service GIS specialists, managers, and scientists. The primary tool used in the conversion process is Airborne Lidar Processing System (ALPS), a multitiered processing system developed by a USGS/NASA collaborative for the use of topographic Lidar in coastal change assessment. 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. These data are then converted to the NAD83 horizontal and NAVD88 vertical datum (using the Geoid 99 model). The final products are 2x2-km map tiles written out in a standard geotiff format with associated metadata information. These tiles are created for visual interpretation and regional quantitative analysis. Metadata files include the standard FGDC format.
  1. How might this data set be cited?
    U.S. Geological Survey, 2007, EAARL Topography-Cape Cod National Seashore: Open File Report 2007-1375, USGS, St. Petersburg, FL.

    Online Links:

    Other_Citation_Details:
    The United States Geological Survey, FISC St. Petersburg, in cooperation with the National Park Service (NPS) and the National Aeronautics and Space Administration (NASA), is to provide the coastal management community with usable, useful digital elevation products. The USGS processes aircraft lidar data (provided by NASA), develops software tools and algorithms to use and analyze the data and make products available to the coastal management community through a variety of media, including the internet, CD-ROMs, DVDs and data reports.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -80.205183
    East_Bounding_Coordinate: -80.104639
    North_Bounding_Coordinate: 25.4769585
    South_Bounding_Coordinate: 25.313834
  3. What does it look like?
    http://pubs.usgs.gov/of/2007/1375/HTML/images/CACO_Tile_inset2.gif (GIF)
    EAARL Topography - Cape Cod National Seashore
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 04-May-2005
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Raster data set. It contains the following raster data types:
      • Dimensions 2000 x 2000 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: 19
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -69.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 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.257222.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: .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:
    The attributes measured are as follows: variables measured by EAARL - distance between aircraft and GPS satellites (m), attitude information (roll, pitch, heading in degrees), scan angle (degrees), second of the epoch (sec), 1-ns time-resolved return intensity waveform (digital counts), and co-registered digital aerial photography. For derived variables, WGS84, NAD83 or other UTM eastings and northings (m), NAVD88 elevations (m), and peak amplitude (intensity). For derived surfaces, bare-earth elevations, and first-return elevations.
    Entity_and_Attribute_Detail_Citation:
    This Digital Elevation Model is a Geotiff derived from point data referenced to WGS84, NAD83 UTM eastings and northings (m). The variables measured by EAARL are: distance between aircraft and GPS satellites (m), attitude information (roll, pitch, heading in degrees), scan angle (degrees), second of the epoch (sec), and 1-ns time-resolved return intensity waveform (digital counts). It is raster data consisting of cells. Each cell has an elevation value associated with it. Cell size is 1 meter by 1 meter.

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?
    The USGS FISC St. Petersburg office, would like to acknowledge NASA Goddard Space Flight Center and the National Park Service for their cooperation and assistance in the development of the data. The USGS would also like to acknowledge park management and personnel at Cape Cod National Seashore.
  3. To whom should users address questions about the data?
    United States Geological Survey, FISC St. Petersburg
    Attn: Dr. John C. Brock
    Physical Oceanographer
    600 4th Street South
    St. Petersburg, FL
    USA

    727 803-8747 ext3088 (voice)
    727 803-2031 (FAX)
    jbrock@usgs.gov
    Hours_of_Service: Monday-Friday, 8-5, EST

Why was the data set created?

One goal of the project is to produce highly detailed and accurate digital elevation maps of National Seashores and coastal parks for use as a management tool and to make these maps available to natural resource managers within the parks.

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: 04-May-2005 (process 1 of 5)
    The data are collected using a Cessna 310 aircraft. The NASA Experimental Advanced Airborne Research Lidar (EAARL) laser scanner collects the data using a green (532nm) 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 USGS FISC St. Petersburg office and the NASA Wallops office. The navigational data are processed at Wallops. The navigational and raw data are then downloaded into the Airborne Lidar Processing System (ALPS). Data are converted from units of time to x,y,z points for elevation. The derived surface data can then be converted into raster data (geotiffs). Person who carried out this activity:
    United States Geological Survey, FISC St. Petersburg
    Attn: Amar Nayegandhi
    Computer Scientist
    600 4th Street South
    St. Petersburg, FL
    USA

    727-803-8747 (voice)
    Hours_of_Service: 8:00am to 5:00pm Monday thru Friday, EST
    Contact_Instructions: Call Survey for Details
    Date: 01-Jan-2007 (process 2 of 5)
    The raster dataset was opened in ERDAS IMAGINE for editing. An Area of Interest (AOI) polygon was drawn around regions of poor data quality. Poor data quality was determined visually by locating gaps in the data as well as artifacts (e.g. spikes, large facets) of the Lidar processing. Pixels within the AOI polygons were given a raster value of -100 to correspond with the classification of 'No Data' Person who carried out this activity:
    United States Geological Survey, FISC St. Petersburg
    600 4th Street South
    St. Petersburg, FL
    USA

    727-803-8747 (voice)
    Hours_of_Service: 8:30-5:00 M-F EST
    Date: 01-May-2007 (process 3 of 5)
    Metadata imported into ArcCatalog from XML file. Person who carried out this activity:
    United States Geological Survey, FISC St. Petersburg
    600 4th Street South
    St. Petersburg, FL
    USA

    727 803-8747 (voice)
    Hours_of_Service: 8:30-5:00 M-F EST
    Date: 24-Jan-2017 (process 4 of 5)
    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 5 of 5)
    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?
    Brock, J.C.; Wright, C.W.; Sallenger, A.H; Krabill, W.B., and Swift, R.N, 2002, Basis and Methods of NASA Ariborne Topographic Mapper Lidar Surveys for Coastal Studies: Journal of Coastal Research Vol. 18, No. 1, pp.1-13, Journal of Coastal Research, West Palm Beach, FL.

    John Brock and Asbury Sallenger, US Geological Survey, 2001, Airborne Topographic Lidar Mapping for Coastal Science and Resource Management: US Geological Survey, St. Petersburg, FL.


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-cm nominal ranging accuracy, and verticle elevation accuracy of +/- 15cm (bare earth). 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.5 meter horizontal accuracy. Processing steps (grid interpolation) may introduce additional error which has not been tested at the time of this publication.
  3. How accurate are the heights or depths?
    Elevations of the DEM are vertically consistent with the point elevation data, +/- 15cm.
  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 -100 m 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.
  5. How consistent are the relationships among the observations, including topology?
    Each file contains data located in a 2-km by 2-km tile, where the upper-left bound can be assessed quickly through the file name. The first 3 numbers in the file name 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, ba_e123_n4567_20).

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints:
Any use of these data signifies a user's agreement to comprehension and compliance of the USGS Standard Disclaimer. Ensure all portions of metadata are read and clearly understood before using these data in order to protect both user and USGS interests. See section 6.3 Distribution Liability.
Use_Constraints:
Although the USGS is making these data sets available to others who may find the data of value, the USGS does not warrant, endorse, or recommend the use of these data setse for any given purpose. The user assumes the entire risk related to the use of these data. These data sets are not for navigational purposes. The USGS is providing these data "as is", and the USGS disclaims any and all warranties, whether expressed or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose. In no event will the USGS be liable to you or to any third party for any direct, indirect, incidental, consequential, special, or exemplary damages or lost profits resulting from any use or misuse of these data.Acknowledgement of the U.S. Geological Survey, FISC St. Petersburg office, as a data source would be appreciated in products developed from these data, and such acknowledgement as is standard for citation and legal practices for data source is expected by users of this data. Sharing new data layers developed directly from these data would also be appreciated by the USGS staff. Users should be aware that comparisons with other data sets for the same area from other time periods may be inaccurate due to inconsistencies resulting from changes in photo interpretation, mapping conventions, and digital processes over time. These data are not legal documents and are not to be used as such.
  1. Who distributes the data set? (Distributor 1 of 1)
    United States Geological Survey, FISC St. Petersburg
    600 4th Street South
    St. Petersburg, FL
    USA

    727-803-8747 (voice)
    Hours_of_Service: 8:30-5:00 M-F EST
    Contact_Instructions: Call USGS for Details
  2. What's the catalog number I need to order this data set? OFR_2007-1375
  3. What legal disclaimers am I supposed to read?
    Neither the United States Geological Survey nor the National Park Service shall be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such.The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data.The United States Geological Survey gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from a USGS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the United States Geological Survey, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.
  4. How can I download or order the data?
  5. Is there some other way to get the data?
    Call USGS for Details

Who wrote the metadata?

Dates:
Last modified: 09-Nov-2021
Metadata author:
United States Geological Survey, St. Petersburg Coastal and Marine Science Center
Attn: SPCMSC Data Management Group
600 4th Street South
St. Petersburg, Florida
US

727-502-8000 (voice)
gs-g-spcmsc_data_inquiries@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/of2007-1375metadata.faq.html>
Generated by mp version 2.9.50 on Tue Nov 9 16:47:42 2021