Hello everyone,
I'm currently working on validating Sentinel-3 atmospheric corrections over various types of inland water. I've got some really high errors when validating blue-green bands only over turbid water, but this is not happening with all data (figure attached of turbid water, grey line is in-situ Rrs data, yellow line is POLYMER estimated S3 Rrs data).
I executed POLYMER v4.16.1 using the run_atm_corr script with directional normalization disabled (normalize=2) and ERA5 auxiliary data. Did anyone else experience these errors?
Blue-green bands error over turbid water with Sentinel-3
-
- Posts: 5
- Joined: Wed Apr 17, 2019 9:37 am
- company / institution: University of Valencia
- Location: Spain
Blue-green bands error over turbid water with Sentinel-3
You do not have the required permissions to view the files attached to this post.
-
- Posts: 25
- Joined: Mon Mar 07, 2022 9:54 am
- company / institution: Finnish Environment Institute
- Location: Helsinki, Finland
Re: Blue-green bands error over turbid water with Sentinel-3
Maybe you could show the area and the name of the OLCI file you have used?
If the outlier pixels exhibit logfb and logchl values that are significantly different from those of other pixels, the optimisation probably hasn't converged properly. Polymer v4.15 provides an option to do an initial grid search which helps with convergence issues, see the `CHANGELOG.txt`.
If the outlier pixels exhibit logfb and logchl values that are significantly different from those of other pixels, the optimisation probably hasn't converged properly. Polymer v4.15 provides an option to do an initial grid search which helps with convergence issues, see the `CHANGELOG.txt`.
- fsteinmetz
- Site Admin
- Posts: 315
- Joined: Fri Sep 07, 2018 1:34 pm
- company / institution: Hygeos
- Location: Lille, France
- Contact:
Re: Blue-green bands error over turbid water with Sentinel-3
Hello,
Indeed this kind of behaviour is possible in complex cases. However, these results should be flagged, and not interpreted as valid results. See section "flagging" in README.md.
As said by sakvaka_env (thanks !), the specific test case could be useful, and the experimental OLCI configuration may improve these results, see release notes from v4.15 in the changelog.
Cheers,
François
Indeed this kind of behaviour is possible in complex cases. However, these results should be flagged, and not interpreted as valid results. See section "flagging" in README.md.
As said by sakvaka_env (thanks !), the specific test case could be useful, and the experimental OLCI configuration may improve these results, see release notes from v4.15 in the changelog.
Cheers,
François
-
- Posts: 5
- Joined: Wed Apr 17, 2019 9:37 am
- company / institution: University of Valencia
- Location: Spain
Re: Blue-green bands error over turbid water with Sentinel-3
Hello sakvaka, fsteinmetz, thank you for your replies.
I'm working over several inland waters in Spain and Brazil. I checked the logchl and logfb values of two of the images, taken over Albufera de Valencia, Spain (lat 39.3353 lon -0.3525):
[1] S3A_OL_1_EFR____20220222T101229_20220222T101529_20220223T135752_0179_082_179_2340_LN1_O_NT_002.SEN3 [2] S3A_OL_1_EFR____20230201T095344_20230201T095644_20230202T102859_0179_095_079_2340_PS1_O_NT_003.SEN3 Image [1] has a single pixel with logchla and logfb values matching the surrounding pixels, whereas image [2] has two pixels with values that differ greatly from the others. Regarding the flagging, I have set it to the recommended value for OLCI (bitmask & 1023 == 0). Is it your recommendation to return to v4.15 to improve these results?
Kind regards,
Patricia
I'm working over several inland waters in Spain and Brazil. I checked the logchl and logfb values of two of the images, taken over Albufera de Valencia, Spain (lat 39.3353 lon -0.3525):
[1] S3A_OL_1_EFR____20220222T101229_20220222T101529_20220223T135752_0179_082_179_2340_LN1_O_NT_002.SEN3 [2] S3A_OL_1_EFR____20230201T095344_20230201T095644_20230202T102859_0179_095_079_2340_PS1_O_NT_003.SEN3 Image [1] has a single pixel with logchla and logfb values matching the surrounding pixels, whereas image [2] has two pixels with values that differ greatly from the others. Regarding the flagging, I have set it to the recommended value for OLCI (bitmask & 1023 == 0). Is it your recommendation to return to v4.15 to improve these results?
Kind regards,
Patricia
You do not have the required permissions to view the files attached to this post.