Grib messages can now be selected more explicitly using the new param_find and level_find arguments in grib_opts(). This can be necessary when local grib tables are used and shortNames are unknown, or fields use a different vertical coordinate than expected.
The PR also introduces a set of functions use_grib_*() to help set the values for param_find and level_find.
As an example, a grib file containing precipitation with indicatorOfParameter = 206 and unknown grib shortName can be read with:
Additionally level find can be used to select multiple vertical levels from grib files (read_grid() or read_forecast() can only read in one or all levels)
Resolves #46
Grib messages can now be selected more explicitly using the new
param_find
andlevel_find
arguments in grib_opts(). This can be necessary when local grib tables are used and shortNames are unknown, or fields use a different vertical coordinate than expected.The PR also introduces a set of functions
use_grib_*()
to help set the values forparam_find
andlevel_find
.As an example, a grib file containing precipitation with indicatorOfParameter = 206 and unknown grib shortName can be read with:
Another example might have 2m temperature stored with shortName "TA" and on the surface coordinate:
Additionally level find can be used to select multiple vertical levels from grib files (
read_grid()
orread_forecast()
can only read in one or all levels)