Open
Conversation
Author
|
After testing the code for myself, I determined that I needed to search both tags (BC/BU) in a similar way as the release folder, so I made that change. |
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
1 participant
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.
I wrote a couple of functions to generate the UAVSAR SLC filenames (from asf search results) and download them from the JPL site, which I thought might be useful to add to this repository. There are a couple of things that I couldn't find in the ASF metadata (what I call tag and the release folder). For the release folder, the code just brute force searches for a valid link, and for the tag, I let the user determine what tags to look for. I tested them in a notebook called slc_download_test.ipynb. Let me know if you have any feedback!