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.

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

Update faq.rst #9208

Closed
wants to merge 1 commit into from
Closed

Conversation

TimothyCera-NOAA
Copy link
Contributor

Adding grib2io to the file format table as a way to work within xarray with GRIB2 files.

Adding grib2io to the file format table as a way to work within xarray with GRIB2 files.
Copy link
Collaborator

@headtr1ck headtr1ck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing!

While there are no strict rules about that, in the FAQ section there are only xarray internal backends. Third party libraries should instead go to the ecosystem page.

Also, feel free to add an entry in whats-new!

@TimothyCera-NOAA
Copy link
Contributor Author

cfgrib is the default that if installed will be used, however it isn't internal to xarray. Where pygrib is neither internal nor the default and is only mentioned throughout all of xarray in the faq.rst. On the other hand I understand that you don't want every package listed here that has an xarray backend.

I will look at the ecosystem page.

@headtr1ck
Copy link
Collaborator

cfgrib is the default that if installed will be used, however it isn't internal to xarray.

you are right. cfgrib once was xarray internal but got deprecated because it ships with its own backend now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants