issues: 350899839
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 350899839 | MDU6SXNzdWUzNTA4OTk4Mzk= | 2368 | Let's list all the netCDF files that xarray can't open | 1197350 | closed | 0 | 32 | 2018-08-15T17:41:13Z | 2023-11-30T04:36:42Z | 2023-11-30T04:36:42Z | MEMBER | At the Pangeo developers meetings, I am hearing lots of reports from folks like @dopplershift and @rsignell-usgs about netCDF datasets that xarray can't open. My expectation is that xarray doesn't have strong requirements on the contents of datasets. (It doesn't "enforce" cf compatibility for example; that's optional.) Anything that can be written to netCDF should be readable by xarray. I would like to collect examples of places where xarray fails. So far, I am only aware of one:
Are there other distinct cases? Please provide links / sample code of netCDF datasets that xarray can't read. Even better would be short code snippets to create such datasets in python using the netcdf4 interface. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2368/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |