merge_cubes and mask will now try to automatically resample input data cubes if required, reducing the need to always use resample_cube_spatial
When catalogs contain 2 versions of the same product, we now detect this better and try to use the most recent version. This improves performance, but also reproducibility.
This is not ideal wrt reproducibility, I think. Different back-ends behave differently then.
It's non breaking as it purely adds behavior for what before just threw an error.
Proposed solution:
We discussed this in the PSC and it seems reasonable here to be user-friendly and implicitly add the resampling to the merge_cubes process in general. It would be described just as an implicit call to resample_cube_spatial where the first cube is always the baseline.
Process ID: merge_cubes
Describe the issue:
@jdries wrote at https://discuss.eodc.eu/t/terrascope-backend-upgrade/542:
This is not ideal wrt reproducibility, I think. Different back-ends behave differently then. It's non breaking as it purely adds behavior for what before just threw an error.
Proposed solution:
We discussed this in the PSC and it seems reasonable here to be user-friendly and implicitly add the resampling to the merge_cubes process in general. It would be described just as an implicit call to
resample_cube_spatial
where the first cube is always the baseline.