⇐ ⇒

[CF-metadata] Applying multiple conventions

From: David Hassell <d.c.hassell>
Date: Fri, 6 Mar 2015 12:21:01 +0000

Hello Martin,

Good news - this is covered by trac ticket #76 "More than one name in
Conventions attribute" (http://cf-trac.llnl.gov/trac/ticket/76).

This has been accepted and should be in 1.7 (if it wasn't already in
1.6?):

    It is possible for a netCDF file to adhere to more than one set of
    conventions, even when there is no inheritance relationship among
    the conventions. In this case, the value of the Conventions
    attribute may be a single text string containing a list of the
    convention names separated by blank space (recommended) or commas
    (if a convention name contains blanks). This is the Unidata
    recommended syntax from NetCDF Users Guide, Appendix B. If the
    string contains any commas, it is assumed to be a comma-separated
    list.

    For example:

         :Conventions = "CF-1.6 ACDD-1.0" ;


All the best,

David

---- Original message from martin.juckes at stfc.ac.uk (12PM 06 Mar 15)

> Date: Fri, 6 Mar 2015 12:02:29 +0000
> From: martin.juckes at stfc.ac.uk
> To: cf-metadata at cgd.ucar.edu
> Subject: [CF-metadata] Applying multiple conventions
>
> Hello,
>
> There is a proposal floating around to use the UGRID conventions for unstructured grids in CMIP6 data. One issue is that the CF Convention specifies a specific string for the "Conventions" and the UGRID convention specific a different specific string. Is there any chance of modifying CF to accept, e.g. Conventions = "CF-1.8, UGRID-0.9"?
>
> regards,
> Martin
> _______________________________________________
> 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 (NCAS)
Department of Meteorology, University of Reading,
Earley Gate, PO Box 243,
Reading RG6 6BB, U.K.
Tel   : +44 118 3785613
E-mail: d.c.hassell at reading.ac.uk
Received on Fri Mar 06 2015 - 05:21:01 GMT

This archive was generated by hypermail 2.3.0 : Tue Sep 13 2022 - 23:02:42 BST

⇐ ⇒