This is up for discussion: We should possible add a /time dimension to each product to explicitly label the displacement time. We should be able to follow the CF-conventions (which do specify that the name should be "time") by using h5netcdf.
downsides:
shape becomes (1, rows, cols) so some things will complain, e.g. if you directly plot the (1, rows, cols) image (This already happens when you use rasterio to load a 1-band image)
upsides:
concatenating multiple becomes more straightforward because the time dimension is explicitly encoded
everyone doesn't have to write a string/name parser (i.e. you can just do xr.open_mfdataset() and it should just work)
This is up for discussion: We should possible add a
/timedimension to each product to explicitly label the displacement time. We should be able to follow the CF-conventions (which do specify that the name should be "time") by usingh5netcdf.(1, rows, cols)so some things will complain, e.g. if you directly plot the (1, rows, cols) image (This already happens when you use rasterio to load a 1-band image)xr.open_mfdataset()and it should just work)