Text files of the navigation logged with HYPACK Software during field activity 2013-003-FA in 2013 by the U.S. Geological Survey south of Martha's Vineyard and north of Nantucket, Massachusetts

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 field activity 2013-003-FA in 2013 by the U.S. Geological Survey south of Martha's Vineyard and north of Nantucket, Massachusetts
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 sea floor 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 geophysical data were collected during a survey in 2013 during USGS Field Activity 2013-003-FA (http://cmgds.marine.usgs.gov/fan_info.php?fa=2013-003-FA) and cover approximately 185 square kilometers of the inner continental shelf.
  1. How might this data set be cited?
    U.S. Geological Survey, 2016, Text files of the navigation logged with HYPACK Software during field activity 2013-003-FA in 2013 by the U.S. Geological Survey south of Martha's Vineyard and north of Nantucket, Massachusetts: Open-File Report 2016-1168, 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., Brothers, Laura L., Foster, David S., Andrews, Brian D., Baldwin, Wayne E., and Schwab, William C., 2016, High-Resolution Geophysical Data From the Inner Continental Shelf: South of Martha's Vineyard and North of Nantucket, Massachusetts: Open-File Report 2016-1168, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.810609
    East_Bounding_Coordinate: -70.029975
    North_Bounding_Coordinate: 41.390816
    South_Bounding_Coordinate: 41.192901
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 22-May-2013
    Ending_Date: 11-Jun-2013
    Currentness_Reference:
    ground condition of survey dates: 20130522-20130611; see Completeness_Report for more information
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: tabular 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:
    Not all files contain the same HYPACK strings, but this list represents all the HYPACK strings represented in the files. These are the original files, no corrections have been made to these files. The times recorded in the navigation file are in UTC. The EC1 messages, although present in many of the HYPACK files, are invalid. Keywords and the information they provide 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 vessel name, 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 ratio.
    
    PRO: Project information record where TME indicates Transverse Mercator and the central meridian of -69 indicates UTM, zone 19N.
    
    DTM: Datum transformation record.
    
    GEO: Geoid model. Blank if not present. Note: During survey 2013-003-FA, GEOID09 grid #4 for CONUS (g2009u4.geo) was used.
    
    HVU: Horizontal and Vertical Units (meters).
    
    TND: Survey time and date in UTC.
    
    DEV [#]: [Insert data about cruise device #]
    
    DEV 0: For survey 2013-003-FA: Indicates that lines collected with device designation 0 are lines of Differential Global Positioning System (DGPS) collected with the Hemisphere DGPS.
    
    DEV 1: For survey 2013-003-FA: Indicates that lines collected with device designation 1 are lines of Real Time Kinematic GPS data collected with the Novatel GPS DL-V3 receiver.
    
    DEV 2: For survey 2013-003-FA: Indicates that lines collected with device designation 2 are lines of Real Time Kinematic GPS data collected from the Coda F185.  ***Note: this is mislabeled in the header as "F180".***
    
    DEV 3: For survey 2013-003-FA: Indicates that lines collected with device designation 3 are the NMEA string GPGGA lines of Real Time Kinematic GPS data collected from the Coda F185.  ***Note: this is mislabeled in the header as "F180_GGA".***
    
    DEV 4: No good data for survey 2013-003-FA. No valid lines of data from Device 4 occur in these HYPACK navigation files. See EC1 note below.
    
    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.
    
    PRD: Private Device Data, which has multiple formats depending on the type of device generating the data. For example, KTD is a Kinematic Tide Datum File. Note: VDatum transformation grid “MENHMAgome01_8301” was used for the kinematic tide correction process during 2013-003-FA to offset water level heights from the WGS84 ellipsoid to MLLW.
    
    DDT: identifies the device that the computer clock is being synchronized to.
    
    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.
    
    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 [Device 0] and 1 for [Device 1]) 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 19N, WGS84.
    
    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 2013-003-FA there were several different messages were sent from the GPS systems: $GPGGA and $GPVTG were standard throughout the survey. 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.  Note: this message appears to be invalid throughout this survey as this was a dummy depth feed possibly used to plot survey history in the HYPACK real-time display.
    
    GYR: Gyro data (heading) in the format: GYR dn t h, where dn=device number, t=time tag (seconds past midnight), h=heading.
    
    HCP: Heave Compensation in the format: HCP dn t h r p, where dn=device number, t=time tag (seconds past midnight), h=heave in meters, r=roll in degrees (+ port side up), p=pitch in degrees (+ bow up).
    
    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.
    
    KTC: Describes how HYPACK records water levels (tide corrections) when using RTK in the format: KTC dn t nv eh lh u kval offset draft final, where dn = device number, t=time tag (seconds past midnight, matches GPS position), nv=number of values, eh= WGS84ellipsoidal height (from GPS), lh= local ellipsoidal height (on local ellipsoid), u=undulation, kval= K value, offset= antenna offset, draft=draft correction, final=final tide.
    
    $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,160209.00,3806.336689,N,07505.875090,W,4,11,0.9,5.038,M,-36.840,M,1,0378*61 UTC Time = 160209.00 Latitude = 3806.336689 N Longitude = 07505.875090 W Fix Quality = 4 (indicates RTK) Number of satellites = 11 HDOP = 0.9 relative accuracy of horizontal position Altitude = 5.038 meters above mean sea level Height of geoid above WGS84 ellipsoid = -36.840 meters Time since last update = 01 Checksum = *61.
    
    $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.
    
    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, http://www.hypack.com/new/portals/1/pdf/sb/09_11/The%20KTC%20Record%20in%20HYPACK.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?
    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?

These raw navigation data are provided as an archive of the navigation data files acquired during USGS survey 2013-003-FA south of Martha's Vineyard and north of Nantucket. Survey 2013-003-FA was conducted aboard the M/V Scarlet Isabella. HYPACK software (version 13.0.9.21) was used to log these data.

How was the data set created?

  1. From what previous works were the data drawn?
    raw hypack navigation (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 (www.hypack.com). File name convention is LLL_TTTT.DDD, where LLL is the user defined planned 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 2013-005-FA, HYPACK version 13.0.9.21 was used.
  2. How were the data generated, processed, and modified?
    Date: 2013 (process 1 of 4)
    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 filenames are in the format of linenumber_starttime.julianday. For example, filename 959_2200.142 represents planned survey HYPACK line number 959, start time 2200 and Julian Day 142. Times are recorded in UTC (Coordinate Universal Time). Person who carried out this activity:
    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
    Date: 20-Jul-2018 (process 2 of 4)
    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 3 of 4)
    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 4 of 4)
    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?
    Please note that DEV 2 and DEV 3 are mislabeled in the header - (both are data from the Coda F185 and were unintentionally labeled as the F180 in the header of each HYPACK file).
  2. How accurate are the geographic locations?
    Real-Time Kinematic Global Positioning System (RTK-GPS) and Differential GPS (DGPS) navigation data were collected during survey 2013-003-FA using the Coda F185 RTK-GPS, Novatel DL-V3 RTK-GPS and the Hemisphere DGPS. Positioning data from all these sensors were logged using HYPACK navigation software version 13.0.9.21 (www.hypack.com). These data were 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 horizontal positional accuracy is estimated to be within 3-5 m and the accuracy of RTK-GPS is estimated to be less than 1 m.
  3. How accurate are the heights or depths?
    Real-Time Kinematic GPS height data (referenced to the WGS 84 ellipsoid) were recorded using navigation software from HYPACK, Inc. (www.hypack.com). Vertical accuracy of RTK-GPS is estimated to be less than 1 m..
  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 2013-003-FA south of Martha's Vineyard and north of Nantucket. The first survey line collected is associated with HYPACK file 959_2200.142, however several other HYPACK files from earlier on JD 142 were recorded during equipment calibration testing. Time gaps occurred during this field activity where no surveying was done due to bad weather, rough seas and stops in port for crew changes. Planned surveying was paused and no main survey line data were collected during these times:
    JD143 15:20 - JD146 20:06 (no data were collected on JD144 or JD145)
    JD149 15:40 - JD151 18:59 (no data were collected on JD150)
    JD153 00:01 - JD153 14:32
    JD155 18:16 - JD156 02:06
    JD158 06:12 - JD160 19:15 (no data were collected on JD159)
    
  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:
These data are NOT to be used for navigation. Mariners should refer to the appropriate nautical chart. 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)
    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? USGS data release 2013-005-FA contains raw HYPACK navigation files collected south of Martha's Vineyard and north of Nantucket, Massachusetts (2013-005-FA_HYPACK.zip). The zip file contains 317 raw HYPACK files that serve as a navigation archive and Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata files (2013-005-FA_HYPACK.xml) in standard formats.
  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. 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 unzipping the zip file, 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/ofr2016-1168/2013-003-FA_HYPACK_meta.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:41 2021