[CF-metadata] Pre-proposal for "charset"
j.m.gregory at reading.ac.uk
Fri Feb 24 08:56:33 MST 2017
I must have overlooked that example, sorry. Please could you spell it out for
----- Forwarded message from David Hassell <david.hassell at ncas.ac.uk> -----
> Date: Fri, 24 Feb 2017 08:38:13 +0000
> From: David Hassell <david.hassell at ncas.ac.uk>
> To: Jonathan Gregory <j.m.gregory at reading.ac.uk>
> CC: CF Metadata <cf-metadata at cgd.ucar.edu>
> Subject: Re: [CF-metadata] Pre-proposal for "charset"
> I think that Jonathan is right about the CF-compliance of the example DSG
> file. I think that the confusion still exists for "proper" data variables,
> though. Are the Argo profile float profiles (single char data that are
> stored in char arrays that Bob mention earlier in the thread) data
> variables, or metadata to other data variables?.
> On 23 February 2017 at 16:22, Jonathan Gregory <j.m.gregory at reading.ac.uk>
> > Dear Bob
> > > CF section 9.5 says: "The variable carrying the cf_role attribute may
> > > have any data type."
> > > And that makes sense, because some profile_id might be an integer and
> > > theoretically could be a single char.
> > >
> > >> Yes, I agree that on the basis of netCDF
> > >> alone
> > >> you can't tell whether it's a string or a 10-char array. However, the
> > >> cf_role
> > >> is a string-valued attribute, according to the CF convention, so it must
> > >> be a
> > >> string. I expect that for contents of netCDF files that follow the CF
> > con-
> > >> vention this ambiguity shouldn't arise - but if there are cases where it
> > >> does
> > >> we should consider them.
> > Sorry. Being in a hurry, because you mentioned cf_role, I assumed you were
> > referring to the attribute, rather than the variable which has that
> > attribute.
> > Looking again at the example you sent, I'd say that this file is not a
> > proper
> > CF DSG file; it contains a number of variables which could be individual
> > timeseries, but they haven't been combined into a single data variable so
> > there is no element (or "station") dimension. The "timeseries" variable
> > which
> > you asked about isn't referred to by any of the data variables. I agree
> > that
> > its function is unclear, but I would say it's not CF-compliant anyway, so
> > CF
> > doesn't need to provide an answer to this ambiguity. The file should look
> > like Example H3, H6 or H7 of the CF document.
> > Best wishes
> > Jonathan
> > _______________________________________________
> > CF-metadata mailing list
> > CF-metadata at cgd.ucar.edu
> > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
> David Hassell
> National Centre for Atmospheric Science
> Department of Meteorology, University of Reading,
> Earley Gate, PO Box 243, Reading RG6 6BB
> Tel: +44 118 378 5613
----- End forwarded message -----
More information about the CF-metadata