Text files of the navigation logged with HYPACK Software during survey 2010-004-FA conducted in Buzzards Bay and Vineyard Sound by the U.S. Geological Survey offshore of Massachusetts in 2010.

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

Frequently anticipated questions:


What does this data set describe?

Title:
Text files of the navigation logged with HYPACK Software during survey 2010-004-FA conducted in Buzzards Bay and Vineyard Sound by the U.S. Geological Survey offshore of Massachusetts in 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 (WHSC). 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 5 to 30 meters (m) deep. 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 the study area in Buzzards Bay, Massachusetts, include high-resolution geophysics (bathymetry, backscatter intensity, and seismic reflection) and ground validation (sediment samples, video tracklines, and bottom photographs). The geophysical data are released in USGS Open-File Report 2012-1002, High-Resolution Geophysical Data from the Inner Continental Shelf: Buzzards Bay, Massachusetts (http://pubs.usgs.gov/of/2012/1002/). The sampling data have not been prepared for publication yet. The geophysical data were collected during four separate surveys conducted between 2004 and 2011 (National Oceanic and Atmospheric Administration (NOAA) survey H11319 (in 2004; bathymetry only) and USGS surveys 2009-002-FA, 2010-004-FA, and 2011-004-FA)) and cover 410 square kilometers of the inner continental shelf. More information about the individual USGS surveys conducted as part of the Buzzards Bay project can be found on WHCS Field Activity Web pages: 2009-002-FA: http://woodshole.er.usgs.gov/operations/ia/public_ds_info.php?fa=2009-002-FA 2010-004-FA: http://woodshole.er.usgs.gov/operations/ia/public_ds_info.php?fa=2010-004-FA 2011-004-FA: http://woodshole.er.usgs.gov/operations/ia/public_ds_info.php?fa=2011-004-FA Information about the NOAA survey can be found at: H11319: http://surveys.ngdc.noaa.gov/mgg/NOS/coast/H10001-H12000/H11319/DR/
  1. How might this data set be cited?
    U.S. Geological Survey, 2013, Text files of the navigation logged with HYPACK Software during survey 2010-004-FA conducted in Buzzards Bay and Vineyard Sound by the U.S. Geological Survey offshore of Massachusetts in 2010.: Open-File Report 2012-1002, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    This is part of the following larger work.

    Ackerman, Seth D., Andrews, Brian D., Foster, David S., Baldwin, Wayne E., and Schwab, William C., 2013, High-Resolution Geophysical Data from the Inner Continental Shelf: Buzzards Bay, Massachusetts.: Open-File Report 2012-1002, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -71.0291467
    East_Bounding_Coordinate: -70.4490317
    North_Bounding_Coordinate: 41.6697367
    South_Bounding_Coordinate: 41.3210983
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 15-May-2010
    Ending_Date: 04-Jun-2010
    Currentness_Reference:
    ground condition of individual survey on the following dates: 20100515-20100604
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: text 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. The SDDBT and EC1 messages, although present in many of the HYPACK files, are invalid. Keywords and the information they provide are as follows:
    
    
    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.
    
    
    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: For survey 2010-004-FA: Indicates that lines collected with device designation 0 are lines of Differential Global Positioning System (DGPS) collected with the Ashtech BRG2 receiver. The label for this device was "DGPS" in all HYPACK files throughout this survey.
    
    
    OFF: Device Offsets in the format "OFF dn n1 n2 n3 n4 n5 n6 n7" where dn = device number; n1 = starboard or port offset (positive starboard); n2 = forward or aft offset (positive forward); n3 = height (antenna) or depth (transducer draft) offset; n4 = yaw rotation angle (positive for clockwise rotation); n5 = roll rotation angle (port side up is positive); n6 = pitch rotation angle (bow up is positive); n7 = device latency in seconds.
    
    
    DDT: Unknown String (This appears in the HYPACK manual for Device Driver setup under YSI_6600.dll but there is no further explanation. It seems like some kind of place holder for a custom device driver of a "SMI" (Special Marine Instrument)).
    
    
    DEV 1: For survey 2010-004-FA: Indicates that the lines with device designation 1 are lines of Real Time Kinematic Global Positioning System (RTK-GPS) data collected with the NovAtel DL-V3 receiver - note: this device was labeled "DLV3" throughout this survey. This device recorded the RTK-GPS heights and was capable of recording antenna elevations above a vertical datum.
    
    
    DEV 2: For survey 2010-004-FA: Indicates that the lines with device designation 2 are lines of RTK-GPS collected by the Ashtech Z-Extreme receiver; note: this device was labeled "AshtZ" throughout this survey.
    
    
    DEV 3: For survey 2010-004-FA: Indicates that the lines with device designation 3 are lines of bathymetry information collected by an UNKNOWN device; note: this device was labeled "Bathy" throughout this survey although the only data record for this device is the line "MSG 3 15605.617 $SDDBT,0023.3,f,00020.0,M,003.9,F" which repeats throughout the survey and does not change, seemingly yielding no useful data. This was a dummy depth feed used by HYPACK during acquisition to plot recent survey line history to ensure that completed survey lines were not re-surveyed.
    
    
    DEV 4: For survey 2010-004-FA: Indicates that the lines with device designation 4 are lines of instrument information had it actually been recording any data; note: this device was labeled "Disabled" through all of this survey.
    
    
    LIN 2: planned line data follows
    
    
    PTS: planned line waypoints (easting and northing, UTM, zone 19N, meters)
    
    
    LBP: planned line begin point (easting and northing, UTM zone 19N, meters)
    
    
    LNN: planned line name
    
    
    EOL: end of planned line
    
    
    USR: user information
    
    
    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 (0 for Ashtech BRG2 DGPS) 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. Not all data types were recorded in each HYPACK file.
    
    
    POS: Position of the ship 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 19, 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 0 = fix not available or invalid; 1 = GPS fix; 2 = Differential GPS fix; 3 = GPS PPS Mode fix; 4 = RTK fix; and 5 = RTK Float. The last 3 values are decoded from GST message: standard deviation of latitude error (meters); standard deviation of longitude error (meters); Standard deviation of semi-major axis of error ellipsis (meters).
    
    
    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 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.
    
    
    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. During survey 2010-004-FA there were several different messages were sent from the GPS systems: $GPGGA, $GPVTG, $GPZDA and $SDDBT were standard throughout the survey. Message $SDDBT appears to be invalid. These message strings will be defined below.
    
    
    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 (singe frequency) in the format "EC1 dn t rd" where dn=device number, t=time tag (seconds past midnight), rd=raw depth.
    
    
    GYR: Gyro data (heading) in the format "GYR dn t h" where dn=device number, t=time tag (seconds past midnight), h=heading.
    
    
    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 $GPGGA, $GPVTG, $GPZDA, $SDDBT are stored in the HYPACK file. 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
    
    
    UTC year = 2007
    
    
    Local zone hours = null
    
    
    Local zone minutes = null
    
    
    Checksum = *69
    
    
    $SDDBT is Depth Below the Transducer in the format "$SDDBT,xxx.x,f,xxx.x,M,xxx.x,F*CS" where xxx.x=depth in feet, xxx.x=depth in meters and xxx.x=depth in fathoms). Note: this NMEA message appears to be invalid throughout this survey as this was a dummy depth feed used to plot survey history in the HYPACK real-time display.
    
    
    Example: $SDDBT,6.6,f,2.0,M,1.1,F
    
    
    Depth in Feet = 6.6
    
    
    Depth in Meters = 2.0
    
    
    Depth in Fathoms = 1.1
    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, http://www.nps.gov/gis/gps/NMEA_sentences.html

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?
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov

