2010-072-FA_hypack: Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey from Muskeget Channel, MA, 2010

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

Frequently anticipated questions:

What does this data set describe?

Title:
2010-072-FA_hypack: Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey from Muskeget Channel, MA, 2010
Abstract:
These data were collected in a collaboration between the Woods Hole Oceanographic Institution and the U.S. Geological Survey (USGS). The primary objective of this program was to collect baseline bathymetry for Muskeget Channel, Massachusetts, and identify areas of morphologic change within and around the channel. Repeat surveys in select areas were collected one month apart to monitor change. These data were collected to support an assessment of the effect on sediment transport that a tidal instream energy conversion facility would have within Muskeget Channel. Accurate data and maps of sea-floor topography are important first steps in monitoring bedform migration, fish habitat, marine resources, and environmental changes due to natural or human impacts. The data include high-resolution bathymetry, acoustic-backscatter intensity, sound velocity in water, and navigation data. These data were collected during two surveys between October 2010 and November 2011 onboard the research vessel (RV) Rafael using an SEA Ltd. SwathPlus interferometric sonar (234 kilohertz). More information about the cruise can be found on the Woods Hole Coastal and Marine Science Center field activity Web page at <http://woodshole.er.usgs.gov/operations/ia/public_ds_info.php?fa=2010-072-FA>
  1. How should this data set be cited?

    U.S. Geological Survey, 2014, 2010-072-FA_hypack: Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey from Muskeget Channel, MA, 2010: Open-File Report 2012-1258, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Pendleton, Elizabeth A., Denny, Jane F., Danforth, William W., Baldwin, Wayne E., and Irwin, Barry J., 2014, High-Resolution Swath Interferometric Data Collected within Muskeget Channel, Massachusetts: Open-File Report 2012-1258, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -70.498
    East_Bounding_Coordinate: -70.400
    North_Bounding_Coordinate: 41.417
    South_Bounding_Coordinate: 41.293

  3. What does it look like?

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

    Calendar_Date: 12-Oct-2010
    Currentness_Reference: ground condition

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

    Geospatial_Data_Presentation_Form: document

  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.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Degrees, minutes, and decimal seconds.

      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 -69 indicates UTM, zone 19.
    DTM: Datum transformation record
    GEO: Geoid model. Blank if not present. The number after the model indicates the orthometric height correction in meters.
    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 a Communications Systems International (CSI), Inc. LGBX Pro (single frequency) receiver.
    OFF 0: device offsets for device 0. Format of the value is OFF dn n1 n2 n3 n4 n5 n6 n7 where dn=device number; n1=starboard, port offsets where positive is starboard; n2=forward, aft offset where positive is forward; n3=height (antenna) or depth (transducer draft) offset - always positive; n4=yaw rotation angle where positive for clockwise rotation; n5=roll rotation angle where port side up is positive; n6=pitch rotation angle where bow up is positive; n7=device latency in seconds. No offset for device 0 during this data collection.
    DEV 1: Indicates that the lines with device designation 1 are lines of RTK data acquired with the Novatel DLV3 (dual frequency) receiver.
    OFF 1: device offsets, where antenna height is -2.48 meters.
    DEV 2: Indicates that the lines with device designation 2 are lines of DGPS data acquired with a Garmin 5312 (single frequency, echosounder) receiver.
    OFF 2: device offsets, where antenna height is 0.6 meters.
    DEV 3: Indicates that the lines with device designation 3 are lines of RTK data acquired with an Ashtech Z-xtreme (dual frequency, echosounder) receiver.
    OFF 3 device offsets, where antenna height is -2.48 meters.
    DDT 3: identifies the device (3) that the computer clock is being synchronized to.
    LIN: planned line data follows in the format "LIN nw" where nw=number of waypoints.
    PTS: planned line waypoints; easting, northing in UTM zone 19N, meters.
    LBP: planned line begin point; easting, northing in UTM zone 19N, 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 Ashtech Z-Extreme receiver) 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 z" where dn=device number; t=time tag (seconds past midnight); x=easting; y=northing. On this cruise these values are in UTM, Zone 19N, 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)
    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 in the format ddmmmm.mmmm. To convert to ddmm.mmmmm multiply by 100; long=raw longitude in the format ddmmmm.mmmm. To convert to ddmm.mmmmm multiply by 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, five different messages were sent from the DGPS: $GPGGA, $GPZDA, $GPVTG, $SDDPT, $GPHDT. These will be defined later.
    TID: Tide correction in the format "TID dn t dc" where dn=device number, t=time tag (seconds past midnight), dc = draft correction.
    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 in meters.
    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, $GPZDA, $SDDPT, $GPGGA and $GPHDT. These are defined as follows:
    $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 hemisphere; q=fix quality where 0=fix not available or invalid; 1=GPS fix; 2=Differential GPS fix; 3=GPS PPS Mode fix; 4=RTK fix; 5=RTK float; 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.
    Example: $GPGGA,173356.00,4204.848996,N,07036.929067,W,4,09,01.1,00003.278,M,-028.888,M,01,0000*56 UTC Time = 173356 Latitude = 4204.848996 N Longitude = 7036.929067 W Fix Quality = 4 (indicates RTK) Number of satellites = 9 HDOP = 01.1 relative accuracy of horizontal position Altitude = 3.278 meters above mean sea level Height of geoid above WGS84 ellipsoid = -28.888 meters Time since last update = 01 Checksum = *57.
    $GPVTG is track made good and ground speed in the format "$GPVTG, true, T, mag, M, grsp1, N, grsp2, K, mode", where t=true course made good over ground in degrees, T= True, m=magnetic course made good over ground in degrees, M=magnetic, grsp1=ground speed, N=Knots, grsp2=ground speed, K=Kilometers per hour, mode=Mode indicator (A=Autonomous, D=Differential, E=Estimated, N=Data not valid).
    Example: $GPVTG,340.39,T,356.37,M,005.50,N,010.18,K,D*27 True course made good: 340.39 Magnetic course made good: 356.37 Ground speed (knots) = 5.5 Ground speed (kilometers) = 10.18 Mode=Differential
    $GPZDA is UTC Date/Time and Local Time Zone Offset in the format "$GPZDA,hhmmss.ss,xx,xx,xxxx,xx,xx" where hhmmss.ss=UTC, xx=Day, 01 to 31, xx=month, 01 to 12, xxx=Year, xx=Local zone description, 00 to +/- 13 hours, xx=Local zone minutes description (same sign as hours), checksum.
    Example: $GPZDA,173357.00,28,04,2007,,*69 UTC= 173357.00 UTC day = 28 UTC month = 04 UTM year = 2007 Local zone hours = null Local zone minutes = null Checksum = *69
    $SDDPT is water depth in the format "$SDDPT, data_meters, offset *checksum"
    Example: $SDDPT,1.6,0.0*50 Depth in meters = 1.6 Offset from transducer:0.0 Positive - distance from transducer to water line, or Negative - distance from transducer to keel
    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>

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?

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

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

