HYPACK ASCII navigation files collected by the U.S. Geological Survey in the Madison Swanson and Steamboat Lumps Marine Protected Areas, Gulf of Mexico in 2000 (Geographic, WGS 84)

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

Frequently anticipated questions:


What does this data set describe?

Title:
HYPACK ASCII navigation files collected by the U.S. Geological Survey in the Madison Swanson and Steamboat Lumps Marine Protected Areas, Gulf of Mexico in 2000 (Geographic, WGS 84)
Abstract:
The U.S. Geological Survey (USGS) mapped approximately 22 square miles of the Madison Swanson Marine Protected Area (MPA) and Steamboat Lumps MPA, which are located on the Florida shelf edge in the northeastern Gulf of Mexico in 2000 using sidescan sonar and high-resolution chirp seismic-reflection systems. This survey was conducted as part of a larger study of the effectiveness of no-fishing reserves in protecting grouper spawning aggregations. Field activity information for this cruise is available on-line through the U.S. Geological Survey Coastal and Marine Geoscience Data System at https://cmgds.marine.usgs.gov/fan_info.php?fa=2000-005-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 2016, HYPACK ASCII navigation files collected by the U.S. Geological Survey in the Madison Swanson and Steamboat Lumps Marine Protected Areas, Gulf of Mexico in 2000 (Geographic, WGS 84): data release DOI:10.5066/F7JD4TVC, 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.

    Scanlon, Kathryn M., and Buczkowski, Brian J., 2016, High-resolution geophysical data collected in the Madison Swanson and Steamboat Lumps Marine Protected Areas, Gulf of Mexico in 2000, U.S. Geological Survey Field Activity 2000-005-FA: data release DOI:10.5066/F7JD4TVC, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -85.846575
    East_Bounding_Coordinate: -84.597457
    North_Bounding_Coordinate: 29.283575
    South_Bounding_Coordinate: 28.047345
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 16-Feb-2000
    Ending_Date: 02-Mar-2000
    Currentness_Reference:
    ground condition during 20000216 - 20000302
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: text 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 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:
    HYPACK (unknown version) was used to record navigation. The times recorded in the navigation file are in UTC. 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.
    
    
    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. ***In this case, the information recorded in at least some of the files was from another survey. This affects files in the MadSwan folder (001*.DAT through 006_0422.DAT). More files could be affected.
    
    
    FIL: Raw format file.
    
    
    ELL: Ellipsoid information. The name of the ellipsoid followed by the semi-major axis in meters and the flattening ratio.
    
    
    PRO: Projection information record where TME indicates Transverse Mercator and the central meridian of -87 indicates UTM, zone 16.
    
    
    TND: Survey time and date in UTC.
    
    
    DEV 0: Indicates that the lines with device designation 0 are lines of DGPS data collected with the Ashtech system.
    
    
    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 range to fish.
    
    
    OFF 1: device offsets for device 1 - see description above.
    
    
    DEV 2: Indicates that the lines with device designation 2 are lines of depth collected by the Furuno echosounder.
    
    
    OFF 2: device offsets for device 2 - see description above.
    
    
    DEV 3: Indicates that the lines with device designation 3 are related to navigation values for the towfish taking into account the range to fish. This is the assumption being made based on the information provided.
    
    
    OFF 3: device offsets for device 3 - see description above.
    
    
    DEV 4: Indicates that the lines with device designation 4 are related to values sent to the ISIS system which records the SIS1000 data. This is the assumption being made based on the information provided.
    
    
    OFF 4: device offsets for device 4 - see description above.
    
    
    DDT 3: unknown HYPACK header element. Found in HYPACK drive documentation for device driver setup under YSI_6600.dll (version 2.2.0.0) with no further explanation. Seems to be some kind of place holder for a custom device driver of a "SMI" (Special Marine Instrument). And the assumption is that the 3 represents the device associated with this element.
    
    
    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. ***In this case, easting and northing UTM zone 19N, meters.
    
    
    LBP: planned line begin point in the format "LBP x y" where x=x grid position; y=y grid position. ***In this case I believe the values represent easting and northing, UTM Zone 16N, 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 (0 for Ashtech) 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 location - in the format "POS dn t x y" where dn=device number; t=time tag (seconds past midnight); x=easting; y=northing. During this survey these values are in UTM, Zone 16, WGS84.
    
    
    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.
    
    
    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.
    
    
    DFT: No defined, but assumed to be either the depth to the towfish or elevation of the towfish above the sea floor in the format "DFT dn t rd" where dn=device number; t=time tag (seconds past midnight); rd=raw depth or elevation.
    
    
    TOW: Uncertain as to the meaning of this tag but can make some assumptions. I believe it's the position of the tow fish as calculated using the range to fish. The format is assumed to be TOW dn t n x y ? ? ? where dn=device number; t=time tag (seconds past midnight); n=number of values to follow; x=easting; y=northing. The 3 values represented by ? ? ? are unknown. During this survey the easting and northing values are in UTM, Zone 16N, WGS84.
    
    
    GYR: Gyro Data (heading) in the format "GYR dn t h" where dn=device number; t=time tag (seconds past midnight); h=shipheading angle.
    
    
    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 HYPACK files do not contain any NMEA strings.
    Entity_and_Attribute_Detail_Citation:
    The definitions of the HYPACK strings were acquired from the HYPACK software manual available from: http://www.hypack.com/.

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?
    U.S. Geological Survey
    Attn: Kathryn M. Scanlon
    Research Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    USA

    508-548-8700 x 2323 (voice)
    508-457-2310 (FAX)
    kscanlon@usgs.gov

