wiki:Documentation/Forcings

Development Activities

Documentation

Source Code

Reference Simulations

Group Activities

Atmospheric forcing data for ORCHIDEE

ORCHIDEE needs several forcing data in order to run correctly. The number of requested data is dependant of the configuration used.

In On-Line mode, the data needed are related to soil texture and color. If the vegetation is prescribed, ORCHIDEE needs in addition a vegetation information defining the fraction of each PFT per gridcell. Vegetation types gathered in these vegetation maps can be either PFT or Holson categories.

In Off-Line mode, ORCHIDEE is forced by weather data based on observations or climate model reanalysis. Last, depending of the options activated within a run of ORCHIDEE, additional maps might be used for irrigation, slope for routing scheme, ...

0. General information

(a) ORCHIDEE accepts meteorological forcing files at different frequencies:

  • high frequency meteorological files have a forcing step lower than or equal to six hours (most of the datasets below are 3-hourly or 6-hourly);
  • daily files (for example ISI-MIP files);
  • monthly files (see WG files below).

It is the role of the driver to inter/extrapolate timeseries of the forcing meteorological variables at the time step of ORCHIDEE (usually 30 min) based on the forcing dataset.

(b) Two versions of the driver are available to do do both the reading and the inter/extrapolation of the forcing datasets. They differ in the way they interpret the time at which the diffrent variables are read in the forcing dataset (further called the timestamp, while the interval refers to the period between two succesive timestamps):

  • the old driver (src_driver/dim2driver), which assumes that scalar variables (Tair,Qair,Psurf,Wind) are instantaneous values at the timestamp, while flux variables (Rainf,Snowf, SWdown, LWdown) are mean values over the interval ending at the timestamp. This driver also requires that the first value of the annual files corresponds to 00UTC+dt_forcing (for instance 03UTC for a 3hourly forcing), and that the last value is for Dec 31st at 24UTC = 00UTC on Jan 1st of the following year.
  • the new driver (src_driver/orchideedriver.f90) is more flexible and can normally deal with any temporal structure of the forcing datasets, provided the required attributes are inserted in the forcing files. Yet, orchideedriver is not yet compatible with libIGCM. This document Description_Forcing_Files.pdf provides details of how forcing files need to be prepared. It addresses in particular the issues one may face when the fluxes are averaged and scalar variables instantaneous. The driver needs to take this into account else the diurnal cycle can be misplaced. Some data providers have different convention for representing averaged fluxes and this type of details matter.

A longer discussion on the differences between the two drivers (dated in 2016) can be found on https://forge.ipsl.jussieu.fr/orchidee/wiki/Branches/Driver_Improvements.

(c) Adding the cell_methods attribute to files. It is a good practice to add the cell_methods attribute to each of the forcing variable in order to document how they relate to the time axis and their representativity in time. This attribute will say if the variable represents a point in time (instantaneous) or averages over an interval (mean). Furthermore it can inform how the time interval over which the variable is valid relates to the discrete points in time the axis provides. The general form of the attribute follows the CF convention and is "cell_methods = axname : method(position)" where the folowing values can be inserted :

  • axname : The name of the time axis within the file that is valid for the current variable
  • method : instantaneous, mean
  • position : start, centre, end

Obviously for an instantaneous variable, the position information is not relevant as it is only the point in time provided by the axis which matters. On the other hand, for an average, it is essential to know if the point in time provided by the axis is at the beginning, middle or end of the interval used for computing the mean. More details and examples are provided in this document : https://forge.ipsl.jussieu.fr/orchidee/wiki/Branches/Driver_Improvements.

(d) Usually, the forcing files are stored in the shared accounts in IGCM/SRF/METEO directory. The shared accounts are found:

  • At TGCC: /ccc/work/cont003/dsm/p86ipsl/IGCM
  • At IDRIS:
    • On the ada machine: /workgpfs/rech/psl/rpsl035/IGCM
    • On the ergon machine: /u/rech/psl/rpsl035/IGCM
  • LSCE, obelix : /home/orchideeshare/igcmg/IGCM
  • IPSL Ciclad : /prodigfs/ipslfs/igcmg/IGCM
  • At the web by DODS : ​http://dods.ipsl.jussieu.fr/igcmg/IGCM

