issue_comments: 405304149

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/pull/2287#issuecomment-405304149 https://api.github.com/repos/pydata/xarray/issues/2287 405304149 MDEyOklzc3VlQ29tbWVudDQwNTMwNDE0OQ== 10050469 2018-07-16T16:22:42Z 2018-07-16T16:22:42Z MEMBER

Generally, image containers opened by imageio represents a single Dataset only, which is why I default names to their readout sequences. However, there are indeed cases where multiple variables exist, such as pyramids of image sequences, each pyramid layer represents a different resolution for the sequence.

Can you show some examples of how imageio works: - in the case of a single array - in the case of multiple variables ?

However, it is my understanding, and please correct me if I am wrong, that rasterio backend is aimed at being a read-only I/O for xarray without having the extensibility for write ability, and I'm really eager to keep the ability to aggregate multiple files through dask, as well as saving data through imageio transparently (if plausible) :p

This can be done regardless. You can add open_imageio and to_imageio methods to DataArrays/Datasets without the existing abstractions which were written for NetCDF-like files.

Do you already have an idea of how the to_imageio API would look like? This looks quite a complex topic...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   341321742