Often asked questions Eva Červená CZECH HYDROMETEOROLOGICAL INSTITUTE

Slides:



Advertisements
Similar presentations
1 Often asked questions Eva Červená CZECH HYDROMETEOROLOGICAL INSTITUTE WORLD METEOROLOGICAL ORGANIZATION RA VI Training Workshop on BUFR and Migration.
Advertisements

CREX CREX Code Form Examples of CREX messages Sections of a CREX message Section 0 – Indicator Section CREX Beginning of a CREX message.
Templates and Regulations
BUFR decoding Dominique Lucas – Milan Dragosavac
FM 94 BUFR and FM 95 CREX Table Driven Code Forms (or “Self-descriptive” Code Forms). The term "self-descriptive" means that the form and content of the.
Commission for Instruments and Methods of Observation Fourteenth Session Geneva, 7 – 14 December 2006 INSTRUMENTS AND METHODS OF OBSERVATION FOR SURFACE.
UPDATING TABLE DRIVEN CODE FORMS 18 April 2006 (Joël Martellet, WMO, World Weather Watch, Data Processing and Forecasting Systems)
CLIMAT (CLIMAT TEMP) History: 1935 – IMO (International Meteorological Organization) that mean monthly values of the main climatological elements at certain.
WHY TABLE DRIVEN CODE FORMS?
Training on Meteorological Telecommunications Alanya, Turkey, September 2010 General Philosophy of Table Driven Code Forms Simon Elliott, EUMETSAT.
1 Often asked questions Eva Červená CZECH HYDROMETEOROLOGICAL INSTITUTE TRAINING ON METEOROLOGICAL TELECOMMUNICATIONS WMO RTC-Turkey facilities, Alanya,
SYNOPTIC OBSERVATIONS DECODING & PLOTTING. ENCODING WEATHER INFORMATION In order for people to send information around the world using the WMO discussed.
CLIDATA ATACO Ltd. METEOHYDEX Introduction Primary archiving of the climatology data Primary archiving of the climatology data Replaced the Clicom.

Status, Evaluation and New Developments of the Automated Cloud Observations in the Netherlands Wiel Wauben, Henk Klein Baltink, Marijn de Haij, Nico Maat,
Dominic Lowe, British Atmospheric Data Centre, STFC OGC TC, Boulder.
Introduction to BUFR TRAINING ON METEOROLOGICAL TELECOMMUNICATIONS WMO RTC-Turkey facilities, Alanya, Turkey September 2010.
WMO RTC-Turkey facilities, Alanya, Turkey Templates and Regulations
WORLD METEOROLOGICAL ORGANIZATION RA-VI Regional Training on BUFR and Migration to Table Driven Code Forms Langen, Germany, April, 2007 General.
IN THE NAME OF GOD SYNOPTIC METEOROLOGY CHAPTER ONE: METEOROLOGICAL STATIONS AND DATA SUMMER, 2011.
Deutscher Wetterdienst Implementation of GRIB2 A Discussion COSMO Working Group 6: Reference Version and Implementation Working Group Coordinator: Ulrich.
Reflections on the theme of classifying, documenting and exchanging meteorological data, and some additional comments on agro meteorological and biological.
WMO GRIB Edition 3 Enrico Fucile Inter-Program Expert Team on Data Representation Maintenance and Monitoring IPET-DRMM Geneva, 30 May – 3 June 2016.
The Course of Synoptic Meteorology
WIGOS regulatory and guidance material
Device Security in Cognitive Radio
Emergency Call Support
THURSDAY TARGETED TRAINING: Reporting Regulations and Requirements
Binary Universal Form Representation (BUFR) Paul Hamer November, 2009
Standard Data Encoding
Weather Forecasting.
Control Structures II Chapter 3
SAP University Alliances
Parts of an Academic Paper
Climate , Climate Change, and climate modeling
Need to condense this information in a small space
Lessons from incompatible units of time-integrated GRIB parameters
The Price IS Right: What can the billing module do for me?
IT 0213: INTRODUCTION TO COMPUTER ARCHITECTURE
Roadmap to Enhanced Technical Regulations of WMO
WMO, World Weather Watch, Data Processing and Forecasting Systems)
Weather Maps.
Much information is needed to interpret what is happening with the atmosphere.
Secretariat 12 to 16 February 2017 Abu Dhabi, UAE
Surface Weather Observations
(Part 3-Floating Point Arithmetic)
Decisions on CBS activities to support WMO priority activities
Aim: What are station models?
The Course of Meteorological Instrumentation and Observations
Handbook on Meteorological Observations
Linear Equations in Linear Algebra
Closure ESF programs Very brief overview of where we stand with this exercise.
EG1204: Earth Systems: an introduction
Technical Coordinator - Data Buoy Cooperation Panel
QoS aware Load Balancing
Coding issues BUFR Binary Universal code Form for the Representation of meteorological data Binary Table driven code form (BUFR, CREX) Efficient compression.
Copyright © Cengage Learning. All rights reserved.
Example I: Predicting the Weather
Peter Seibel Practical Common Lisp Peter Seibel
QoS aware Load Balancing
William Stallings Computer Organization and Architecture 10th Edition
CHAPTER – 1.1 UNCERTAINTIES IN MEASUREMENTS.
Computer Organization and Architecture Designing for Performance
AWS Network Requirements Analysis and Network Planning
International Whole Vehicle Type Approval
Linear Equations in Linear Algebra
Summer Ozone Data Exchange
The Course of Synoptic Meteorology
CSPA Templates for sharing services
CSPA Templates for sharing services
Presentation transcript:

