GTS_FILTER(1)

💖 NAME 💖

okay so bestie, welcome to GTS_FILTER(1), a User Commands page, and no cap it's a whole little cutie. The star of the show is gts_filter — that's the manual page for gts_filter. Yeah, the manpage introduces the program by saying "this is the manpage for the program", which is giving iconic circular energy but we respect it 💅

---

✨ DESCRIPTION ✨

🦋 NAME 🦋

gts_filter

💅 DESCRIPTION 💅

So what does it actually do? It applies the rules defined in rules_file to each GTS message in the GTS files you hand over as arguments. And here's the cute part: if you specify - (a single dash) for the rules_file, the rules get read from standard input instead. Slay, stdin rules, we love a flexible entry point 🫶

🎀 USAGE 🎀

gts_filter [options] rules_file file file ...

That's the whole vibe: [options], then your rules_file, then as many files as your little heart desires.

🔥 OPTIONS 🔥

• -f — Force. It forces the execution not to fail on error. Like, "bestie we are finishing this, idc" 😤
• -o output_file — Output is written to output_file. And if an output file is required but you didn't use -o, the output goes to filter.out. Default city, population: your output 🌸
• -M — Multi-field support off. Turns off support for multiple fields in a single GRIB message.
• -V — Print version. Just a lil "hey here's what version I am" moment 👑
• -g — Copy GTS header.
• -G — GRIBEX compatibility mode.
• -7 — Does not fail when the message has wrong length. (Yeah, the flag is literally the number seven. We don't question it, we just use it ⭐)
• -v — Verbose. It will talk to you. Main character energy, honestly 💅

💀 and then... it says the ENTIRE thing all over again 💀

not me scrolling and finding out this manpage literally repeats itself word for word 🙈 anyway, here it is again, because it's in the original and I am nothing if not faithful:

🌷 NAME 🌷

gts_filter

🌈 DESCRIPTION 🌈

Apply the rules defined in rules_file to each GTS message in the GTS files provided as arguments. If you specify - (a single dash) for the rules_file, the rules will be read from standard input.

🍓 USAGE 🍓

gts_filter [options] rules_file file file ...

🧚 OPTIONS 🧚

• -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
• -M — Multi-field support off. Turn off support for multiple fields in a single GRIB message.
• -V — Print version.
• -g — Copy GTS header.
• -G — GRIBEX compatibility mode.
• -7 — Does not fail when the message has wrong length.
• -v — Verbose.

---

psa bestie: that was the whole page. No extra lore, no secret flags hiding in the back, that's genuinely it 💖

and that's a wrap, bestie — gts_filter, page dated October 2026, filed under GTS_FILTER(1). go filter something gorgeous 🦋✨