Missing ECMWF variables from grib tables?

[weathermon83]

Hi guys,

I'm using wgrib2 3.4.0 on the latest ECMWF IFS data and noticed that there are several variables that appear to be not matching up correctly:

wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep disc
4:4672668:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=1 parm=193:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:
52:88201140:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=19 parm=192:surface:90 hour fcst:
59:100142296:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=62:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:
65:110525896:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=63:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:
78:131293268:d=2024111318:var discipline=2 center=98 local_table=1 parmcat=0 parm=201:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:

I did a wgrib2 -gribtable_used to find out these variables and had a quick look on the EC grib parameters page here https://codes.ecmwf.int/grib/param-db/?ordering=id&encoding=grib2

The first one (message 4, parameter 193) is the Total Precipitation variable, so I made a quick user table, exported it in my shell environment and it now shows up:

export grib2table=/data/metcentre/grads2/wgrib2_tables/grib2table
wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep disc
52:88201140:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=19 parm=192:surface:90 hour fcst:
59:100142296:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=62:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:
65:110525896:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=63:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:
78:131293268:d=2024111318:var discipline=2 center=98 local_table=1 parmcat=0 parm=201:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0

wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep -i tp
4:4672668:d=2024111318:TP:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0:
45:74702624:d=2024111318:TPRATE:surface:90 hour fcst:

cat /data/metcentre/grads2/wgrib2_tables/grib2table
0:0:0:255:98:1:1:193:TP:Total Precipitation:m

