Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DESCRIPTION

Get values of some header keys from a

...

BUFR file. It is similar to

...

bufr_ls, but fails returning an error code when an error occurs (e.g. key not found).

USAGE

bufr_get [options] file file ...

OPTIONS

...

Force. Force the execution not to fail on error.

...

Declaration of keys to print. For each key a string (key:s)

...

, a double (key:d) or

...

an integer (key:

...

i) type can be requested. Default type is string.

...

C style format for floating

...

-

...

point

...

values

...

.

...

...

As -p adding the declared keys to the default list.

...

Where clause.

...

Messages are processed only if they match all the key/value constraints. A valid constraint is of type key=value or key!=value. For each key a string (key:s)

...

, a double (key:d) or

...

an integer (key:

...

i) type can be specified. Default type is string. In the value you can also use the forward-slash character '/' to specify an OR condition (i.e. a logical disjunction) Note: only one -w clause is allowed.

...

All the keys belonging to namespace are printed.

...

Key/values to set. For each key a string (key:s)

...

, a double (key:d) or

...

an integer (key:

...

i) type can be defined. By default the native type is set.

...

Version.

...

Minimum width of each column in output. Default is 10.

...

Mars keys are printed

...

.

...

Copy GTS header

...

.

...

Does not fail when the message has wrong length

...

bufr_get examples

  1. bufr_get fails if a key is not found.

    Code Block
     
    > bufr_get -p centreName ../data/bufr/syno_1.bufr