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.
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 18.104.22.168) was used to log these data.
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)
Are there legal restrictions on access or use of the data?
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.
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.
|Data format:||ASCII text files containing RAW HYPACK data. This zip file also includes associated metadata. in format ASCII (version HYPACK (version 22.214.171.124)) Text file Size: 625|
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.