Skip to content

GRIB2_ipdtmpl_index and GRIB2_ipdtmpl_value usage #1046

Discussion options

You must be logged in to vote

Looking carefully, I think I see the issue. There's an example of setting this in this Chapter of the MET User's Guide:

GRIB2_ipdtmpl_index=[8, 26];
GRIB2_ipdtmpl_val=[1, 2];

Comparing that to what you sent, please try switching to the following:

     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ -1 ]; },
     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ 0 ]; },
     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ 1000 ]; },
     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ 2000 ]; },
     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ 5000 ]; },
     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ 10000 ]; },
     { GRIB2_ipdtmpl_index=[ 21 ]; GRIB2_ipdtmpl_val=[ 20…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@BinbinZhou-NOAA
Comment options

Answer selected by JohnHalleyGotway
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment