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

Satpy built-in composite for dust RGB (MSG/SEVIRI data) does not generate expected color pattern #896

Closed
anikfal opened this issue Sep 6, 2019 · 26 comments

Comments

@anikfal
Copy link

anikfal commented Sep 6, 2019

Among Satpy's built-in composites for MSG/SEVIRI data, "dust" which is supposed to generate dust RGB color image, does not show an expected image.
The standard MSG Dust RGB images should be like the image bellow:
msg_standard_DustRGB
But the result is totally different:
dust_20190401_090010
The SEVIRI data used in the code:
https://drive.google.com/file/d/1IKqTMndqR-huKO98Z8J5WYXTqP3OJjZs/view?usp=sharing

from satpy import Scene
from glob import glob
filenames = glob("W_XX-EUMETSAT-Darmstadt,VIS+IR+HRV+IMAGERY,MSG1+SEVIRI_C_EUMG_20190401090010.nc")
scn = Scene(reader="seviri_l1b_nc", filenames=filenames)
composite = 'dust'
#composite = 'night_fog'
scn.load([composite])
scn.show(composite)
#scn.save_datasets(writer='simple_image')
@mraspaud
Copy link
Member

mraspaud commented Sep 6, 2019

Hi,
Welcome and thanks for reporting this. I tried with the file you provided and other seviri file, and can't reproduce the problem. Can you tell us about what version of satpy, xarray, dask, pyresample and rasterio you are using ?

@djhoese
Copy link
Member

djhoese commented Sep 6, 2019

AND how you are viewing the images?

@anikfal
Copy link
Author

anikfal commented Sep 6, 2019

Hi and thanks for your consideration.

  • satpy: 0.16.0
  • xarray: 0.12.1
  • dask: 2.3.0
  • pyresample: 1.12.3
  • rasterio: 1.0.26

Furthermore, by using NCL, I manually calculated the brightness temperatures for the three SEVIRI channels (ch7, ch9, and ch10) used in generating dust RGB images. the BT values calculated by NCL for ch9 and ch10 seemed to be identical with the BT values calculated by Satpy. But the calculated BT values for ch7 were totally different.

@djhoese
Copy link
Member

djhoese commented Sep 6, 2019

Any chance you have customized your Satpy installation at all? Do you have PPP_CONFIG_DIR set? Do you have any custom YAML files in your local directory?

@anikfal
Copy link
Author

anikfal commented Sep 6, 2019

I have not created any composite configuration and custom files, and have not set PPP_CONFIG_DIR.

@pnuu
Copy link
Member

pnuu commented Sep 6, 2019

And which python and numpy versions? Just a check that this isn't an integer division error or similar with Python 2 :-)

@djhoese
Copy link
Member

djhoese commented Sep 6, 2019

@anikfal Some of the other pytroll community have tried this and are seeing different results depending on how they are showing the image. Do you get the same "bad" image if you save to a geotiff and open it?

@simonrp84
Copy link
Member

Hi @anikfal, this might be related to the library versions you are using.
I just tried in a jupyter notebook and saw the same result as you. Then I ran conda update --all and tried again. After the update the image looks as it should.

I get the correct output with these versions:
satpy: 0.16.1
xarray: 0.12.3
dask: 2.3.0
pyresample: 1.12.3
rasterio: 1.0.25

@djhoese
Copy link
Member

djhoese commented Sep 6, 2019

Looks like some SEVIRI calibration issues were fixed in 0.16.1: #826

Try updating to satpy 0.16.1 and see if that fixes things.

@anikfal
Copy link
Author

anikfal commented Sep 6, 2019

Problem solved. Thank you guys so mush.
According to #826, some terms in the seviri_l1b_nc.yaml file should be changed. one of them (ch7) incorporates in the calculation of Dust RGB composites.
The corrected Dust RGB image:
dust_20190401_090010

@mraspaud
Copy link
Member

mraspaud commented Sep 6, 2019

