Upgrade data access #290
Open
Upgrade data access #290
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
added 2 commits
March 10, 2025 12:47
…ud coverage, different output formats
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
I have upgraded the integration of SH into EO-TDL by adding two additional collections: Landsat 8-9 L2 and HLS (Harmonized Landsat Sentinel). In the search functionality, users can now set the maximum cloud coverage they want in the advanced search. During processing, users can now choose the output format, define their own evalscript, or select one of the predefined ones.
I have also fixed some bugs I discovered while adding these features. Additionally, I renamed SUPPORTED_SENSORS to SUPPORTED_COLLECTION_IDS and changed all 'sensor' parameters to 'collection_id', as I believe the term "sensor" is not the most appropriate. This is the only change that might break existing implementations for users. However, I can revert this naming change if necessary to avoid disrupting working code.
Please check if any corrections are needed, and in the meantime, I will fix and update 10_search_sentinel_imagery and 11_download_sentinel_imagery.