Processed Continuous Resistivity Profiles from Cape Cod National Seashore, May 19, 2004

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. Bathymetry point data was collected with a separate system and logged as text files.

The data were transferred from the logging computer via AGISSAdmin software. The data files available for this day are chatham7*, chatham8*, chatham9*, chatha10*, chatha11*, chatha12*, chatha13*, chatha14*, chatha15*, chatha16*, chatha17*, and chatha18*.

The bathymetry text files needed to be merged with the GPS navigation files. The logging of the navigation files started at the same time as the logging of the resistivity files. Although the bathymetry data contains no time stamps, the assumption was made that the time span was the same as the navigation file. The bathymetry data was acquired in feet at a faster rate than the navigation data. An awk script was written to convert the bathymetry data to meters, pull the appropriate bathymetry point to match up with the navigation point, and output the format as SDDBT (the format that EarthImager expects). The points to pull was based on the assumption that the time span of navigation and bathymetry was the same, so took the total number of bathymetry points and divided it by the number of navigational fixes, and pulled the bathymetry point at that increment. Another awk script was written to merge the navigation data and bathymetry data into a single file.

$GPRMC lines with the GPS file that had bad time stamps or were otherwise corrupt were deleted.

The resistivity data were merged with the navigation data and linearized using AGI's Marine Log Manager software. (Note that the Marine Log Manager version is different than the software version of the AGISSAdmin software of which it is a part - although shipped together, the software is developed separately). In some instances, only a portion of the line was exported for processing. In particular, turns are removed before processing.

The file was then exported to a new STG file, and accompanying DEP file. The DEP file contains the distance along line and bathymetry values.

The DEP file was checked for anomalous bathymetry values, or duplicated distance along values, and those lines in the file were deleted.

EarthImager software does not require that a default resistivity value for the water column be supplied in the DEP file. If one is not supplied, then it calculates a value based on the first electrode pair. No instrument was available to measure the water resistivity, so this value was left blank.

EarthImager version 1.7.8 was used to process the data files. The *.ini file accompanying the results contains the parameters used during the processing. These parameters include: minimum voltage: 0.02; minimum abs(V/I): 2E-5; max repeat error: 3%; min apparent res: 0.03; max apparent res: 1000; max reciprocal error: 5%; remove spikes, robust model inversion; finite difference method; Cholesky decomposition; Dirichlet boundary condition; thickness incremental factor: 1.1; depth factor: 1.1; number of iterations: 8; stop criteria: max RMS 3%; error reduction 6%; L2Norm; CRP processing using a 65% overlap

The results of the processing are JPEG images of the resistivity profile (a short and extended version), and an XYZ file containing the distance along, depth, apparent resistivity (ohm-m). The JPEG files produced use a color scale that is based on the data from that particular file.

The XYZ output file was then loaded into Matlab, along with the depth information, to create a new JPEG image with the same color scale for all the data files. In this manner, the JPEG images can be compared directly. Care was taken to try to get the vertical and horizontal scales uniform as well, although this was not always possible due to Matlab limitations. These images reside in the "matlabimages" folder.

The XYZ output file was also loaded into Matlab with the DEP file so that those resistivity values in the water column could be removed. The extrapolated value at the sediment water interface was exported, as well as all the values in the original XYZ file below the DEP line. These new XYZ files are in the folder "trimxyz".

Edits to the metadata were made to fix any errors that MP v 2.9.36 flagged. This is necessary to enable the metadata to be successfully harvested for various data catalogs. In some cases, this meant adding text "Information unavailable" or "Information unavailable from original metadata" for those required fields that were left blank. Other minor edits were probably performed (title, publisher, publication place, etc.). Added online link to the data in the distribution section. Attempted to modify http to https where appropriate. Moved the minimal source information provided to make it the first process step. The distribution format name was modified in an attempt to be more consistent with other metadata files of the same data format. The metadata date (but not the metadata creator) was edited to reflect the date of these changes. The metadata available from a harvester may supersede metadata bundled within a download file. Compare the metadata dates to determine which metadata file is most recent.

Added keywords section with USGS persistent identifier as theme keyword.