The datasets available from the shared accounts are noted with a *. Some additional forcings not yet on the shared acount can be found at climserv/ciclad here /bdd/ORCHIDEE_Forcing/BC/OOL/OL2

Read more about the shared accounts and IGCM repository here http://forge.ipsl.jussieu.fr/igcmg_doc/wiki/DocBenvEcommonfiles

(e) Tips and script examples when building/using meteorological forcing files:

  • Land compressed files:
    • The spatial structure of ORCHIDEE forcing files can either be 2D, or 1D if we exclude the sea points to construct a vector of land points. In both cases, this imposes a land-sea mask, to define the land points on which ORCHIDEE will run if we use 2D files, or to construct the 1D files. In the latter case, the landpoint indices are initialized in the NW corner, and increase for each land point encountered when scanning the 2D array from W to E then from N to S.
    • In dim2driver ("old"), this part is addressed in readdim2 > forcing_read_interpol > flinget_buffer > flinget_r3d > flinget_mat. For a 2D forcing, the sea mask is defined by the undef values found for variable Tair.
    • To define the sea points, the missing_value attribute is mandatory in forcing files containing only land points, with a value outside of the valid range of the variables, for example missing_value=1.e+20. In flinget_mat, the default value is set to 0, if this value is kept, oceanic points will be filled with it and treated as land points because 0. is a valid value for some fields (Qair) but ORCHIDEE will crash because it's not valid for others (PSurf), causing the usual problems in qsatcalc.
    • FORTRAN 90 script to create a land points only forcing file (use of the compress attribute) mk_grid.f90
  • SPRED_PREC for forcings at 3 and 6 hourly time step:
    • This externalizable keyword defines the nb of orchidee time steps on which the precipitation total of the forcing time step is spread. It can induce significant chnages on the model's behavior (interception and interception loss, infiltration, runoff and ET), although this hasn't been assessed in a systematic way.
    • By default, we spread the precipitation over half the forcing time step (1.5h and 3h respectively for 3-hourly and 6-hourly files).
  • New driver: you need to add a time attribute to each variable, e.g. "time: instantaneous" our "time: mean(end)", further details in Description_Forcing_Files.pdf.
  • Old driver:
    • The above time attributes are optional but recommended so the files can also be used by the new driver.
    • This time attributes should be "time: instantaneous" for the scalars (Tair,Qair,Psurf,Wind), and "time: mean(end)" for the fluxes (Rainf,Snowf, SWdown, LWdown). If the physical definitions of your forcing variables do not fit this scheme, then you should avoid using this forcing with dim2driver, unless you manage to adapt your files to these constraints.
    • dim2driver also requires that the first value of the annual files corresponds to 00UTC+dt_forcing (for instance 03UTC for a 3hourly forcing), and that the last value is for Dec 31st at 24UTC = 00UTC on Jan 1st of the following year. Your files must be prepared accordingly.
  • Physical definition of the forcing variables: both drivers follow the same conventions. In particular, the following measurement heights are assumed by default: 2m for Tair and Qair; 10m for Wind. Further details in Description_Forcing_Files.pdf.

1. Forcing data stored in IGCM repository

1.1 CRU-NCEP

The meteorological fields are generated by N. Viovy following the protocol described here: https://vesg.ipsl.upmc.fr/thredds/fileServer/store/p529viov/cruncep/readme.html
The standard files are produced using the python script "cruncep.py" made available by Bryce Nordgren here: https://github.com/bnordgren/pylsce

There are several versions of CRU-NCEP. All of them are compatible with the old driver.

CRU-NCEP / v7.2

v7.2 extends till 2016.
Contributor(s):

  • original 0.5° files made by N. Viovy (2016/07)
  • adaptation for use with the standard and new drivers and interpolation towards 1- and 2-degree resolutions made by F. Maignan (2017/06)

CRU-NCEP / v6.1

v6.1 is based on a new CRU version and extends till 2014.
For the next driver, it contains:

  • added attributes for cell_methods,
  • a corresponding new time axis,
  • variables Height_Lev1 and Height_Levuv,
  • attributes units and long_name for variables nav_lat and nav_lon.

