Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize the use of ROI in data cube regularization #1151

Closed
EstefaPizarro opened this issue Jun 7, 2024 · 1 comment
Closed

Standardize the use of ROI in data cube regularization #1151

EstefaPizarro opened this issue Jun 7, 2024 · 1 comment
Assignees
Milestone

Comments

@EstefaPizarro
Copy link

Describe the requested improvement
When regularizing a data cube for a bounded region, smaller than a full tile, different satellites handle geometry cropping differently. While Sentinel-2 generates a regular crop by taking the maximum dimensions of the vector file, Sentinel-1 and COP-DEM mask the geometry. This generates disagreements in a possible subsequent treatment of a "merge" cube, because, although the union of the different cubes generated is allowed, the bands that make up it do not have the same dimensions of rows and columns. For example, it is not allowed as input for the segmentation process.

@OldLipe
Copy link
Contributor

OldLipe commented Jun 18, 2024

Create an internal function called .cube_crop() that will be used in sits_mosaic() and sits_regularize().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants