...
- Unreliable: The data value is unreliable and cannot be used for calculations like transformations or external models. It can still be viewed and exported with a regular exportModule as long as the unreliable flag is shown with it.
...
Enumeration | Description |
0 | Original/Reliable
The data value is the original value retrieved from an external source and it successfully passes all validation criteria set. |
1 | Corrected/Reliable
The original value was removed and corrected. Correction may be through interpolation or manual editing. |
2 | Completed/Reliable
Original value was missing. Value has been filled in through interpolation, transformation (e.g. stage discharge) or a model. |
3 | Original/Doubtful
Observed value retrieved from external data source. Value is valid, but marked as suspect due to soft validation limits being exceeded. |
4 | Corrected/Doubtful
The original value was removed and corrected. However, the corrected value is doubtful due to validation limits. |
5 | Completed/Doubtful
Original value was missing. Value has been filled in as above, but resulting value is doubtful due to limits in transformation/interpolation or input value used for transformation being doubtful. |
6 | Missing/Unreliable
Observed value retrieved from external data source. Value is invalid due to validation limits set. Value is removed |
7 | Corrected/Unreliable
The original value was removed and corrected. However, corrected value is unreliable and is removed. |
8 | Completed/Unreliable
Original value was missing. Value has been filled in as above, but resulting value is unreliable and is removed. |
9 | Missing value in originally observed series. Note this is a special form of Original/Unreliable. Missing values are automatically unreliable |
10 | Deleted Only used for non-equidistant series when timestep is deleted |
11, 12, 13 | Not used |
14 | Reset Used for rainfall data processing when the storage is reset (canister reset) |
Next to the flag it is also possible to get or set information why the flag is as it is through the so-called flagSource. Since version 2012.01 FEWS stores not only the quality flags, but also the source of the flag, the so-called flagSource. So the user is able to see why a certain value is validated as unreliable, eg. due to exceeding of the hard max.
The list of flagSources is:
...