Often asked questions Eva Červená CZECH HYDROMETEOROLOGICAL INSTITUTE WORLD METEOROLOGICAL ORGANIZATION RA VI Training Workshop on BUFR and Migration to Table-Driven Code Forms Langen, Germany, 17-20 April 2007 Often asked questions Eva Červená CZECH HYDROMETEOROLOGICAL INSTITUTE

Usage of common sequence descriptors is highly recommended: Q: Are the common sequence descriptors mandatory? This leads to inclusion of too many missing values. Usage of common sequence descriptors is highly recommended: - It is suitable for data processing (filtering, etc.). - It prevents introduction of rather serious mistakes caused by not quite qualified modifications of the existing templates. - The data description section is expressed in a concise way.

Q: Why the version of BUFR master table has to be indicated in the Section 1 although all descriptors are kept in the tables, including the entries that should not to be used anymore? The version number of BUFR master table allows to create different tables. The deprecated entries do not have to be necessarily included in the next version of the tables. Thus, the archived data could not be properly processed without the indication of version number of the tables. Moreover, the time may come when some of the tables will be filled to their capacity and the deprecated entries might be needed for the newly introduced elements.

Q: The number of cloud layers or masses should be positive in a NIL report. Why not 0? This question applies to the number of cloud layers (0 31 001), but the same question could be asked referring to the number of levels in the upper-air data (0 31 002). Or to a sequence, where 0 31 000 is used. In a NIL report, all parameters shall be set to “missing”, with the exception of the station identification and delayed replication factors. To oblige this definition, the delayed replication factors 0 31 000, 0 31 001 and 0 31 002 shall be set to 1, so that the entries (to be replicated) could be set to missing. Moreover, if the report is included in a BUFR multi-subset message to be compressed, 0 31 000, 0 31 001 or 0 31 002 shall be set to 1, 2, 3, … (number of replications has to be identical in all subsets). Generally expressed, delayed replication factors have to be positive in a NIL report.

Q: The number of cloud layers or masses shall never be missing. Why Q: The number of cloud layers or masses shall never be missing. Why? If the observation is not made, the number of cloud layers is not known. Delayed descriptor replication factors, e.g. 0 31 001, must never be set to missing (number of replications has to be known to allow the encoding/decoding procedure). If the observation is not made, e.g. at an automatic station without ceilometer, then 0 31 001 preceding 3 02 005 shall be set to 1 and all the parameter within 3 02 005 shall be set to a missing value.

Q: How should be a missing value of a CCITT IA5 element encoded Q: How should be a missing value of a CCITT IA5 element encoded? By all bits set to 0 or all bits set to 1? A missing value is expressed by all bits set to 1 within the data width of the element. This applies to all elements, including those with the “Unit” defined as CCITT IA5.

Q: In BUFR flag tables, bits are numbered from 1 to x. Bit No Q: In BUFR flag tables, bits are numbered from 1 to x. Bit No. 1 is the rightmost one or the leftmost one? Bit No. 1 in all BUFR flag tables is the leftmost one, i.e. the bit No. 1 is the most significant within the data width. The rightmost bit (x) is the least significant and is set to 1 only if all bits are set to 1 to express “missing”.

Q: Total precipitation past 24 hours is included in 3 02 035 (Basic synoptic “instantaneous” data). Why is it so, if it refers to the previous 24 hours? “Instantaneous” parameter is a parameter that is not coupled to a time period descriptor. Total precipitation past 24 hours (013023) expresses the required meaning by itself, and therefore does not need to be preceded by 0 04 024 (Time period in hours). It was introduced to represent R24R24R24R24 (SYNOP, section 3, group 7). The amount of precipitation in groups 6RRRtR is reported from different periods, and therefore they are represented by Total precipitation (0 13 011 ) being preceded by 0 04 024.

Q: The order of entries in the template TM 307080 does not correspond with the order of the elements in a SYNOP message. Why? In a SYNOP message, elements of “period” character are followed by “instantaneous” elements. In a BUFR message, all “instantaneous” elements have to be reported first and only then the elements of “period” character may follow. Once a period descriptor is introduced, it applies to all following elements until it is redefined by another period descriptor. TDCF allow more precise data representation, consequently their flexibility being somewhat limited.