Are there plans to include the updated ECMWF variable names in version 3.5 at all? I use all the default NCEP names for my variables to keep things consistent across scripts. I did have a quick look at the wgrib2/gribtables/ecmwf/create_ecmwf_gribtable.sh script however it appears to be hitting an old url that no longer exists (https://codes.ecmwf.int/grib/json/?discipline=All&category=All&filter=grib2:) so assuming it needs to be updated to hit https://codes.ecmwf.int/parameter-database/api/v1/param/?encoding=grib2&format=json&limit=20&offset=0&ordering=id&regex=false instead

Cheers, Mike

[webisu]

Mike, Thanks for the info. I will take a look at the ECMWF grib table situation. It's probably time to see if the NCEP tables have changed too. I'll have to document the procedure for updating the grib tables too. Wesley

…

On Thu, Nov 14, 2024 at 7:27 PM weathermon83 ***@***.***> wrote: Hi guys, I'm using wgrib2 3.4.0 on the latest ECMWF IFS data and noticed that there are several variables that appear to be not matching up correctly: wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep disc 4:4672668:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=1 parm=193:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 52:88201140:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=19 parm=192:surface:90 hour fcst: 59:100142296:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=62:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 65:110525896:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=63:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 78:131293268:d=2024111318:var discipline=2 center=98 local_table=1 parmcat=0 parm=201:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: I did a wgrib2 -gribtable_used to find out these variables and had a quick look on the EC grib parameters page here https://codes.ecmwf.int/grib/param-db/?ordering=id&encoding=grib2 The first one (message 4, parameter 193) is the Total Precipitation variable, so I made a quick user table, exported it in my shell environment and it now shows up: export grib2table=/data/metcentre/grads2/wgrib2_tables/grib2table wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep disc 52:88201140:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=19 parm=192:surface:90 hour fcst: 59:100142296:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=62:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 65:110525896:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=63:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 78:131293268:d=2024111318:var discipline=2 center=98 local_table=1 parmcat=0 parm=201:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0 wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep -i tp 4:4672668:d=2024111318:TP:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 45:74702624:d=2024111318:TPRATE:surface:90 hour fcst: cat /data/metcentre/grads2/wgrib2_tables/grib2table 0:0:0:255:98:1:1:193:TP:Total Precipitation:m Are there plans to include the updated ECMWF variable names in version 3.5 at all? I did have a quick look at the wgrib2/gribtables/ecmwf/create_ecmwf_gribtable.sh script however it appears to be hitting an old url that no longer exists ( https://codes.ecmwf.int/grib/json/?discipline=All&category=All&filter=grib2:) so assuming it needs to be updated to hit https://codes.ecmwf.int/parameter-database/api/v1/param/?encoding=grib2&format=json&limit=20&offset=0&ordering=id&regex=false instead Cheers, Mike — Reply to this email directly, view it on GitHub <#291>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEIB7ZQWD6YUD4EVQD3L2UD2AU5V3AVCNFSM6AAAAABR2CQRRGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3DANBRG4ZTONY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[weathermon83]

Hi Wesley, Fantastic, that would be great! Cheers, Mike From: webisu ***@***.***> Sent: Saturday, November 16, 2024 12:10 AM To: NOAA-EMC/wgrib2 ***@***.***> Cc: weathermon83 ***@***.***>; Author ***@***.***> Subject: Re: [NOAA-EMC/wgrib2] Missing ECMWF variables from grib tables? (Issue #291) Mike, Thanks for the info. I will take a look at the ECMWF grib table situation. It's probably time to see if the NCEP tables have changed too. I'll have to document the procedure for updating the grib tables too. Wesley On Thu, Nov 14, 2024 at 7:27 PM weathermon83 ***@***.*** <mailto:***@***.***> > wrote:

Hi guys, I'm using wgrib2 3.4.0 on the latest ECMWF IFS data and noticed that there are several variables that appear to be not matching up correctly: wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep disc 4:4672668:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=1 parm=193:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 52:88201140:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=19 parm=192:surface:90 hour fcst: 59:100142296:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=62:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 65:110525896:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=63:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 78:131293268:d=2024111318:var discipline=2 center=98 local_table=1 parmcat=0 parm=201:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: I did a wgrib2 -gribtable_used to find out these variables and had a quick look on the EC grib parameters page here https://codes.ecmwf.int/grib/param-db/?ordering=id <https://codes.ecmwf.int/grib/param-db/?ordering=id&encoding=grib2> &encoding=grib2 The first one (message 4, parameter 193) is the Total Precipitation variable, so I made a quick user table, exported it in my shell environment and it now shows up: export grib2table=/data/metcentre/grads2/wgrib2_tables/grib2table wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep disc 52:88201140:d=2024111318:var discipline=0 center=98 local_table=1 parmcat=19 parm=192:surface:90 hour fcst: 59:100142296:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=62:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 65:110525896:d=2024111318:var discipline=0 master_table=33 parmcat=2 parm=63:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 78:131293268:d=2024111318:var discipline=2 center=98 local_table=1 parmcat=0 parm=201:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0 wgrib2 -ncpu 8 /data/metcentre//data/grib/ec_ifs/2024111318/ecv2_090.grb2 -s | grep -i tp 4:4672668:d=2024111318:TP:surface:0-90 hour acc@(fcst,dt=450 sec),missing=0: 45:74702624:d=2024111318:TPRATE:surface:90 hour fcst: cat /data/metcentre/grads2/wgrib2_tables/grib2table 0:0:0:255:98:1:1:193:TP:Total Precipitation:m Are there plans to include the updated ECMWF variable names in version 3.5 at all? I did have a quick look at the wgrib2/gribtables/ecmwf/create_ecmwf_gribtable.sh script however it appears to be hitting an old url that no longer exists ( https://codes.ecmwf.int/grib/json/?discipline=All <https://codes.ecmwf.int/grib/json/?discipline=All&category=All&filter=grib2> &category=All&filter=grib2:) so assuming it needs to be updated to hit https://codes.ecmwf.int/parameter-database/api/v1/param/?encoding=grib2 <https://codes.ecmwf.int/parameter-database/api/v1/param/?encoding=grib2&format=json&limit=20&offset=0&ordering=id&regex=false> &format=json&limit=20&offset=0&ordering=id&regex=false instead Cheers, Mike — Reply to this email directly, view it on GitHub <#291>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEIB7ZQWD6YUD4EVQD3L2UD2AU5V3AVCNFSM6AAAAABR2CQRRGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3DANBRG4ZTONY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** <mailto:***@***.***> >

— Reply to this email directly, view it on GitHub <#291 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARPLKSJJ5HEYEGFESOSVXZL2AX6DTAVCNFSM6AAAAABR2CQRRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYHE2TGMBYGQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ARPLKSO5J27DWVMOP43AM4D2AX6DTA5CNFSM6AAAAABR2CQRRGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUTYHJHY.gif> Message ID: ***@***.*** ***@***.***> >