Talk:Quality control coding
During our shear probe group meeting on March 28, 2022, we discussed the possibility of using a different flagging scheme for the shear probe data. Suggestions were to use a binary system that allows to relate the flagging number to one or more specific data quality control tests that would be unique weven if multible quality control tests were failed by the data set. However, this flagging scheme would only apply to our data and international data centres or data display display servers (e.g. https://www.ocean-ops.org/board) would not recognize this. Perhaps a solution would be to use a two-level scheme, as also suggeted by the Intergovernmental Oceanographic Commission (IOC). On the primary level, we use a common quality flagging as shown below. The secondary level could then be a unique number that points to the quality test the data has failed. The lagging scheme below is taken from a best practice IOC document (link). The secondary level could then complement the primary level flags by reporting the results of specific QC tests performed and data processing history. As suggested by IOC best practices "The secondary level content varies in number and description and is chosen by those who implement the scheme, representing information on the applied quality tests (e.g., excessive spike check, regional data range check) and data processing history (e.g., interpolated values, corrected values)."
| Value | Primary-level flag short name | Definition |
|---|---|---|
| 1 | Good | Passed documented required QC tests |
| 2 | Not evaluated, not available or unknown | Used for data when no QC test performed or the information on quality is not available |
| 3 | Questionable/suspect | Failed non-critical documented metric or subjective test(s) |
| 4 | Bad | Failed critical documented QC test(s) or as assigned by the data provider |
| 9 | Missing data | Used as place holder when data are missing |
Would that work?
