issues: 2270275688
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2270275688 | I_kwDOAMm_X86HUaho | 8985 | update `to_netcdf` docstring to list support for explicit CDF5 writes | 9221710 | open | 0 | 4 | 2024-04-30T00:41:13Z | 2024-04-30T20:48:46Z | NONE | Is your feature request related to a problem?I cannot get to_netcdf() to write files in CDF5 format as identifed by the 'ncdump -k' command. Describe the solution you'd likeWhen I write a netcdf file using: D.to_netcdf( filename ) then ask ncdump to tell me the kind of file I have, ncdump -k filename it returns 'netCDF-4'. Unfortunately, this file won't work in the Community Atmpshere Model (CAM), as an initial condition for example. CAM will bomb when it tries to read it. After converting the file with this command: nccopy -k cdf5 filename cdf5_filename the file now works in CAM. Also, the command ncdump -k cdf5_filename returns 'cdf5'. I confess I don't know what the nccopy command is doing, but it seems to be needed for the file to be readable by CAM. I am looking for an option in the to_netcdf method that will explicitly write 'cdf5' files without needing to resort to the nccopy command. Describe alternatives you've consideredWriting netcdf-4 files from xarray and converting via nccopy -k cdf5 filename cdf5_filename Additional contextNo response |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8985/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | issue |