You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This note was written in the draft OG1.0. We turn it into an issue to keep this topic live and anticipate future release.
Note: It is anticipated to upgrade the ancillary variable related to QC by refining the ancillary variable name like < PARAM >_qc_generic, < PARAM >_qc_spike_test, _qc_land_test, etc. Current _QC attributes based on CF guidance (http://cfconventions.org/Data/cf-conventions/cf-conventions-1.10/cf-conventions.html#flags) and use the GOOS networks 0-4 flagging convention.
The text was updated successfully, but these errors were encountered:
vturpin
added
question
Further information is requested
1.X
For stuff to postpone and resolve only after the 1.0 release
labels
May 24, 2024
I believe GOOS is following the IOC flag scheme documented here: Paris. Intergovernmental Oceanographic Commission of UNESCO, 2013. Ocean Data Standards, Vol.3:Recommendation for a Quality Flag Scheme for the Exchange of Oceanographic and Marine Meteorological Data. (IOC Manuals and Guides, 54, Vol. 3.) 12 pp. (English.)(IOC/2013/MG/54-3) https://repository.oceanbestpractices.org/bitstream/handle/11329/413/MG54_3.doc
In my latest files, I provide this reference as an attribute on each of the qc variables. Examples of that metadata (for a delayed mode data collection) are here: https://spraydata.ucsd.edu/erddap/info/scrippsGlidersSQ/index.html. This dataset includes a primary and secondary flag scheme.
Hi Jen,
Yes I think this is exactly the same reference. @justinbuck will confirm !
Do you use the Quartod methodology for this ? If yes, how do you map the QUARTOD flag with "GOOS/IOC" flags ?
I did not get the point on primary and secondary flags.
Moderator: @OceanGlidersCommunity/format-maintainers
This note was written in the draft OG1.0. We turn it into an issue to keep this topic live and anticipate future release.
Note: It is anticipated to upgrade the ancillary variable related to QC by refining the ancillary variable name like < PARAM >_qc_generic, < PARAM >_qc_spike_test, _qc_land_test, etc. Current _QC attributes based on CF guidance (http://cfconventions.org/Data/cf-conventions/cf-conventions-1.10/cf-conventions.html#flags) and use the GOOS networks 0-4 flagging convention.
The text was updated successfully, but these errors were encountered: