search

davidfrantz / force

Framework for Operational Radiometric Correction for Environmental monitoring
GNU General Public License v3.0
172 stars 50 forks source link

Optional cirrus buffer #227

Closed davidfrantz closed 1 year ago

davidfrantz commented 2 years ago

Discussed in https://github.com/davidfrantz/force/discussions/224

Originally posted by **maxfreu** September 15, 2022 Hi! It seems like cirrus clouds are not buffered. Is this intentional? If yes, why? Here's an example where I would think a buffer could be useful to exclude compromised pixels: ![image](https://user-images.githubusercontent.com/67329240/190382720-5342cc85-f101-42fc-9fa0-e586c5d60212.png)

To-Do: implement optional cirrus buffer

davidfrantz commented 1 year ago

An optional cirrus buffer is now available within the dev branch: https://github.com/davidfrantz/force/commit/6f1335aa2e0c86e1a0dc41a4d29b138963f384b4

Excerpt from version history:

It is now possible to enable a buffer by using a buffer size > 0 for the new parameter CIRRUS_BUFFER. Note, that both the cirrus buffer won’t be represented in the “cloud buffer” QAI bit, but will be subsumed in the cirrus cloud bit (similar to snow buffer). This is because the bit structure would need to be disruptively changed to accomodate for a dsitinction.