Rrs Output Differences Acolite vs. Polymer

Discussion of your results and ACOLITE in general
Post Reply
GHesketh
Posts: 3
Joined: Mon Sep 28, 2020 10:07 pm

Rrs Output Differences Acolite vs. Polymer

Post by GHesketh »

Hello,

I have been testing which softwares to use for level-2 gen outputs, especially remote sensing reflectance. I have found Acolite performs well, but in particular the HYGEOS software called Polymer seems better for the Gulf of Maine coastline which I am currently researching. All images use the 2021 January version of Acolite, using only the standard processing options but with specific gains (see below). Polymer does not have gain options and only one processing algorithm. Rrs was processed in Matlab by dividing the Acolite and Polymer rhow products by pi.

My gain line for the acolite_settings.txt file:

gains_l8_oli=1.018,1.01,1.007,1.0098,1.0,1.0,1.0


Here we see a noticeable difference in Rrs at all values. The location is Machias Bay in Maine.
20181025acolvpoly_Rrs_Landsat_10_29_Machias.png
20181025acolvpoly_Rrs_Landsat_10_29_Machias.png (42.54 KiB) Viewed 39316 times
This is especially problematic for regions such as Biscay Pond, a humic, low-turbidity, freshwater lake where we expect Rrs to approach 0 in the 440 nm red band. However, Acolite seems to have problems with this region, and bands past 443 even increase in Rrs.
20151109acolvpoly_Rrs_Landsat_11_29_Biscay.png
20151109acolvpoly_Rrs_Landsat_11_29_Biscay.png (46.09 KiB) Viewed 39316 times
20161010acolvpoly_Rrs_Landsat_11_29_Biscay.png
20161010acolvpoly_Rrs_Landsat_11_29_Biscay.png (44.67 KiB) Viewed 39316 times
My posting these images is not to discredit Acolite at all, I see in most cases the curve follows the same trajectory but with a set gap. Are there any settings recommendations for these discrepancies?
quinten
Posts: 1004
Joined: Tue Mar 03, 2015 8:13 am

Re: Rrs Output Differences Acolite vs. Polymer

Post by quinten »

Thanks for your question! Don't worry about discrediting ACOLITE - I think you have some valid concerns, and are perhaps hitting the limits of the current implementation.

First, the approach to atmospheric correction is quite different between ACOLITE and POLYMER, whereas the former models the atmosphere and subtracts that signal from the TOA, the latter has the outputs constrained by a full spectrum water model. So POLYMER will in most cases give a realistic (looking) water spectrum. This retrieved spectrum typically matches very well with in situ measurements - if the target falls within the scope of the water model. (If it doesn't, e.g. in turbid waters, the reflectance tends to be underestimated - at least that's what we found in the Belgian Coastal Zone. Paper coming soon in RSE!)

The ACOLITE/DSF atmospheric correction finds dark targets over a certain spatial extent and fits the atmospheric path reflectance to those targets assuming no surface reflectance. There are errors inherent to this approach - there can be e.g. an overestimation of the path reflectance if there is no truly dark pixel nearby, or an underestimation if the dark pixel e.g. has a lower aerosol load, is in cloud shadows, or is impacted by sensor noise. (Due to its design the DSF is more sensitive to "negative" noise.) There could be a tendency to underestimate the path reflectance also if any of the bands have a too low top-of-atmosphere calibration. By over/underestimation of the path reflectance the retrieved spectrum will look weird, shifted down or up.

In general I see an underestimation of the path reflectance for ACOLITE, this is driven likely by the DSF not allowing negatives anywhere in the spectrum, where allowing slight negatives in the NIR for clearer waters may not be an issue. These errors tend to matter less for more reflective waters, where they are a smaller fraction of the target signal. For low reflectance waters - such as yours - these may be much more important.

In your case there seems to be an offset of about Rrs 0.005 sr-1 or around 0.016 in reflectance in the first two plots and an offset of about Rrs 0.001 sr-1 or around 0.003 in reflectance in the last plot. This seems to correspond quite well with the results for the 440 band I found here (https://doi.org/10.1364/OE.397456), e.g. Figs. 5 and 6 (note these plots are in reflectance). Although our main intent is for ACOLITE to work well over turbid waters, I am currently investigating whether this performance at can be improved for low water signals.

It seems like a smoothing of the top-of-atmosphere data before extracting the dark spectrum may work reasonably well to reduce some of the errors leading to an underestimation. Here are some plots from work in progress that shows the current standard ACOLITE output (blue) for a matchup to in situ data in the Adriatic Sea (black). There is a clear offset of similar magnitude to what you observed. When applying a filter at TOA before running the DSF, the retrieved reflectances are quite a bit closer (orange and green lines for continental and maritime models). This seems to indicate that a part of the underestimation could be due to noise and that a median/percentile filter can smooth out these outliers. Unfortunately in other examples (e.g. land proximity) this approach does not so well.
ex1.png
ex1.png (26.67 KiB) Viewed 39303 times
ex2.png
ex2.png (24.37 KiB) Viewed 39303 times

The ACOLITE performance depends also a little bit on a few other factors either from your settings (e.g. processing a ROI or using fixed/tiled processing) or from the target (e.g. is it a narrow pond surrounded by land - looking at you Biscay Pond). The processing settings can change the area where a dark pixel is found, e.g. you could use a fixed path reflectance for a crop just around Biscay Pond. The Pond has a potential issue of strong adjacency effects in NIR and SWIR (and perhaps red/green in Spring/Summer) that will be present in the output reflectance from ACOLITE. I think this is what you see in your last plot, where the reflectance goes up again towards the NIR. Since the land/vegetation adjacency effects do not look like water, POLYMER will probably be able to exclude them as it directly models the water spectrum.

A long answer... that I hope was somewhat useful!

In short, if the POLYMER results are closer to your expectations you should use them! I am not sure of the POLYMER performance for small inland waters such as Biscay Pond. In the medium term I plan to evaluate how to improve low reflectance performance for ACOLITE/DSF.

Quinten

p.s. The gains you are using do not impact these results significantly I think, but it should be noted that they are for a specific sensor+processing system so they are perhaps not directly applicable to ACOLITE.
GHesketh
Posts: 3
Joined: Mon Sep 28, 2020 10:07 pm

Re: Rrs Output Differences Acolite vs. Polymer

Post by GHesketh »

Sorry for the late reply, but thanks for your very detailed explanation! Much appreciated!
Asim12
Posts: 51
Joined: Thu Oct 22, 2020 8:54 am

Re: Rrs Output Differences Acolite vs. Polymer

Post by Asim12 »

Hi,

How can we smooth the TOA data before applying DSF? I have the same issue.

Regards
Asim
quinten
Posts: 1004
Joined: Tue Mar 03, 2015 8:13 am

Re: Rrs Output Differences Acolite vs. Polymer

Post by quinten »

Hi Asim

This is not directly supported at the moment.

You can apply smoothing on the original L1 data files before processing them in ACOLITE. Alternatively you can use the ACOLITE L1R NetCDF outputs and apply the smoothing technique of your choice, and save a smoothed L1R file to be used as input to ACOLITE.

Quinten
Post Reply