GTS_DUMP(1)

πŸ’– NAME πŸ’–

gts_dump β€” the manual page for gts_dump. That's the whole thing. Short, iconic, no notes. πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay bestie, sit down, because this description is literally a whole manual page nested inside another manual page, and then it does the entire thing a second time. Twice. Back to back. That is genuinely what's in the source, I'm not being extra, I promise. 🫢

✨ NAME ✨

gts_dump

πŸŽ€ DESCRIPTION πŸŽ€

Dump the content of a GTS file in different formats. Lowkey the whole point of the program. 🌸

🌈 USAGE 🌈

gts_dump [options] file file ...

Not one file, not two files β€” file file ..., plural, keep 'em coming. ✨

πŸ‘‘ OPTIONS πŸ‘‘

  • -O β€” Octet mode. Dumps it the WMO documentation style way. 🧚
  • -D β€” Debug mode.
  • -d β€” Print all the data values. All of them. Every single one. πŸ’€
  • -t β€” Print type information.
  • -H β€” Print the octet content in hexadecimal format. Hex girlies rise. πŸ”₯
  • -a β€” Dump aliases.
  • -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,... β€” The where clause. Messages only get processed if they match all the key/value constraints. A valid constraint looks like key=value or key!=value. For each key you can say it's a string (key:s), a double (key:d) or an integer (key:i) β€” default type is string if you don't specify. And in the value you can use the forward-slash character / to write an OR condition (a logical disjunction, iykyk). > Heads up bestie: only one -w clause is allowed. One. Not two. Periodt.
  • -7 β€” Does not fail when the message has the wrong length. Chaotic but forgiving. πŸ™ˆ
  • -V β€” Print version.
  • -x β€” Fast parsing option β€” only headers get loaded. Speed demon behaviour. ⚑

And now… round two, same energy, because the page literally repeats itself. Not a glitch in the matrix, bestie. πŸ’œ

✨ NAME ✨ (yes, again πŸŽ€)

gts_dump

πŸŽ€ DESCRIPTION πŸŽ€ (again, fr fr)

Dump the content of a GTS file in different formats.

🌈 USAGE 🌈 (again 🌸)

gts_dump [options] file file ...

πŸ‘‘ OPTIONS πŸ‘‘ (the sequel πŸ¦‹)

  • -O β€” Octet mode. WMO documentation style dump. 🧚
  • -D β€” Debug mode.
  • -d β€” Print all data values. πŸ’€
  • -t β€” Print type information.
  • -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. Same rule as before, it did not change in the last thirty seconds. πŸ™ˆ
  • -7 β€” Does not fail when the message has wrong length.
  • -V β€” Print version.
  • -x β€” Fast parsing option, only headers are loaded. ⚑

That's the whole page, bestie β€” every flag, every default, every little caveat, fully intact, no cap. This one's gts_dump, and it's dated October 2026. Go dump some GTS files, you absolute icon. πŸ‘‘πŸ’–βœ¨

πŸ“¦ where this page comes from