[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #ZKD-949849]: use of CF metadata conventions in an ad-hoc manner.

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #ZKD-949849]: use of CF metadata conventions in an ad-hoc manner.
  • Date: Fri, 10 Jan 2014 14:02:08 -0700
Hi Randy,

> It is convenient and easy to use flag varianbles with the CF attributes 
> “flag_mask”, “flag_meanings”, and “flag_values”, but we don’t necessarily 
> want to use other CF metadata standards because it increases the amount of 
> software development.  Do you guys have an opinion on an approach such as 
> this ?

Sorry, I'm not sure that I understand the question you're asking.

Do you mean the amount of software development for you, users of your data, 
developers of other software for using your data, or us?

I think use of CF attributes ultimately makes software easier to write,
because, as I wrote in a NASA standard for CF Metadata conventions:

  ... Conventions that select a single way to represent metadata make it 
  practical to write software that “understands” the metadata. The 
  resulting uniformity of access supports the development of applications 
  with powerful extraction, regridding, analysis, visualization, and 
  processing capabilities.

  -- 
https://earthdata.nasa.gov/sites/default/files/esdswg/spg/rfc/esds-rfc-021/ESDS-RFC-021-v0.01.pdf

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: ZKD-949849
Department: Support netCDF
Priority: Normal
Status: Closed