Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harmonize SEVIRI area definitions #1192

Closed
sfinkens opened this issue May 7, 2020 · 3 comments
Closed

Harmonize SEVIRI area definitions #1192

sfinkens opened this issue May 7, 2020 · 3 comments

Comments

@sfinkens
Copy link
Member

sfinkens commented May 7, 2020

Feature Request

Is your feature request related to a problem? Please describe.

As described by @ameraner in #1186 , the SEVIRI readers provide slightly different area extents:

Reader north up lower left x lower left y upper right x upper right y width/height
nc yes -5570248.477339745 -5567248.074173927 5567248.074173927 5570248.477339745 11137496.551513672
hrit no 5567248.28340708 5570248.686685662 -5570248.686685662 -5567248.28340708 11137496.970092742
hrit (pre 2018) no 5568748.28340708 5568748.686685662 -5568748.686685662 -5568748.28340708 11137496.970092742
native no 5567248.074173927 5570248.477339745 -5570248.477339745 -5567248.074173927 11137496.551513672
native (pre 2018) no 5568748.275756836 5568748.275756836 -5568748.275756836 -5568748.275756836 11137496.551513672

So there are two different image extents (absolute width/height) among the readers. Also, the georeferencing offset correction is exactly 1500 meters in the HRIT reader (hard coded somewhere), whereas it is 1500.2 meters (half a pixel) in the native reader. The MSG Level 1.5 Image Data Format Description (link) says:

The problem is a constant shift of the image by 0.5 low resolution pixels North plus 0.5 low
resolution pixels West. The HRV channel appears shifted by 1.5 HRV pixels North plus 1.5
HRV pixels West.

So the implementation in the native reader, shifting the image by pixel amounts and not hardcoded exact meters, is the most correct.

Describe the solution you'd like
Check whether the image data in the different data formats is identical. If so, find out which area extent is correct and make all SEVIRI readers return that extent (in terms of values; order may differ as we want to keep the orientation of the original data). For the flipped data, a north_up reader kwarg would be nice, to make the image upright.

Describe any changes to existing user workflow
None.

Additional context
There is ongoing work on the utility function for computing the geostationary area extents: #1179

@ameraner
Copy link
Member

As for the comment about the possibility of flipping data upright, this was implemented in #1194 as a load kwarg, e.g.: scn.load(['ir_105'], upper_right_corner='NE')

@ameraner
Copy link
Member

Fixing this would also benefit the quest for standardising geos AreaDefinition (names) in #1248 :)

@sfinkens
Copy link
Member Author

Fixed (including documentation) by #1485

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants