-
Notifications
You must be signed in to change notification settings - Fork 179
Error constructing GRIB2 var names #854
Comments
Greetings @msdsoftware, The key difference between the two files is the time unit encoded into the GRIB record. In file
whereas in file
In both cases, a time interval of |
So do you think this constitutes a bug in the NJ code? Or if not necessarily a bug, then something that NJ might catch with a sanity test and try to "correct"? I forwarded your comments to the NOAA people -- they said thanks much for the analysis. They are going to try to figure out where/why in the processing chain some files are generated with octet 18 value of 11. The theory has been advanced that someone fat-fingered an 11 rather than a 1 when writing some code. |
I received some follow-up from NOAA about the datasets that cause the unexpected behavior:
|
@msdsoftware - thanks for following up with NOAA! This is quite helpful to know in general. The code that creates the interval name can be found here. It looks to me like the multiplication by I've made a PR (#861) to see if removing this breaks anything in our test suite, but I think it should be ok. |
Not that simple. The scaling by
|
I've heard from some NOAA people about trouble using Panoply to read some GRIB2 data, but IDV also has the problem. So assuming that the datasets are okay (and I'm assured that they are), then the problem would seem to lie in the NJ code for reading/constructing GRIB2 metadata.
The issue is that variable IDs and variable names in some datasets are reported with the wrong accumulation or averaging period, e.g.., the var names are shown with "XXX_36_Hour_Accumulation_XXX" when they should be "XXX_6_Hour_Accumulation_XXX".
Sample datasets are at
http:https://nomads.ncep.noaa.gov/pub/data/nccf/com/gefs_legacy/prod/gefs_legacy.20170606/00/pgrb2a/
An example that shows the var names as 36-hour is geavg.t00z.pgrb2af258
However, a dataset that shows them as the expected 6-hour is geavg.t00z.pgrb2af252
The text was updated successfully, but these errors were encountered: