Dear Karl
In answer to your other question, yes, the computed_standard_name should be
an attribute of the vertical coordinate variable, as well as the standard_name,
as shown in Example 4.3.
Best wishes
Jonathan
----- Forwarded message from Martin Juckes - UKRI STFC <martin.juckes at stfc.ac.uk> -----
> Date: Thu, 7 Mar 2019 14:28:26 +0000
> From: Martin Juckes - UKRI STFC <martin.juckes at stfc.ac.uk>
> To: "Taylor, Karl E." <taylor13 at llnl.gov>, "cf-metadata at cgd.ucar.edu"
> <cf-metadata at cgd.ucar.edu>
> Subject: Re: [CF-metadata] parametric vertical coordinate standard_name
> confusion
>
> Hi Karl,
>
>
> I think it is in there (table A.1) .. between "compress" and "Conventions",
>
>
> regards,
>
> Martin
>
>
> ________________________________
> From: CF-metadata <cf-metadata-bounces at cgd.ucar.edu> on behalf of Taylor, Karl E. <taylor13 at llnl.gov>
> Sent: 07 March 2019 00:49
> To: cf-metadata at cgd.ucar.edu
> Subject: [CF-metadata] parametric vertical coordinate standard_name confusion
>
> HI all,
>
> I hope someone can provide some help here:
>
> In Appendix D of the conventions where parametric vertical coordinates
> are discussed, a "computed_standard_name" attribute is defined for some
> coordinates, but "computed_standard_name" doesn't appear in Appendix A.
> Should it?
>
> Also does computed_standard_name get attached to the coordinate variable
> along with the actual standard_name of the coordinate variable?
>
> thanks,
> Karl
>
> _______________________________________________
> 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
----- End forwarded message -----
Received on Thu Mar 07 2019 - 09:24:17 GMT