Contributor(s):

  • original 0.5° files made by N. Viovy (2015/07)
  • adaptation for use with the standard and new drivers made by Y. Chao and F. Maignan (2015/07)

CRU-NCEP / v5.3.2

The former version (5.3) had a problem on all years before 1948 with a loss of correlation between Tair and Qair.

Contributor(s):

  • original 0.5° files made by N. Viovy (2015/04)
  • standard driver 0.5° files made by Y. Chao (2015/04)
  • standard driver 1° and 2° files made by F. Maignan (2015/04)
Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
cruncep_halfdeg_yyyy.nc -180:180; -90:90 720x360 1901 2013 113 6H 8 avril 2015 346 GB
cruncep_onedeg_yyyy.nc -180:180; -90:90 360x180 1901 2013 113 6H 8 avril 2015 359 GB
cruncep_twodeg_yyyy.nc -180:180; -90:90 180x90 1901 2013 113 6H 8 avril 2015 90 GB

Archived CRU-NCEP versions:

Other versions have been removed from the syncronized repository. They are listed at the end of this page.

1.2 FLUXNET

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
IdSite_Fyear-Lyear.nc eg. FR-LBr_1996-2006.nc / in-situ site-specific 30minutes http://dods.ipsl.jussieu.fr/igcmg/IGCM/BC/OOL/OL2/FLUXNET/README.pdf http://www.earth-syst-sci-data-discuss.net/8/23/2015/essdd-8-23-2015.html 4Mo per year