Why was the data set created?

These data are supplied to provide the raw navigation collected during USGS field activity 2000-005-FA. 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 Navigation Data.

    Type_of_Source_Media: hard disk
    Source_Contribution:
    Raw navigation data were saved in HYPACK format (http://www.hypack.com). File name convention is LLL_TTTT.DAT, where LLL is the HYPACK line number, TTTT is the 24 hour time for the beginning of the file, and DAT is the DAT data file extension. Times were recorded in UTC (Coordinate Universal Time). HYPACK version 8.9 was used for data logging.
  2. How were the data generated, processed, and modified?
    Date: 2000 (process 1 of 4)
    Raw HYPACK navigation files were transferred from the navigation acquisition computer to a data server for accessibility and archive. The raw HYPACK navigation files are stored in separate directories indicating the general location the data were collected in (MadSwan, Steam, Control, Tieline, and Transit), corresponding to data from the Madison Swanson Marine Protected Area, Steamboat Lumps Marine Protected Area and northern control test data from this site, tie line in the Steamboat Lumps Mairne Protected Area, and the transit from one survey area to the other. The filenames in each folder are in the format of linenumber_starttime.DAT. For example, filename 002_1809.DAT represents HYPACK line number 002, start time 1809. Times are recorded in UTC (Coordinate Universal Time). Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    USA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
    Date: 06-Apr-2017 (process 2 of 4)
    The online links to the data were updated to reflect the new server hosting the data. Additionally, other small edits could be made to the metadata, such as modifying http to https where appropriate. The metadata date (but not the metadata creator) was edited to reflect the date of these changes. 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: 20-Jul-2018 (process 3 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: 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?
    Capone, Mark, Scanlon, Kathryn M., and Swift, B. Ann, 2002, Archive of Chirp Subbottom Data Collected During USGS Cruise ORGN00005, Northeastern Gulf of Mexico, 15 February - 2 March, 2000: Open-File Report 2002-045, 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?
    Differential GPS (DGPS), with an Ashtech BR2G beacon receiver, was used to navigate the ship. 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. The towed geophysical equipment will have a reduced positional accuracy.
  3. How accurate are the heights or depths?
    The elevation data recorded in the HYPACK files is from a Furuno echosounder. No draft was applied to the Furuno during acquisition, and the transducer was approximately 1 meter under the surface. The elevation values are not corrected for tides.
  4. Where are the gaps in the data? What is missing?
    These files represent all of the raw navigation recorded by the HYPACK software during USGS field activity 2000-005-FA.
  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. At least one file (018_1942.DAT in the MadSwan folder) is known to have incorrect navigation. The line numbers represented in the HYPACK files do not necessarily correspond to geophysical line numbers.

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 originator of the dataset. These data are not to be used for navigation.
  1. Who distributes the data set? (Distributor 1 of 1)
    Brian J. Buczkowski
    U.S. Geological Survey
    Physical Scientist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    USA

    508-548-8700 x2361 (voice)
    508-457-2310 (FAX)
    bbuczkowski@usgs.gov
  2. What's the catalog number I need to order this data set? The 2000-005-FA_hypack.zip file contains 5 subfolders: Control, MadSwan, Steam, Tieline, Transit. Each folder contains the HYPACK navigation files associated with that survey area. In addition to the ASCII navigation files, the zip file also contains the FGDC CSDGM metadata in the following formats: XML, HTML, and text.
  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?
    This WinZip file contains the DAT files and associated metadata 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:
Brian J. Buczkowski
U.S. Geological Survey
Physical Scientist
384 Woods Hole Road
Woods Hole, Massachusetts
USA

508-548-8700 x2361 (voice)
508-457-2310 (FAX)
bbuczkowski@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/field_activities/2000_005_fa/2000-005-FA_hypackmeta.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:13 2021