Add possibility to define the dataset rectification longitude in seviri_l2_bufr reader #2078
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
…add_rectification_longitude_to_seviri_l2_bufr_reader
…add_rectification_longitude_to_seviri_l2_bufr_reader
Codecov Report
@@ Coverage Diff @@
## main #2078 +/- ##
=======================================
Coverage 93.79% 93.80%
=======================================
Files 283 283
Lines 42284 42295 +11
=======================================
+ Hits 39662 39673 +11
Misses 2622 2622
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
mraspaud
reviewed
Apr 6, 2022
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 SEVIRI L2 BUFR data are originally been extracted from a rectified two-dimensional SEVIRI grid with a given central longitude (typically the sub-satellite point). Previously this longitude was hard-coded for each SEVIRI instrument (Meteosat satellite) in the reader, following the current operational grids. This is sub-optimal when working with e.g. historic data where the operational grid for a given instrument is different, as this will lead to an incorrect
AreaDefinitionin case the data are returned with one (with_area_definition=True). Since the information about the satellite position or original grid rectification longitude is not available in the file itself or the filename (for files from the EUMETSAT archive) and cannot be reliably derived from all datasets themselves, this PR adds the possibility to provide this information as areader_kwarg(rectification_longitude) when initializing theSceneobject for theseviri_l2_bufrreader.If this
reader_kwargis not provided, the default longitude defined for a given satellite/instrument will be used (unless the information can be extracted from the filename (internal EUMETSAT files)) thus following the previous implementation.The PR also modifies the default SSP_LON for Meteosat-9 in preparation for it's upcoming relocation to the IODC service at 45.5 degrees east.