You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFAIK, the dataset is created from mk_dataset function which creates the coordinates from odc.geo.xr.xr_coords. This function allows for controlling the dimension name using the dims parameter, a feature unavailable currently at the loader level. Hoisting this parameter to the level of the load function would provide some control over the unpredictability of the dimension name. I am happy to help implementing this feature if people think this is useful.
The text was updated successfully, but these errors were encountered:
@harryle95 we can't keep jamming more and more extra **kwargs into .load, we first need to implement "builder pattern" or maybe "configuration context" kinda thing for configuring various things in a more extensible way first.
@clausmichele I don't think cube extension is relevant here, my understanding of cube extension is about describing "datacube asset", whatever that might be, probably zarr, hdf or parquet, without needing to actually read that information from the file. While this is more like: I want my output to have specific names for spatial coordinates, and I don't want to rename them manually after load.
AFAIK, the dataset is created from mk_dataset function which creates the coordinates from odc.geo.xr.xr_coords. This function allows for controlling the dimension name using the
dims
parameter, a feature unavailable currently at the loader level. Hoisting this parameter to the level of the load function would provide some control over the unpredictability of the dimension name. I am happy to help implementing this feature if people think this is useful.The text was updated successfully, but these errors were encountered: