-
Notifications
You must be signed in to change notification settings - Fork 303
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
Angle interpolation for MODIS data missing #405
Angle interpolation for MODIS data missing #405
Comments
Thanks for the issue. Could you please give the full traceback for the KeyError you got. I know @mraspaud started tracking down the exact issue, but any additional information will be helpful. |
KeyError Traceback (most recent call last) /usr/local/lib/python2.7/dist-packages/satpy/scene.pyc in load(self, wishlist, calibration, resolution, polarization, level, generate, unload, **kwargs) /usr/local/lib/python2.7/dist-packages/satpy/scene.pyc in generate_composites(self, nodes) /usr/local/lib/python2.7/dist-packages/satpy/scene.pyc in _read_composites(self, compositor_nodes) /usr/local/lib/python2.7/dist-packages/satpy/scene.pyc in _generate_composite(self, comp_node, keepables) /usr/local/lib/python2.7/dist-packages/satpy/composites/init.pyc in call(self, projectables, optional_datasets, **info) /usr/local/lib/python2.7/dist-packages/satpy/composites/init.pyc in get_angles(self, vis) KeyError: 'satellite_longitude' |
Thanks @AranJM So the error comes from satpy trying to compute the angle with pyorbital as they are not available as dataset. Computing with pyorbital, the way it is implemented in satpy at the moment only works for geostationary satellites, and expect a The deaper cause is that when loading angles for resolutions other than the ones provided in the file (1000m in this case), it doesn't work because interpolation of angles isn't implemented in the reader. |
Hi, would it be possible to get any update on this or any estimated time when it might be resolved, please? |
I might have time to look at it next week. Of course any help would be highly appreciated! |
I have the very same problem here with Himawari-8 data from EumetCast ( |
@honnorat What problem are you exactly running in to? As far as I know the |
I came across this issue because I googled "KeyError: 'satellite_longitude'" and it appears that my problem produces exactly the same traceback and is deeply linked with this one. After digging into the code, it seems linked to |
Interesting. This must be a bug with the @honnorat Would you mind filing a separate bug for this with a minimal example and the traceback you receive? Thanks. |
Of course. However not before next week, I fear. |
@AranJM As you can see I just submitted a PR that should fix this issue. It's still work in progress, but if you could try is out and see if it is a step in the right direction, it would be great. |
Hi @mraspaud, thanks! I hope to have time to look at it tomorrow. |
Describe the bug
When producing an image from level 2 MODIS data, the processing fails for any resolution below 1 km because the software cannot find the sun and satellite angle. These angles are provided in a different file (MOD03) for 1 km resolution, but the software does not interpolate them when trying to produce a finer resolution image.
To Reproduce
Expected behavior
A 500m resolution image is loaded.
Actual results
KeyError: 'satellite_longitude'
Environment Info:
The text was updated successfully, but these errors were encountered: