Polyline shapefile of ship tracklines along which continuous resistivity profiling data were collected in Greenwich Bay, Rhode Island, May 14 and 15, 2009, on U.S. Geological Survey Field Activity 2009-021-FA (Geographic, WGS84)

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

Frequently anticipated questions:


What does this data set describe?

Title:
Polyline shapefile of ship tracklines along which continuous resistivity profiling data were collected in Greenwich Bay, Rhode Island, May 14 and 15, 2009, on U.S. Geological Survey Field Activity 2009-021-FA (Geographic, WGS84)
Abstract:
As part of a larger investigation to understand groundwater-surface water interactions in Greenwich Bay, Rhode Island, a geophysical survey was conducted from a small research boat on 14-15 May 2009. The specific research objective was to gain an improved understanding of the role of direct groundwater discharge in delivery of excess nitrogen to the bay, which may have contributed to the development of low-oxygen conditions in waters of the bay and associated fish kills. Data collected in this survey included digital navigation information, continuous resistivity profiling (CRP) data, and point salinity measurements. The CRP method is a survey and data processing approach that is sensitive to differences in electrical properties of surface water and underlying porewater in sediments that have contrasting salinities. During the survey, Greenwich Bay salinity was approximately 27 ppm, so surface water would be expected to have low electrical resistivity (high conductivity), and any areas of active groundwater discharge from less salty aquifer sources would yield relatively higher resistivity values. This survey is identified as field activity 09021 (also referenced as 2009-021-FA) by the U.S. Geological Survey, Woods Hole, Massachusetts, and additional information is available from: https://cmgds.marine.usgs.gov/fan_info.php?fan=2009-021-FA.
  1. How might this data set be cited?
    Cross, VeeAnn A., 2018, Polyline shapefile of ship tracklines along which continuous resistivity profiling data were collected in Greenwich Bay, Rhode Island, May 14 and 15, 2009, on U.S. Geological Survey Field Activity 2009-021-FA (Geographic, WGS84): data release DOI:10.5066/F7DR2TSX, 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.

    Bratton, John F., and Cross, VeeAnn A., 2018, Continuous Resistivity Profiling Data and Associated Data from Greenwich Bay, Rhode Island collected in 2009, U.S. Geological Survey Field Activity 2009-021-FA: data release DOI:10.5066/F7DR2TSX, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Bratton, J.F., and Cross, V.A., 2018, Continuous resistivity profiling data and associated data from Greenwich Bay, Rhode Island collected in 2009, U.S. Geological Survey Field Activity 2009-021-FA: U.S. Geological Survey data release, https://doi.org/10.5066/F7DR2TSX.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -71.452350
    East_Bounding_Coordinate: -71.369483
    North_Bounding_Coordinate: 41.696383
    South_Bounding_Coordinate: 41.651083
  3. What does it look like?
    https://cmgds.marine.usgs.gov/data/field-activity-data/2009-021-FA/data/geophysics/navigation/2009_021_FA_res_lines.jpg (JPEG)
    Browse graphic of the tracklines along which CPR data were acquired.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 14-May-2009
    Ending_Date: 15-May-2009
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector 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. It contains the following vector data types (SDTS terminology):
      • String (47)
    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 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?
    2009-021-FA_res_lines
    Esri polyline shapefile (Source: Esri)
    FID
    Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: Esri) Coordinates defining the features.
    Id
    Automatically generated attribute. (Source: U.S. Geological Survey)
    Range of values
    Minimum:0
    Maximum:0
    Units:unitless
    line
    The alphanumeric name corresponding to the prefix of the GPS filename. This name reflects the name assigned to the line of data acquisition and incorporates modifiers to reflect modification of the GPS file if the GPS file was split into more than one part. A file split during acquisition may be named L19F2, while a file split during processing is name L18F1_part1, L18F1_part2 etc. (Source: U.S. Geological Survey) Character set.
    gpstime
    GPS time in the format HHMMSS. GPS time is +4 hours from local time during the survey. (Source: U.S. Geological Survey) Although the value is represented as a number in a text defined field, 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.
    depth_m
    Depth of the water below the fathometer at the start of the line measured 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. (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:9
    Units:meters
    temp_c
    Water temperature in degrees Celsius as recorded at the Lowrance fathometer transducer at the start of the line. (Source: U.S. Geological Survey)
    Range of values
    Minimum:14.1
    Maximum:16.6
    Units:degrees Celsius
    gpsdate
    The date of data acquisition in the format YYYYMMDD. (Source: 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 month, day, and year are broken out does the number have meaning.
    jul_date
    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. (Source: U.S. Geological Survey)
    Range of values
    Minimum:134
    Maximum:135
    Units:day
    streamer
    The CRP streamer length used for data collection. (Source: U.S. Geological Survey) Character set where 50-m indicates the 50-m streamer was used for data acquisition, and 100-m indicates the 100-m streamer was used for data acquisition.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • VeeAnn A. Cross
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov

Why was the data set created?

This polyline shapefile provides the boat's XY position, water depth, and water temperature during the collection of continuous resistivity profile data in Greenwich Bay, Rhode Island in May 2009. This shapefile also acts as an archive of this dataset.

How was the data set created?

  1. From what previous works were the data drawn?
    Raw CRP data (source 1 of 1)
    Bratton, John F., 2015, Raw CRP data.

    Type_of_Source_Media: disk
    Source_Contribution:
    The continuous resistivity profile (CRP) system used on this cruise was an AGI SuperSting marine system described at the website: www.agiusa.com/marinesystem.shtml. Two streamer systems were used during this field activity - a 50-m streamer and a 100-m streamer. The 50-m streamer has an 11 electrode array with electrodes spaced 5 meters apart. The 100-m streamer has an 11 electrode array with electrodes spaced 10 meters apart. In both cases the source electrodes are graphite, while the receiver electrodes are stainless steel. A dipole-dipole configuration was used for the data collection in which two fixed current electrodes are assigned with the measurement of voltage potential between electrode pairs in the remaining electrodes. The maximum depth below the water surface the streamer can reach is approximately 1/4 the streamer length. So for the 50-m streamer, maximum depth is about 12.5 meters while the 100-m streamer maximum depth is about 25 meters. Each line of data acquisition records several files. The two files necessary for processing are the *.stg and the *.gps file. The STG file contains the resistivity data, while the GPS file contains the navigation information. The navigation system used in concert with the CRP system is a Lowrance LMS-480M with an LGC-2000 GPS antenna and a 200 kHz fathometer transducer. The antenna and fathometer transducer were mounted on the starboard side of the boat. The streamer tow point was on the port side aft. The layback offset between the navigation antenna and the first electrode was 16.5 meters. This layback offset was not accounted for during data acquisition, so was entered during processing of the data. The approximately 2.5 m lateral offset between the streamer tow point and the navigation antenna is not accounted for. The Lowrance transducer also contains a temperature sensor that records temperature in degrees Celsius. For depth measurements, Lowrance indicates the speed of sound used by the system is 4800 feet/second, but depths are recorded in meters. Both the temperature and depth information are recorded in the logged GPS file. The CRP system images the subsurface electrical properties of an estuarine, riverine or lacustrine environment. Resistivity differences can be attributed to subsurface geology (conductive vs less conductive layers) and hydrogeologic conditions with fresh water exhibiting high resistivity and saline conditions showing low resistivity.
  2. How were the data generated, processed, and modified?
    Date: May-2009 (process 1 of 8)
    The data were transferred from the logging computer using AGISSAdmin software version 1.3.4.198. These files were then emailed from the field to the USGS office in Woods Hole in a single zip file. The data files included in this release are the *.crs, *.cmd, *.gps, and *.stg. The two files essential for processing are the GPS and STG files. The GPS file contains the navigation, and in the case of the Lowrance system also includes water depth and water temperature. The STG file contains the resistivity measurements from each of the electrodes. The CRS file contains the contact resistance readings. The CMD file contains the parameters for data collection. These last two files aren't necessary for data processing, but can be useful in terms of troubleshooting. The field collection and data transfer were done by Chuck Worley of the USGS. Person who carried out this activity:
    Charles Worley
    U.S. Geological Survey
    Physical Scientist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2250 (voice)
    (508) 457-2313 (FAX)
    cworley@usgs.gov
    Data sources used in this process:
    • Raw CRP data
    Date: May-2009 (process 2 of 8)
    First, the navigation in the GPS files was checked. One file - L18F1 - had several navigation gaps. This file was split into 3 parts effectively eliminating the navigation gaps. The gaps would cause problems in processing of the data. Additionally, the navigation in the GPS files was inspected visually. This was done by quickly parsing the GPS text files into comma-delimited text files with a header line, and then viewing the files in ArcMap 9.2. The AWK scripts used to parse the navigation was awkhold. The scripts used for data collection on May 14, 2009 are as follows.
    
    
    awkhold:
    
    BEGIN {
    FS = ","
    }
    {
    FS = ","
    ARGC = 2
    depth = -9999
    temp = -9999
    if (NR==1)
    	{
    	#printf("utctime, longitude, latitude, depth_m, temp_c, line\n")
    	}
    if ($1=="$GPRMC")
    	{
    	utctime = $2
    	latdeg = substr($4,1,2)
    	latmin = substr($4,3,6)
    	declat = latdeg + (latmin/60)
    	londeg = substr($6,1,3)
    	lonmin = substr($6,4,6)
    	declon = -1 * (londeg + (lonmin/60))
    	if (NR==1) {
    		holddepth = -9999
    		holdtemp = -9999
    		}
    	else {
    		printf("%s, %9.6f, %9.6f, %5.1f, %5.1f, %s\n", holdutctime, >holddeclon, holddeclat, holddepth, holdtemp, ARGV[2])
    	}
    	holdutctime = utctime
    	holddeclon = declon
    	holddeclat = declat
    	holddepth = -9999
    	holdtemp = -9999
    	}
    if ($1=="$SDDPT")
    	{
    	depthreal = $2
    	holddepth = depthreal
    	}
    if ($1=="$SDMTW")
    	{
    	tempreal = $2
    	holdtemp = tempreal
    	}
    }
    END {
    printf("%s, %9.6f, %9.6f, %5.1f, %5.1f, %s\n", holdutctime, holddeclon, holddeclat, >holddepth, holdtemp, ARGV[2])
    }
    
    
    This file was executed by a shell script to effectively batch process all the files in a single folder with the extension gps. The batch processing script was called dohold.
    
    
    dohold:
    
    files=`ls *.gps | cut -d. -f1`
    for file in $files
    do
    	awk -f awkhold $file.gps $file >> may14_09_gps.txt
    done
    
    
    Under Cygwin, all of the hold files were concatenated into a single comma-delimited text file and a header line added to the file. The header line added to the text file was: gpstime, longitude, latitude, depth_m, temp_c, line. Using ArcMap 9.2 - Tools - Add XY Data, the comma-delimited text file was added as an event theme to ArcMap. No erroneous points were detected.
    
    
    This processing step and all subsequent processing steps were performed by the same person - VeeAnn A. Cross. Person who carried out this activity:
    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov
    Data sources used in this process:
    • Raw CRP data
    Data sources produced in this process:
    • Modified (because the navigation was modified) Raw CRP data
    • may14_09_gpssplits.csv
    • may15_09_gps.csv
    Date: May-2009 (process 3 of 8)
    The text editor VI was used under Cygwin to add the following header line to the resulting text file:
    gpstime, longitude, latitude, depth_m, temp_c, line
    
    
    This text file was then imported to ArcMap 9.2 using Tools -AddXY Data. The X field is longitude, Y field is latitude, and the coordinate system as defined as WGS84. This "Event Theme" was converted to a shapefile by right-mouse clicking on the layer - Data - Export Data. Data sources used in this process:
    • may14_09_gpssplits.csv
    • may15_09_gps.csv
    Data sources produced in this process:
    • may14_09_gps_spl_pnts.shp
    • may15_09_gpspnts.shp
    Date: Jul-2013 (process 4 of 8)
    Using ArcMap 9.2, the extension VACExtras (version 2.05, a software package developed and used in Woods Hole, MA) was used to convert the point shapefile to a line shapefile. VACExtras uses the points to line tool to convert the points to polylines. The attribute "line" was used as the line value - the attribute that grouped points into lines. Additionally, the first occurrence of gpstime, depth_m and temp_c were carried over to the output file. Data sources used in this process:
    • may14_09_gps_spl_pnts.shp
    • may15_09_gpspnts.shp
    Data sources produced in this process:
    • may14_09_gps_spl_lns.shp
    • may15_09_gpspnts.shp
    Date: 2013 (process 5 of 8)
    Several additional attributes were added to the shapefile and populated in ArcMap 9.3.1. The attributes added were gpsdate, jul_date, streamer. For the May 14th data, these attributes were populated with the values 20090514, 134, 50-m. This reflects the date of data collection, the Julian day of data collection, and the streamer length of data collection. For the May 15th data, these attributes were populated with the values 20090515, 135, 100-m. Data sources produced in this process:
    • may14_09_gps_spl_lns.shp
    • may15_09_gpspnts.shp
    Date: 2013 (process 6 of 8)
    Using ArcMap 9.3.1, the individual polyline shapefiles were merged into a single shapefile. This was done using ArcToolbox - Data Management Tools - General - Merge. Data sources used in this process:
    • may14_09_gps_spl_lns.shp
    • may15_09_gpspnts.shp
    Data sources produced in this process:
    • res_lines_mergenav.shp
    Date: 2015 (process 7 of 8)
    Filename was changed to include the field activity number for publication purposes. Data sources used in this process:
    • res_lines_mergenav.shp
    Data sources produced in this process:
    • 2009-021-FA_res_lines.shp
    Date: 08-Sep-2020 (process 8 of 8)
    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?
    The navigation system used was a Lowrance 480M with an LGC-2000 Global Positioning System (GPS) antenna. The antenna was located 1.5 meters forward of the resistivity streamer tow point and directly above the fathometer transducer. The GPS is assumed to be accurate to within 10 meters.
  3. How accurate are the heights or depths?
    All bathymetry values were acquired by the 200 kHz Lowrance fathometer. The fathometer was mounted on the starboard side of the University of Rhode Island pontoon boat, 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. No tide corrections were performed.
  4. Where are the gaps in the data? What is missing?
    These polylines represent all the navigation for the CRP lines that are processed. There were no lines 1-4 as there were battery problems during data collection. Line 18 had to be split into three separate parts to be processed due to gaps in the navigation.
  5. How consistent are the relationships among the observations, including topology?
    Each file was looked at individually, but the files as a collection were handled in the same manner.

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:
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.
  1. Who distributes the data set? (Distributor 1 of 1)
    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2251 (voice)
    (508) 457-2310 (FAX)
    vatnipp@usgs.gov
  2. What's the catalog number I need to order this data set? The 2009-021-FA_res_lines.zip file contains the 2009-021-FA_res_lines polyline shapefile and its components, a browse graphic (2009_021_FA_res_lines.jpg) as well as 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?
    The user must be capable of extracting the data from the zip file, reading the shapefile format. This shapefile filename starts with a number and has dashes in it. This filename may not work with some geoprocessing or ArcPy scripts and may need to be renamed.

Who wrote the metadata?

Dates:
Last modified: 08-Sep-2020
Metadata author:
VeeAnn A. Cross
U.S. Geological Survey
Marine Geologist
384 Woods Hole Rd.
Woods Hole, MA

(508) 548-8700 x2251 (voice)
(508) 457-2310 (FAX)
vatnipp@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/2009_021_fa/2009-021-FA_res_lines_meta.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:20:14 2021