Apologies all around. I messed up in searching the document so missed
the critical information already there.
Thanks for providing the answers I should have found myself.
Karl
On 3/7/19 8:24 AM, Jonathan Gregory wrote:
> 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
> -
>
>> Date: Thu, 7 Mar 2019 14:28:26 +
>> From: Martin Juckes - UKRI STFC
>> To: "Taylor, Karl E." , "cf-metadata@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 on behalf of Taylor,
>> Karl E.
>> Sent: 07 March 2019 00:49
>> To: cf-metadata@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@cgd.ucar.edu
>> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>> ___
>> CF-metadata mailing list
>> CF-metadata@cgd.ucar.edu
>> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
> - End forwarded message -
> ___
> CF-metadata mailing list
> CF-metadata@cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
