support for scenes acquired in NRT Slicing mode #112
Merged
Conversation
This file contains 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
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.
In this mode the manifest.safe attributes
sliceNumberandtotalSlicesare 0, which broke with assumptions in S1_NRB.ancillary.check_acquisition_completeness and resulted in a wrong output in S1_NRB.snap.grd_buffer. Incheck_acquisition_completenessan additional cross-check with the ASF database was added. Forgrd_bufferthe metadata of the BEAM-DIMAP input file is modified to contain dummy values that work with the SNAPSliceAssemblyoperator (The start time of the datatake and the acquisition duration of the scene are known; dividing one by the other and converting it to integer gives the new slice number).totalSlicesis set to 100 to be higher than the maximum possible value.