-
Access keys by condition - ecCodes BUFR FAQ (User Documentation) — The key “backscatter” will return an array with all the backscatter values in the BUFR tree, while will return the values of backscatter in the branch of the tree where the condition "beamIdentifier=3" is satisfied.
-
Access keys by rank - ecCodes BUFR FAQ (User Documentation) — Each key can appear several times in a BUFR message.
Examples are:
-
Accessing subsets - ecCodes BUFR FAQ (User Documentation) — BUFR has two different ways of encoding information in the data section
compressed
uncompressed
-
Add/remove local section in a message - ecCodes BUFR FAQ (User Documentation) — In a BUFR message it is possible to have an optional section 2 to be used as local section for information that is relevant for the processing and archiving systems used by a processing centre. Adding or removing a local section from a BUFR message is very easy with ecCodes by setting the key "section2Present"
-
Adding your own local definition - ecCodes BUFR FAQ (User Documentation)
-
Area extraction in bufr_filter - ecCodes BUFR FAQ (User Documentation) — There are keys to allow the user to extract an area from BUFR data
-
BUFR structure - ecCodes BUFR FAQ (User Documentation)
-
Converting edition 1 to 2 - ecCodes GRIB FAQ (User Documentation) — GRIB messages are at the moment exchanged in edition 1 or 2. Although the information content of two messages in different editions is almost the same, their binary format is very different and organised in a different way
-
Dump instructions to create the input - ecCodes BUFR FAQ (User Documentation) — There is a "-E" option in the bufr_dump tool to generate instructions to create (encode) the input BUFR message.
-
Dump instructions to decode the input - ecCodes BUFR FAQ (User Documentation) — There is a "-D" option in the bufr_dump tool to generate instructions to read (decode) the input BUFR message.
-
Encoding of Delayed Replications- ecCodes BUFR FAQ (User Documentation) — A delayed replication is a way of replicating n times a block of data in a BUFR message by expressing the value of n in the data section itself as opposed to repeating the blocks statically in the definition of the structure. This is possible because the structure of the message is defined in section 3 through the sequence of unexpandedDescriptors while the data themselves are encoded in section 4 (data section) according to the structure defined in section 3.
-
GRIB Keys - ecCodes GRIB FAQ (User Documentation) — Some older GRIB decoders used to work on a number-based table to retrieve all the information from the message. This approach forced the user either to learn a code table or to use the documentation intensively. With ecCodes a key name based access is provided so that all the information contained in the GRIB message is retrieved through alphanumeric names.
-
How can I encode pressure with higher precision - ecCodes BUFR FAQ (User Documentation)
-
How can I set the verbosity level to see debug output? - ecCodes FAQ (User Documentation) — There is an environment variable called ECCODES_DEBUG: If set to -1, it will enable brief debug-level logging messages to be displayed by the library. If set to 1, you will get very verbose output.
-
How do I change the data structure in a message - ecCodes BUFR FAQ (User Documentation) — A BUFR message is made of some headers and a data section. The structure of the data section is defined in the headers by a sequence of BUFR descriptors, which are sequences of six digit numbers having a particular meaning (see BUFR tables). To modify this sequence of descriptors ecCodes provides the key unexpandedDescriptors.
Overview
Community Forums
Content Tools