[S1.OSV.catch] fixed bug in finding files starting in previous month #286
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.
The OSV files comprise info for a certain time range of acquisition. Previously, files whose time range started in the previous month of the defined acquisition start were not found.
Example:
S1A_IW_GRDH_1SDV_20220201T163644_20220201T163709_041722_04F6E6_61EB(start in Feb. '22)S1A_OPER_AUX_POEORB_OPOD_20220221T081611_V20220131T225942_20220202T005942(start in Jan. '22)Furthermore, upon zipping the local file, the EOF file is no longer first extracted into the current working directory (where it was not deleted afterwards) and then written to the local zip file. Instead, the file is directly read to memory. Hence, the user is no longer bothered with unpacked EOF files in the working directory.
closes #285