-
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
NWCSAF reader does not support GOES or HIMAWARI #1110
Comments
gerritholl
added a commit
to gerritholl/satpy
that referenced
this issue
Mar 11, 2020
In the nwcsaf-geo reader, add GOES and HIMAWARI to the platform names. At least for GOES-16, this appears to enable the reading of NWCSAF generated GOES-16 data, thus closing pytroll#1110, but I have only tested this for GOES-16.
6 tasks
gerritholl
added a commit
to gerritholl/satpy
that referenced
this issue
Mar 12, 2020
In the nwcsaf-geo reader, add GOES and HIMAWARI to the platform names. At least for GOES-16, this appears to enable the reading of NWCSAF generated GOES-16 data, thus closing pytroll#1110, but I have only tested this for GOES-16.
This works with modern Satpy nowadays. Closing the issue. |
Thanks for checking it out! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Is your feature request related to a problem? Please describe.
The NWCSAF GEO software (v2018.1) supports MSG-HRIT as well as GOES-13, GOES-14, GOES-15, GOES-16 (ABI), and HIMAWARI (see NWC/CDOP3/GEO/AEMET/SW/UM page 21). However, the satpy nwcsaf-geo reader supports only MSG1–4 (Meteosat 8–11):
gives
Describe the solution you'd like
Personally, I only need GOES-16 ABI right now, so I will work on adding this. If this turns out to be as easy as adding a name to the
PLATFORM_NAMES
dictionary, I might as well add the others, but I will not test the others as this would require significant work to generate NWCSAF data. If it turns out to be a little bit more work to add GOES-16 ABI then I have no intention to add HIMAWARI or the older GOES imagers.Describe any changes to existing user workflow
There should be no changes to any workflow.
Additional context
This is part of the project to run fogpy on ABI data. An alternative would be to use ABI L2 data but I have already managed to get NWCSAF to run, and getting satpy to read NWCSAF-GEO ABI data should be easy in comparison.
The text was updated successfully, but these errors were encountered: