1 / 18

BUFR/CREX Templates and Regulations Eva Č ervená

WORLD METEOROLOGICAL ORGANIZATION RA VI Training Workshop on BUFR and Migration to Table-Driven Code Forms Langen, Germany, 17-20 April 2007. BUFR/CREX Templates and Regulations Eva Č ervená. CZECH HYDROMETEOROLOGICAL INSTITUTE.

lada
Download Presentation

BUFR/CREX Templates and Regulations Eva Č ervená

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WORLD METEOROLOGICAL ORGANIZATION RA VI Training Workshop on BUFR and Migration to Table-Driven Code Forms Langen, Germany, 17-20 April 2007 BUFR/CREX Templates and Regulations Eva Červená CZECH HYDROMETEOROLOGICAL INSTITUTE

  2. Traditional codes for which BUFR/CREX templates and regulations have been developed:

  3. Time identification in Section 1 and Section 4

  4. BUFR templates for surface observations Templates TM 307080, TM 307090 and TM 308009 for reporting SYNOP, SYNOP MOBIL and SHIP data in TDCF are constructed in a similar way. They consists of 3 parts: • Station, time and location identification • Instantaneous data • Period data

  5. BUFR templates for surface observations • Instantaneous data “Instantaneous” parameter is a parameter that is not coupled to a time period descriptor. • Period data “Period” parameter is a parameter that is preceded with a time period descriptor, which allows more precise data description than in traditional codes. However, once a period descriptor is introduced, it applies to all following entries until it is redefined by another period descriptor.

  6. BUFR template TM 307080 for SYNOP Station, time and location identification 3 01 090 Instantaneous data • 3 02 031 Pressure data • 3 02 035 Basic synoptic “instantaneous” data • 3 02 036 Clouds with bases below station level • 3 02 047 Direction of cloud drift • 0 08 002 Vertical significance • 3 02 048 Direction and elevation of cloud • 3 02 037 State of ground, snow depth, ground min. temperature Period data • 3 02 043 Basic synoptic “period” data • 3 02 044 Evaporation data • 1 01 002 Replicate next descriptor 2 times • 3 02 045 Radiation data • 3 02 046 Temperature change

  7. Height of sensor Measured values of some elements are significantly influenced by the height of sensor. Based on the requirements of OPAG IOS experts, a new parameter 007032 (Height of sensor above local ground or marine platform) has been introduced to be reported for • Temperature and humidity data • Visibility data • Precipitation data • Wind data In case of marine data, also the height of sensor above water (0 07 033) is required to be reported for • Temperature and humidity data • Visibility data • Wind data

  8. The heights of sensor 007032 and 007033 within the templates for surface data The entries within the “instantaneous data” as well as within the “period data” are grouped according to the requirement for the heights of sensor to be included or not. For example, within 3 02 043 (Basic synoptic “period” data), there is a block of entries: • 3 02 040 Precipitation data, • 3 02 041 Extreme temperature data, • 3 02 042 Wind data, • 0 07 032 Height of sensor above local ground (shall be set to missing to cancel the previous value). The last entry was inserted because the height of sensor is not required for the following data (Evaporation data, etc.).

  9. Modification of templates for surface observations If regional or national reporting practices require inclusion of additional period parameters, the common sequence descriptors 3 07 080, 3 07 090 and 3 08 009 may be supplemented by relevant descriptors. If regional or national reporting practices require inclusion of additional instantaneous parameters, the common sequence descriptors 3 07 080, 3 07 090 and 3 08 009 cannot be used. In this case, they shall be used in the first level expanded form and the new entries shall be inserted to precede 3 02 043 (Basic synoptic period data) or 3 02 060 (SHIP period data).

  10. BUFR template TM 307086 for SYNOP data in compliance with reporting practices in RA VI Station, time and location identification3 01 090 Instantaneous data • 3 02 031 Pressure data • 3 02 035 Basic synoptic “instantaneous” data • 3 02 036 Clouds with bases below station level • 0 08 002 Vertical significance • 3 02 037 State of ground, snow depth, ground min. temperature • 3 02 066 Dangerous weather phenomena (groups 9SPSPsPsP) Period data • 3 02 043 Basic synoptic “period” data • 3 02 044 Evaporation data • 1 01 002 Replicate next descriptor 2 times • 3 02 045 Radiation data • 3 02 046 Temperature change

  11. BUFR templates for upper-air measurements Templates TM 309050, TM 309051 for reporting PILOT, PILOT MOBIL and PILOT SHIP data and TM 309052 for TEMP, TEMP MOBIL, TEMP SHIP and TM 309053 for TEMP DROP data are constructed in a similar way: • Station, time and location identification • Instrumentation • Surface observations (only forTEMP, TEMP MOBIL, TEMP SHIP) • Level data (wind or P,T, U and wind) • Wind shear data

  12. Specific features of Regulations for reporting upper-air data in TDCF • A message should be produced when level 100 hPa is reached. All required data from the entire ascent shall be reported in another message, produced when the sounding is completed. • Time and location of radiosonde shall be included at each level. • If high vertical resolution data is required, data from additional levels may be included, number of levels being limited by the message length – 500000 octets. • The data should be included in descending order with respect to pressure (in ascending order with respect to altitude).

  13. Reporting of additional information If regional reporting practices require inclusion of data at additional levels, these levels shall be indicated by the bit No. 15 set to 1 in Extended sounding significance 008042. Other additional levels shall be specified by all bits of 008042 set to 0. If additional information on sounding instrumentation is required, the common sequence descriptors may be supplemented by one or more parameters to allow representation of such information or by a character data field (using 2 05 Y).

  14. BUFR template for monthly surface data Templates TM 307073 for CLIMAT data and TM 08013 for CLIMAT SHIP data are constructed in a similar way: • Station, time and location identification • Monthly data (with the exception of precipitation) • Monthly precipitation data • Monthly normal values of elements (with the exception of precipitation) • Monthly normal values of precipitation

  15. Period for monthly surface data The time identification refers to the beginning of the one-month period. • Except for precipitation measurements, the one-month period for monthly data is recommended to correspond to the local standard time (LST) month. • In case of monthly precipitation data, the one-month period begins at 06 UTC on the first day of the month and ends at 06 UTC on the first day of the following month. • The same applies for normal values (with the exception of precipitation) and normal values of precipitation.

  16. BUFR template for monthly aerological means Template TM 309054 for reporting CLIMAT TEMP and CLIMAT TEMP SHIP: • Station, time and location identification • Monthly mean data(number of missing days included) Monthly mean data are currently required from 10 levels. If data from additional levels were required in the future or by national decision, they can be included.

  17. Thanks for your attention !

More Related