...
Quality flags describe the quality and origin of data.
The Flags available in Delft-FEWS are a based on a combination of two components: the origin and the quality of the data.
- Origin of the data
...
- Original
- The data value is the original value. It has not been changed.
- Completed
- The original value was missing and has been replaced by a non-missing value.
CorrectedThe original value has been replaced with another (non-missing) value. - : Original / Completed / Corrected
- Quality of the data
...
- Data is reliable and valid
...
- Data validity is uncertain
...
- : Reliable / Doubtful / Unreliable
...
| Note |
|---|
|
|
...
|
...
|
Additional Quality flags
In addition, there are a few other quality flags (or more broadly, time series flags) defined in Delft-FEWS, these are listed and described in the table below.
You can define custom quality flags. This can be useful to store external quality flag information that can't be mapped to the flags known to Delft-FEWS.
Custom Flags have no meaning, other than to store this extra bit of metadata.
The <name> and <description> are not used anywhere in Delft-FEWS (e.g. in the GUI) and only serve as additional information to the Flag mappings defined in the file itself.
ValidationRuleSet labels
The legend of the quality labels also includes optional labels that can be configured in validationRuleSet.xml.
These labels are unrelated to the QualityFlags described on this page.
Enumeration of quality flags
This leads to the The following quality flags available in are known to Delft-FEWS.Table 1 Enumeration of quality flags
Enumeration | Description |
0 | Original/Reliable |
1 | Corrected/Reliable |
2 | Completed/Reliable |
3 | Original/Doubtful |
4 | Corrected/Doubtful |
5 | Completed/Doubtful |
6 | Original/Unreliable |
7 | Corrected/Unreliable |
8 | Completed/Unreliable |
9 | Missing |
10 | Deleted |
11, 12, 13 | Not used |
14 | Accumulation Reset |
FlagSource
| Anchor | ||||
|---|---|---|---|---|
|
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.
Delft-FEWS stores not only the quality flags, but also the source of the flag, the so-called flagSource (Since version flagSource (since 2012.01).
The user is able to see why a certain value is validated as unreliable, eg. due to exceeding of the hard max .Table 1 List of Flag Sourcesvalidation rule.
| flagSource | Description |
|---|---|
CA | Conditional aggregation |
FC | secondary validation, flag comparison |
HN | hard min |
| HX | hard max |
| IMP | flag is imported |
| MAN | manual edit |
| MK | secondary validation, Mann-Kendall test |
| OSC | oscillation |
| ROF | rate of fall |
| ROR | rate of rise |
| SC | secondary validation, series comparison |
| SFP | start flag persistency |
| SN | soft min |
| SR | same reading |
| SVP | secondary validation, Flag persistency (FlagPersistencyCheck) |
| SX | soft max |
| TS | temporary shift |
...