BUFR_DUMP(1)

πŸ¦‹ BUFR_DUMP(1) πŸ¦‹

okay bestie, sit down, hydrate 🫢 this is bufr_dump, section 1 of the manual, filed under User Commands, and she is that girl. full name BUFR_DUMP(1), answers to bufr_dump. πŸ’…


πŸ’– NAME πŸ’–

bufr_dump β€” manual page for bufr_dump. yes she's self-referential, yes it's iconic, we move. ✨

✨ DESCRIPTION ✨

πŸŽ€ NAME

bufr_dump

🌸 DESCRIPTION

Dump the content of a BUFR file in different formats. that's the whole job and she eats every single time πŸ¦‹

🧚 USAGE

bufr_dump [options] bufr_file bufr_file ...

options go first, then as many bufr_file arguments as your heart desires. one file? slay. ten files? also slay. πŸ’–

πŸ’… OPTIONS πŸ’…

  • -j s|f|a β€” JSON mode (JavaScript Object Notation), for when you want your data wearing a little curly-brace outfit. Options: s -> structure, f -> flat (only data), a -> all attributes. Default mode is structure.
  • -D filter|fortran|python|C β€” Decoding dump. Hand it over and it provides instructions to decode the input message. Your options:
    • filter -> filter instructions file to decode input BUFR (for bufr_filter)
    • fortran -> fortran program to decode the input BUFR
    • python -> python script to decode the input BUFR
    • C -> C program to decode the input BUFR

Default mode is filter.

  • -E filter|fortran|python|C β€” Encoding dump. Provides instructions to create the input message. Your options:
    • filter -> filter instructions file to encode input BUFR (for bufr_filter)
    • fortran -> fortran program to encode the input BUFR
    • python -> python script to encode the input BUFR
    • C -> C program to encode the input BUFR

Default mode is filter.

  • -O β€” Octet mode. WMO documentation style dump.
  • -p β€” Plain/Flat dump (key=value format).
  • -d β€” Dump the expanded descriptors.
  • -t β€” Print type information.
  • -f β€” Force. Force the execution not to fail on error.
  • -H β€” Print octet content in hexadecimal format.
  • -a β€” Dump aliases.
  • -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,... β€” 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.
  • -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,... β€” 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.
  • -7 β€” Does not fail when the message has wrong length.
  • -V β€” Print version.
  • -S subset_number β€” Dump the given subset
  • -X offset β€” Input file offset in bytes. Processing of the input file will start from the given offset.
  • -h β€” Display this help text and exit.

πŸ”₯ SEE ALSO πŸ”₯

Full documentation and examples at: <https://confluence.ecmwf.int/display/ECC/bufr_dump>


πŸ’€ and then... IT SAYS IT ALL AGAIN πŸ’€

not the page literally copy-pasting itself 😭😭 bestie I am NOT making this up, the original does the whole thing over β€” same sections, same order, same facts. so for the girlies who scrolled past the first time, here we go again. no skip, no cap. πŸ’…

πŸ’– NAME πŸ’– (the encore)

bufr_dump

✨ DESCRIPTION ✨ (yes, again)

🌸 DESCRIPTION

Dump the content of a BUFR file in different formats. still true, still devouring. πŸ¦‹

🧚 USAGE

bufr_dump [options] bufr_file bufr_file ...

πŸ’… OPTIONS πŸ’…

  • -j s|f|a β€” JSON mode (JavaScript Object Notation). Options: s -> structure, f -> flat (only data), a -> all attributes. Default mode is structure.
  • -D filter|fortran|python|C β€” Decoding dump. Provides instructions to decode the input message. Options:
    • filter -> filter instructions file to decode input BUFR (for bufr_filter)
    • fortran -> fortran program to decode the input BUFR
    • python -> python script to decode the input BUFR
    • C -> C program to decode the input BUFR

Default mode is filter.

  • -E filter|fortran|python|C β€” Encoding dump. Provides instructions to create the input message. Options:
    • filter -> filter instructions file to encode input BUFR (for bufr_filter)
    • fortran -> fortran program to encode the input BUFR
    • python -> python script to encode the input BUFR
    • C -> C program to encode the input BUFR

Default mode is filter.

  • -O β€” Octet mode. WMO documentation style dump.
  • -p β€” Plain/Flat dump (key=value format).
  • -d β€” Dump the expanded descriptors.
  • -t β€” Print type information.
  • -f β€” Force. Force the execution not to fail on error.
  • -H β€” Print octet content in hexadecimal format.
  • -a β€” Dump aliases.
  • -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,... β€” 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.
  • -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,... β€” 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.
  • -7 β€” Does not fail when the message has wrong length.
  • -V β€” Print version.
  • -S subset_number β€” Dump the given subset
  • -X offset β€” Input file offset in bytes. Processing of the input file will start from the given offset.
  • -h β€” Display this help text and exit.

πŸ”₯ SEE ALSO πŸ”₯ (round two)

Full documentation and examples at: <https://confluence.ecmwf.int/display/ECC/bufr_dump>


lowkey the fact that this whole page is in here twice is giving deja vu main character energy πŸ’€ but every single detail stays, so read whichever copy you vibe with. 🫢

and that's the tea, bestie β€” last word goes to the page itself: it's bufr_dump, dated October 2026, wearing the BUFR_DUMP(1) crown. periodt. πŸ‘‘πŸŒΈ

πŸ“¦ where this page comes from