Add support for (some) SLSTR L2 data types#3419
Draft
simon-sat wants to merge 3 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3419 +/- ##
=======================================
Coverage 96.33% 96.34%
=======================================
Files 467 469 +2
Lines 59138 59193 +55
=======================================
+ Hits 56973 57027 +54
- Misses 2165 2166 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Currently only L1b data from Sen3/SLSTR is supported. This PR adds support for L2 products also.
Initially, only the LST product is supported, but I have made this PR in a flexible way so that others can be added in the future.
In addition, to reduce code duplication I have moved many of the L1b reader functions into a new common library file that can be called by both the L1 and L2 readers.