issue_comments: 1098327424
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/6448#issuecomment-1098327424 | https://api.github.com/repos/pydata/xarray/issues/6448 | 1098327424 | IC_kwDOAMm_X85BdyWA | 3924836 | 2022-04-13T17:53:21Z | 2022-04-13T17:53:21Z | MEMBER | One of the main motivations behind the the rioxarray extension is GDAL compatibility. It looks like @snowman2 and @TomAugspurger have discussed saving many geotiffs loaded into xarray as GDAL-compatible Zarr for example https://github.com/corteva/rioxarray/issues/433#issuecomment-967685356. While it seems that the ultimate solution is agreeing on a format standard, here is another small example using the rioxarray extension where format conversion doesn't currently work as you might expect: ```python https://github.com/pydata/xarray-datads = xr.open_dataset('xarray-data/air_temperature.nc', engine='rasterio') TooManyDimensions: Only 2D and 3D data arrays supported.ds.rio.to_raster('test.zarr', driver='ZARR') Does not error, but output not equivalent to
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1194993450 |