Text files of the Wide Area Augmentation System (WAAS) navigation collected by the U.S. Geological Survey in Moultonborough Bay, Lake Winnipesaukee, New Hampshire in 2005 (Geographic, WGS 84, HYPACK ASCII Text Files)

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

Frequently anticipated questions:


What does this data set describe?

Title:
Text files of the Wide Area Augmentation System (WAAS) navigation collected by the U.S. Geological Survey in Moultonborough Bay, Lake Winnipesaukee, New Hampshire in 2005 (Geographic, WGS 84, HYPACK ASCII Text Files)
Abstract:
In freshwater bodies of New Hampshire, the most problematic aquatic invasive plant species is Myriophyllum heterophyllum or variable leaf water-milfoil. Once established, variable leaf water-milfoil forms dense beds that can alter the limnologic characteristics of a waterbody, impacting natural lacustrine communities and their habitats. Variable leaf water-milfoil infestations also disrupt recreational uses of waterbodies and have negatively affected swimming, boating, fishing, and property values in and around several lakes and ponds in New Hampshire.
In 1965, Moultonborough Bay, Lake Winnipesaukee became the first waterbody in New Hampshire where variable leaf water-milfoil was observed. Variable leaf water-milfoil is native to the Southeastern and Midwestern areas of the United States where more alkaline waters appear to limit the growth of this plant. Outside its native range, however, it adapts well to the relatively acidic, low-alkalinity, and nutrient-poor conditions of oligotrophic lakes and bays similar to Moultonborough Bay.
In 2005, the New Hampshire Department of Environmental Services (NHDES) collaborated with the U.S. Geological Survey to investigate the distribution (presence and density) of variable leaf water-milfoil in Moultonborough Bay. This study utilized geophysical systems and conventional water-quality measurements to identify lake-floor environments that may provide suitable habitat for the establishment and growth of variable leaf water-milfoil. The results of the study are intended to assist resource managers in federal and state agencies by providing methods for detecting variable leaf water-milfoil and for identifying areas susceptible to infestation. Ultimately, this information may lead to early detection, prevention, and more effective mitigation strategies.
Field activity information for this cruise is available on-line through the U.S. Geological Survey Coastal and Marine Geoscience Data System https://cmgds.marine.usgs.gov/fan_info.php?fa=2005-004-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 2014, Text files of the Wide Area Augmentation System (WAAS) navigation collected by the U.S. Geological Survey in Moultonborough Bay, Lake Winnipesaukee, New Hampshire in 2005 (Geographic, WGS 84, HYPACK ASCII Text Files): data release DOI:10.5066/F71N7Z4H, 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.

    Denny, J.F., Danforth, W.W., Worley, C.R., and Irwin, B.J., 2014, High-resolution geophysical and sample data collected in Moultonborough Bay, Lake Winnipesaukee, New Hampshire in 2005, USGS Field Activity 2005-004-FA: data release DOI:10.5066/F71N7Z4H, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -71.390517
    East_Bounding_Coordinate: -71.361103
    North_Bounding_Coordinate: 43.728543
    South_Bounding_Coordinate: 43.710999
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 25-Jul-2005
    Ending_Date: 29-Jul-2005Currentness_Reference: ground condition
  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 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 (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: Indicates that lines collected with device designation 0 are referencing Furuno single-beam echo sounder
    OFF: device offsets (none used during this data collection) The number following OFF indicates which device
    DEV 1: Indicated that the lines collected with device designation 1 are using DGPS/WAAS receiver (CSI LGBX Pro)
    LIN 2: planned line data follows
    PTS: planned line waypoints (eastings and northings, UTM, zone 19N, meters)
    LBP: planned line begin point (easting and northings, UTM zone 19N, meters)
    LNN X: planned line name, where X is the line number
    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 (e.g. 1 for Ashtech receiver) 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.
    EC1: echo sounding (singe frequency). Format EC1 dn t rd, where dn=device number, t=time tag (seconds past midnight), rd=raw depth (meters).
    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: Fix (event) mark. Format FIX vn, where n=FIX format version number, Always 2nd record in file.
    The (National Marine Electronics Association) NMEA strings $GPGGA, $GPVTG, and $GPZDA 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 where UTC Time = 163052 Latitude = 4118.964217 N, Longitude = 7036.966471 W, Fix Quality = 4 (RTK), Number of satellites = 10, HDOP = 00.9 relative accuracy of horizontal position, Altitude = 5.332 meters above mean sea leve,l 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, mag=magnetic course made good over ground in degrees, M=magnetic, grsp=ground speed, N=Knots, grdp=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, Checksum = *28
    $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 where UTC day = 09, UTC month = 08, UTC year = 200,7 Local zone hours = null, Local zone minutes = null, Checksum = *60
    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

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Jane F. Denny
    U.S. Geological Survey
    Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    USA

    508-548-8700 x 2311 (voice)
    508-457-2310 (FAX)
    jdenny@usgs.gov

Why was the data set created?

These data are supplied to provide the raw navigation collected by a LGBX Pro receiver and logged using HYPACK, Inc. navigation software (www.hypack.com) during USGS field activity 2005-004-FA.

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: online
    Source_Contribution:
    Raw navigation data were saved in HYPACK format (http://www.hypack.com), version 4.3. 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).
  2. How were the data generated, processed, and modified?
    Date: 2005 (process 1 of 2)
    Raw HYPACK navigation files were transferred from the navigation acquisition computer to a data server for accessibility and archival.
    The raw HYPACK navigation files are stored in separate directories indicating the acquisition Julian Day (JD206 through JD209), corresponding to July 25 - July 28, 2005. The filenames in each folder are in the format of linenumber_starttime.julianday. For example, filename 004_1434.207 represents HYPACK line number 004, start time 1434 and Julian Day 207. Times are recorded in UTC (Coordinate Universal Time).
    Filenames with the following format, 046A2028.206, indicate a rerun of a specific line. For example, 046A2028.206 represents HYPACK line number 46, 'A' signifies a rerun of line 46, 2028 is the start time (HHMM) and 206 is the Julian day.
    Filenames with the following format 25_1.206 represents planned line number 25_1 on Julian Day 206. There is no start time listed in the filenames for these files. An 'A' in the filename signifies a rerun of a specific line. For example, 25_1A.206 is a rerun of line 25_1 on Julian Day 206.
    Julian Days (205, 206 and 207) directory also contains a LOG file that lists the files recorded during that Julian day. Person who carried out this activity:
    Jane F. Denny
    U.S. Geological Survey
    Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    USA

    508-548-8700 x2311 (voice)
    508-457-2310 (FAX)
    jdenny@usgs.gov
    Date: 06-Apr-2017 (process 2 of 2)
    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
  3. What similar or related data should the user be aware of?
    Argue, Denise M., Kiah, Richard G., Denny, Jane F., Deacon, Jeffrey R., Danforth, William W., Johnston, Craig M., and Smagula, Amy P., 2007, Relation of Lake-Floor Characteristics to the Distribution of Variable Leaf Water-Milfoil in Moultonborough Bay, Lake Winnipesaukee, New Hampshire, 2005: Scientific Investigations Report 2007-5125, U.S. Geological Survey, Reston, Virginia.

    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?
    Navigation was acquired with Wide Area Augmentation System ( WAAS), which is accurate to + or - 1 to 2 meters, horizontally. Navigation data were acquired with a LGBX Pro receiver and logged to Hypack acquisition software.
  3. How accurate are the heights or depths?
    The Wide Area Augmentation System (WAAS) navigation was used to record vertical positioning of bathymetric soundings during data acquisition. WAAS is a GPS-based navigation system providing precision guidance to aircraft and provides vertical accuracies of + or - 1.5 meters. Higher precision vertical positioning (for example, RTK-navigation) was not available during this survey effort.
    Absolute water level values are reported as meters and referenced to Mean Lake Level, which is defined to be 504.32 meters above Mean Sea Level (NGVD29). Mean Lake Level measured during the USGS geophysical survey (July 24 - July 30, 2005) averaged 4 feet above Mean Lake Level as reported by the New Hampshire Department of Environmental Services (http://des.nh.gov/index.htm). This value (4 feet (1.3 meters)) is within the vertical accuracy of the survey. Therefore no additional offsets were applied to the data in order to reference to Mean Lake Level.
  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 2005-004-FA.
    Note: No LOG files exist for JD208 and JD209.
  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. The line numbers represented in the HYPACK files do not necessarily correspond to the sonar, bathymetry and seismic 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:
Data are 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 as the originator of the dataset.
  1. Who distributes the data set? (Distributor 1 of 1)
    Jane F. Denny
    U.S. Geological Survey
    Geologist
    384 Woods Hole Road
    Woods Hole, Massachusetts
    USA

    508-548-8700 x2311 (voice)
    508-457-2310 (FAX)
    jdenny@usgs.gov
  2. What's the catalog number I need to order this data set? The file 2005-004-FA_hypack.zip contains the raw HYPACK navigation files and the FGDC CSDGM metadata in the following formats: XML, HTML, FAQ 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 ANSI text HYPACK navigation files as well as the associated metadata files.

Who wrote the metadata?

Dates:
Last modified: 06-Apr-2017
Metadata author:
Jane F. Denny
U.S. Geological Survey
Geologist
384 Woods Hole Road
Woods Hole, Massachusetts
USA

508-548-8700 x2311 (voice)
508-457-2310 (FAX)
jdenny@usgs.gov
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Generated by mp version 2.9.36 on Thu Apr 06 15:05:03 2017