27.03.2013 Views

Guide to WMO Table Driven Code Forms

Guide to WMO Table Driven Code Forms

Guide to WMO Table Driven Code Forms

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Code</strong> <strong>Table</strong> 1.0: GRIB Master <strong>Table</strong>s Version Number<br />

<strong>Code</strong> figure Meaning<br />

0 Experimental<br />

1 Version implemented on 7 November 2001<br />

2 Version implemented on 4 November 2003<br />

3 Version implemented on 2 November 2005<br />

4 Version implemented on 7 November 2007<br />

5 Pre-operational <strong>to</strong> be implemented by next amendment<br />

6-254 Future versions<br />

255 Missing value<br />

<strong>Code</strong> <strong>Table</strong> 1.1: GRIB Local <strong>Table</strong>s Version Number<br />

<strong>Code</strong> figure Meaning<br />

0 Local tables not used. Only table entries and templates from the current Master table are valid.<br />

1-254 Number of local tables version used<br />

255 Missing<br />

The <strong>WMO</strong> Secretariat maintains all versions of the GRIB Master <strong>Table</strong>. Octet 10 contains the<br />

version number of the Master <strong>Table</strong> used <strong>to</strong> generate the data contained in the GRIB message. If<br />

octet 10 contains the value 255, however, a local table was used. In this case, the value in octet<br />

11 – Local <strong>Table</strong> Version Number – is the relevant one. However, <strong>to</strong> obtain the local table version<br />

referred <strong>to</strong> by octet 11, one must contact the centre that originated the data in the GRIB message<br />

as identified by octets 6-7 and 8-9. If local tables were not used, octet 11 will contain the value 0.<br />

The meaning of the Reference Time of the Data in GRIB1 was a source of some confusion<br />

because it was not clearly defined. In an attempt <strong>to</strong> be more precise, the Reference Time of the<br />

Data in GRIB2 is given in terms of both a date/time and its significance. The significance of the<br />

reference time – contained in octet 12 – refers <strong>to</strong> <strong>Code</strong> <strong>Table</strong> 1.2, currently defined as:<br />

<strong>Code</strong> <strong>Table</strong> 1.2: Significance of Reference Time<br />

<strong>Code</strong> figure Meaning<br />

0 Analysis<br />

1 Start of forecast<br />

2 Verifying time of forecast<br />

3 Observation time<br />

4-191 Reserved<br />

192-254 Reserved for local use<br />

255 Missing<br />

This parameter identifies, for example, whether the Reference Date/Time refers <strong>to</strong> the time of an<br />

analysis (octet 12 = 0), the start of a forecast (octet 12 = 1), the verifying time of a forecast (octet<br />

12 = 2), etc. The precise time of the data itself is found by combining the Reference Date/Time<br />

itself, contained in octets 13 – 19, with additional time information given in the Product Definition<br />

Section (Section 4).<br />

16

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!