Thanks for reporting back!

@mraspaud mraspaud closed this as completed Sep 6, 2019
@gisgeo3
Copy link

gisgeo3 commented Sep 17, 2021

Hi
I need help in create RGB for Meteosat.

@djhoese
Copy link
Member

djhoese commented Sep 17, 2021

@gisgeo3 Do you mean the "dust" RGB or another one? This issue has been closed since 2019. It would be best if you created a new issue and gave more details about what you're trying to do, what isn't working as expected, and any other details you can provide.

@gisgeo3
Copy link

gisgeo3 commented Sep 17, 2021

djhoese
Hello dear
I am currently a PhD student majoring in climate and atmospheric sciences.
The topic of my thesis is about air mass, but I do not know how to create an RGB image of air mass, can you help me?

@djhoese
Copy link
Member

djhoese commented Sep 17, 2021

@gisgeo3 Please create a new issue: https://github.com/pytroll/satpy/issues/new/choose

@gisgeo3
Copy link

gisgeo3 commented Sep 17, 2021

Is there anyone who can help me or can I contact them?

@anikfal
Copy link
Author

anikfal commented Sep 17, 2021 via email

@gisgeo3
Copy link

gisgeo3 commented Sep 17, 2021

Can I contact you personally.

@anikfal
Copy link
Author

anikfal commented Sep 17, 2021 via email

@nur-idrissa
Copy link

i mailed you. hope to get your assistance
thanks

@anikfal
Copy link
Author

anikfal commented Sep 23, 2021

@nur-idrissa I responded to your email, but I think it's better to create issues to make it available to all the Satpy community.

@nur-idrissa
Copy link

hello dear family of satpy/github.
i followed the procedure above , i get the image correctly BUT WITH WARNING from proj package and when i try to resample the output to local/region.

the error warning is :
/work/home/fabin/.conda/envs/satpy/lib/python3.7/site-packages/pyproj/crs/crs.py:543: UserWarning: You will likely lose important projection information when converting to a PROJ string from another format. See: https://proj.org/faq.html#what-is-the-best-format-for-describing-coordinate-reference-systems
proj_string = self.to_proj4()
/work/home/fabin/.conda/envs/satpy/lib/python3.7/site-packages/pyproj/crs/crs.py:543: UserWarning: You will likely lose important projection information when converting to a PROJ string from another format. See: https://proj.org/faq.html#what-is-the-best-format-for-describing-coordinate-reference-systems
proj_string = self.to_proj4()
/work/home/fabin/.conda/envs/satpy/lib/python3.7/site-packages/pyproj/crs/crs.py:543: UserWarning: You will likely lose important projection information when converting to a PROJ string from another format. See: https://proj.org/faq.html#what-is-the-best-format-for-describing-coordinate-reference-systems
proj_string = self.to_proj4()
/work/home/fabin/.conda/envs/satpy/lib/python3.7/site-packages/pyproj/crs/crs.py:543: UserWarning: You will likely lose important projection information when converting to a PROJ string from another format. See: https://proj.org/faq.html#what-is-the-best-format-for-describing-coordinate-reference-systems
proj_string = self.to_proj4()

@nur-idrissa
Copy link

HOW DO I SOLVE this error?

and i want to show the boundary of countries. as shown in the previous comments. thank you all

@nur-idrissa
Copy link

pip list command shows proj package is avalaible in the environment.

@nur-idrissa
Copy link

image

@mraspaud
Copy link
Member

@nur-idrissa the warning is nothing you need to worry about.
Regarding the coastline and borders (we call them overlays), for example:

overlay={
         'coast_dir': '/path/to/my/shapefiles/', 'overlays': {'coasts': {'outline': 'red'},
                                                              'borders': {'width': 0.5}}})
my_scene..save_dataset(overlay=overlay)

Also, in the future, please create a new issue if your problem is not directly related to an existing one.

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

No branches or pull requests

7 participants