Hello Roy,
The text at
http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#long-name
doesn't include any mandatory circumstances, as I read it:
*"For backwards compatibility with COARDS this attribute is optional. But
it is highly recommended that either this or the standard_name attribute
defined in the next section be provided to make the file self-describing.
If a variable has no long_name attribute then an application may use, as a
default, the standard_name if it exists, or the variable name itself."*
What do you think?
All the best,
David
On Wed, 13 Mar 2019 at 10:29, Lowry, Roy K. <rkl at bodc.ac.uk> wrote:
> Dear David,
>
> My understanding is that the long_name attribute is mandatory, not just
> highly recommended, if there is no standard_name attribute.
>
> Cheers, Roy.
>
> I have now retired but will continue to be active through an Emeritus
> Fellowship using this e-mail address.
>
> ------------------------------
> *From:* CF-metadata <cf-metadata-bounces at cgd.ucar.edu> on behalf of David
> Hassell <david.hassell at ncas.ac.uk>
> *Sent:* 13 March 2019 09:53
> *To:* Klaus Zimmermann
> *Cc:* CF Metadata
> *Subject:* Re: [CF-metadata] Addition of HFC standard names
>
> Hello Klaus,
>
> You are indeed correct - the CF "long_name" attribute contains a long
> descriptive name that is non-standardised. It is optional, though its use
> is highly recommended if there is no standard name.
>
> Projects such as CMIP may, and do, insist on particular long names, but
> that is entirely outside of the CF conventions. The description of a
> standard name in the official table (e.g. "Mole fraction" is used in the
> construction "mole_fraction_of_X_in_Y", where X, .....") provides the
> precise definition of the quantity, but is not intended to be used as a
> long name in netCDF datasets.
>
> All the best,
>
> David
>
> On Wed, 13 Mar 2019 at 09:33, Klaus Zimmermann <klaus.zimmermann at smhi.se>
> wrote:
>
> Good morning,
>
> just a technical clarification: long names are not standardized within
> cf, correct?
>
> Indeed, typical long names don't follow the snake_case convention, but
> are rather more free-form and human readable/understandable. They are
> chosen by the user, often giving information beyond the standard names.
>
> Examples from CMIP6 (Omon table, variables tos and tosga):
> tos:
> - standard name: sea_surface_temperature
> - long name: Sea Surface Temperature
> tosga:
> - standard name: sea_surface_temperature
> - long name: Global Average Sea Surface Temperature
>
> Cheers
> Klaus
>
>
> On 13/03/2019 10:11, Dan Say wrote:
> > Good morning,
> >
> >
> > I am happy to go with the IUPAC names if needs be however, hfc is
> > standard nomenclature and I would have thought the most likely term to
> > be searched. I also note that there are already standard names for
> > several HCFCs and CFCs, for which the standard names are
> > 'mole_fraction_of_cfc11_in_air' etc. Nevertheless, see below a list of
> > the requested standard/long names and definitions, using both HFC and
> > IUPAC nomenclature. I am happy for you to choose which ones we use,
> > please advise.
> >
> >
> > *HFC nomenclature:*
> >
> >
> > Standard name: mole_fraction_of_hfc134a_in_air
> >
> > Long name: mole_fraction_of_hfc134a_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y. The
> > IUPAC name for hfc134a is 1,1,1,2-tetrafluoroethane.
> >
> >
> > Standard name: mole_fraction_of_hfc143a_in_air
> >
> > Long name: mole_fraction_of_hfc143a_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y. The
> > IUPAC name for hfc143a is 1,1,1-trifluoroethane.
> >
> >
> > Standard name: mole_fraction_of_hfc125_in_air
> >
> > Long name: mole_fraction_of_hfc125_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y. The
> > IUPAC name for hfc125 is 1,1,1,2,2-pentafluoroethane.
> >
> >
> > Standard name: mole_fraction_of_hfc152a_in_air
> >
> > Long name: mole_fraction_of_hfc152a_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y. The
> > IUPAC name for hfc152a is 1,1-difluoroethane.
> >
> >
> > Standard name: mole_fraction_of_hfc32_in_air
> >
> > Long name: mole_fraction_of_hfc32_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y. The
> > IUPAC name for hfc32 is difluoromethane.
> >
> >
> > Standard name: mole_fraction_of_hfc23_in_air
> >
> > Long name: mole_fraction_of_hfc23_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y. The
> > IUPAC name for hfc23 is trifluoromethane.
> >
> >
> >
> >
> >
> > *IUPAC nomenclature:*
> >
> >
> > Standard name: mole_fraction_of_1,1,1,2-tetrafluoroethane_in_air
> >
> > Long name: mole_fraction_of_1,1,1,2-tetrafluoroethane_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y.
> > 1,1,1,2-tetrafluoroethane is described by its common name, HFC-134a.
> >
> >
> > Standard name: mole_fraction_of_1,1,1-trifluoroethane_in_air
> >
> > Long name: mole_fraction_of_1,1,1-trifluoroethane_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y.
> > 1,1,1-trifluoroethane is described by its common name, HFC-143a.
> >
> >
> > Standard name: mole_fraction_of_1,1,1,2,2-pentafluoroethane_in_air
> >
> > Long name: mole_fraction_of_1,1,1,2,2-pentafluoroethane_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y.
> > 1,1,1,2,2-pentafluoroethane is described by its common name, HFC-125.
> >
> >
> > Standard name: mole_fraction_of_1,1-difluoroethane_in_air
> >
> > Long name: mole_fraction_of_1,1-difluoroethane_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y.
> > 1,1-difluoroethane is described by its common name, HFC-152a.
> >
> >
> > Standard name: mole_fraction_of_difluoromethane_in_air
> >
> > Long name: mole_fraction_of_difluoromethane_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y.
> > Difluoromethane is described by its common name, HFC-32.
> >
> >
> > Standard name: mole_fraction_of_trifluoromethane_in_air
> >
> > Long name: mole_fraction_of_trifluoromethane_in_air
> >
> > Definition: Mole fraction is used in the construction
> > mole_fraction_of_X_in_Y, where X is a material constituent of Y.
> > Trifluoromethane is described by its common name, HFC-23.
> >
> >
> >
> > Cheers,
> >
> >
> > Dan
> >
> >
> >
> > */________________________________
> > /*
> > */
> > /*
> > *Dr Daniel Say*
> > Postdoctoral Research Associate
> > Atmospheric Chemistry Research Group
> > School of Chemistry
> > University of Bristol
> > Tel: (+44) 117 3317042
> > ------------------------------------------------------------------------
> > *From:* Lowry, Roy K. <rkl at bodc.ac.uk>
> > *Sent:* 12 March 2019 17:17:12
> > *To:* Dan Say; cf-metadata at cgd.ucar.edu
> > *Subject:* Re: Addition of HFC standard names
> >
> > HI again,
> >
> > I'd prefer it to be somewhere in the Standard Name entry because that is
> > searchable either through the XML document on the CF site or through the
> > vocabulary servers handling Standard Names. That way your data gets
> > discovered by other communities who might search for
> > '1,1,1,2-tetrafluoroethane'. I've dealt with quite a few oceanographic
> > halocarbon data sets over the years, but had never come across the 'hfc'
> > nomenclature before.
> >
> > To my knowledge the long name doesn't get scraped by data discovery
> > systems. It is used more as usage metadata to help users better
> > understand the measurements. By all means include the IUPAC name in the
> > long name, but I would also keep the hfc synonym there.
> >
> > Cheers, Roy.
> >
> > I have now retired but will continue to be active through an Emeritus
> > Fellowship using this e-mail address.
> >
> >
> > ------------------------------------------------------------------------
> > *From:* Dan Say <dan.say at bristol.ac.uk>
> > *Sent:* 12 March 2019 16:59
> > *To:* Lowry, Roy K.; cf-metadata at cgd.ucar.edu
> > *Subject:* Re: Addition of HFC standard names
> >
> >
> > Hi Roy,
> >
> >
> > Would it make more sense to leave the standard name as suggested, but
> > replace 'hfc134a' with '1,1,1,2-tetrafluoroethane' in the long name, for
> > simplicity? This is my first venture into the CEDa archives so please
> > advise, I am happy to change the long names if needs be.
> >
> >
> > Cheers,
> >
> >
> > Dan
> >
> >
> > */________________________________
> > /*
> > */
> > /*
> > *Dr Daniel Say*
> > Postdoctoral Research Associate
> > Atmospheric Chemistry Research Group
> > School of Chemistry
> > University of Bristol
> > Tel: (+44) 117 3317042
> > ------------------------------------------------------------------------
> > *From:* Lowry, Roy K. <rkl at bodc.ac.uk>
> > *Sent:* 12 March 2019 16:56:17
> > *To:* Dan Say; cf-metadata at cgd.ucar.edu
> > *Subject:* Re: Addition of HFC standard names
> >
> > Dear Dan,
> >
> > I think it would be better to have the IUPAC names somewhere
> > (e.g. 1,1,1,2-tetrafluoroethane for hfc134a if Wikipedia is correct) in
> > the Standard Name entry. I'd be happy with it in the definition but
> > would not object to it being in the Standard Name itself.
> >
> > Cheers, Roy.
> >
> > I have now retired but will continue to be active through an Emeritus
> > Fellowship using this e-mail address.
> >
> >
> > ------------------------------------------------------------------------
> > *From:* CF-metadata <cf-metadata-bounces at cgd.ucar.edu> on behalf of Dan
> > Say <dan.say at bristol.ac.uk>
> > *Sent:* 12 March 2019 16:43
> > *To:* cf-metadata at cgd.ucar.edu
> > *Subject:* [CF-metadata] Addition of HFC standard names
> >
> >
> > Dear All,
> >
> > I'd like to request an addition to the standard name list for
> > atmospheric measurements of hydrofluorocarbons HFC-134a, HFC-143a,
> > HFC-125, HFC-152a, HFC-32 and HFC-23. Here are the details of the
> > proposed standard names.
> >
> > Proposal for a new standard variable names:
> >
> > Names:
> > mole_fraction_of_hfc134a_in_air
> > mole_fraction_of_hfc143a_in_air
> > mole_fraction_of_hfc125_in_air
> > mole_fraction_of_hfc152a_in_air
> > mole_fraction_of_hfc32_in_air
> > mole_fraction_of_hfc23_in_air
> >
> > Description: Atmospheric measurements of hydrofluorocarbons (HFC) are
> > reported as mole fraction data in units of parts per trillion (ppt,
> > 1E-12). The long name will remain the same as the standard name.
> >
> > Thanks in advance,
> >
> > Dan
> >
> > */________________________________
> > /*
> > */
> > /*
> > *Dr Daniel Say*
> > Postdoctoral Research Associate
> > Atmospheric Chemistry Research Group
> > School of Chemistry
> > University of Bristol
> > Tel: (+44) 117 3317042
> >
> >
> > This email and any attachments are intended solely for the use of the
> > named recipients. If you are not the intended recipient you must not
> > use, disclose, copy or distribute this email or any of its attachments
> > and should notify the sender immediately and delete this email from your
> > system.
> > UK Research and Innovation has taken every reasonable precaution to
> > minimise risk of this email or any attachments containing viruses or
> > malware but the recipient should carry out its own virus and malware
> > checks before opening the attachments. UK Research and Innovation does
> > not accept any liability for any losses or damages which the recipient
> > may sustain due to presence of any viruses.
> > Opinions, conclusions or other information in this message and
> > attachments that are not related directly to UK Research and Innovation
> > business are solely those of the author and do not represent the views
> > of UK Research and Innovation.
> >
> >
> >
> > This email and any attachments are intended solely for the use of the
> > named recipients. If you are not the intended recipient you must not
> > use, disclose, copy or distribute this email or any of its attachments
> > and should notify the sender immediately and delete this email from your
> > system.
> > UK Research and Innovation has taken every reasonable precaution to
> > minimise risk of this email or any attachments containing viruses or
> > malware but the recipient should carry out its own virus and malware
> > checks before opening the attachments. UK Research and Innovation does
> > not accept any liability for any losses or damages which the recipient
> > may sustain due to presence of any viruses.
> > Opinions, conclusions or other information in this message and
> > attachments that are not related directly to UK Research and Innovation
> > business are solely those of the author and do not represent the views
> > of UK Research and Innovation.
> >
> >
> > _______________________________________________
> > CF-metadata mailing list
> > CF-metadata at cgd.ucar.edu
> > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
> >
> _______________________________________________
> 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 3785183
> http://www.met.reading.ac.uk/
>
>
> This email and any attachments are intended solely for the use of the
> named recipients. If you are not the intended recipient you must not use,
> disclose, copy or distribute this email or any of its attachments and
> should notify the sender immediately and delete this email from your
> system.
> UK Research and Innovation has taken every reasonable precaution to
> minimise risk of this email or any attachments containing viruses or
> malware but the recipient should carry out its own virus and malware checks
> before opening the attachments. UK Research and Innovation does not accept
> any liability for any losses or damages which the recipient may sustain due
> to presence of any viruses.
> Opinions, conclusions or other information in this message and attachments
> that are not related directly to UK Research and Innovation business are
> solely those of the author and do not represent the views of UK Research
> and Innovation.
>
>
--
David Hassell
National Centre for Atmospheric Science
Department of Meteorology, University of Reading,
Earley Gate, PO Box 243, Reading RG6 6BB
Tel: +44 118 3785183
http://www.met.reading.ac.uk/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20190313/262f44ec/attachment-0001.html>
Received on Wed Mar 13 2019 - 05:18:02 GMT
