CODES_BUFR_FILTER(1)

πŸ’– CODES_BUFR_FILTER β€” bestie's guide to the codes_bufr_filter manual page πŸ’–

so okay, the manual name for this whole thing is CODES_BUFR_FILTER(1) and we are going to get into it together ✨ buckle up


✨ NAME ✨

codes_bufr_filter β€” the manual page for codes_bufr_filter. that's it, that's the name, she's a little meta like that πŸ’…

🌸 DESCRIPTION 🌸

🫢 NAME 🫢

bufr_filter β€” yes bestie, there's a whole second NAME hiding inside the DESCRIPTION, iconic behaviour, we love a nested reveal πŸ’€

πŸ’œ DESCRIPTION (for real this time) πŸ’œ

Apply the rules defined in rules_file to each BUFR message in the BUFR files you hand over as arguments. every single one, no skipping, she's thorough πŸ¦‹

And listen β€” if you pass - (a single dash) as the rules_file, the rules get read from standard input. that's the plot twist right there, periodt πŸŽ€

🌈 USAGE 🌈

bufr_filter [options] rules_file bufr_file bufr_file ...

that's the shape of it: options, then your rules file, then as many BUFR files as your heart desires πŸ’«

πŸ‘‘ OPTIONS πŸ‘‘

  • -f β€” Force. literally force the execution not to fail on error. she's pushing through, no cap πŸ”₯
  • -o output_file β€” Output gets written to output_file. but here's the tea: if an output file is required and you did not use -o, the output goes to filter.out instead. default behaviour, we don't make the rules πŸ™ˆ
  • -V β€” Print version. show me the numbers, bestie ⭐
  • -g β€” Copy GTS header. yes queen, bring the header along πŸŽ€
  • -7 β€” Does not fail when the message has wrong length. she's forgiving like that πŸ’…
  • -v β€” Verbose. tell me everything, I'm sat πŸ“
  • -h β€” Display this help text and exit. the classic escape hatch πŸ’–

🧚 SEE ALSO 🧚

Full documentation and examples at:

<https://confluence.ecmwf.int/display/ECC/bufr_filter>

go read, iykyk πŸ“š


okay so real talk β€” the page prints this ENTIRE block twice. not me making it up, go look, it's right there. so obviously we're keeping every detail and serving you the ✨encore✨, because the vibe changes but the facts never do, fr fr πŸ’…

✨ NAME ✨ (again, because the page said so)

codes_bufr_filter β€” the manual page for codes_bufr_filter 🫢

🌸 DESCRIPTION 🌸 (encore)

🫢 NAME 🫢

bufr_filter πŸ’œ

πŸ’œ DESCRIPTION πŸ’œ

Apply the rules defined in rules_file to each BUFR message in the BUFR files provided as arguments. And if you specify - (a single dash) for the rules_file, the rules will be read from standard input. same energy, same facts 🌈

🌈 USAGE 🌈

bufr_filter [options] rules_file bufr_file bufr_file ...

πŸ‘‘ OPTIONS πŸ‘‘ (round two, baby)

  • -f β€” Force. Force the execution not to fail on error. πŸ”₯
  • -o output_file β€” Output is written to output_file. If an output file is required and -o is not used, the output is written to filter.out πŸ’–
  • -V β€” Print version. ⭐
  • -g β€” Copy GTS header. πŸŽ€
  • -7 β€” Does not fail when the message has wrong length. πŸ’…
  • -v β€” Verbose. πŸ“
  • -h β€” Display this help text and exit. πŸ™ˆ

🧚 SEE ALSO 🧚 (yes, again)

Full documentation and examples at:

<https://confluence.ecmwf.int/display/ECC/bufr_filter> 🌸


and that's the whole page, bestie! πŸ₯³ this little love letter is signed codes_bufr_filter, dated October 2026, and it lives under the manual name CODES_BUFR_FILTER(1). you understood it, you slayed it, go filter some BUFR messages πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from