ctd.read.ctd(file, type=NULL, columns=NULL, station=NULL,
monitor=FALSE, debug=getOption("oceDebug"), processingLog, ...)
read.ctd.sbe(file, columns=NULL, station=NULL, missing.value,
monitor=FALSE, debug=getOption("oceDebug"), processingLog, ...)
read.ctd.woce(file, columns=NULL, station=NULL, missing.value=-999,
monitor=FALSE, debug=getOption("oceDebug"), processingLog, ...)
read.ctd.odf(file, columns=NULL, station=NULL, missing.value=-999,
monitor=FALSE, debug=getOption("oceDebug"), processingLog, ...)NULL, then the first line is studied, in order to determine the
file type. If type="SBE19", then a Seabird 19 (or similar) CTD
format is assumed. If type="WOCE" then a
WOCE-exchange file is NULL, then read.ctd tries to infer column names from the
header. If a list, then it will be taken to be the list
of columns. The list must include "pressure", "temperature"
and either NA upon reading.TRUE to provide an indication
of line of data read. (This may be useful in debugging problems in
reading files that are misconfigured.)class "ctd", which is a
list with elements detailed below.
The most important elements are the station name and position, along
with the profile data that are contained in the data frame named data.
(Other elements in the list may be deleted in future versions of the
package, if they prove to be of little use in practice, or if they prove
to have been idiosyncratic features of the particular files used in
early development of oce.)data$pressure,
data$salinity, data$temperature, and
data$sigmatheta. ($\sigma_\theta$ is calculated
using swSigmaTheta.)oce format.read.ctd is a dispatch function that analyzes some of
the file contents, and then calls either read.ctd.sbe (for
files created by Seabird CTD instruments) or read.ctd.woce (for
files stored in the exchange format used by the World Ocean
Circulation Experiment.) The functions attempt to infer a wide range of meta-information from
file headers, but variations in these headers impose some limitations
on the process. For example, in the first file tested during
development, the sampling rate was written as * sample rate = 1
scan every 0.5 seconds, while the second test file had *
Real-Time Sample Interval = 0.125 seconds; dealing with such
variations is not easy. Similarly, the functions can be challenged in
parsing latitudes and longitudes in the wide variety of ways that
humans choose (decimal versus degree-minute-second, signed versus
"east" and "west", or "e" and "w".). The solution to the challenge is
simple: do a reasonable job with common file formats, and provide
users with the tools to correct (or insert) information that would
ideally be gleaned from the headers. This can be done by direct
manipulation of the entries in the object's metadata,
e.g. writing object@metadata$latitude <- 33 + 1/3.
It should be noted that different file types provide different
meta-information. For example, the WOCE exchange format binds
together the institute name and the initials of the chief scientist
into a single string that read.ctd cannot parse, so both
object@metadata$institute and object@metadata$scientist are
left blank for WOCE files.
The WOCE-exchange format is described at
The ODF format, used by the Canadian Department of Fisheries and Oceans, is
described at
read.ctd.odf. However, it was only a
starting point, for examination of data files revealed many variants in the
names of the data columns. If anything odd happens with ODF files (e.g. if
they cannot be plotted), the first thing to do is to reread the files with
debug=1, to see if column names were converted properly.
sealevel-class explains the
structure of sealevel objects, and also outlines the other functions
dealing with them.library(oce)
woce <- read.oce(
"http://woce.nodc.noaa.gov/woce_v3/wocedata_1/whp/exchange/example_ct1.csv")
plot(woce)Run the code above in your browser using DataLab