Authentication working group
Thomas LOUBRIEU
Thomas.Loubrieu at ifremer.fr
Tue Jul 3 09:22:52 PDT 2007
Dear all,
I'm starting to study how I could extend our ocean in-situ observation
OPeNDAP server (DAP4COR at IFREMER/CORIOLIS :
http://www.ifremer.fr/dap4cor/) in order to serve datasets which are not
vertical profile measurements (XBT, CTD, profiling floats...).
These datasets may be :
- mooring (which may have different group of sensors at different depth
level)
- drifting buoys (which may also have different group of sensors at
different depth level, they also may have a drogue which gives
information on current at a given depth level), vessel measurements
along the track (thermosalinograph, ferry box)
Moreover some sensors measure multi-dimension parameters such as waves
spectrum or ADCP (acoustic doppler current profilers).
From the example for time series in DAPPER convention
(http://www.epic.noaa.gov/epic/software/dapper/dapperdocs/conventions/) :
Dataset {
Sequence {
Float32 lat;
Float32 lon;
Float32 elev;
Int32 _id;
Sequence {
Float32 visibility;
Float64 time;
Float32 max_wind_gust;
...
} time_series;
} location;
...
} gsod_time_series;
I understand that a mooring with air sensors and underwater sensors
(eventually at different depths) has to be divided into different
sequences (for depth level). It is not very convenient because then the
colocation of measurements will be lost.
But I am not sure if we should provide a different structure for each
instrument architecture (it would not be easy to read and to mix
measurements from different sources).
Do someone know where I can get further information on the issue ? Maybe
the DAPPER working group is the good place for that ? But there may be
interesting models outside the OPeNDAP community as well (WFS
observation profiles ?)
I do not plan to manage every kind of observation data now but I would
like to be sure the structures I will chose are part of a model with a
long term support.
Thanks for any information you could give to me,
Thomas
John Caron wrote:
> I've put a draft proposal for an "Authentication" working group at:
>
> http://docs.opendap.org/index.php/Authentication
> Please join if interested. (Contact James if you need a password)
>
> (I think "security" is probably better reserved for "server security
> issues", so i created a different working group name.)
>
> Since this seems to be the first, suggestions on the format or content
> of working group pages would be useful so that other groups can use it
> as a template.
>
More information about the Opendap-tech
mailing list