Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey - Woods Hole Coastal and Marine Science Center offshore of the Elizabeth Islands, MA, 2010

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

Frequently anticipated questions:


What does this data set describe?

Title:
Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey - Woods Hole Coastal and Marine Science Center offshore of the Elizabeth Islands, MA, 2010
Abstract:
These data were collected under a cooperative agreement between the Massachusetts Office of Coastal Zone Management (CZM) and the U.S. Geological Survey (USGS), Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center (WHCMSC). Initiated in 2003, the primary objective of this program is to develop regional geologic framework information for the management of coastal and marine resources. Accurate data and maps of seafloor geology are important first steps toward protecting fish habitat, delineating marine resources, and assessing environmental changes due to natural or human impacts. The project is focused on the inshore waters of coastal Massachusetts, primarily in water depths of 2-30 meters. Data collected for the mapping cooperative have been released in a series of USGS Open-File Reports (<http://woodshole.er.usgs.gov/project-pages/coastal_mass/>). The data collected in this study area located around the western extent of the Elizabeth Islands includes high resolution bathymetry, acoustic-backscatter intensity, seismic-reflection, and navigation data. These data were collected during a nearshore cruise in September 2010 onboard the R/V Rafael using the following equipment: an SEA Ltd SwathPlus interferometric sonar (234 kHz), Klein 3000 dual frequency sidescan sonar, an Edgetech 424 chirp subbottom profiling system, and 4 GPS antennae. More information about the cruise conducted as part of the project: Geologic Mapping of the Seafloor Offshore of Massachusetts can be found on the Woods Hole Coastal and Marine Science Center Field Activity webpage: <http://quashnet.er.usgs.gov/data/2010/10003/>
  1. How might this data set be cited?
    U.S. Geological Survey, 2012, Raw HYPACK navigation logs (text) collected by the U.S. Geological Survey - Woods Hole Coastal and Marine Science Center offshore of the Elizabeth Islands, MA, 2010: Open-File Report 2011-1184, 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., Twichell, David C., Foster, David S., Worley, Charles R., Irwin, Barry J., and Danforth, William W., 2012, High-resolution geophysical data from the sea floor surrounding the western Elizabeth Islands, Massachusetts: Open-File Report 2011-1184, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.994895
    East_Bounding_Coordinate: -70.85
    North_Bounding_Coordinate: 41.462
    South_Bounding_Coordinate: 41.387572
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 09-Sep-2010
    Ending_Date: 16-Sep-2010
    Currentness_Reference:
    Data were not collected on 20100915 due to and weather conditions, respectively.
  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 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. In the HYPACK files this line suggests that the data were collected in Penobscott Bay, however, this is an inaccurate entry left over from a previous cruise.
    
    
    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.
    
    
    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 RTK data acquired with the Novatel DLV3 (dual frequency) receiver.
    
    
    OFF 0: device offsets (none used during this data collection)
    
    
    DEV 1: Indicates that the lines with device designation 1 are lines of DGPS data acquired with a Communications Systems International (CSI), Inc. LGBX Pro (single frequency) receiver.
    
    
    OFF 1: device offsets (none used during this data collection)
    
    
    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 (none used during this data collection)
    
    
    DEV 3: Indicates that the lines with device designation 3 are lines of DGPS data acquired with an Ashtech Z-extreme (dual frequency) receiver.
    
    
    OFF 3: device offsets (none used during this data collection)
    
    
    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.
    
    
    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
    
    
    $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
    
    
    Example: $GPHDT,005.533,T*35 Heading in Degrees = 5.533 True = T Checksum = *35
    
    
    $SDDPT is water depth relative to the transducer in meters in the format "$SDDPT, data_meters, offset_meters, checksum.
    
    
    Example: $SDDPT,3.71,0.50*57 Depth in meters = 3.71 Offset from transducer: Positive - distance from transducer to water line, or Negative - distance from transducer to keel ((this definition from <http://www.actisense.com/Downloads/TechTalk/NMEA%200183/The%20NMEA%200183%20Information%20Sheet.pdf>)
    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)
    • U.S. Geological Survey
  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 Road
    Woods Hole, MA
    USA

    508-548-8700 x2266 (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 Elizabeth Islands, 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?
    Information unavailable from original metadata. (source 1 of 1)
    The source information was incomplete and had to be modified to meet the standard. Assumed to be USGS., unknown, Information unavailable from original metadata..

    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). Julian Day 253 is an exception to this naming convention. Due to generator trouble, the survey team was troubleshooting instrument function and data collection was abandoned for the day. The HYPACK lines that were collected were namedd S16.253, S15.253, and S14.253.
  2. How were the data generated, processed, and modified?
    Date: 18-Sep-2010 (process 1 of 5)
    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 separate directories indicating the acquisition Julian Day. The filenames in each folder are in the format of linenumber_starttime.julianday. For example, filename 004_0850.254 represents HYPACK line number 004, start time 0850, and Julian Day 254. 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
    USA

    (508)-548-8700 x2259 (voice)
    (508)-457-2310 (FAX)
    ependleton@usgs.gov
    Date: 31-May-2016 (process 2 of 5)
    Edits to the metadata were made to fix any errors that MP v 2.9.32 flagged. This is necessary to enable the metadata to be successfully harvested for various data catalogs. In some cases, this meant adding text "Information unavailable" or "Information unavailable from original metadata" for those required fields that were left blank. Other minor edits were probably performed (title, publisher, publication place, etc.). The link to the data in the Identification_Information section had to be fixed. Fixed a link to the project page in the abstract. Fixed a link in the cross-reference section to the SEG-Y format documentation. The source information was incomplete and had to be modified to meet the standard. The distribution format name was modified in an attempt to be more consistent with other metadata files of the same data format. The metadata date (but not the metadata creator) was edited to reflect the date of these changes. The metadata available from a harvester may supersede metadata bundled within a download file. Compare the metadata dates to determine which metadata file is most recent. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
    Date: 20-Jul-2018 (process 3 of 5)
    USGS Thesaurus keywords added to the keyword section. 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
    Date: 18-Nov-2019 (process 4 of 5)
    Crossref DOI link was added as the first link in the metadata. 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
    Date: 08-Sep-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?

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.), sub-bottom, and sidescan sonar 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) antenna, also mounted above the swath transducers, was used to acquire water-level heights for tidal corrections. A Garmin 5312 was used to drive the boat and monitor water depths. Additionally, an Ashtech Z-Extreme was also used to record positions to HYPACK, but these data were not logged to any instrument. All DGPS data are assumed to be accurate to within + or - 1 to 2 meters.
  3. How accurate are the heights or depths?
  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-003-FA. The GPS data recorded to HYPACK include the following receivers: a Novatel DLV3 (RTK), Communications Systems International (CSI), Inc. LGBX Pro (DGPS), a Garmin 5312 (echosounder for boat navigation), and an Ashtech Z-extreme (DGPS). 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 Ashtech Z-extreme was used for redundancy and recorded to HYPACK, but was not recorded as navigation for any instrument. The Novatel DL-V3 (RTK) was used only to acquire z-values for tidal corrections to the bathy. The RTK, x and y values were not used for any instrument navigation.
  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. No HYPACK files were recorded on Julian day 258 (Sept. 15, 2010 ) due to weather conditions. Julian day 252 navigation is from instrument calibration.

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

    (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: 08-Sep-2020
Metadata author:
Elizabeth A. Pendleton
U.S. Geological Survey
Geologist
384 Woods Hole Rd.
Woods Hole, MA

(508) 548-8700x2259 (voice)
(508) 457-2310 (FAX)
ependleton@usgs.gov
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/open_file_report/ofr2011-1184/2010-003-FA_hypack_metaholder.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:36 2021