Raw navigation files logged with HYPACK Survey software during a geophysical survey conducted by the USGS within Red Brook Harbor, MA, 2009

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

Frequently anticipated questions:


What does this data set describe?

Title:
Raw navigation files logged with HYPACK Survey software during a geophysical survey conducted by the USGS within Red Brook Harbor, MA, 2009
Abstract:
These data were collected under a cooperative agreement with 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 (5-30 m deep) of Massachusetts between the New Hampshire border and Cape Cod Bay. 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/). This is the spatial dataset for the Red Brook Harbor survey area within Buzzards Bay, Massachusetts. These data are the results of a high-resolution geophysical (bathymetry, backscatter intensity, and seismic reflection) and ground validation (sediment samples and bottom photographs) survey, conducted in 2009. In addition to inclusion within the USGS-CZM geologic mapping effort, these Red Brook Harbor data will be used to assess the shallow-water mapping capability of the geophysical systems deployed for this project, with an emphasis on identifying resolution benchmarks for the interferometric sonar system. (http://woodshole.er.usgs.gov/operations/ia/public_ds_info.php?fa=2009-018-FA)
  1. How might this data set be cited?
    U.S. Geological Survey, 2012, Raw navigation files logged with HYPACK Survey software during a geophysical survey conducted by the USGS within Red Brook Harbor, MA, 2009: Open-File Report 2010-1091, 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.

    Turecek, Aaron M., Danforth, William W., Baldwin, Wayne E., and Barnhardt, Walter A., 2012, High-Resolution Geophysical Data Collected Within Red Brook Harbor, Buzzards Bay, Massachusetts, in 2009: Open-File Report 2010-1091, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.678892
    East_Bounding_Coordinate: -70.616102
    North_Bounding_Coordinate: 41.692125
    South_Bounding_Coordinate: 41.661905
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 28-Sep-2009
    Ending_Date: 17-Nov-2009
    Currentness_Reference:
    ground condition
  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 Vector data set. It contains the following vector data types (SDTS terminology):
      • String (203)
    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 attributes are present in each navigation file. The following list explains the attributes that may be present in each HYPACK navigation file. GPS receivers were recorded as devices 0, 1 and 3. Tide correction values from device 3 (Novatel DL-V3 RTK GPS) were used to tide correct bathymetry data during post-processing. Device 0 (Ashtech Surveyor RTK GPS) data was not recorded to nav files during sediment sampling operations on julian days 320 and 321 (11/16/2009 and 11/17/2009). The times recorded in the navigation file are in UTC (Coordinate Universal Time). 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 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. HVU: Horizontal and Vertical Units (meters). TND: Survey time and date in UTC. DEV 0: RTK receiver (Ashtech Surveyor RTK GPS). OFF 0: Device 0 offsets. Format for value is: OFF dn n1 n2 n3 n4 n5 n6 n7, where dn=device number; n1=starboard/port offset (starboard is positive, port is negative); n2=forward/aft offset (forward is positive, aft is negative); n3=height of antenna or depth of transducer draft (always positive); n4=yaw rotation angle (clockwise rotation is positive); n5=roll rotation angle (port side up is positive); n6=pitch rotation angle (bow up is positive); n7=device latency in seconds. DEV 1: DGPS receiver (CSI LGBX Pro DGPS). OFF 1: Device 1 offsets. Format for value is: OFF dn n1 n2 n3 n4 n5 n6 n7, where dn=device number; n1=starboard/port offset (starboard is positive, port is negative); n2=forward/aft offset (forward is positive, aft is negative); n3=height of antenna or depth of transducer draft (always positive); n4=yaw rotation angle (clockwise rotation is positive); n5=roll rotation angle (port side up is positive); n6=pitch rotation angle (bow up is positive); n7=device latency in seconds. DEV 2: Disabled DEV 3: RTK Tides (Novatel DL-V3 RTK GPS). OFF 3: Device 3 offsets. Format for value is: OFF dn n1 n2 n3 n4 n5 n6 n7, where dn=device number; n1=starboard/port offset (starboard is positive, port is negative); n2=forward/aft offset (forward is positive, aft is negative); n3=height of antenna or depth of transducer draft (always positive); n4=yaw rotation angle (clockwise rotation is positive); n5=roll rotation angle (port side up is positive); n6=pitch rotation angle (bow up is positive); n7=device latency in seconds. DEV 4: Disabled DEV 5: Echosounder - NMEA string LIN: Planned line data follows in the format "LIN nw" where nw=number of waypoints PTS: Planned line waypoints in the format "PTS x y" where x=waypoint easting; y=waypoint northing (UTM zone 19N, meters, WGS84 for this survey) LBP: Planned line begin point in the format "LBP x y" where x=x grid position; y=y grid position (UTM zone 19N, meters, WGS84 for this survey) 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 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. GYR: Gyro Data (Heading). Format "GYR dn t h", where dn=device number, t=time tag (seconds past midnight), h=ship heading 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. These message strings are defined further down in the NMEA definition section. EC1: echo sounding (singe frequency). Format "EC1 dn t rd", where dn=device number, t=time tag (seconds past midnight), rd=raw depth. 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; 5=RTK float. 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. 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. These numbers are incremented by the software. TID: Tide correction in the format "TID dn t dc" where dn=device number; t=time tag (seconds past midnight); dc=draft correction. TID 3 (from Novatel DL-V3 RTK GPS receiver) was applied to bathy in post-processing The (National Marine Electronics Association) NMEA strings $GPGGA, $GPVTG, $GPZDA and $SDDPT 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,163052.00,4118.964217,N,07036.966471,W,4,10,00.9,00005.332,M,-030.544,M,01,*57 UTC Time = 163052 Latitude = 4118.964217 N Longitude = 7036.966471 W Fix Quality = 4 Number of satellites = 10 HDOP = 00.9 relative accuracy of horizontal position Altitude = 5.332 meters above mean sea level Height of geoid above WGS84 ellipsoid = -30.554 meters Time since last update = 01 Checksum = *57. $GPVTG is track made good and ground speed in the format "$GPCTG, true, T, mag, M, grsp, N, grdp, 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, gdsp=ground speed, N=Knots, grsp=ground speed, K=Kilometers per hour, mode=Mode indicator (A=Autonomous, D=Differential, E=Estimated, N=Data not valid). Example: $GPVTG,089.23,T,104.82,M,004.86,N,009.02,K,D*28 True course made good: 089.23 Magnetic course made good: 104.82 Ground speed (knots) = 4.86 Ground speed (kilometers) = 9.02 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,163053.00,09,08,2007,,*60 UTC= 163053.00 UTC day = 09 UTC month = 08 UTC year = 2007 Local zone hours = null Local zone minutes = null Checksum = *60 $SDDPT is water depth relative to the transducer in meters in the format "$SDDPT, depth meters, offset *checksum" Example: $SDDPT, 3.71, 0.50*57 Depth in meters = 3.71 Offset from transducer: Positive value is distance from transducer to water line; Negative value is 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. The SDDPT definiteion was obtained from: http://www.eye4software.com/products/gpstoolkit/nmea

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?
    Aaron Turecek
    U.S. Geological Survey
    Geographer
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2230 (voice)
    508-457-2310 (FAX)
    aturecek@usgs.gov

Why was the data set created?

This dataset contains raw HYPACK navigation files for a geophysical survey conducted by the U.S. Geological Survey in Red Brook Harbor, Massachusetts.

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: Information unavailable from original metadata.
    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 (UTC) for the beginning of the file, and DDD is the Julian day. Times in the file were recorded in UTC (Coordinate Universal Time).
  2. How were the data generated, processed, and modified?
    Date: 2009 (process 1 of 5)
    RTK and DGPS positions were recorded to raw files by HYPACK Survey software. Filenames are in the format of linenumber_starttime.julianday. For example, filename 017_1455.150 represents HYPACK line number 017, start time 1455 and Julian Day 150. Times are recorded in UTC (Coordinate Universal Time). Person who carried out this activity:
    Aaron Turecek
    U.S. Geological Survey
    Geographer
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2230 (voice)
    508-457-2310 (FAX)
    aturecek@usgs.gov
    Date: 15-Apr-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.). Fixed URL in abstract. The source information was incomplete and had to be modified to meet the standard. 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?
    Navigation antennas (one Differential Global Positioning System (DGPS) and two Real-Time Kinematic (RTK) GPS antennas) were mounted on a horizontal crossbar atop the vertical transducer mount pole at the bow of the R/V Rafael. Position data from an Ashtech Surveyor RTK GPS, a Novatel DL-V3 RTK GPS, and a CSI LGBX Pro DGPS were recorded by HYPACK survey software to HYPACK raw files. RTK positional accuracy is sub-meter; DGPS accuracy is estimated to be approximately 2 meter.
  3. How accurate are the heights or depths?
    Real-Time Kinematic (RTK) positions were collected with an Ashtech Z-Extreme receiver, and recorded by HYPACK Survey software to HYPACK raw files. RTK vertical positions were used to post-process tidal corrections for bathymetry data. RTK positional accuracy is sub-meter.
  4. Where are the gaps in the data? What is missing?
    These files represent all of the DGPS and RTK navigation recorded by HYPACK software during USGS survey 09018.
  5. How consistent are the relationships among the observations, including topology?
    These are the original files recorded by the HYPACK navigation software. No additional checks or corrections have been made to these files. Surveying may not have occurred on consecutive days.

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)
    Aaron Turecek
    U.S. Geological Survey
    Geographer
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2230 (voice)
    508-457-2310 (FAX)
    aturecek@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: This WinZip file contains the raw HYPACK navigation files as well as the associated metadata files. in format HYPACK (version 9.0.5.17) Size: 21.3
      Network links: http://pubs.usgs.gov/of/2010/1091/GIS/navigation/RB_Nav.zip
      Media you can order: DVD-ROM (Density 4.75 Gbytes) (format UDF)
    • Cost to order the data: none

  5. What hardware or software do I need in order to use the data set?
    The user must have software capable of uncompressing the WinZip file, such as WinZip or pkUnzip.

Who wrote the metadata?

Dates:
Last modified: 16-Nov-2021
Metadata author:
Aaron Turecek
U.S. Geological Survey
Geographer
384 Woods Hole Rd.
Woods Hole, MA
USA

508-548-8700 x2230 (voice)
508-457-2310 (FAX)
whsc_data_contact@usgs.gov
Contact_Instructions:
The metadata contact email address is a generic address in the event the metadata contact is no longer with the USGS or the email is otherwise invalid.
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/ofr2010-1091/RB_Nav.hypack.faq.html>
Generated by mp version 2.9.50 on Tue Nov 16 10:06:39 2021