Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center offshore of the Gulf Islands, MS, 2010

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

Frequently-anticipated questions:

What does this data set describe?

Title:
Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center offshore of the Gulf Islands, MS, 2010
Abstract:
In 2010, the U.S. Geological Survey in Woods Hole, MA and St. Petersburg, FL, in partnership with the U.S. Army Corps of Engineers, Mobile District conducted geologic mapping to characterize the seafloor and shallow subsurface stratigraphy offshore of the Gulf Islands of Mississippi. The mapping was carried out during two cruises in March, 2010 on the R/V Tommy Munro of Biloxi, MS. Data were acquired with the following equipment: an SEA Ltd SwathPlus interferometric sonar (both 234 kHz and 468 kHz systems), a Klein 3000 and a Klein 3900 dual frequency sidescan-sonar, and an Edgetech 512i chirp subbottom profiling system. The long-term goal of this mapping effort is to produce high-quality, high-resolution geologic maps and geophysical interpretations that can be utilized to identify sand resources within the region and better understand the Holocene evolution and anticipate future changes in this coastal system. More information on the field work can be accessed from the Woods Hole Coastal and Marine Science Center Field Activity webpage <http://quashnet.er.usgs.gov/data/2010/10012/> or the St. Petersburg Coastal and Marine Geology InfoBank <http://walrus.wr.usgs.gov/infobank/m/m210gm/html/m-2-10-gm.meta.html>.
  1. How should this data set be cited?

    U.S. Geological Survey, 2011, Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center offshore of the Gulf Islands, MS, 2010: USGS Open-File Report 2010-1178, U.S. Geological Survey, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Pendleton, Elizabeth A. , Baldwin, Wayne E. , Danforth, William W. , Dewitt, Nancy T. , Forde, Arnell S. , Foster, David S. , Kelso, Kyle W. , Pfeiffer, William R. , Turecek, Aaron M. , Flocks, James G. , and Twichell, David C. , 2011, Geophysical Data from offshore of the Gulf Islands National Seashore, Cat Island to Western Horn Island, Mississippi: Open-File Report 2010-1178, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -89.035786
    East_Bounding_Coordinate: -88.637281
    North_Bounding_Coordinate: 30.215336
    South_Bounding_Coordinate: 30.126883

  3. What does it look like?

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

    Beginning_Date: 19-Mar-2010
    Ending_Date: 29-Mar-2010
    Currentness_Reference:
    Data were not collected on 20100321-20100326 due to weather conditions, crew changes, or survey location.

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

    Geospatial_Data_Presentation_Form: vector 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.

    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.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.

  7. How does the data set describe geographic features?

    Entity_and_Attribute_Overview:
    The times recorded in the navigation file are in UTC. Keyword definitions and the information listed below are comprehensive and not found in every file. The definitions are as follows:
    FTP: The first record located at the top of the header used to identify the file format.
    VER: HYPACK version number.
    INF: General survey information filled in by the data technician. This typically contains the survey participants, the vessel name, other agencies involved with the survey, and the location of the survey. The three numbers at the end refer to initial tide correction at start-of-line, initial draft correction at start-of-line and sound velocity from the navigation parameters.
    FIL: Raw format file.
    ELL: Ellipsoid information. The name of the ellipsoid followed by the semi-major axis in meters and the flattening ration.
    PRO: Project information record where TME indicates Transverse Mercator and the central meridian of -81 indicates UTM, zone 17.
    DTM: Datum transformation record
    GEO: Geoid model. Blank if not present.
    HVU: Horizontal and Vertical Units (meters).
    TND: Survey time and date in UTC.
    DEV 0: Indicates that the lines with device designation 0 are lines of DGPS data acquired with the Coda Octopus F190R motion reference unit antenae.
    OFF: device offsets (none used during this data collection) The number following OFF indicates which device
    LIN: planned line data follows in the format "LIN nw" where nw=number of waypoints.
    PTS: planned line waypoints; easting, northing in UTM zone 16N, meters.
    LBP: planned line begin point; easting, northing in UTM zone 16N, meters.
    LNN X: planned line name where X is the line name
    EOL: end of planned line
    EOH: end of header
    The remaining elements have similar information in the first 3 columns. The first column will indicate the data type, the second column will indicate the device that recorded the information (e.g. 0 for Coda Octopus F190R reciever) and the third column is the time tag (seconds past midnight) that is also sometimes referred to as the latency. The remaining information on each line is specific to the data type.
    POS: Position of the ship - in this case the antenna - in the format "POS dn t x y" where dn=device number; t=time tag (seconds past midnight); x=easting; y=northing. On this cruise these values are in UTM, Zone 16N, WGS84.
    QUA: Position quality information in the format "QUA dn t n m h sat mode" where dn=device number; t=time tag (seconds past midnight); n=number of values to follow; m = 10 minus HDOP (horizontal dilution of precision); h=HDOP; sat=number of satellites; mode=GPS mode (NMEA 0183 standard values) where 2=Differential GPS fix.
    RAW: Position information in the format "RAW dn t n lat long alt utc" where dn=device number; t=time tag (seconds past midnight); n=number of values to follow; lat=raw latitude X 100; long=raw longitude X 100; alt=antenna altitude above ellipsoid (meters); utc=GPS time in the format HHMM.
    GYR: Gyro Data (heading) in the format "GYR dn t h" where dn=device number; t=time tag (seconds past midnight); h=shipheading angle.
    MSG: Message string in the format "MSG dn t message" where dn=device number; t=time tag (seconds past midnight); message is the message sent from the device. On this cruise, three different messages were sent from the DGPS: $GPGGA $GPHDT $GPVTG. These will be defined later.
    EC1: Echo Sounding (single frequency) in the format "EC1 dn t rd" where dn=device number; t=time tag (seconds past midnight); rd=raw depth.
    EC1 on device 0 - found it in 001_0910.RAW in folder 079_10. Looks like it's in other files too.
    FIX: events marked manually by the user in the format "FIX dn t event_number" where dn=device number (typically 99 as there is no device for manual events); t=time tag (seconds past midnight); event_number=event number such as 1,2,3,4.
    The National Marine Electronics Association (NMEA) strings present in the HYPACK file are the $GPVTG, $GPGGA and $GPHDT. These are defined as follows:
    $GPVTG is track made good and ground speed in the format "$GPVTG, t, T, m, M, n, N, k, K refcheck" where t=true course made good over ground, degrees; T indicates the previous number refers to true course; m=magnetic course made good over ground, dgrees; M indicates the previous number refers to magnetic course; n=ground speed; N indicates the previous number refers to Knots, k=ground speed; K indicates the previous number refers to Kilometers per hour, refcheck= checksum at the end of the string with the first character an *.
    $GPGGA is GPS fix data in the format "$GPGGA, t, lat, lath, long, longh, q, sat, h, a, M, alt, M, t2, refcheck" where t=time in UTC in the format hhmmss.ss; lat=latitude in the format ddmm.mmmmmm; lath= N or S indicating the latitude hemisphere; long=longitude in the format dddmm.mmmmmm; longh=E or W indicating the longitude hemisphere; q=fix quality where 2 is a DGPS fix; sat=number of satellites; h=Horizontal Dilution of Precision (HDOP); a=Antenna altitude above mean sea level (geoid); M= units of antenna altitude in meters; alt=height of geoid above WGS84 ellipsoid; M=units of geoidal height in meters; t2=time since last DGPS update; refcheck=DGPS reference station id and the checksum.
    $GPHDT is Actual vessel heading in degrees in format "$GPHDT,xxx.x,T" where xxx.x=heading in degrees and T indicates True Heading, checksum
    Entity_and_Attribute_Detail_Citation:
    The definitions of the HYPACK strings were acquired from the HYPACK software manual available from: <http://www.hypack.com/>. The definitions of the NMEA strings were obtained from: <http://home.mira.net/~gnb/gps/nmea.html> and <http://www.actisense.com/Downloads/TechTalk/NMEA%200183/The%20NMEA%200183%20Information%20Sheet.pdf>.

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?

    David C. Twichell
    U.S. Geological Survey
    Oceanographer
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700x2266 (voice)
    (508) 457-2310 (FAX)
    dtwichell@usgs.gov