Q: If an element is reported as missing, is the height of sensor and the time period mandatory? The height of sensor is considered to be mandatory regardless whether the element is reported as a missing or non-missing value. The time period is mandatory to be included in the reports, when the element is required be reported in compliance with the global or regional regulations, e.g. in RA VI, maximum temperature of the preceding 12 hours shall be reported at 18 UTC. As no other period than preceding 12 hours is required in RA VI, the first value of 0 04 024 may be set to -12 and the second value of 0 04 024 may be set to 0 in all reports. The amount of precipitation in group 6RRRtR of Section 1 is reported from the preceding 12 hours at 06 and 18 UTC and from the preceding 6 hours at 00 and 12 UTC. Therefore, 0 04 024 shall set to -12 at 06 and 18 UTC and shall set to -6 at 00 and 12 UTC even if the value of 0 13 011 is missing.

Q: When should be the type of station reported as “hybrid”? Type of station (0 02 001) shall be reported using code figure 2 (Hybrid) in BUFR messages containing monthly values (CLIMAT and CLIMAT SHIP data) to indicate that the station operated as a manned station for part of the day and as an automatic station for the rest of the day during the relevant month period. Regarding synoptic data in BUFR, it is highly recommended to use code figure 1 (Manned) in reports produced under the supervision of an observer, and code figure 0 (Automatic) in reports produced while the station operates in the automatic mode in compliance with the values of ix in the TAC reports.

Q: How should be encoded 3 02 004, if sky clear is observed? Cloud data 0 20 010 Cloud cover total = 0 % 0 08 002 Vertical significance = 62 (sky clear) 0 20 011 Cloud amount (of low or middle clouds) = 0 0 20 013 Height of base of clouds = missing 0 20 012 Cloud type = 30 (No low clouds) Cloud type = 20 (No middle clouds) Cloud type = 10 (No high clouds)

Q: How should be encoded 3 02 004, if sky is obscured by fog? Cloud data 0 20 010 Cloud cover total = 113 % 0 08 002 Vertical significance = 5 (ceiling) 0 20 011 Cloud amount (of low or middle clouds) = 9 0 20 013 Height of base of clouds = vertical visibility 0 20 012 Cloud type = 62 (CL clouds invisible .....) Cloud type = 61 (CM clouds invisible ….) Cloud type = 60 (CH clouds invisible ….)

Q: If only high clouds CH are observed, vertical significance in 3 02 004 should be set to 0. Why not to 9 (High cloud)? Vertical significance 0 08 002 is used to specify two following elements, i.e. cloud amount 0 20 011 and height of cloud base 0 20 013. E.g. if CL clouds are observed, 0 08 002 = 7 expresses that both following elements refer to low clouds. If only high clouds CH are observed, however, the cloud amount refers to CL and CM (0 20 011 = 0), whereas the height of cloud base refers to CH. Therefore 0 08 002 has to be set to 0 (Observing rules of FM 12 SYNOP and FM 13 SHIP apply). It is the only case, when 0 08 002 is to be set to 0.

Q: How should be encoded 0 08 002 (vertical significance) in 3 02 005 if four cloud layers are reported, a Cb in the second layer? If sky is not obscured by fog or other meteorological phenomena, vertical significance 0 08 002 within 3 02 005 is encoded using code figures 1, 2, 3 and 4, where 4 = Cumulonimbus layer. Four cloud layers: 1/8 St 250 m, 2/8 Cb 300 m, 3/8 Sc 600m and 5/8 Ac 3000 m (81708 82910 83620 85360 in SYNOP). In this case, 0 08 002 shall be set to 1, 4, 2 and 3 in the first, second, third and fourth replication of 3 02 005, respectively.

Q: How should be encoded 0 08 002 (vertical significance) in 3 02 005 if four cloud layers are reported from a ceilometer of an AWS? An automatic station equipped with a ceilometer may be able to report cloud amount and height of the base of the individual cloud layers, but the type of clouds is not available. If four cloud layers are reported from an AWS, e.g. 81/11 83/14 85/24 88/56 in SYNOP, vertical significance 0 08 002 shall be set to 1, 2, 3 and missing in the first, second, third and fourth replication of 3 02 005, respectively.

Q: Is reporting of normal monthly values mandatory? Normal monthly values are mandatory in BUFR messages containing monthly values (CLIMAT and CLIMAT SHIP data). It is recommended to include the normal values to ease the maintenance of the database of these values (to avoid potential problems caused by the normals or their changes being available for very limited period in the TAC data).

Q: Regulation B/C 25.8.4.2 about no maximum wind level might need clarification. “When no maximum wind level is observed, no level shall be indicated by bit No. 4 of 0 08 042 set to 1.” When no maximum wind level is observed, bit No. 4 of 0 08 042 shall be set to 0 at all levels. These two statements are fully equivalent.

Q: What are the currently produced Category 1 data in RA VI ? TEMP Netherlands SYNOP Germany Czech Republic Israel IUSD01 EHDB ISMD42 EDZW ISMD01 OKPR ISMD01 LLBD ISID42 EDZW ISMD11 OKPR ISMD42 LLBD IUSD40 OKLI ISND42 EDZW ISID01 OKPR ISID21 LLBD Jordan ISID11 OKPR ISID42 LLBD IUSD01 LLBD ISMD01 OJAM ISND11 OKPR CLIMAT IUSD02 LLBD ISID01 OJAM ISCD01 LLBD

Other questions?