[Met_help] [rt.rap.ucar.edu #79859] History for GRIB2 Issue
John Halley Gotway via RT
met_help at ucar.edu
Thu Apr 6 08:56:01 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, I am trying to degrib a grib2 file ( I placed it on the ftp server).
My config file is attached. Below is the error message I am getting:
['/h/WXQC/met-5.2/bin/grid_stat',
'/h/data/global/WXQC/data/geps_verify/qcsave/2017030300/grib2.2017030300.002
4', '/h/data/global/WXQC/data/met/tmp/obnetcdf.nc',
'/h/WXQC/met-5.2/data/config/GridStatConfig_geps_updated', '-outdir',
'/h/data/global/WXQC/data/met/gdstat/geps/', '-v', '4']
DEBUG 1: Default Config File:
/h/WXQC/met-5.2/share/met/config/GridStatConfig_default
DEBUG 1: User Config File:
/h/WXQC/met-5.2/data/config/GridStatConfig_geps_updated
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb2".
DEBUG 3: Switching the GRIB2 radius of the earth value of 6367.47 km to
6371.2 km for internal consistency.
DEBUG 4:
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll: -90
DEBUG 4: lon_ll: -0
DEBUG 4: delta_lat: 1
DEBUG 4: delta_lon: 1
DEBUG 4: Nlat: 181
DEBUG 4: Nlon: 360
DEBUG 4:
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 126
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 127
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 130
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 131
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 131
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 3, parm: 131
Any ideas?
Thanks
Bob
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: GRIB2 Issue
From: John Halley Gotway
Time: Wed Mar 22 11:37:03 2017
Bob,
Found one more of your questions was left unanswered. I grabbed the
GRIB2
file you posted to our anonymous FTP site:
ftp://ftp.rap.ucar.edu/incoming/irap/met_help/craigr_data/grib2.2017030300.0024
Running it through wgrib2, I see a lot of this:
1:0:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=126:surface:24 hour fcst:ENS=hi-res ctl
2:73116:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=127:surface:24 hour fcst:ENS=hi-res ctl
3:163225:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:200 mb:24 hour fcst:ENS=hi-res ctl
4:216141:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:250 mb:24 hour fcst:ENS=hi-res ctl
5:270341:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:300 mb:24 hour fcst:ENS=hi-res ctl
6:327280:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:350 mb:24 hour fcst:ENS=hi-res ctl
....
That means that wgrib2 doesn't know about this combination of GRIB2
settings. If you have your desired definition of these, you'd set up
custom GRIB2 table definition and point MET to it, as I mentioned in a
previous email.
Hope that helps.
Thanks,
John
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #79859] GRIB2 Issue
From: robert.craig.2 at us.af.mil
Time: Mon Mar 27 14:26:00 2017
John, just wanted to make sure you received the questions sent last
Friday.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, March 22, 2017 12:37 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79859] GRIB2 Issue
Bob,
Found one more of your questions was left unanswered. I grabbed the
GRIB2
file you posted to our anonymous FTP site:
ftp://ftp.rap.ucar.edu/incoming/irap/met_help/craigr_data/grib2.2017030300.0024
Running it through wgrib2, I see a lot of this:
1:0:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=126:surface:24 hour fcst:ENS=hi-res ctl
2:73116:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=127:surface:24 hour fcst:ENS=hi-res ctl
3:163225:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:200 mb:24 hour fcst:ENS=hi-res ctl
4:216141:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:250 mb:24 hour fcst:ENS=hi-res ctl
5:270341:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:300 mb:24 hour fcst:ENS=hi-res ctl
6:327280:d=2017030300:var discipline=0 master_table=10 parmcat=3
parm=130:350 mb:24 hour fcst:ENS=hi-res ctl
....
That means that wgrib2 doesn't know about this combination of GRIB2
settings. If you have your desired definition of these, you'd set up
custom GRIB2 table definition and point MET to it, as I mentioned in a
previous email.
Hope that helps.
Thanks,
John
------------------------------------------------
Subject: GRIB2 Issue
From: John Halley Gotway
Time: Thu Apr 06 08:55:49 2017
Bob,
I was reviewing open tickets and ran across this one. I'll resolve
this one since I believe we've addressed this issue in other message
threads.
If that's not the case, please let me know.
Thanks,
John
------------------------------------------------
More information about the Met_help
mailing list