...
- 4:TIGGE operational products
- 5: TIGGE test products
...
Ensemble and
...
deterministic forecasts
Control and perturbed forecasts are identified in section 1 and 4. The following tables explains how to code them in GRIB2:
| Section 1 | ||||
|---|---|---|---|---|
| ensemble forecast | deterministic forecast | |||
| Octets | Example perturbed (pf) | Example control (cf) | forecast * (fc) | |
| 21 | type of processed data | 4 | 3 | 2 |
(*) high-resolution forecast interpolated to ensemble resolution (new request from 2020 for TIGGE, phase III)
| Ensemble (section 4, template 4.61) | |||||
|---|---|---|---|---|---|
| ensemble forecast | deterministic forecast | ||||
| Octets | Example perturbed (pf) | Example controlcontrol (cf) | forecast * (fc) | ||
| 8-9 | product definition template number | 1/11* | 1/11* | 0/8* | |
| 35 | type of ensemble forecast | 255 (missing) | 3 | 1255 (missing) | |
| 36 | perturbation number | 7<eps number> | 0 | ||
| 37 | number of forecasts in ensemble | 51<eps size>51 | <eps size> | ||
- statistically processed (typeOfStatisticalProcessing is set up)
...
Data exchange
The input fields should be split by the output data type, level type and eps number as per below. All steps should be merged into the same file.
Naming convention
tigge_CCCC_YYYYMMDDHH_VVVV_TT_LL_NNN.grib2 ... for ensemble forecasts
...
- CCC: centre acronym (e.g. kwbc for NCEP data)
- YYYYMMDDHH: date * time stamp (e.g. 2019100100 for 0Z run on 2019-10-01)
- VVVV: test/prod
- TT: cf/pf/fc (output type i.e. control forecast/eps member/high resolution forecast)
- LL: pl/sl/pt/pv (level type i.e. pressure/surface/pv level/pt level data)
- NNN: eps number (cf=0000, eps1=1001,....)