Why was the data set created?

These raw navigation data are included as an archive documenting the survey area surrounding Muskeget Channel, Massachusetts 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?

    USGS (source 1 of 1)
    U.S. Geological Survey.

    Type_of_Source_Media: disc
    Source_Contribution:
    Raw navigation data were saved in HYPACK format. File name convention is LLL_TTTT.JJJ, where LLL is the HYPACK line number, TTTT is the 24 hour time for the beginning of the file, and JJJ is the Julian Day of data collection. Times were recorded in UTC (Coordinate Universal Time).

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

    Date: 2010 (process 1 of 1)
    Raw HYPACK (9.0.5.17) navigation files were transferred from the navigation acquisition computer to an external drive. The raw HYPACK navigation files are stored in directories indicating the acquisition Julian Day. For example, filename 004_0850.287 represents HYPACK line number 004, start time 0850, and Julian Day 287. Times are recorded in UTC (Coordinate Universal Time).

    Person who carried out this activity:

    Elizabeth A. Pendleton
    U.S. Geological Survey
    Geologist
    U.S. Geological Survey
    Woods Hole, MA 02543-1598
    USA

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

  3. What similar or related data should the user be aware of?

    Poppe, L.J., McMullen, K.Y., Foster, D.S., Blackwood, D.S., Williams, S.J., Ackerman, S.D., Moser, M.S., and Glomb, K.A., 2010, Geological Interpretation of the Sea Floor Offshore of Edgartown, Massachusetts: Open-File Report 2009-1001, U.S. Geological Survey, Reston, VA.

    Online Links:

    Denny, J.F., Danforth, W.W., Foster, D.S., and Sherwood, C.R., 2009, Geophysical Data Collected off the South Shore of Martha's Vineyard, Massachusetts: Open-File Report 2008-1288, U.S. Geological Survey, Reston, VA.

    Online Links:

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?

    Positions of the ship (HYPACK line nav.) were determined using a Communications Systems International (CSI), Inc. LGBX Pro differential global positioning system (DGPS) antenna mounted above the cabin on the R/V Rafael. Swath bathymetry, continuous sound velocity at the sonar head, and attitude data were determined using a CodaOctopus F180 DGPS antenna mounted on a rigid, vertical pole aproximately 3-m above the swath transducers. A Novatel DL-V3 Real-Time Kinematic (RTK) and an Ashtech Z-xtreme antenna, mounted above the swath transducers, were used to acquire water-level heights for tidal corrections. A Garmin 5312 was used to drive the boat and monitor water depths. All DGPS data are assumed to be accurate to within + or - 1 to 2 meters.

  3. How accurate are the heights or depths?

    Vertical (RTK) heights were collected with a Novatel receiver and sn Ashtech Z-Extreme receiver, then recorded to HYPACK Survey software. RTK positions were used to post-process tidal corrections for bathymetry data (using the Novatel heights). RTK positional accuracy is sub-meter. EC1 depth values were collected with a Furuno FRS 1000 plotter/radar/sounder, which has an assumed vertical accuracy of 0.5 meters.

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

    These files represent four of the five global positioning systems used on the R/V Rafael during cruise 2010-072-FA. The GPS data recorded to HYPACK include the following receivers: a Novatel DLV3 (RTK), Communications Systems International (CSI), Inc. LGBX Pro (DGPS), an Ashtech Zxtreme (RTK), and a Garmin 5312 (echosounder for boat navigation). An additional antenna and receiver for the Coda Octopus F180 was used for navigation for the Swath interferometric and attitude data, and imported directly into SwathPlus without being logged in HYPACK. The Novatel DL-V3 (RTK) was used to acquire z-values for tidal corrections to the bathy. The Ashtech Z-extreme (RTK) was used for redundancy and recorded to HYPACK, but was not recorded for any instrument.

  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:
Not to be used for navigation. 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 A. 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 U.S. Geological Survey 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. 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: 09-Jun-2014
Metadata author:
Elizabeth A. 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)

Generated by mp version 2.9.27 on Mon Jun 09 15:06:28 2014