Skip to content

GitLab

Open
Created by Robert Schweppe@ottorOwner

fully support CFConventions

We should support the CF conventions. This shall include adding an attribute to each produced file:

  • global attributes:
    • Conventions = "CF-1.7"
    • title = A succinct description of what is in the dataset. -> read from namelist, issue warning if not present
    • institution = Specifies where the original data was produced. -> read from namelist, issue warning if not present
    • source = The method of production of the original data. If it was model-generated, source should name the model and its version, as specifically as could be useful. If it is observational, source should characterize it (e.g., "surface observation" or "radiosonde"). -> MPR version, and path to namelist
    • history = Provides an audit trail for modifications to the original data. Well-behaved generic netCDF filters will automatically append their name and the parameters with which they were invoked to the global history attribute of an input netCDF file. We recommend that each line begin with a timestamp indicating the date and time of day that the program was executed. -> left blank
    • references = Published or web-based references that describe the data or methods used to produce it. comment -> MPR paper
  • data variable attributes (only for those that are written to file):
    • units -> read from namelist, issue warning if not present
    • long_name -> read from namelist, issue warning if not present
    • standard_name -> read from namelist, issue warning if not present
    • _FillValue -> already there
    • scale_factor -> automatically, if user specifies a target dtype in namelist
    • add_offset -> automatically, if user specifies a target dtype in namelist
    • enforce relative order of T, then Z, then Y, then X coordinates in the CDL definition corresponding to the file, issue a warning if not compatible
  • coordinate variable attributes (only for those that are written to file):
Edited by Robert Schweppe