1GRIB_DUMP(1) User Commands GRIB_DUMP(1)
2
3
4
6 grib_dump - manual page for grib_dump
7
9 NAME grib_dump
10
11 DESCRIPTION
12
13 Dump the content of a GRIB file in different formats.
14
15 USAGE
16
17 grib_dump [options] grib_file grib_file ...
18
19 OPTIONS
20
21 -O Octet mode. WMO documentation style dump.
22
23 -D Debug mode.
24
25 -d Print all data values.
26
27 -j JSON mode (JavaScript Object Notation).
28
29 -t Print type information.
30
31 -H Print octet content in hexadecimal format.
32
33 -a Dump aliases.
34
35 -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
36
37 Where clause. Messages are processed only if they match all the
38 key/value constraints. A valid constraint is of type key=value
39 or key!=value. For each key a string (key:s), a double (key:d)
40 or an integer (key:i) type can be specified. Default type is
41 string. In the value you can also use the forward-slash charac‐
42 ter '/' to specify an OR condition (i.e. a logical disjunction)
43 Note: only one -w clause is allowed.
44
45 -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,...
46
47 Key/values to set. For each key a string (key:s), a double
48 (key:d) or an integer (key:i) type can be defined. By default
49 the native type is set.
50
51 -M Multi-field support off. Turn off support for multiple fields in
52 single GRIB message.
53
54 -T T | B | M | A
55 Message type. T->GTS, B->BUFR, M->METAR (Experimental), A->Any
56 (Experimental). The input file is interpreted according to the
57 message type.
58
59 -7 Does not fail when the message has wrong length
60
61 -V Version.
62
63 -p key1,key2,...
64
65 Declaration of keys to dump. Only those keys are dumped (not the
66 whole message).
67
68 -X offset
69
70 Input file offset in bytes. Processing of the input file will
71 start from the given offset.
72
73 -x Fast parsing option, only headers are loaded.
74
75 NAME grib_dump
76
77 DESCRIPTION
78
79 Dump the content of a GRIB file in different formats.
80
81 USAGE
82
83 grib_dump [options] grib_file grib_file ...
84
85 OPTIONS
86
87 -O Octet mode. WMO documentation style dump.
88
89 -D Debug mode.
90
91 -d Print all data values.
92
93 -j JSON mode (JavaScript Object Notation).
94
95 -t Print type information.
96
97 -H Print octet content in hexadecimal format.
98
99 -a Dump aliases.
100
101 -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
102
103 Where clause. Messages are processed only if they match all the
104 key/value constraints. A valid constraint is of type key=value
105 or key!=value. For each key a string (key:s), a double (key:d)
106 or an integer (key:i) type can be specified. Default type is
107 string. In the value you can also use the forward-slash charac‐
108 ter '/' to specify an OR condition (i.e. a logical disjunction)
109 Note: only one -w clause is allowed.
110
111 -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,...
112
113 Key/values to set. For each key a string (key:s), a double
114 (key:d) or an integer (key:i) type can be defined. By default
115 the native type is set.
116
117 -M Multi-field support off. Turn off support for multiple fields in
118 single GRIB message.
119
120 -T T | B | M | A
121 Message type. T->GTS, B->BUFR, M->METAR (Experimental), A->Any
122 (Experimental). The input file is interpreted according to the
123 message type.
124
125 -7 Does not fail when the message has wrong length
126
127 -V Version.
128
129 -p key1,key2,...
130
131 Declaration of keys to dump. Only those keys are dumped (not the
132 whole message).
133
134 -X offset
135
136 Input file offset in bytes. Processing of the input file will
137 start from the given offset.
138
139 -x Fast parsing option, only headers are loaded.
140
141
142
143grib_dump December 2022 GRIB_DUMP(1)