Switch to otb for direct grid - #78
Merged
Merged
Conversation
aburie-cs
requested changes
Jul 15, 2026
Collaborator
This was referenced Jul 16, 2026
Closed
|
aburie-cs
self-requested a review
July 16, 2026 14:20
aburie-cs
approved these changes
Jul 16, 2026
This was referenced Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
goal is to use otb instead of gdal, since otb can't manage direct grid, we use "sen2vm_invloc_from_dir_loc_grid.py" to go from direct grids to inverse grid.
Then we use the otb function to managed the inverse grid : otbcli_GridBasedImageResampling
Finally since otb lack georeferencing, we use gdal_translate, and then gdal_merge to create a mosaic.