Open mhidas opened 6 years ago
Hello Marty,
Argo is using such a scheme, although it does not appear as a two-tiered flagging.
Explanations in Argo user's manual, version 3.2, September 11th 2017 http://dx.doi.org/10.13155/29825
A QC flags scale : see page 78 §3.2 “Reference table 2: Argo quality control flag scale”
A history section that records the list of tests performed and the list of passed/failed tests: see page 122 §5 “Using the History section of the Argo netCDF Structure”
Best regards,
Thierry
De : Marty Hidas notifications@github.com Envoyé : mercredi 18 avril 2018 12:36 À : IQuOD/Formats Formats@noreply.github.com Cc : Subscribed subscribed@noreply.github.com Objet : [IQuOD/Formats] QC flag scheme (#6)
It's been suggested that we could have a two-tiered flagging scheme:
Both of these could be applied on a per-profile and a per-level basis.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/IQuOD/Formats/issues/6 , or mute the thread https://github.com/notifications/unsubscribe-auth/AS5znADuKdyoLgkShKHn0gT8SOCYznrwks5tpxcsgaJpZM4TZ045 . https://github.com/notifications/beacon/AS5znDn60rQoA0En_oERuf3KlitKiqsRks5tpxcsgaJpZM4TZ045.gif
The scheme recommended by Tim is the IODE flagging scheme. Here is the link: https://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=10762 I suggest we need to continue with the simple scheme followed in Argo and GTSPP. Can we fit it with the IODE scheme? I think we should avoid using history records if possible. The reason for choice of flag should be clear in the flags that we select.
It's been suggested that we could have a two-tiered flagging scheme:
Both of these could be applied on a per-profile and a per-level basis.