Versions Compared

Key

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

...

Type
(CMIP5)
Coordinate Name
(CMIP5)
Dimension Names
(CMIP5)
Axisstandard_namelong_name
(CMIP5)
units
(CF canonical units)
positivevalid_min
(CMIP5)
valid_max
(CMIP5)
boundsNotes
doublelatlatYlatitudelatitudedegrees_northN/A-90.90.lat_bnds

Values (1x1deg grid) prescribed:
center of 1-degree cells
dimension lat=180

[-89.5, -88.5 , ..., -0.5, 0.5 ... 89.5]

doublelonlonXlongitudelongitudedegrees_eastN/A0.360.lon_bndsValues (1x1deg grid) prescribed:
center of 1-degree cells
dimension lon=360

[0.5 , 1.5 , ..., 358.5, 359.5]

doubleplevplevZair_pressurepressure

Pa

downN/AN/A 

This is also referred to as isobaric level by some tools
Values prescribed:
dimension plev=11

[925., 850., 700., 500., 400., 300., 200., 100., 50., 30., 10.]
(NOTE: values here written in hPa, they should be Pa)

 
doubledepthdepthZdepthdepth

m

downN/AN/Adepth_bndsOnly used for soil model levels
NOTE: Number and depth of levels is not prescribed by C3S
doubleheight(scalar auxiliary coordinate)Zheightheightmup or down

CMIP5:

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

CMIP5:

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

 

Used for single level fields (height, soil,SST)

e.g. 2 m (for Temperature)

C3S: string

 

 realizationstr31=31


E realizationrealization1N/AN/AN/A 

members are not a physical quantity. Realization is a discrete coordinate and the members its categorical values (ordered or non-ordered ones)

SPECS approach: rXXiYYpZZ

Note about interpolation, etcNOTE about the horizontal coordinates: The regridding procedure to provide the data in the 1-degree grid must take into account that the full definition of the gird cells is done by the cell boundaries (lat_bnds, lon_bnds)

Time Coordinates

TypeCoordinate NameDimension NamesAxisstandard_namelong_namecalendarunitsboundsNotes
doublereftimeN/AN/Aforecast_reference_time"Start date of the forecast"gregorianUDUNITS time units
e.g.
"hours since YYYY-MM-DD hh:mm:ss TZhh:TZmm"
N/AIn SPECS it is a "global_attribute"
It has been additionally introduced here as a coordinate variable to ease future netCDF management (e.g. file merging)
doubleleadtimeleadtimeN/Aforecast_period"Time elapsed since the start of the forecast"N/A

SPECS: days
C3S: requested units can be relaxed to equivalent time units

leadtime_bnds

The interval of time between the forecast reference time and the valid time

Boundaries not needed when this time coordinate is used for instantaneous values (note that "time:point" is used as cell_method in those cases)

When boundaries are required, the value of the coordinate must be in the centre of the correspondent time cell boundaries

doubletimeleadtimeN/A

time

"Verification time of the forecast"gregorian

SPECS: "days since 1850-01-01"

C3S: requested units can be relaxed to equivalent time units

time_bnds

Time for which the forecast is valid

Boundaries not needed when this time coordinate is used for instantaneous values (note that "time:point" is used as cell_method in those cases)

When boundaries are required, the value of the coordinate must be in the centre of the correspondent time cell boundaries

 

NOTE: Definitions for "leadtime" and "time" have been taken from SPECS. The introduction of "reftime" as a variable has been adapted from SPECS global attribute description for the forecast reference time.

...

Warning

"leadtime" has been selected as dimension (instead of "time") for both time and leadtime. That means "leadtime" is the coordinate and "time" is an auxiliary coordinate

  • This diverges from SPECS (where "time" was the name of the dimension and the coordinate, and "leadtime" was an auxiliary coordinate)
  • Here it has been done like that because
    1. both reftime and leadtime are the relevant (let's say "orthogonal") coordinates as coming from time = reftime + leadtime
    2. doing like that has some advantages when merging netcdf files ("leadtime" can be easily shared by different variables in a merged file, while "time" notcannot)

 

 

Cell boundaries

 As described in section 7.1 Cell Boundaries of CF convention.

Info

To represent cells we add the attribute bounds to the appropriate coordinate variable(s). The value of bounds is the name of the variable that contains the vertices of the cell boundaries. We refer to this type of variable as a "boundary variable." A boundary variable will have one more dimension than its associated coordinate or auxiliary coordinate variable. The additional dimension should be the most rapidly varying one, and its size is the maximum number of cell vertices. Since a boundary variable is considered to be part of a coordinate variable’s metadata, it is not necessary to provide it with attributes such as long_name and unitsas long_name and units

  • where to put the time coordinate (beginning, middle, end of the bounds) ?

e.g.
time=20160922 06
timebounds = [20160922 00, 20160922 06]

  • for 24h time steps:
[0,24] is that convention always valid?
Bounds NameDimensionsComments
time_bndsleadtime, bnds 
Bounds NameDimensionsComments
time_bndstime, bnds
leadtime_bnds
lat_bndslat, bndsValues (1x1deg grid) prescribed:
[-90., 89.], [-89., -88.], ... [89., 90.]
lon_bndslon, bnds

Values (1x1deg grid) prescribed:

[0., 1.], [1., 2.], ... [359., 360.]

depth_bndsdepth,bndsShould define the full vertical extent of the soil model layers

...

  attributes 
name
(CMIP5)
dimensionsstandard_namelong_name
(CMIP5)
unitscoordinatescell_methodsNOTES
zgtime,plev,lat,longeopotential_height"Geopotential Height"m "time: point"

C3S: required 
CF:
recommended

 
tatime,plev,lat,lonair_temperature"Air Temperature"K "time: point"

C3S: required 
CF:
recommended

 
hustime,plev,lat,lonspecific_humidity"Specific Humidity"1 "time: point"

C3S: required 
CF:
recommended

 

 

N/A in CMIP

time,plev,lat,lonatmosphere_relative_vorticity

 

N/A in CMIP

s-1 "time: point"

C3S: required 
CF:
recommended

 

 

N/A in CMIP

time,plev,lat,londivergence_of_wind

 

N/A in CMIP

s-1 "time: point"

C3S: required 
CF:
recommended

 
uatime,plev,lat,lonx_wind"Eastward Wind"m s-1 "time: point"

C3S: required 
CF:
recommended

 
vatime,plev,lat,lony_wind"Northward Wind"m s-1 "time: point"

C3S: required 
CF:
recommended

 

 

 

 

 

When boundaries are required, the value of the coordinate must be in the centre of the correspondent time cell boundaries