Thanks you for raising this, Lars. I support your initiative to do something
about it. I agree that doing nothing but updating the links would be to correct
a defect.
Going further than that would be an enhancement, as you say, and I agree with
others that we should do so. As far as I know, the correspondence of standard
names with PCMDI names and GRIB codes has only even been partial and never
updated. I was responsible for including these in the first version of the
standard name list. At that time it was desirable to make those links because
standard names were a new idea, and by showing their relationship to existing
standards we could make them more attractive to potential users. Now, however
(twenty years later), standard names are well-established in their own right, I
would say, and the mapping between different metadata standards belongs better
_outside_ the standard, in neutral territory.
Hence, I would propose we should
* delete the two lines you mention.
* delete this sentence earlier in 3.3: "When appropriate, the table entry also
contains the corresponding GRIB parameter code(s) (from ECMWF and NCEP) and
AMIP identifiers."
* delete this text from Appendix B:
> Entry elements may optionally also contain the following elements:
<grib>GRIB parameter code</grib>
<amip>AMIP identifier string</amip>
> Not all variables have equivalent AMIP or GRIB codes. ECMWF GRIB codes start
> with E, NCEP codes with N. Standard codes (in the range 1-127) are not
> prefaced. When a variable has more than one equivalent GRIB code, the
> alternatives are given as a blank-separated list.
* delete the `<grib>` and `<amip>` tags in Example B1 and in the standard name
table.
I wonder what others think, especially Alison, of removing all this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/261#issuecomment-618900454
This list forwards relevant notifications from Github. It is distinct from
[email protected], although if you do nothing, a subscription to the
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to
[email protected].
