Hi Phil,
while I agree with you that the only clean solution would have to be
defined in the netcdf API itself (not in CF), I don't think that groups are
what we are looking for here. This namespace thing is entirely related to
attributes, while groups are a variable concept. What would
Hello Nan, et al.,
Any of these special characters, other than the '_', would probably
cause problems for code that deals with NetCDF files. The '.' is
used in Matlab for access to structures, and the '@' is used to
identify a variable as a function handle. There are work-arounds,
but they
Hello Dennis
It should be noted however that dot in particular
causes problems for accessing remote datasets
through DAP because the dot character is used
in DAP constraints to specify fields inside
DAP Sequences or Structures or Grids.
I'm afraid that I'm not familiar with DAP. Do you mean
There is no interaction with the syntax of
the processing language, surely?
I checked to see if the Matlab NetCDF built-in routines would
allow attributes with dots in them, and they do; both global
and variable level atts can contain 'cf.'.
My code, though, has to be able to write files for
Hi Nan,
I agree with Roy that CF should be the default namespace in a
CF compliant file...
What does that mean?
Until we agree on the meaning and mechanism of namespace-handling within
CF-compliant files and software, I fear that such statements do not
provide much guidance at the
.
From: CF-metadata [cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Schultz,
Martin [m.schu...@fz-juelich.de]
Sent: 24 January 2013 18:54
To: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Usage of the 'Conventions' attribute (Nan
Galbraith)
Dear all
Roy et al.,
Martin's comments on namespace highlight a concern I
identified whilst doing the research for the SeaDataNet
specification. Several communities have added large numbers
of both global and variable attributes with no indication of
namespace. Not only does this make it
With respect to netcdf (at least the C version),
it is the case that these characters can appear
unescaped: _.@+-
It should be noted however that dot in particular
causes problems for accessing remote datasets
through DAP because the dot character is used
in DAP constraints to specify fields
Any of these special characters, other than the '_', would probably
cause problems for code that deals with NetCDF files. The '.' is used
in Matlab for access to structures, and the '@' is used to identify a
variable as a function handle. There are work-arounds, but they
likely wouldn't add
[ngalbra...@whoi.edu]
Sent: 28 January 2013 20:25
To: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Usage of the 'Conventions' attribute
Any of these special characters, other than the '_', would probably
cause problems for code that deals with NetCDF files. The '.' is used
in Matlab
Dear All,
Currently, the 'Conventions' attribute is restricted to be a global attribute.
There is currently a requirement to label multiple QC flag variables following
different conventions with their source convention and having the 'Conventions'
attribute as a variable attribute for these
I'm currently working with a group looking at profiling glider date a files
from multiple countries. We've identified a similar need to differentiate qc
tests on a per variable basis. I support the idea and the problem and I suppose
one solution is the conventions attribute.
Regards,
Derrick
Hi Roy -
As far as I know, there is nothing to prevent you from having
Conventions attributes other than the global one. Only the
global attribute is part of CF, but you could certainly implement
similar syntax in Conventions attributes for multiple variables.
Or are you looking for more of a
to Thursday. E-mail
response on other days is possible but not guaranteed!
-Original Message-
From: CF-metadata [mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Nan
Galbraith
Sent: 23 January 2013 15:16
To: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Usage of the 'Conventions
14 matches
Mail list logo
