GRIB_DUMP(1)

🦋 NAME 🦋

grib_dump — manual page for grib_dump 💅

Oh and heads up bestie, this one lives in the User Commands manual, so if you're scrolling man pages looking for her, that's where she hangs out.

---

✨ DESCRIPTION ✨

Okay so picture this: you've got a GRIB file and you need to see what's inside it. That's the whole job. Dump the content of a GRIB file in different formats. Pick your fave format, she's flexible ✨

ngl the original page prints this entire block — NAME, DESCRIPTION, USAGE, OPTIONS, SEE ALSO — twice, back to back, word for word. not me reading it twice 😭 once is enough, so here it is once, slay.

🎀 USAGE 🎀

grib_dump [options] grib_file grib_file ...

Yep, plural files. You can hand her more than one grib_file and she'll deal with all of them, no cap.

---

👑 OPTIONS 👑

Every single flag, accounted for. Let's go 🫶

• -O — Octet mode. WMO documentation style dump. It's giving official document energy 📜
• -D — Debug mode. For when you wanna be nosy about what's going on under the hood 🕵️
• -d — Print all data values. All of them. Every single value. rip to your scrollback, fr fr 💀
• -j — JSON mode (JavaScript Object Notation). Yes bestie, actual JSON, feed it straight to your pipeline 🌈
• -t — Print type information. So you know what kind of thing each thing is 🏷️
• -H — Print octet content in hexadecimal format. Hex vibes only 🔥
• -a — Dump aliases. Every alias gets exposed, main character reveal 👑
• -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,... — The 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 you can specify a string (key:s), a double (key:d) or an integer (key:i) type — 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. Yeah. One. That's the rule 😤
• -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,... — Key/values to set. For each key you can define a string (key:s), a double (key:d) or an integer (key:i) type. By default the native type is set. So just hit send and she'll figure out the type herself 💁
• -M — Multi-field support off. Turns off support for multiple fields in a single GRIB message. One field, one message, we're keeping it simple 🎀
• -T T | B | A — Message type. T->GTS, B->BUFR, A->Any (Experimental). The input file is interpreted according to the message type. Ngl that A one is marked Experimental, so proceed with the awareness of a girl who reads the fine print 🧚
• -7 — Does not fail when the message has wrong length. Chaotic but brave, and honestly? iconic 💅
• -V — Print version. Gotta know which build you're on ⭐
• -p key1,key2,... — Declaration of keys to dump. Only those keys get dumped, not the whole message. Perfect for when you want a lil snack instead of the whole meal 🍓
• -X offset — Input file offset in bytes. Processing of the input file will start from the given offset. Skip to the good part 🦋
• -x — Fast parsing option, only headers are loaded. Zoom zoom, headers only, no baggage 🚀
• -h — Display this help text and exit. Your "hello?? how does this work" button, absolutely zero shame in it 💖

---

🌈 SEE ALSO 🌈

Full documentation and examples at:

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

Go read the docs bestie, they ate 👑

---

and that's the whole page, periodt 💜 this was the grib_dump page from the User Commands manual, dated October 2026 — screenshot it, bookmark it, keep it in the group chat 🌸