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
A user is requesting to load Sentinel-2 data in the original 10m and 20m resolution (resolution depends on band), and then to apply a UDF, receiving those bands in the original resolution.
I haven't entirely figured it out yet.
One option is a complex contraction of merge_cubes and apply_neighborhood where cubes do not need full alignment and the UDF receives an xarray Dataset with the variables having different resolutions.
Another option, which I will probably implement as a first solution, is simply trying to load the 10m and 20m bands in a single datacube, and then applying a UDF with a new signature that takes an xarray Dataset.
I think I will be able to implement the second option, only problem is that it doesn't comply with the datacube model, as the virtual datacube will be fully 10m resolution, while the udf will still receive bands with mixed resolutions.
The text was updated successfully, but these errors were encountered:
A user is requesting to load Sentinel-2 data in the original 10m and 20m resolution (resolution depends on band), and then to apply a UDF, receiving those bands in the original resolution.
I haven't entirely figured it out yet.
One option is a complex contraction of merge_cubes and apply_neighborhood where cubes do not need full alignment and the UDF receives an xarray Dataset with the variables having different resolutions.
Another option, which I will probably implement as a first solution, is simply trying to load the 10m and 20m bands in a single datacube, and then applying a UDF with a new signature that takes an xarray Dataset.
I think I will be able to implement the second option, only problem is that it doesn't comply with the datacube model, as the virtual datacube will be fully 10m resolution, while the udf will still receive bands with mixed resolutions.
The text was updated successfully, but these errors were encountered: