Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do not implicitly set generatingProcessIdentifier when writing GRIB numpy fieldlist #274

Closed
sandorkertesz opened this issue Jan 9, 2024 · 0 comments · Fixed by #275
Closed

Do not implicitly set generatingProcessIdentifier when writing GRIB numpy fieldlist #274

sandorkertesz opened this issue Jan 9, 2024 · 0 comments · Fixed by #275
Labels
bug Something isn't working

Comments

@sandorkertesz
Copy link
Collaborator

What happened?

When a GRIB numpy fieldlist is written to disk

ds.save("my_file.grib")

the generatingProcessIdentifier ecCodes key is implicitly set to 255 for each message. This should be controlled by an option.

What are the steps to reproduce the bug?

See above

Version

4.0

Platform (OS and architecture)

all

Relevant log output

No response

Accompanying data

No response

Organisation

ECMWF
@sandorkertesz sandorkertesz added the bug Something isn't working label Jan 9, 2024
@sandorkertesz sandorkertesz mentioned this issue Jan 9, 2024
Merged
@sandorkertesz sandorkertesz changed the title Add option to set generatingProcessIdentifier when writing GRIB numpy fieldlist to disk Do not implicitly set generatingProcessIdentifier when writing GRIB numpy fieldlist Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not implicitly set generatingProcessIdentifier when writing GRIB data ecmwf/earthkit-data
1 participant
@sandorkertesz