...
You can use the grib_dump command with the "-D" option:
Code Block |
---|
$% grib_dump -D my.index |
And the output will look something like this:
Code Block |
---|
--- grib_index_build: processing***** FILE: my.idx GRIB File: data/tigge_cf_ecmwf.grib2 --- grib_index_buildGRIB File: processing data/tigge_af_ecmwf.grib2 --- grib_index_build: keys included in the index file idx: --- mars.date, mars.stream, mars.type, mars.step, mars.param, mars.levtype, mars.levelist, mars.number --- mars.date = {Index keys: key name = mars.date values = 20070122, 20060630, 20060623, 20060811, 20060619 } --- key name = mars.stream values = { enfo, oper } --- key name = mars.type values = { cf, fc } --- key name = mars.step values = { 96, 0 } --- key name = mars.param values = { 165228039, 166228139, 59133, 260207189, 156168, 172121, 151122, 228002167, 179147, 3176, 60177, 260210134, 235146, 228141130, 228144228164, 228039136, 228139228228, 133131, 189132, 168, 121, 122, 167, 147, 176, 177, 134, 146 } ---0 key name = mars.levtype values = { sfc, pl, pv, pt } --- key name = mars.levelist values = { undef, 925, 2, 320 } --- key name = mars.number values = { 0, undef } ---Index 83count messages indexed= 8 |
You can see which GRIB files were used to build that index as well as the keys and their values. In the above example the keys belonged to the "mars" namespace.
Related articles
Content by Label | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...