VeeAnn A. Cross
2014
JD103HYPACK.SHP: Parsed HYPACK navigation from April 13, 2010 of U.S. Geological Survey Field Activity 2010-006-FA in Indian River Bay, Delaware (Geographic, WGS 84)
1
vector digital data
Open-File Report
2011-1039
Woods Hole Coastal and Marine Science Center, Woods Hole, MA
U.S. Geological Survey, Coastal and Marine Geology Program
http://pubs.usgs.gov/of/2011/1039/data/navigation/hypack/processed/jd103hypack.zip
http://pubs.usgs.gov/of/2011/1039/html/ofr2011-1039-catalog.html
V.A. Cross
J.F. Bratton
H.A. Michael
K.D. Kroeger
A. Green
E. Bergeron
2014
Continuous Resistivity Profiling and Seismic-Reflection Data Collected in April 2010 from Indian River Bay, Delaware
1
Open-File Report
2011-1039
Reston, VA
U.S. Geological Survey
http://pubs.usgs.gov/of/2011/1039/
http://dx.doi.org/10.3133/ofr20111039
A geophysical survey to delineate the fresh-saline groundwater interface and associated sub-bottom sedimentary structures beneath Indian River Bay, Delaware, was carried out in April 2010. This included surveying at higher spatial resolution in the vicinity of a study site at Holts Landing, where intensive onshore and offshore studies were subsequently completed. The total length of continuous resistivity profiling (CRP) survey lines was 145 kilometers (km), with 36 km of chirp seismic lines surveyed around the perimeter of the bay. Medium-resolution CRP surveying was performed using a 50-meter streamer in a bay-wide grid. Results of the surveying and data inversion showed the presence of many buried paleochannels beneath Indian River Bay that generally extended perpendicular from the shoreline in areas of modern tributaries, tidal creeks, and marshes. An especially wide and deep paleochannel system was imaged in the southeastern part of the bay near White Creek. Many paleochannels also had high-resistivity anomalies corresponding to low-salinity groundwater plumes associated with them, likely due to the presence of fine-grained estuarine mud and peats in the channel fills that act as submarine confining units. Where present, these units allow plumes of low-salinity groundwater that was recharged onshore to move beyond the shoreline, creating a complex fresh-saline groundwater interface in the subsurface. The properties of this interface are important considerations in construction of accurate coastal groundwater flow models. These models are required to help predict how nutrient-rich groundwater, recharged in agricultural watersheds such as this one, makes its way into coastal bays and impacts surface water quality and estuarine ecosystems. For more information on the survey conducted for this project, see http://woodshole.er.usgs.gov/operations/ia/public_ds_info.php?fa=2010-006-FA.
The purpose of this point shapefile is to provide the parsed data from the raw HYPACK (VER 9.0.5.17) navigation files. The parsed data will contain latitudes, longitudes, and depth values. The depth values are particularly necessary to fill depth data gaps in the continuous resistivity profile GPS data.
20100413
ground condition
None planned
-75.203600
-75.062150
38.618983
38.566450
General
U.S. Geological Survey
USGS
Coastal and Marine Geology Program
CMGP
Woods Hole Coastal and Marine Science Center
WHCMSC
Field Activity Number 2010-006-FA
Info Bank ID K-6-10-DL
navigation
bathymetry
R/V Knob
Lowrance GPS
HYPACK
point shapefile
Open-file Report 2011-1039
ISO 19115 Topic Category
elevation
location
oceans
oceans and estuaries
oceans and coastal
General
North America
North Atlantic Ocean
United States
Delaware
Indian River Bay
Indian River Inlet
Holts Landing
Piney Neck
Sussex County
Rosedale Beach
None.
The 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.
VeeAnn A. Cross
U.S. Geological Survey
Marine Geologist
mailing and physical address
Woods Hole Coastal and Marine Science Center
384 Woods Hole Rd.
Woods Hole
MA
02543-1598
(508) 548-8700 x2251
(508) 457-2310
vatnipp@usgs.gov
http://pubs.usgs.gov/of/2011/1039/data/navigation/hypack/processed/jd103hypack.gif
Thumbnail GIF image showing HYPACK navigation points collected April 13, 2010. The coastline is included for spatial reference.
GIF
Microsoft Windows Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.4095
All of the HYPACK files were handled in the same manner.
This point shapefile represents every location fix and accompanying depth parsed from the raw HYPACK ASCII files.
The navigation system used was a Lowrance 480M with an LGC-2000 Global Positioning System (GPS) antenna. The antenna was located directly above the fathometer transducer mount point. GPS data are assumed to be accurate within 10 meters on this survey.
All bathymetry values were acquired by the 200 kHz Lowrance fathometer. The fathometer was mounted on the starboard side of the R/V Knob, directly below the GPS antenna. The Lowrance manufacturer indicates the speed of sound used by the system to calculate depth is 4800 feet/second. The depth values are not corrected for the approximately 0.2 m transducer draft. All depth values are assumed to be accurate to within 1 meter.
All the ASCII HYPACK (VER 9.0.5.17) navigation files collected on April 13, 2010 were placed in their own folder on the computer. Each file has the following filename convention: LLL_TTTT.RAW where LLL is the line number and TTTT is the start time (UTC) of data collection in the format HHMM. In order to parse these files to extract navigation and depth information, two scripts were run under a Cygwin operating system. The first script "donav" is an executable script that cycles through all the *.raw files in the folder and calls another script to extract particular lines of information.
>donav:
>files=`ls *.RAW | cut -d. -f1`
>for file in $files
>do
> awk -f awkit $file.RAW > $file.navdep
>done
The AWK script "awkit" simply extracts any line of information in the HYPACK file that contains either the string "GPGGA" or "SDDBT" and writes this information to a new file with the extension navdep.
>awkit:
>{
>if ($0 ~ /GPGGA|SDDBT/) {
> print $0
> }
>}
This process step and all subsequent process steps were performed by the same person - VeeAnn A. Cross.
*.RAW
201004
*.navdep
VeeAnn A. Cross
U.S. Geological Survey
Marine Geologist
mailing and physical address
Woods Hole Coastal and Marine Science Center
384 Woods Hole Rd.
Woods Hole
MA
02543-1598
(508) 548-8700 x2251
(508) 457-2310
vatnipp@usgs.gov
With the particular lines of interest extracted from the original HYPACK files, additional scripts were run to extract the specific information of interest. The next two scripts run are doholdhypack and awkholdhypack. The doholdhypack is a shell script run under Cygwin which cycles through all the *.navdep files in the folder and calls the awkholdhypack AWK script to process the file, with the results output to *.holdhypack. Of note, if the SDBPT record does not contain a depth value, a value of -9999 is written to the output file - acting as a nodata value.
>doholdhypack:
>files=`ls *.navdep | cut -d. -f1`
>for file in $files
>do
> awk -f awkholdhypack $file.navdep > $file.holdhypack
>done
>awkholdhypack:
>BEGIN {
>FS = ","
>}
{
>FS = ","
>depth = -9999
>if ($1 ~ /GPGGA/)
> {
> utctime = $2
> latdeg = substr($3,1,2)
> latmin = substr($3,3,6)
> declat = latdeg + (latmin/60)
> londeg = substr($5,1,3)
> lonmin = substr($5,4,6)
> declon = -1 * (londeg + (lonmin/60))
> if (NR==1) {
> holddepth = -9999
> }
> else {
> printf("%s, %9.6f, %9.6f, %5.1f\n", holdutctime, holddeclon, holddeclat, holddepth)
> }
> holdutctime = utctime
> holdutcdate = utcdate
> holddeclon = declon
> holddeclat = declat
> holddepth = -9999
> }
>if ($1 ~ /SDDBT/)
> {
> if ($4 != "")
> {
> depthreal = $4
> holddepth = depthreal
> }
> else
> {
> depthreal = -9999
> holddepth = -9999
> }
> }
>}
>END {
>printf("%s, %9.6f, %9.6f, %5.1f\n", holdutctime, holddeclon, holddeclat, holddepth)
>}
*.navdep
201004
*.holdhypack
With each individual HYPACK file processed, I want to concatenate all the individual files on a given day into a single file. Because the file naming convention starts with the line number, and surveying wasn't done in numerical order of lines, I have to look at the order the files were acquired. The time is in the filename, but another additional file written during acquisition was a LOG file containing the order of the lines. By editing this file and converting it to a shell script, the individual files can be concatenated in chronological order. On April 13, 2010, the LOG file was RAW0413.LOG. This file, copied to a new file "catit", edited, converted to an executable file, and run under Cygwin successfully concatenated the files.
catit:
>cat 201_1213.holdhypack \
>202_1414.holdhypack \
>203_1441.holdhypack \
.204_1600.holdhypack > jd103hypack.csv
*.holdhypack
201004
jd103hypack.csv
Using VI editor, under Cygwin, the resulting CSV file was edited to add the header line "gpstime, longitude, latitude, depth_m". With this header line added, the CSV file can be imported to ArcMap 9.2 as an event theme using Tools - Add XY data and defining the projection as Geographic, WGS84. This event theme is then converted to a point shapefile by right mouse click - data - export and saving the shapefile as jd103hypack.shp.
jd103hypack.csv
201004
jd103hypack.shp
The table of this shapefile was edited in ArcMap 9.2 to add two additional attributes: gpsdate and jday.
jd103hypack.shp
201004
jd103hypack.shp
Vector
Entity point
26688
0.000001
0.000001
Decimal degrees
D_WGS_1984
WGS_1984
6378137.000000
298.257224
Local surface
0.1
meters
Attribute values
jd103hypack
ESRI point shapefile
ESRI
FID
Internal feature number.
ESRI
Sequential unique whole numbers that are automatically generated.
Shape
Feature geometry.
ESRI
Coordinates defining the features.
gpstime
GPS time in the format HHMMSS. GPS time is +4 hours from local time during the survey.
U.S. Geological Survey
Although the value is represented as a number, the number as a whole doesn't have a particular meaning. Only when the individual parts for hours, minutes, and seconds are broken out does the number have meaning.
longitude
Longitude position of the point (decimal degrees, WGS84)
U.S. Geological Survey
-75.2036
-75.06215
decimal degrees
latitude
Latitude position of the point (decimal degrees, WGS84)
U.S. Geological Survey
38.56645
38.618983
decimal degrees
depth_m
Depth of the water below the fathometer in meters recorded by the ship's fathometer/navigation system. Datum is local surface (no tides taken into account). A value of -9999 indicates no data.
U.S. Geological Survey
0.2
24.2
meters
gpsdate
The date recorded in the GPS navigation in the format DDMMYY. Because of the time offset from local time, this date could actually be different than the local acquisition date.
U.S. Geological Survey
Although the value is represented as a number, the number as a whole doesn't have a particular meaning. Only when the individual parts for day, month, and year are broken out does the number have meaning.
jday
This number represents the Julian day of data collection based on the GPS day. Julian day is the integer number representing the interval of time in days since January 1 of the year.
U.S. Geological Survey
103
103
days
VeeAnn A. Cross
U.S. Geological Survey
Marine Geologist
mailing and physical address
Woods Hole Coastal and Marine Science Center
384 Woods Hole Rd.
Woods Hole
MA
02543-1598
(508) 548-8700 x2251
(508) 457-2310
vatnipp@usgs.gov
Downloadable Data
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.
Shapefile
ArcGIS 9.2
This WinZip (v. 14) file contains the point shapefile as well as the associated metadata files.
0.54 MB
http://pubs.usgs.gov/of/2011/1039/data/navigation/hypack/processed/jd103hypack.zip
http://pubs.usgs.gov/of/2011/1039/html/ofr2011-1039-catalog.html
http://dx.doi.org/10.3133/ofr20111039
None.
This zip file contains data available in ESRI point shapefile format. The user must have software capable of uncompressing the zip file and reading/displaying the shapefile.
20140630
VeeAnn A. Cross
U.S. Geological Survey
Marine Geologist
mailing and physical address
Woods Hole Coastal and Marine Science Center
384 Woods Hole Rd.
Woods Hole
MA
02543-1598
(508) 548-8700 x2251
(508) 457-2310
vatnipp@usgs.gov
FGDC Content Standards for Digital Geospatial Metadata
FGDC-STD-001-1998
local time
http://www.esri.com/metadata/esriprof80.html
ESRI Metadata Profile