Why was the data set created?

To provide all of the navigation data files acquired during USGS 2010-004-FA, in Buzzards Bay and Vineyard Sound, Massachusetts. Survey 2010-004-FA was conducted aboard the M/V Megan T. Miller. HYPACK software was used to log these navigation data.

How was the data set created?

  1. From what previous works were the data drawn?
    none (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, raw HYPACK data.

    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.DDD, where LLL is the HYPACK line number, TTTT is the 24 hour time for the beginning of the file, and DDD is the Julian day (JD). Times were recorded in UTC (Coordinate Universal Time). During survey 2010-004-FA HYPACK version 10.0.5.31 was used.
  2. How were the data generated, processed, and modified?
    Date: 2010 (process 1 of 5)
    Raw HYPACK navigation files were transferred from the navigation acquisition computer to a centralized data server on the survey vessel for accessibility and archival. 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 284_1816.151 represents planned survey HYPACK line number 284, start time 1816 and Julian Day 151. Many of the folders also contain a .LOG file which is a text file listing the names of the files that HYPACK logged in that given day. Times are recorded in UTC (Coordinate Universal Time). Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Road
    Woods Hole, MA
    USA

    (508) 548-8700 x2315 (voice)
    (508) 457-2310 (FAX)
    sackerman@usgs.gov
    Data sources produced in this process:
    • HYPACK navigation files
    Date: 08-Dec-2015 (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 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?
    Andrews, B.D., Ackerman, S.D., Baldwin, W.E., Foster, D.S., and Schwab, W.C., 2012, High-resolution geophysical data from the inner continental shelf at Vineyard Sound, Massachusetts: U.S. Geological Survey Open-File Report 2012-1006: Open-File Report 2012-1006, U.S. Geological Survey, Reston, VA.


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?
    Real-Time Kinematic GPS (RTK-GPS), Differential GPS (DGPS) and Wide Area Augmentation System enabled DGPS (DGPS+WAAS) data were collected during this survey using an Ashtech Z-Surveyor Extreme, Coda Octopus F180, NovAtel DL-V3, Ashtech BRG2 and Garmin receivers. The data were processed and recorded using navigation software from HYPACK, Inc (http://www.hypack.com). These data were typically incorporated into the geophysical data during acquisition and logged to these HYPACK files in the event that post-processing the horizontal and vertical positional information was necessary. The DGPS positional accuracy is estimated to be within 3-5 m; WAAS enable DGPS accuracy is estimated to be less than 3 m and the accuracy of RTK-GPS is estimated to be less than 1 m. (http://www.nos.noaa.gov; http://www.ngs.noaa.gov; http://www.nstb.tc.faa.gov; http://www.navcen.uscg.gov).
  3. How accurate are the heights or depths?
    Real-Time Kinematic GPS (RTK-GPS) height data were collected, processed and recorded using navigation software from HYPACK, Inc (http://www.hypack.com). The data were logged to these HYPACK files so that they could be post-processed to extract the RTK-GPS heights and provide improved vertical accuracy for the swath bathymetric data during post-cruise processing. RTK-GPS provides accuracies on the order of tens of centimeters (http://www.navcen.uscg.gov).
  4. Where are the gaps in the data? What is missing?
    These files represent all the navigation recorded by the HYPACK software during USGS survey 2010-004-FA (which may also be referred to in the old field activity number style as 10004). This is raw navigation data for survey data that was released in USGS Open-File Reports 2012-1002 and 2012-1006 in Buzzards Bay and Vineyard Sound, Massachusetts, respectively.
  5. How consistent are the relationships among the observations, including topology?
    These are the original files recorded by the HYPACK navigation software. These data were checked but no modifications 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 source of this information.
  1. Who distributes the data set? (Distributor 1 of 1)
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@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?
    • Availability in digital form:
      Data format: ASCII text files containing RAW HYPACK data. This zip file also includes associated metadata. in format HYPACK (version 10.0.5.31) text files Size: 372
      Network links: http://pubs.usgs.gov/of/2012/1002/GIS/navigation/BB_10004_Hypack_nav.zip
      Media you can order: DVD-ROM (Density 4.75 GB) (format UDF)
    • Cost to order the data: none

  5. What hardware or software do I need in order to use the data set?
    These data are available as ASCII text files. To utilize these data, the user must have software capable of viewing text files and parsing the HYPACK navigation strings.

Who wrote the metadata?

Dates:
Last modified: 08-Sep-2020
Metadata author:
Seth Ackerman
U.S. Geological Survey
Geologist
384 Woods Hole Rd.
Woods Hole, MA
USA

508-548-8700 x2315 (voice)
508-457-2310 (FAX)
sackerman@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/ofr2012-1002/BB_10004_Hypack_nav.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:36 2021