geometry buffering for minimum overlap #147
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.
For geocoding, the processor first selects all MGRS tiles in a particular UTM zone with a SAR scene. The bounding box of the selected tiles is then used as subset for geocoding only parts of the scene. It can happen that the selected subset is too small and SNAP trows an error. This is more likely to occur near the poles where up to nine different UTM zones were observed to overlap with one EW scene.
With this PR, a new function is introduced to buffer the subset geometry to have a minimum overlap of 1% with the scene's footprint to ensure a sufficiently large subset for geocoding.
This is handled by functions
ancillary.buffer_min_overlap
andtile_extraction.aoi_from_scene
. The latter was outsourced from code insnap.process
.