The data have been prepared for all sites of the Free Access Fluxnet database (http://www.fluxdata.org/DataInfo) as available in August, 2012 (~150 sites).

1.3 WFDEI_CRU

Where ? Not in IGCM repository or IGCM_ARCHIVE.

This data corresponds to the one described in the publication Weedon et al. 2014 (http://onlinelibrary.wiley.com/doi/10.1002/2014WR015638/abstract). Compared to WFD, WFDEI offers values in the 21st century owing the ERA-Intermin reanalysis.

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
WFDEI_CRU_yyyy.nc WFDEI_CRU -180:180; -90:90 720x360 1979 2016 34 3H November 2017 314 GB

As this data is based on the ERA-I re-analysis the fluxes are cumulated over the 3h period preceding the time-stamp. All other variables are instantaneous at the given date. This is now properly described by the cell_method data in the netCDF file.

1.4 WFDEI_GPCC

There are several versions of WFDEI_GPCC.

WFDEI_GPCC

This is the same atmospheric forcing as the one described above (1.6 WFDEI_CRU) except that rainfall is now corrected with the GPCC data : http://www.dwd.de/bvbw/appmanager/bvbw/dwdwwwDesktop?_nfpb=true&_windowLabel=T12404818261141645314319&_urlType=action&switchLang=en&_pageLabel=_dwdwww_klima_umwelt_datenzentren_wzn As this rainfall series is shorter, WFDEI_GPCC has fewer years than WFDEI_CRU.

WFDEI_GPCC/v1/noleap

This dataset is available in the shared accounts (IGCM/SRF/METEO directory).

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
WFDEI_GPCC_yyyy.nc -180:180; -90:90 720x300 1979 2009 31 3H 3 juin 2013 182 GB

The old driver (dim2driver) needs a forcing that has its first record at 0 UTC, in addition to instanteaneous "scalars" and fluxes as mean(end), to work correctly. The original WFDEI starts at 3UTC, and to make it compatible with with dim2driver, a lag of 3 hours has been introduced by Ben Poulter and Fabienne Maignan.

WFDEI_GPCC/v2/leap

This dataset is available in the shared accounts (IGCM/SRF/METEO directory).

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
WFDEI_GPCC_yyyy.nc -180:180; -90:90 720x360 1990 2011 33 3H 26 avril 2014 265 GB

NB: Year 2011 is incomplete. NB2: A longer version is available from Jan up to 2014 at least.

The above shift has not been done here, and this forcing should only be used with the new driver (orchideedriver.f90).

1.5 Princeton_GPCC

This dataset is available in the shared accounts (IGCM/SRF/METEO/Princeton_GPCC/v1/1deg_3h directory).

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
PGF_GPCC_1deg_3h_yyyy.nc -180:180; -90:90 360x180 1948 2010 63 3H REAME in the shared accounts 11 Feb 2015

The dataset is based on the data provided by Princeton University, itself based on the NCEP-NCAR reanalysis. Further details are given in Sheffield, J., G. Goteti, and E. F. Wood, 2006: Development of a 50-yr high-resolution global dataset of meteorological forcings for land surface modeling, J. Climate, 19 (13), 3088-3111. Users must cite this reference. The Princeton forcing uses CRU data for bias-correction, but the present forcing includes an additional bias-correction of total precipitation, based on the monthly GPCC data. This has been performed by Bertrand Decharme (CNRM, Toulouse).

1.6 GSWP3

This forcing has been constructed for the GSWP3 experiment, cf. http://hydro.iis.u-tokyo.ac.jp/GSWP3/exp1.html#boundary-conditions. It is based on the 20th Century Reanalysis (20CR) [Compo et al., 2011 http://hydro.iis.u-tokyo.ac.jp/GSWP3/refs.html#compo2011] at the global 2° resolution, dynamically downscaled into T248 (~0.5°). Several versions are available.

General information on GSWP3 data from personal communication between Hyunjun Kim and Agnes Ducharne:

  • All variable treated in the same way in terms of time averaging. First time record should corresponds to 00UTC, but please note values represents "backward averaging" which means 00UTC is mean of -03 ~ 00UTC.
  • Wind should be assumed to represent speed at 10 m. Downscaled reanalysis wind speed is at 10m, but CRU CL2.0 data which is used to correct long-term mean has not been corrected for any measurement height related issue. New et al. (2002) says "Wind speed is measured at heights above the surface of between 2 and 20 m. Measurement height varies both within and between countries, and in many cases the heights were not specified. Consequently, no corrections were made to wind data. The large majority of known heights were 10 m, and the interpolated wind field should be assumed to represent speed at this height."

GSWP3/v1

This is the official v1 release of GSWP3, dated on 2017-06-01. It is 3-hourly with a spatial resolution of 0.5°, and covers 1901-2010. An extension to 2014 is under way. The original files are 2D, and only the wind is not worldwide and can serve as a land mask. This dataset has been formatted to be used by ORCHIDEE, and should be functional with both the old and new drivers, since it includes the cell_method attributes.

The scripts (R and bash) to do the formatting are committed on https://forge.ipsl.jussieu.fr/orchidee/browser/trunk/TOOLS/GENERATE_ATMOS_FORCING/GSWP3_halfdeg_v1

A detailed analysis of the formatted dataset was done by Salma Tafasca (PhD student at METIS) using the old driver, see Preparing_GSWP3_V1_Official.pdf. A comparison of the interpretation of this forcing by the two drivers was done by Vlad: https://orchidas.lsce.ipsl.fr/mapper/meteo_inter.php The results show a lag of 1h30 for the scalars and the interpolation by the new driver is a priori better. For the fluxes, SW results are identical with the two drivers, LW results are different but would probably be identical if this flux was not interpolated linearly but uniformly (recommended to conserve the fluxes), and the differences in precipitation comme from different spred_prec parameters.

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
GSWP3_halfdeg_3h_yyyy.nc -180:180; -90:90 720x360 1901 2010 110 3H Preparing_GSWP3_V1_Official.pdf

GSWP3/CMIP6_144x143_v1

These forcing files were generated for LS3MIP at the resolution of LMDZ6-LR (144x142), based on bilinear interpolation of the GSWP3 forcing at 0.5°.

WARNING: the version of this 0.5° forcing dataset (v1.06) is different from the one used to get the formatted forcing above. The differences are : (1) continuous wind fields with no data gap over oceans; (2) data extends until 2014.

The scripts (R and bash) to do the interpolation and formatting are committed on https://forge.ipsl.jussieu.fr/orchidee/browser/trunk/TOOLS/GENERATE_ATMOS_FORCING/GSWP3_144x142_CMIP6

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
GSWP3_CM6LR_3h_yyyy.nc -180:180; -90:90 144x142 1901 2014 114 3H https://forge.ipsl.jussieu.fr/orchidee/browser/trunk/TOOLS/GENERATE_ATMOS_FORCING/GSWP3_144x142_CMIP6/README

1.7 WG

Monthly timestep to test the weather generator.

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
WG_yy.nc -180:180; -90:90 320x160 79 93 15 1M may 2007 20 MB
WG_CRU.nc (noleap) -180:180; -90:90 720x360 1 1M may 2007 37 GB

1.8 E2OFD

This dataset was build in the framework of the Earth2Observe FP7 project. It is available on the IPSL Meso-centre under /bdd/ORCHIDEE_Forcing/BC/OOL/OL2/E2OFD. It was prepared by Jan Polcher based on the data prepared by ECMWF for the Earth2Observe project.

The originality of this forcing is that it is 1/4°. Most atmospheric forcing data sets were extrapolated from the ERA-I fields with the same bias corrections applied as in the WFDEI cases. The most original feature is the rainfall which is the very original MSWEP product : https://www.hydrol-earth-syst-sci.net/21/589/2017/

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
E2OFD_yyyy.nc E2OFD -180:180; -90:90 1440x720 1979 2014 36 3H July 2016 31 GB/yr

2. Forcing data stored elsewhere

2.1 WFD_CRU

This data set is available at ciclad here: /bdd/ORCHIDEE_Forcing/BC/OOL/OL2/WFD_CRU .

The data corresponds to the one described in the publication Weedon et al. 2011 (http://journals.ametsoc.org/doi/abs/10.1175/2011JHM1369.1)

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
WFD_CRU_yyyy.nc WFD_CRU -180:180; -90:90 720x360 1901 2001 1000 3H 14 Nov 2014 592 GB

2.2 GSWP3v0 (ISIMIP2)

This dataset is available on ergon in /arch/home/rech/lmd/rlmd979/GSWP3_forcing/halfdeg_v1.

It was prepared by Jinfeng Chang for the ISIMIP2 simulations, using the TRENDY land mask. It was also upscaled at the 1° resolution by Fabienne Maignan for the ORCHIDEE-MICT paper (https://www.geosci-model-dev.net/11/121/2018/)

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
GSWP3_halfdeg_3h _yyyy.nc GSWP3 -180:180; -90:90 720x360 1901 2007 107 3H 24 April 2016 5.5 GB/yr

2.3 ERAI_05

This data set is available at ciclad here: /bdd/ORCHIDEE_Forcing/BC/OOL/OL2/ERAI_05 .

This meteorological data set has been prepared by ECMWF in the framework of the Earth2Observe project : http://www.earth2observe.eu/

Using a simple bi-linear interpolation the data of the ERA-I re-analysis on the Gaussian grid (N128) output was projected to a regular lat/lon grid at 0.5deg resolution, without special consideration for the land/sea mask. It was thus considered, in consultation with Emanuel Dutra of ECMWF, that it was not unreasonable to use the same land/sea mask as WFDEI and hope that the atmospheric forcing on coastal points will not be too badly affected by the methodology.

The value of this forcing lies in its close relation to the ERA-I re-analysis and its extension to December 2014.

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
ERAI_yyyy.nc ERAI_05 -180:180; -90:90 720x360 1979 2014 36 3H 20 June 2015 293 GB

2.4 ERAI_05_GPCP

This data set is available at ciclad here: /bdd/ORCHIDEE_Forcing/BC/OOL/OL2/ERAI_05_GPCP .

This is the same forcing as ERA_05 except for the rainfall and snow fall from the re-analysis which were corrected with the GPCP estimates (http://precip.gsfc.nasa.gov/).

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
ERAI_GPCP_yyyy.nc ERAI_05_GPCP -180:180; -90:90 720x360 1979 2014 36 3H 20 June 2015 298 GB

3. Archived forcing data previously stored in IGCM repository

Obsolete data set previously stored in IGCM repostiory are removed and stored in a IGCM_ARCHVE folder at ciclad and at TGCC. They can be found here:

TGCC : /ccc/store/cont003/igcmg/igcmg/IGCM_ARCHIVE/SRF/METEO
ciclad : /prodigfs/ipslfs/igcmg/IGCM_ARCHIVE/SRF/METEO

3.1 CRU-NCEP

CRU-NCEP / v5.4

v5.4 contains the same data as v5.3.2 with:

  • added attributes for cell_methods,
  • a corresponding new time axis,
  • variables Height_Lev1 and Height_Levuv,
  • attributes units and long_name for variables nav_lat and nav_lon.

Contributor(s):

  • adaptation for use with the new driver made by F. Maignan (2015/06)
Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
cruncep_halfdeg_yyyy.nc -180:180; -90:90 720x360 1901 2013 113 6H 8 avril 2015 346 GB

CRU-NCEP / v5.3

This version is archived at IDRIS/ergon : /linkhome/rech/psl/rpsl035/IGCM_backup_2015-06-15/STORAGE/BC/OL2/CRU-NCEP

CAUTION: DO NOT USE ANYMORE: This version has a problem on all years before 1948 with a loss of correlation between Tair and Qair.

Contributor(s):

  • original 0.5° files made by N. Viovy (2014/10)
  • standard driver 0.5° files made by Y. Chao (2014/10)
  • standard driver 1° and 2° files made by F. Maignan (2014/10)
Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
cruncep_halfdeg_yyyy.nc -180:180; -90:90 720x360 1901 2013 113 6H 1 oct 2014 346 GB
cruncep_onedeg_yyyy.nc -180:180; -90:90 360x180 1901 2013 113 6H 1 oct 2014 359 GB
cruncep_twodeg_yyyy.nc -180:180; -90:90 720x360 1901 2013 113 6H 1 oct 2014 90 GB

CRU-NCEP / v5.2

This version is archived at IDRIS/ergon : /linkhome/rech/psl/rpsl035/IGCM_backup_2015-06-15/STORAGE/BC/OL2/CRU-NCEP

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
cruncep_yyyy.nc -180:180; -90:90 720x360 1901 2012 112 6H 25 sept 2013 343 GB

CRU-NCEP / v5.2_2x2deg

This version is archived at IDRIS/ergon : /linkhome/rech/psl/rpsl035/IGCM_backup_2015-06-15/STORAGE/BC/OL2/CRU-NCEP

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
cruncep_yyyy_2x2.nc -180:180; -90:90 180x90 1901 2012 112 6H 25 sept 2013 89 GB

CRU-NCEP / v2

This version is archived at IDRIS/ergon : /linkhome/rech/psl/rpsl035/IGCM_backup_2015-06-15/STORAGE/BC/OL2/CRU-NCEP

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
cruncep_halfdeg_yyyy.nc -180:180; -90:90 720x360 1901 2010 110 6H 5 juin 2013 362 GB
cruncep_halfdeg_yyyy_noleap.nc -180:180; -90:90 720x360 1904 2008 27 6H 5 juin 2013 89 GB
cruncep_halfdeg_yyyy_leap.nc -180:180; -90:90 720x360 1904 2008 27 6H 5 juin 2013 89 GB

Default is to use the noleap files (through symbolic links).

3.2 CRU

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
forceyyyy.nc -180:180; -90:90 720x360 1901 2002 103 monthly oct 2004 10.7 GB
forceyyyy_yyyy.nc -180:180; -90:90 720x360 1901_1909 1994_2002 7 monthly oct 2004

3.3 ERA_New_Global

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
ERA_Global_yyyy.nc -180:180; -90:90 512x256 1979 2012 34 3H 22 juin 2013 437 GB

3.4 ISLSCP

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
islscp_for_1987.nc -180:180; -90:90 360x179 1987 1987 1 6H 28 jun 2005 1.1 GB

3.5 ISLSCP2

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
islscp_for_yyyy.nc -180:180; -90:90 360x179 1982 1995 14 3H (6H for 1982) 28 jun 2005 19 GB

3.6 NCC

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
ncc_for_yyyy.nc -180:180; -90:90 360x180 1948 2000 52 6H info sept 2005 ref 37 GB

3.7 NLDAS

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
orchidee_NLDAS_forcing_yyyymm.nc -67:-24; 25:52 464x224 199701 200212 6 1H mai 2008 197 GB

3.8 WFD3/annual

Name Spatial information Temporal information Web documentation Size
Abbreviation Full name Coverage Resolution First year Last year Number of years Resolution Informations Data download References GB
WFD_yyyy.nc -180:180; -90:90 720x360 1958 2001 44 3H april 2010 300 GB
Last modified 10 days ago Last modified on 11/05/18 12:54:52

Attachments (3)