fix: handle incompatible coords in merge_cubes #148
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@LukeWeidenwalker, in load_stac, stackstac loads many additional metadata as data variables/coordinates. It is an advantage when we want to have a complete overview on the dataset but in this case creates an issue when trying to merge different datasets, An example is in this notebook I recently created:
https://github.com/clausmichele/openeo-python-client/blob/add_stac_notebook/examples/notebooks/Client_Side_Processing/client_side_processing_STAC_data_fusion.ipynb
This fix removes the unnecessary coordinates if the merge fails and tries to merge the datacubes again. I spent a lot of time trying to find a more elegant solution, but I couldn't.