2010Multibeam Sonar Data collected from the CCGS Amundsen Barge

Metadata also available as - [Outline]

Frequently anticipated questions:

What does this data set describe?

Title: 2010Multibeam Sonar Data collected from the CCGS Amundsen Barge
Abstract:
Ocean Mapping Group binary format data generated from the 2010 multibeam sonar survey on the 2010 CCGS Amundsen ArcticNet Cruise. The data includes high-resolution bathymetry, acoustic backscatter and watercolumn backscatter.
Supplemental_Information:
Information for Ocean Mapping Group activities are online at <http://www.omg.unb.ca>
  1. How should this data set be cited?

    Ocean Mapping Group (OMG), 2010, 2010Multibeam Sonar Data collected from the CCGS Amundsen Barge: Ocean Mapping Group, University of New Brunswick, Fredericton, New Brunswick, Canada.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -133
    East_Bounding_Coordinate: -61
    North_Bounding_Coordinate: 72
    South_Bounding_Coordinate: 55

  3. What does it look like?

    <http://www.omg.unb.ca/Projects/Arctic/google/index.html> (Tiled Google Maps)
    Google Maps Interface of the OMG Arctic Multibeam Data

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 12-Jul-2010
    Ending_Date: 27-Oct-2010
    Currentness_Reference: NULL

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: OMG Merged Files, ESRI Grids and Images

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.00001. Longitudes are given to the nearest 0.00001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is WGS84 (G1150).
      The ellipsoid used is WGS84.
      The semi-major axis of the ellipsoid used is 6378137.00 meters.
      The flattening of the ellipsoid used is 1/298.257 223 563.

  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)

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    Ocean Mapping Group
    Attn: John Hughes Clarke
    Chair in Ocean Mapping
    Department of Geodesy and Geomatics Engineering University of New Brunswick 15 Dineen Drive P.O. Box 4400
    Fredericton, New Brunswick E3B 5A3
    Canada

    506-453-4568 (voice)
    506-453-4943 (FAX)
    jhc@omg.unb.ca

Why was the data set created?

Multibeam Surveys were carried out as part of the Ocean Mapping Group's role in the ArcticNet program.

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: 01-Jan-2011 (process 1 of 3)
    Multibeam bathymetry, watercolumn and backscatter data were collected using a Kongsberg Simrad EM3002 multibeam sonar system. Standard collection settings used auto depth mode, angular coverage of +/- 65 degrees and highdensity equidistant beamforming. SIS was used to collect the data, while daily cleaning of data outliers was done using the Ocean Mapping Group's Swathed toolkit after conversion to OMG binary format. IMU data was parsed by the SIS software from a Coda Octopus F185. RTG GPS data from a CNav 2000 GPS was used to correct and improve the position output from the F185. Soundspeed information was from YSI CastAway CTD casts. F185 Firmware Version:, Software Version:, SIS Version:,; EM3002 PU Version:, CNav Unit: 2000, WaterColumn Settings: x_log_offset = 20

    Person who carried out this activity:

    James Muggah
    Ocean Mapping Group (OMG)
    Research Assistant
    Department of Geodesy and Geomatics Engineering University of New Brunswick 15 Dineen Drive P.O. Box 4400
    Fredericton, New Brunswick E3B 5A3
    Canada

    506-453-5146 (voice)
    jmuggah@unb.ca

    Date: 01-Jan-2011 (process 2 of 3)
    - Multibeam Data was converted from the Kongsberg binary format to the Ocean Mapping Group binary format. - Primary navigation was set as the F185 output position.- The Attitude information was merged with the sounding data.- The Navigation data was merged with the sounding data- Tides were applied using predicted tides from the Arctic8c tide model data. Depths are referenced to MSL.- Backscatter data was generated- Watercolumn data was extracted from the Kongsberg binary wcd format

    Person who carried out this activity:

    James Muggah
    Ocean Mapping Group (OMG)
    Research Assistant
    Department of Geodesy and Geomatics Engineering University of New Brunswick 15 Dineen Drive P.O. Box 4400
    Fredericton, New Brunswick E3B 5A3
    Canada

    506-453-5146 (voice)
    jmuggah@unb.ca

    Date: 01-Jan-2011 (process 3 of 3)
    - The sounding data was inspected for errors in Sound Velocity using the soundscape software package.- The data was checked for integrity to ensure that previous processing steps were not missed.- The bathymetry and backscatter data was gridded into our 15'x30' basemap series. (<http://www.omg.unb.ca/Projects/Arctic/basemaps/index.html>)- The bathymetry and backscatter basemap tiles were used to generate the google map tiles. (<http://www.omg.unb.ca/Projects/Arctic/google/index.html>)

    Person who carried out this activity:

    James Muggah
    Ocean Mapping Group (OMG)
    Research Assistant
    Department of Geodesy and Geomatics Engineering University of New Brunswick 15 Dineen Drive P.O. Box 4400
    Fredericton, New Brunswick E3B 5A3
    Canada

    506-453-5146 (voice)
    jmuggah@unb.ca

  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?

    All sounding data was inspected daily and in post-processing and then all overlapping data was checked to ensure reliability.

  2. How accurate are the geographic locations?

    1.0 meter (95% confidence) from CNav RTG GPS

  3. How accurate are the heights or depths?

    Tidal accuracy estimated at 0.3 m (95% confidence) from Arctic8c tidal model

  4. Where are the gaps in the data? What is missing?

    Data was collected during daylight hours, when the EM3002 was deployed for seabed mapping.

  5. How consistent are the relationships among the observations, including topology?

    NULL

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: Public
Use_Constraints: Not to be used for navigation

  1. Who distributes the data set? (Distributor 1 of 1)

    Ocean Mapping Group (OMG)
    Department of Geodesy and Geomatics Engineering University of New Brunswick 15 Dineen Drive P.O. Box 4400
    Fredericton, NB E3B 5A3
    Canada

    506-453-4568 (voice)

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    Research programs, the Ocean Mapping Group or ArcticNet take no liability for the use or transmission of this data

  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 27-Feb-2015
Last Reviewed: 27-Feb-2015
Metadata author:
James Muggah
Ocean Mapping Group (OMG)
Research Assistant
Department of Geodesy and Geomatics Engineering University of New Brunswick 15 Dineen Drive P.O. Box 4400
Fredericton, NB E3B 5A3
Canada

(506) 453-5146 (voice)
jmuggah@unb.ca

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Generated by mp version 2.9.13 on Tue Mar 3 10:03:18 2015