Versions Compared

Old Version 6

changes.mady.by.user Eduardo Penabad

Saved on

compared with

New Version 7

changes.mady.by.user Eduardo Penabad

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

 

Global attributes

The following properties are intended to provide information about where the data came from and what has been done to it. This information is mainly for the benefit of human readers and data discovery mechanisms. The attribute values are all character strings. When an attribute appears both globally and as a variable attribute, the variable’s version has precedence.

 

A methodology to build this 'temperature from CTD #1234'; ''.
Attribute NameValueExamplesComment
ConventionsCF convention string  [Other convention] :..."CF-1.6"
"CF-1.6 C3S-0.1"

Multiple conventions may be included (separated by blank spaces)

title

A controlled vocabulary will be provided

CF: Free text

ACDD (highly recommended)

"IPSL-CM5A-LR model output prepared for CMIP5 RCP4.5"
A short phrase or sentence describing the dataset. In many discovery systems, the title will be displayed in the results list from a search, and therefore should be human readable and reasonable to display in a list of such names
references

URIs (such as a URL or DOI) for papers or other references. A valid doi is recommended

CF: Free text

"doi:10.5194/gmd-8-1509-2015"
Published or web-based references that describe the data or methods used to produce it.The validity of the doi values will be checked. Warnings will be raised for any other content.
sourceA methodology to build this source attribute will be provided
  • "world model v.0.1
  • "
  • "model-generated, GloSea5-GC2"
  • "IPSL-CM5A-LR (2010) : atmos : LMDZ4 (LMDZ4_v5, 96x95x39); ocean : ORCA2 (NEMOV2_3, 2x2L31); seaIce : LIM2 (NEMOV2_3); ocnBgchem : PISCES (NEMOV2_3); land : ORCHIDEE (orchidee_1_9_4_AR5)"

Where the data is from. The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is defined in the CF Conventions. Examples:, as specifically as it could be useful

institutioninstitution

CF: Free text

C3S: A controlled vocabulary will be provided

CF: Free text

 

"Met Office"

Francisco Doblas-Reyes I'm not convinced "Met Office" is descriptive enough. Shouldn't it be something like "C3S"?

Unknown User (brookshaw): "institution" is the origin of the data. Things like C3S will be specified elsewhere (e.g. project)

Specifies where the original data was produced.

Who produced the data

Antonio S. Cofino Gonzalez: The name of the institution principally responsible for originating this data.This attribute is recommended by the CF convention.

contact

Copernicus

contact

CF: Free text

C3S: Copernicus User Support URI should be used
http://copernicus-support.ecmwf.int

 CF: Free text

"http://copernicus-support.ecmwf.int"

Antonio S. Cofino Gonzalez: The CMIP5/SPECS DRS define this attribute. The ACDD defines: creator_name, creator_email, creator_url, publisher_name, publisher_email, publisher_url

 

project

"C3S Seasonal Forecast" should be used

project

CF: Free text

C3S: "C3S Seasonal Forecast" is required, additional project info (e.g. ITT details) is optional  

"C3S Seasonal Forecast"

 Antonio S. Cofino Gonzalez: The name of the project(s) principally responsible for originating this data. Multiple projects can be separated by commas, as described under Attribute Content Guidelines. Examples: 'PATMOS-X', 'Extended Continental Shelf Project'.

creation_date

SPECS: YYYY-MM-DDThh:mm:ss<zone>

NOTE: This is ISO 8601:2004 extended format

"2011-06-24T02:53:46Z"
Antonio S. Cofino Gonzalez:

The date on which this version of the data was created. (Modification of values implies a new version, hence this would be assigned the date of the most recent values modification.) Metadata changes are not considered when assigning the creation_date

. The ISO 8601:2004 extended date format is recommended.

 

NOTE: The ACDD 1.3 names this attribute as date_create
SPECS conventions will be followed  

commentFree text
  • "
This 21th century simulation has been forced by prescribed concentration following the rcp 4.5 scenario."
  • Produced by University of Hamburg for DWD at ECMWF HPC facilities"
  • "Run by CMCC at CINECA"
Antonio S. Cofino Gonzalez:

Miscellaneous information about the data, not captured elsewhere

. This attribute is defined in the CF Conventions

.

forecast_typeC3S: Controlled Vocabulary

"forecast" or "hindcast"

"forecast"To identify the type of data
history

Each line should begin with a timestamp indicating the date and time of day when the program was executed

CF: Free Text

  • "Produced using CDS Toolbox on 1/6/2016"
  • "Model raw output postprocessing with modelling environment (IMDI) at DKRZ: URL: http://svn-mad.zmaw.de/svn/mad/Model/IMDI/trunk, REV: 3436 2011-07-17T15:14:45Z CMOR rewrote data to comply with CF standards and CMIP5 requirements."

To record relevant information, such as the command history which led to this file being producedFrancisco Doblas-Reyes I understand that the versioning of the software used to create the data can be included either here or in the commit attribute. Any idea how/when to make the decision? . 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

 

commit,

iso_lineage or lineage

Free text (ISO Lineage model 19115-2)"Produced using CDS Toolbox v1.0"

trace of the tools/scripts used.

Paco: include information about the versioning of the software used to create the data

Antonio S. Cofino Gonzalez: We need a more implementtios examples on this. This could achiived in EQC WP where metadata is been part of their activities (i.e. WP4@QA4SEAS). ISO 19115-2 defines a linage model where this is been considered. TBD.

summary

The content will be provided

ACDD (highly recommended): Text, defined phrase

C3S: The content will be provided		 A short paragraph describing the dataset
keywords

The content will be provided

ACDD (highly recommended) : text, controlled vocabularyC3S: The content will be provided

 A comma separated list of key words and phrases.
forecast_reference_time

SPECS: YYYY-MM-DDThh:mm:ssZ

NOTE: This is ISO 8601:2004 extended format

"2011-06-01T00:00:00Z"

time of the analysis from which the forecast was made

UTC zone is required

...

Spatial Coordinates

FinalisedType
CMIP5		Coordinate Name
(CMIP5)		Dimension Names
(CMIP5)		Axisstandard_namelong_name
(CMIP5)		units
(CF canonical units)		positivevalid_min
(CMIP5)		valid_max
(CMIP5)		Notes
YdoublelatlatYlatitudelatitudedegrees_northN/A-90.90.Bounds required
Values (1x1deg grid) required
YdoublelonlonXlongitudelongitudedegrees_eastN/A0.360.Bounds required
Values (1x1deg grid) required
YdoubleplevplevZair_pressurepressure

Pa

downN/AN/AThis is also referred to as isobaric level by some tools
Value (plevels) required (ITT)
YdoubledepthdepthZdepthdepth

m

downN/AN/AUsed for soil model levels
NOTE: Number and depth of levels is not prescribed by C3S
YdoubleheightheightZheightheightmup

CMIP5:

2mtemp: 1.
10mu/v: 1.

CMIP5:

2mtemp: 10.
10mu/v: 30.

can be used for single level (height, soil)

e.g. 2 m (for Temperature)

N

C3S: string

 

ISSUE:

Then, it needs an auxiliary coordinate
(string len)

 realization

C3S: realization_dim

CF: a different name is needed for dim/variable
(see comment)


N/A realizationrealization1N/AN/AN/Amembers are not a physical quantity. Realization is Discrete Axis and the mebers it categorical values (ordered or non-ordered ones)

...