| read.ctd.odv {oce} | R Documentation |
Read an ODV-type CTD File
read.ctd.odv(
file,
columns = NULL,
station = NULL,
missingValue,
deploymentType,
monitor = FALSE,
debug = getOption("oceDebug"),
processingLog,
...
)
file |
a connection or a character string giving the name of the file to
load. For |
columns |
an optional list that can be used to convert unrecognized
data names to resultant variable names. This is used only by
d <- read.ctd(f, columns=list(
salinity=list(name="SAL",
unit=list(unit=expression(),
scale="PSS-78"))))
would assign the |
station |
optional character string containing an identifying name or number for the station. This can be useful if the routine cannot determine the name automatically, or if another name is preferred. |
missingValue |
optional missing-value flag; data matching this value will
be set to |
deploymentType |
character string indicating the type of deployment. Use
|
monitor |
boolean, set to |
debug |
an integer specifying whether debugging information is
to be printed during the processing. This is a general parameter that
is used by many |
processingLog |
if provided, the action item to be stored in the log. This is typically only provided for internal calls; the default that it provides is better for normal calls by a user. |
... |
additional arguments, passed to called routines. |
read.ctd.odv() attempts to read files stored in ODV format,
used by some European data providers. This works only crudely, as of
2020-05-17. In particular, the translation from ODV parameter names to oce
names is very limited. For example, only one of the dozens of possibilities
for variants of phosphate is handled at the moment, and that is because
this was the variant supplied in a test file sent to the author on
2020-05-16. It is unlikely that full support of ODV files will
become available in read.ctd.odv(), given the lack of a comprehensive source
listing ODV variable names and their meanings, and low user
interest.
a ctd object. The details of the contents
depend on the source file. The metadata slot is particularly
variable across data formats, because the meta-information provided
in those formats varies so widely.
Dan Kelley
https://www.bodc.ac.uk/resources/delivery_formats/odv_format/ describes
the ODV format.
https://vocab.nerc.ac.uk/collection/P07/current/ may be worth consulting for variable names.
Other things related to ctd data:
CTD_BCD2014666_008_1_DN.ODF.gz,
[[,ctd-method,
[[<-,ctd-method,
as.ctd(),
cnvName2oceName(),
ctd-class,
ctd.cnv,
ctdDecimate(),
ctdFindProfiles(),
ctdRaw,
ctdRepair(),
ctdTrim(),
ctd_aml.csv,
ctd,
d200321-001.ctd,
d201211_0011.cnv,
handleFlags,ctd-method,
initialize,ctd-method,
initializeFlagScheme,ctd-method,
oceNames2whpNames(),
oceUnits2whpUnits(),
plot,ctd-method,
plotProfile(),
plotScan(),
plotTS(),
read.ctd.itp(),
read.ctd.odf(),
read.ctd.sbe(),
read.ctd.woce.other(),
read.ctd.woce(),
read.ctd(),
setFlags,ctd-method,
subset,ctd-method,
summary,ctd-method,
woceNames2oceNames(),
woceUnit2oceUnit(),
write.ctd()