Fix handling of HRV channel navigation for RSS data in seviri_l1b_native reader #1262
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.
This PR fixes the navigation of the HRV channel from Rapid Scanning Service data in the SEVIRI native format reader.
The issue was caused by the wrong assumption that the HRV RSS data is formatted the same way as HRV ROI data. This was causing wrong navigations, with stretched and shifted images.
Instead, the RSS HRV is handled similarly to the full-disk case; the navigation still needs to be done using the "
Actual
" lines and columns positions stored in the trailer information. The difference w.r.t. the full-disk case is that only one area is present, instead of two separate ones.flake8 satpy