Why was the data set created?

These raw navigation data are included as an archive documenting the survey area surrounding the Gulf Islands National Seashore and the instrumentation used to manage the ship's navigation.

How was the data set created?

  1. From what previous works were the data drawn?

    (source 1 of 1)
    Type_of_Source_Media: disc
    Source_Contribution:
    Raw navigation data were saved in HYPACK format (<http://www.hypack.com>). File name convention is LLL_TTTT.RAW, where LLL is the HYPACK line number and TTTT is the 24 hour time (UTC) for the beginning of the file. Times in the file were recorded in UTC (Coordinate Universal Time).

  2. How were the data generated, processed, and modified?

    Date: 2010 (process 1 of 1)
    Raw HYPACK (version 9.0.5.9) navigation files were transferred from the navigation acquisition computer to an external drive. The raw HYPACK navigation files are stored in separate directories indicating the acquisition Julian Day. The filenames in each folder are in the format of linenumber_starttime.RAW. For example, filename 010_2257.RAW represents HYPACK line number 010, start time 2257. Times are recorded in UTC (Coordinate Universal Time).

  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?

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

    All raw HYPACK lines from 10cct02 are included from within the survey area west of Petit Bois Island.

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

    These are the original raw data files recorded by the HYPACK navigation software. No additional checks or corrections have been made to these files.

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 as the originator of the dataset.

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

    Elizabeth Pendleton
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700x2259 (voice)
    (508) 457-2310 (FAX)
    ependleton@usgs.gov

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

    Downloadable Data

  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?

  5. Is there some other way to get the data?

    Digital copies of these raw navigation data may also be obtained upon request.

  6. What hardware or software do I need in order to use the data set?

    These data can be viewed with any text editing software.

Who wrote the metadata?

Dates:
Last modified: Oct-2010
Last Reviewed: 2010
Metadata author:
Elizabeth Pendleton
U.S. Geological Survey
Geologist
384 Woods Hole Rd.
Woods Hole, MA 02543-1598

(508) 548-8700x2259 (voice)
(508) 457-2310 (FAX)
ependleton@usgs.gov

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

Generated by mp version 2.9.6 on Fri Apr 29 14:55:36 2011