-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing v
component in nam.t06z.awip3d00.tm00.grib2 after filter_by_keys
#45
Comments
@bbonenfant finally I'm on this and I can confirm it is indeed a bug. |
The plot thickens, by using
But by looping on the lowest level python bindings all (and only) the
@shahramn I only use |
@shahramn identified that the nam GRIB files use MULTI-FIELD messages, a rare feature, that ecCodes can handle just fine but only after being requested to do it by calling I'll need a bit of time to implement the feature correctly, but it is basically solved. |
Hello again, I'm just now revisiting this, an I'm still experiencing the same bug where the
|
I think I may have found a bug or at least something I do not understand in the implementation of the
filter_by_keys
argument.Here is some output I receive when trying to open one of those NAM grib files:
You can see that it successfully returns a Dataset, but looking at the variables it returns, there is the U component of the wind but not the V component of the wind. I'm not sure why this is the case, since I've inspected the grib and find nothing apparent wrong with the v-winds. I've additionally tried this on other NAM gribs with similar results (even in your comment above on Sept. 30 this was the case).
I am unsure if this is an error on my part or if there is a way around this.
Thank you.
Originally posted by @bbonenfant in #2 (comment)
The text was updated successfully, but these errors were encountered: