Hi Sara:
Thanks for adding your example to the mix. This appears to be a timeseries at a
single x,y location with all the measurements on single, but different levels
(?)
Because these are single level, I would be inclined to use a variation of the station
representation. One possibility is
Hi Roy, Nan:
Let me try to see where the mapping between the two classifications is
currently at:
Lowry, Roy K wrote:
Dear All,
I come from Nan's community with the added complication of exposure to CSML
through working with NDG. From this position in BODC we have developed a
collection
.
From: Richard Signell [rsign...@gmail.com]
Sent: 15 November 2009 15:00
To: Lowry, Roy K
Cc: ngalbra...@whoi.edu; cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] CF point observation Conventions ready for review
Roy,
I come from this community also
Hmm, I think this is an unfortunate choice of terms - we make a fairly
clear distinction between profile data and station data - but I don't think
it's just a local semantic problem.
While I realize that the storage for multiple profiles and multiple-depth
time series data are similar, I
Nan Galbraith wrote:
Hi John -
This file has a single variable from a single mooring deployment. A
complete mooring deployment file would have 3 (or 4) depth coordinate
variables, one each for temperature, velocity, and salinity measurements,
since we measure temperature everywhere and add
Dear Nan and John:
I've been monitoring this conversation for just a short period. So I
apologize ahead for chiming in so late in the game.
It is very important for observational data model to represent the
actual system that is deployed. The point that Nan and others have
raised is a
Steve Hankin wrote:
Its approaching two weeks (Oct 27) since a revised CF point
observation Conventions proposal was made:
https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions
https://cf-pcmdi.llnl.gov/trac/ticket/37
Given the complexity of the proposal, it would be
Nan Galbraith wrote:
Steve Hankin wrote:
Its approaching two weeks (Oct 27) since a revised CF point
observation Conventions proposal was made:
https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions
https://cf-pcmdi.llnl.gov/trac/ticket/37
Given the complexity of the
Nan-
Alternatively, it seems like you could use a stationTimeSeries and just
have different locations (stations) to indicate the different depths.
The x/y would be the same, but the z would be different for each
location. It sounds like you are interested in a time series at each
depth
Hi All,
Its approaching two weeks (Oct 27) since a revised CF point observation
Conventions proposal was made:
https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions
https://cf-pcmdi.llnl.gov/trac/ticket/37
Given the complexity of the proposal, it would be helpful if
I have complete a new version of the CF point observation Conventions at:
https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions
Discussion is at:
https://cf-pcmdi.llnl.gov/trac/ticket/37
I have incorporated various feedback from the past year, and made a
preliminary
11 matches
Mail list logo
