Difference between revisions of "RECOMMENDATIONS"
| Line 23: | Line 23: | ||
or under weather conditions featuring: | or under weather conditions featuring: | ||
* '''strong winds''' | * '''strong winds''' | ||
| − | * '''heavy | + | * '''heavy rainfall''' |
bear the danger of missed alarms. | bear the danger of missed alarms. | ||
| Line 29: | Line 29: | ||
| − | == How false/missed alarms are | + | == How false/missed alarms are tackled in the GFMS== |
This discuss the abovementioned issues of SAR-based water mapping which potentially cannot be directly solved by the proposed flood detection algorithms using only NRT-available backscatter information and hence indication need on pixel level for potential misclassification due to reduced sensitivity. <br> | This discuss the abovementioned issues of SAR-based water mapping which potentially cannot be directly solved by the proposed flood detection algorithms using only NRT-available backscatter information and hence indication need on pixel level for potential misclassification due to reduced sensitivity. <br> | ||
| Line 35: | Line 35: | ||
As a note: <u>Static</u> is understood here with respect to the GFMS reprocessing cycle, i.e., static layers remain unchanged during NRT processing, but they might be updated in the course of a reprocessing after evolution activities. | As a note: <u>Static</u> is understood here with respect to the GFMS reprocessing cycle, i.e., static layers remain unchanged during NRT processing, but they might be updated in the course of a reprocessing after evolution activities. | ||
| − | + | '''Static effects'''bound to ground surface characteristics like: | |
* land cover (e.g., '''flat impervious areas''', '''urban areas''', '''densely vegetated areas''') | * land cover (e.g., '''flat impervious areas''', '''urban areas''', '''densely vegetated areas''') | ||
* shadowing ('''radar shadowing''') | * shadowing ('''radar shadowing''') | ||
| − | are addressed by the | + | are addressed by the '''[[Exclusion Mask]]'''. <br> |
Pixels that could not be classified by the SAR sensor into flood area, permanent/seasonal water body, and non-water area, are highlighted in this product layer as no-data pixels. | Pixels that could not be classified by the SAR sensor into flood area, permanent/seasonal water body, and non-water area, are highlighted in this product layer as no-data pixels. | ||
| − | + | '''Dynamic effects''' triggered by weather conditions | |
| − | * meteorological | + | * meteorological features ('''strong wind''', '''heavy rainfall''') |
| − | Both layers are delivered with the other flood product layers and aim | + | * meteorological-induced state of the soil ('''soil dryness''', '''frozen ground''', or '''wet snow''' |
| − | The Advisory Flags layer aims | + | are flagged by the dynamic '''[[Advisory Flags]]'''. The '''[[Advisory Flags]]''' indicate locations where the SAR data might be disturbed by such processes during the acquisition, but leaves the flood and water extent layers unmasked. |
| + | |||
| + | Both layers are delivered with the '''[[PRODUCTS | other flood product layers]]''' and aim at improving the reliability, usefulness and user acceptance of the GFMS product. <br> | ||
| + | The design of this mask/flag-system recognises also the User perspective: with our approach, we provide a simple '''[[Exclusion Mask]]''' indicating all the pixels that could not be classified by the input Sentinel-1 data, consulting statistical parameters from the data cube as well as auxiliary datasets. <br> | ||
| + | The pixels addressed by '''[[Exclusion Mask]]''' thus can be directly discarded as no-data, leaving the interpretation of the produced flood extent and the (adjacent) no-data-gaps to the users, who commonly know best their area-of-interest. We believe that users are have in general good skill to deal with no-data-gaps, as long as the general reliability of the product is assured. | ||
| + | |||
| + | The '''[[Advisory Flags]]''' layer aims to raise awareness that meteorological processes comprising wind or frozen conditions might impair the water body detection. <br> | ||
| + | As the '''[[Advisory Flags]]''' can only be retrieved at a coarser resolution, we do not forward the information of the flags to the masking or to the '''[[Exclusion Mask]]'''. <br> | ||
| + | As coming in the form of the additional layer, it should guide the users when interpreting the product, allowing additional insight on its local reliability at the time of Sentinel-1 acquisition. | ||
Revision as of 11:38, 12 November 2020
In general, we can distinguish between effects leading to both over- and underestimation of detected flood extent (related to false alarms and missed alarms, respectively).
While false alarms draw the attention of users unnecessarily and thus could create frustration and mistrust in the product, missed alarms on the other hand would lead to situation where the flood event is not detected and leaves the users without notice, possibly losing time for reaction measures.
False alarms
The here mentioned water-look-alikes would yield false alarms:
- very dry or sandy soils
- frozen ground
- wet snow
- flat impervious areas (e.g. smooth tarmac covers as airfields or roads)
These surfaces and artifacts usually feature very low backscatter signatures and appear thus as water-look-alikes in SAR imagery, rendering the water and flood mapping a difficult task.
Another common effect in SAR remote sensing is radar shadowing, which appear over strong terrain (especially at the far-range section of the SAR image) as well as in the vicinity of high objects above the ground, like high buildings and along forest borders.
Missed alarms
As opposite, floods occurring in:
- urban areas
- densely vegetated areas
or under weather conditions featuring:
- strong winds
- heavy rainfall
bear the danger of missed alarms. In particular, wind and heavy rainfall are hard-to-spot dynamic process as they roughen water surfaces and hence undermine the initial assumption of low backscatter due to specular reflection on smooth water surfaces.
How false/missed alarms are tackled in the GFMS
This discuss the abovementioned issues of SAR-based water mapping which potentially cannot be directly solved by the proposed flood detection algorithms using only NRT-available backscatter information and hence indication need on pixel level for potential misclassification due to reduced sensitivity.
The aforementioned challenges are the classified into Static effects and Dynamic effects with the first bound to the ground surface, land cover or topography, and the latter resulting from meteorological dynamics. This is also done with the perspective on a performant global NRT processing.
As a note: Static is understood here with respect to the GFMS reprocessing cycle, i.e., static layers remain unchanged during NRT processing, but they might be updated in the course of a reprocessing after evolution activities.
Static effectsbound to ground surface characteristics like:
- land cover (e.g., flat impervious areas, urban areas, densely vegetated areas)
- shadowing (radar shadowing)
are addressed by the Exclusion Mask.
Pixels that could not be classified by the SAR sensor into flood area, permanent/seasonal water body, and non-water area, are highlighted in this product layer as no-data pixels.
Dynamic effects triggered by weather conditions
- meteorological features (strong wind, heavy rainfall)
- meteorological-induced state of the soil (soil dryness, frozen ground, or wet snow
are flagged by the dynamic Advisory Flags. The Advisory Flags indicate locations where the SAR data might be disturbed by such processes during the acquisition, but leaves the flood and water extent layers unmasked.
Both layers are delivered with the other flood product layers and aim at improving the reliability, usefulness and user acceptance of the GFMS product.
The design of this mask/flag-system recognises also the User perspective: with our approach, we provide a simple Exclusion Mask indicating all the pixels that could not be classified by the input Sentinel-1 data, consulting statistical parameters from the data cube as well as auxiliary datasets.
The pixels addressed by Exclusion Mask thus can be directly discarded as no-data, leaving the interpretation of the produced flood extent and the (adjacent) no-data-gaps to the users, who commonly know best their area-of-interest. We believe that users are have in general good skill to deal with no-data-gaps, as long as the general reliability of the product is assured.
The Advisory Flags layer aims to raise awareness that meteorological processes comprising wind or frozen conditions might impair the water body detection.
As the Advisory Flags can only be retrieved at a coarser resolution, we do not forward the information of the flags to the masking or to the Exclusion Mask.
As coming in the form of the additional layer, it should guide the users when interpreting the product, allowing additional insight on its local reliability at the time of Sentinel-1 acquisition.
