DESCRIPTION

Dump the content of a grib file in different formats.

USAGE

grib_dump [options] grib_file grib_file ...

OPTIONS


-O

Octet mode. WMO documentation style dump.


-D

Debug mode.


-d

Print all data values.


-j

JSON mode (JavaScript Object Notation).


-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)


-s key[:{s/d/i}]=value,key[:{s/d/i}]=value,...

Key/values to set. For each key a string (key:s), a double (key:d) or an integer (key:i) type can be defined. By default the native type is set.


-M

Multi-field support off. Turn off support for multiple fields in single grib message.


-T T | B | M | A

Message type. T->GTS, B->BUFR, M->METAR (Experimental),A->Any (Experimental). The input file is interpreted according to the message type.


-7

Does not fail when the message has wrong length


-V

Version.


-X offset

Input file offset in bytes. Processing of the input file will start from "offset".


-x

Fast parsing option, only headers are loaded.

grib_dump examples

  1. To dump in a WMO documentation style with hexadecimal octet values (-H). 

    > grib_dump -OH ../data/reduced_gaussian_model_level.grib1


  2. To add key aliases and type information. 

    > grib_dump -OtaH ../data/reduced_gaussian_model_level.grib1


  3. To obtain all the key names (computed keys included) available in a grib file. 

     
>  grib_dump -D ../data/regular_latlon_surface.grib1