Long_name and comments are not managed or mandated by the CF Conventions, neither regarding their content or being present at all. A data producer or user may of course use them to that effect (for my own personal use I often think of a long_name as way to provide a succinct and generic plot title or similar.) In principle the CF Conventions are not linked to the netCDF file format, but in practice this is often case. And in netCDF files the variable name is the key unique identifier that distinguish one variable from another.
-- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/366*issuecomment-1126037940__;Iw!!G2kpM7uM-TzIFchu!gWVrzMp37MLum6ruSW-ooNlLnakVThoPcd9DYXsO6_4wQZGCFxGIMPh57JKnkr01T14N89iqSg4$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/366/1126037...@github.com> This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
