GRIB2 Meta Data and grib_api Keys for Section 1: Identification Section

Last updated: January 2013

This table lists the GRIB2 meta data and associated grib_api keys for the Identification Section of GRIB2 messages. The most important values of according Code Tables are also listed in the comments for a reference. Fixed COSMO-values or strategies are given on a light-blue background.


Octets Key Name Comments
1-4 section1Length Length of section in octets (21 or nn)
5 numberOfSection Number of section (1)
6-7 centre Identification of originating / generating centre (Common Code Table C-11)
7kwbcNCEP
76 Moscow (RosHydroMet)
78edzwOffenbach (DWD)
80cnmcRome (USAM)
96 Athens (HNMS)
98ecmfECMWF
215 Zürich (MeteoSwiss)
220 Warsaw (IMGW)
242 Romania (NMC)
250 COSMO
8-9 subCentre Identification of originating / generating sub-centre (allocated by originating / generating centre)
10 tablesVersion GRIB Master Tables Version Number: Local tables shall define those parts of the master tables which are reserved for local use except for the case described below. In any cases, the use of local tables in messages intended for non-local or international exchange is strongly discouraged.
5Version implemented on 4 November 2009
6Version implemented on 15 September 2010
7Version implemented on 4 May 2011
8Version implemented on 2 November 2011
9Version implemented on 2 May 2012
10Version implemented on 7 November 2012
11Pre-operational to be implmeented by next amendment
12-254Future versions
Which version is used depends on grib_api and the implemented definitions. It will be set by grib_api.
11 localTablesVersion Version number of GRIB Local Tables used to augment Master Tables: If octet 10 contains 255 then only local tables are in use, the local tables version number (Octet 11) must not be zero nor missing, and local tables may include entries from the entire range of the tables.
0Local tables not used. Only table entries and templates from the current master table are valid
1-254Number of local tables version used
255Missing
The COSMO-Model does not set localTablesVersion on its own, but uses the value read with the sample file.
12 significanceOfReferenceTime Significane of reference time according to Code Table 1.2
0Analysis
1Start of forecast
2Verifying time of forecast
3Observation time
4-191Reserved
192-254Reserved for local use
255Missing
13-14 year Year (4 digits)
15 month Month
16 day Day
17 hour Hour
18 minute Minute
19 second Second
20 productionStatusOfProcessedData Production status of processed data in this GRIB message according to Code Table 1.3:
0Operational products
1Operational test products
2Research products
3Re-analysis products
4THORPEX Interactive Grand Global Ensemble (TIGGE)
5THORPEX Interactive Grand Global Ensemble (TIGGE) test
6-191Reserved
192-254Reserved for local use
255Missing
21 typeOfProcessedData Type of processed data in this GRIB message according to Code Table 1.4:
0Analysis products
1Forecast products
2Analysis and forecast products
3Control forecast products
4Perturbed forecast products
5Control and perturbed forecast products
6Processed satellite observations
7Processed radar observations
8Event probability
8-191Reserved
192-254Reserved for local use
255Missing
22-nn Reserved: need not be present


Back to full table