[CF-metadata] Best representation of wire-crawling profiler

Signell, Richard rsignell at usgs.gov
Tue Feb 28 12:18:54 MST 2017

CF Folks,

Okay, with help from the ERDDAP community
I think I figured this out:

The solution would be to use nominal "time(profiles)" and
"precise_time(obs)".   So we would write something like


with both "time" and "precise_time", but instead of using the
multidimensional representation, use the ragged representation, like this


So in addition to "precise_time(obs)" we would also have data variables
like "temperature(obs)".


On Tue, Feb 28, 2017 at 7:27 AM, Signell, Richard <rsignell at usgs.gov> wrote:

> CF Folks,
> What would be the best DSG featureType to represent a wire-crawling
> sensor that has a fixed lon,lat location, but non-uniform depth
> interval as it goes up and down, and takes enough time that the
> profile might not be accurately represented with a single time value?
> On this ERDDAP site the featureType is "trajectory":
> http://ooi-data.marine.rutgers.edu/erddap/info/
> CP04OSPM-WFP01-04-FLORTK000-flort_kn_stc_imodem_
> instrument-telemetered-d0005/index.html
> and I'm wondering if that's the best, or whether "timeSeriesProfile"
> would be better, written as as ragged array with profile_index?
> Certainly if we assigned a "nominal time" for each cast, then it would
> clearly be representable as timeSeriesProfile, but it's not clear to
> me that it meets the CF conventions if time varies within the cast.
> There would be value in allowing the time-varying values within the
> profile, but also labeling/indexing the profiles,  so that people
> could easily extract, say, all the "down" profiles, excluding the "up"
> (or vice versa).
> Thanks,
> Rich
> --
> Dr. Richard P. Signell   (508) 457-2229
> USGS, 384 Woods Hole Rd.
> Woods Hole, MA 02543-1598

Dr. Richard P. Signell   (508) 457-2229
USGS, 384 Woods Hole Rd.
Woods Hole, MA 02543-1598
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20170228/ae736d8f/attachment.html>

More information about the CF-metadata mailing list