Since the discipline, parameter category or parameter > 191, the table entry is a "locally defined" variable. 1 - I7=parameter category (code table 4.1).253 - I5=center (use -1 for a wild card).Type "help", "copyright", "credits" or "license" for more information.Īny suggestion and comments are appreciated. However, thus obtained GRIB data provides the parameter to be 191 when read with pygrib. When I changed the “parameter” field (in above example 208) to 190 or 191, it worked $ wgrib2 out.grib -set_var WNISI -grib out.grbĢ:179:d=2022071400:WNISI:0 mb:12 hour fcst: *** FATAL ERROR: set_var: could not find WNISI *** I’m making a GRIB2 file of a locally defined parameter (say, WNISI) using wgrib2.Īnd make a local table (my_grib2table) 0:23:0:255:253:7:1:208:WNISI:WNI Storm Index:?Īnd then got $ wgrib2 out.grib -set_var WNISI -grib out.grb
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |