> 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 a wide variety
of observation types, so the attributes, like the variables, are
fields in a Matlab structure; and Matlab uses the '.' for field access
in structures. I can say wnde.standard_name = 'eastward_wind'
but wnde.cf.standard_name would mean something different.
This is probably more than anyone wants to know, and while
it's not an insurmountable problem, it would require a substantial
redesign; the work-around for me would be to not use the new
syntax, at least not in my own files. I'm assuming that I'm not
the only one who would have this problem.
Cheers - Nan
On 1/29/13 4:05 AM, David Hassell wrote:
> 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 '_at_' is used to
>> identify a variable as a function handle. There are work-arounds,
>> but they likely wouldn't add efficiency or elegance to our code.
> I have a grave feeling that I'm missing your point here, but the
> attribute names are just strings which need to be split according to a
> string-valued delimiter. There is no interaction with the syntax of
> the processing language, surely?
>
>> I agree with Roy that CF should be the default namespace in a CF
>> compliant file, and that this problem belongs to groups that are writing
>> extensions.
> I aggree with this, too.
>
> All the best,
>
> David
--
*******************************************************
* Nan Galbraith (508) 289-2444 *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 *
*******************************************************
Received on Tue Jan 29 2013 - 07:17:15 GMT
