Text files of the navigation logged with HYPACK Software during survey 2014-002-FA conducted along the Delmarva Peninsula, MD and VA by the U.S. Geological Survey in 2014

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 2014-002-FA conducted along the Delmarva Peninsula, MD and VA by the U.S. Geological Survey in 2014
Abstract:
The Delmarva Peninsula is a 220-kilometer-long headland, spit, and barrier island complex that was significantly affected by Hurricane Sandy. A U.S. Geological Survey cruise was conducted in the summer of 2014 to map the inner continental shelf of the Delmarva Peninsula using geophysical and sampling techniques to define the geologic framework that governs coastal system evolution at storm-event and longer timescales. Data collected during the 2014 cruise include swath bathymetry, sidescan sonar, chirp and boomer seismic-reflection profiles, acoustic Doppler current profiler, and sample and bottom photograph data. Processed data in raster and vector format are released here for the swath bathymetry, sidescan sonar, and seismic-reflection profiles. More information about the USGS survey conducted as part of the Hurricane Sandy Response-- Geologic Framework and Coastal Vulnerability Study can be found at the project website or on the WHCMSC Field Activity Web pages: https://woodshole.er.usgs.gov/project-pages/delmarva/ and https://cmgds.marine.usgs.gov/fan_info.php?fan=2014-002-FA
  1. How might this data set be cited?
    U.S. Geological Survey, 2015, Text files of the navigation logged with HYPACK Software during survey 2014-002-FA conducted along the Delmarva Peninsula, MD and VA by the U.S. Geological Survey in 2014: data release DOI:10.5066/F7MW2F60, 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, E.A., Ackerman, S.D., Baldwin, W.E., Danforth, W.W., Foster, D.S., Thieler, E.R., and Brothers, L.L., 2015, High-resolution geophysical data collected along the Delmarva Peninsula 2014, U.S. Geological Survey Field Activity 2014-002-FA: data release DOI:10.5066/F7MW2F60, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -75.6031379955789
    East_Bounding_Coordinate: -74.65660495738244
    North_Bounding_Coordinate: 38.465827972474074
    South_Bounding_Coordinate: 37.526953449184454
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 18-Jun-2014
    Ending_Date: 25-Jul-2014
    Currentness_Reference:
    ground condition; data were not collected on 20140702-20140704; 20140709; and 20140714-20140715 due to weather.
  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 Vector data set.
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 18 N
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -75
      Latitude_of_Projection_Origin: 0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 0.5
      Ordinates (y-coordinates) are specified to the nearest 0.5
      Planar coordinates are specified in meters
      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. 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 -75 indicates UTM, zone 18.
    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 2014-002-FA: Indicates that lines collected with device designation 0 are lines of Differential Global Positioning System (DGPS) collected with the Hemisphere DGPS receiver. When sampling began and geophysical surveying ended on Julian Day 203. The Hemisphere DGPS was disabled at DEV 0 and enabled as a DEV 5 with an offset to relocate the GPS at the stern of the vessel where the sampler was being deployed. All files ending in ***.203 and later will have a DEV 5.
    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 onf the type of device generating the data. KTD for is example is a Kinematic Tide Datum File.
    DDT: identifies the device that the computer clock is being synchronized to.
    DEV 1: For survey 2014-002-FA: Indicates that the device designation 1 is a web-interface that is relaying the hypack feed from the acquisition van to a bridge monitor and the processing van.
    DEV 2: For survey 2014-002-FA: Indicates that the lines with device designation 1 are lines of Real Time Kinematic Global Positioning System (RTK-GPS) data collected with the Ashtech ProFlex 800 GPS RTK receiver. This device recorded the RTK-GPS heights and was capable of recording antenna elevations above a vertical datum (Kinematic Tide Datum).
    DEV 3: For survey 2014-002-FA: Indicates that the lines with device designation 3 are lines of fathometer information collected by a Sitex DepthFinder. This device is utilized by the MVP30 to transmit depth measurements ensuring that the sound velocity profiler would not deploy below 4 meters from the sea floor.
    DEV 4: For survey 2014-002-FA: Indicates the device designation 4 are NMEA Output lines.
    DEV 5: For survey 2014-002-FA: indicates that the device designation 5 are also lines of Hemisphere DGPS, but only during 3 days at the end of the survey when samples were being collected. The DEV 0 hemisphere was disables and became DEV 5 with an offset (-13) to the stern as a backup for sample location.
    LIN 2: planned line data follows
    PTS: planned line waypoints (easting and northing, UTM, zone 18N, meters)
    LBP: planned line begin point (easting and northing, UTM zone 18N, 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 or 5 for Hemisphere 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 18, 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 2014-002-FA there were several different messages were sent from the GPS systems: $GPGGA, $GPVTG, and $SDDPT 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.
    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 where “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.
    The (National Marine Electronics Association) NMEA strings $GPGGA, $GPVTG, $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,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
    $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
    $SDDPT is Depth Below the EchoSounder (Sitex)Transducer in the format "$SDDPT,x.x,x.x,F*CS" where x.x=depth in meters, x.x=offset from transducer: positive is distance from transducer to water line, or neative is distance from transducer to keel.
    Example: $SDDPT,3.6,0.0*52 Depth in Meters = 3.6, Offset from transducer = 0.0., CRC Checksum of NMEA data = 0.0*52.
    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.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?
    U.S. Geological Survey
  3. To whom should users address questions about the data?
    Elizabeth Pendleton
    U.S. Geological Survey
    Geologist
    U.S. Geological Survey
    Woods Hole, MA

    (508) 548-8700x2259 (voice)
    (508)-457-2310 (FAX)
    ependleton@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 2014-002-FA along the Delmarva Peninsula. Survey 2014-002-FA was conducted aboard the M/V Scarlet Isabella. HYPACK software (version 14.0.9.47) was used to log these data.

How was the data set created?

  1. From what previous works were the data drawn?
    raw 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 (<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 2014-002-FA, HYPACK version 14.0.9.47 was used.
  2. How were the data generated, processed, and modified?
    Date: 30-Jul-2014 (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 24_1816.203 represents planned survey HYPACK line number 24, start time 1816 and Julian Day 203. Times are recorded in UTC (Coordinate Universal Time). Filenames that start with 000 have no geophysical data line associated with them because they were logging navigation associated with sediment samples and bottom photographs. Person who carried out this activity:
    Elizabeth Pendleton
    U.S. Geological Survey
    Geologist
    U.S. Geological Survey
    Woods Hole, MA
    USA

    (508) 548-8700x2259 (voice)
    (508)-457-2310 (FAX)
    ependleton@usgs.gov
    Date: 18-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?

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 ProFlex 800, Coda Octopus F185R, Hemisphere DGPS, and Sitex Marine Electronics Depthfinder 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.
  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 (if needed to replace zone tidal model). 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 2014-002-FA along the Delmarva Peninsula.
  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:
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 (USGS) as the source of this information.
  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? USGS data release 2014-002-FA: HYPACK navigation from the Delmarva Peninsula area (2014-002-FA_hypack.zip). The zip file contains FGDC CSDGM metadata files (2014_002_Hypack_nav.xml) in four standard formats and 294 raw HYPACK files that serve as a navigation archive.
  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. Is there some other way to get the data?
    none
  6. 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:
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
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/2014_002_fa/2014_002_HYPACK.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:14 2021