Continuous Resistivity Profile Tracklines of Data Collected in 2004 in the Neuse River, North Carolina

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

Frequently-anticipated questions:

What does this data set describe?

Title:
Continuous Resistivity Profile Tracklines of Data Collected in 2004 in the Neuse River, North Carolina
Abstract:
The Neuse River Estuary in North Carolina is a broad, V-shaped water body located on the southwestern end of Pamlico Sound. This estuary suffers from severe eutrophication for which several water quality models have recently been developed to aid in the management of nutrient loading to the estuary. In an effort to help constrain model estimates of the fraction of nutrients delivered by direct ground-water discharge, continuous resistivity profile (CRP) measurements were made during the spring of 2004 and 2005. CRP is used to measure electrical resistivity of sediments, a property that is sensitive to difference in salinity of submarine ground water. The 2004 and 2005 surveys used floating resistivity streamers of 100 m and 50 m respectively. The depth penetration of the streamers is approximately 20% of the streamer length which translates to approximately 20-25 m with the 100 m streamer and 12-14 m with the 50 m streamer. These data were processed using AGI's EarthImager 2D software. CRP data enables the mapping of the extent and depth of the fresher ground water within the estuary.
  1. How should this data set be cited?

    Bratton, John F. , and Cross, VeeAnn A. , 2005, Continuous Resistivity Profile Tracklines of Data Collected in 2004 in the Neuse River, North Carolina:.

    Online Links:

    This is part of the following larger work.

    Cross, VeeAnn A. , Bratton, John F. , Bergeron, Emile, Meunier, Jeff K. , Crusius, John, and Koopmans, Dirk, 2005, Continuous Resistivity Profiling Data from the Upper Neuse River Estuary, North Carolina, 2004-2005: Open-File Report 2005-1306, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Science Center, Woods Hole, MA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -76.984117
    East_Bounding_Coordinate: -76.713317
    North_Bounding_Coordinate: 35.055067
    South_Bounding_Coordinate: 34.938517

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 19-Apr-2004
    Ending_Date: 23-Apr-2004
    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 (23)

    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.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    restracklines_04

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    ID

    LINENAME
    Prefix of the filename used during data acquisition. (Source: Technician.)

    character set

    GPSTIME
    GPS time for the start of the trackline. (Source: Data processor.)

    Range of values
    Units:Time in hr:min:sec

    DATESTR
    A numeric string representing the date the data was acquired as recorded by the GPS. (Source: Data processor.)

    numeric set representing the data in the form ddmmyr

    LENGTH
    Length in meters of the complete trackline based on UTM, Zone18, NAD83 projection. (Source: Computer calculated.)

    Range of values
    Minimum:666.349
    Maximum:43483.078
    Units:meters

    SPLITPART
    Prefix filename assigned to the datafile if the STG file was split. This value is the same as Linename if no split occurred. (Source: Data processor.)

    character set

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?

    VeeAnn A. Cross
    U.S. Geological Survey
    Marine Geologist
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

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

Why was the data set created?

This shapefile is provided to show the tracklines were continuous resistivity profile data were collected.

How was the data set created?

  1. From what previous works were the data drawn?

    (source 1 of 1)
    Source_Contribution:
    These data were acquired with an AGI SuperSting Marine system that is described at the website: www.agiusa.com/marinesystem.shtml. The particular system used for this acquisition was an 11 stainless steel electrode array with electrodes spaced 10 meters apart. A dipole-dipole configuration was used for the data collection in which two fixed current electrodes are assigned with the measurement of voltage potentials between electrode pairs in the remaining electrodes. Each line of data acquisition records several files. The two files necessary for processing are the *.stg and *.gps file. The STG file contains the resistivity data, while the GPS file contains the navigation information.

  2. How were the data generated, processed, and modified?

    (process 1 of 6)
    The GPS files were processed using an AWK script to parse out the navigational information from the $GPRMC string and concatenated into a single file.

    Data sources used in this process:

    • *.gps

    Data sources produced in this process:

    • allgps.txt

    (process 2 of 6)
    This comma delimited text file was then imported as a table into ArcView 3.3.

    Data sources used in this process:

    • allgps.txt

    (process 3 of 6)
    The table was then added as an event theme into ArcView.

    (process 4 of 6)
    An avenue script (pnts2lines.ave) was run that converted the event theme to a polyline shapefile. The unique attribute "Linename" was used to generate a separate record for each individual acquisition line.

    Data sources produced in this process:

    • allgps_lns.shp

    (process 5 of 6)
    Lines for which there was no valid resistivity data were deleted.

    (process 6 of 6)
    The shapefile was loaded into ArcMap v9.0 and resistivity lines that were split for processing purposes were split with the editor based on distance along line. This was done so that a direct correlation between processed line JPEG image and navigation position could be determined.

    Data sources used in this process:

    • allgps_lns.shp

    Data sources produced in this process:

    • restracklines_04.shp

  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?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?

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 U.S. Geological Survey must be referenced as the originator of the dataset in any future products or research derived from these data.

  1. Who distributes the data set? (Distributor 1 of 1)

    John F. Bratton
    U.S. Geological Survey
    384 Woods Hole Rd.
    Woods Hole, MA 02543-1598

    (508) 548-8700 x2254 (voice)
    (508) 457-2310 (FAX)

  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    These data were prepared by an agency of the United States Government. Neither the United States government nor any agency thereof, nor any of their employees, make any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed in this report, or represents that its use would not infringe privately owned rights. Reference therein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States government or any agency thereof. Any views and opinions of authors expressed herein do not necessarily state or reflect those of the United States government or any agency thereof. Although all data published in this report have been used by the USGS, no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and related materials and/or the functioning of the software. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of this data, software, or related materials.

  4. How can I download or order the data?

Who wrote the metadata?

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

(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)
Metadata extensions used:

Generated by mp version 2.8.6 on Tue Sep 13 12:40:19 2005