EWs will have 2-digit zero padded burst index in filename #55
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.
Because EWs can have burst indexes over 9, I'm giving EWs a two digit, zero padded bust index in the filename, like
S1A_EW_SLC__1SDH_20220928T143201_20220928T143304_045206_05673A_155E_EW1_HH_00.tiffIWs will continue to have single digit bust IDs because they max out at
8.We should consider giving both IWs and EWs double digits for consistency's sake. What do you think? Would it help with your workflows to not have to take into consideration IW vs EW and length of filename, etc?