-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removal of all unused legacy _qc variables #278
Comments
See 911b4a1 The following were addressed:
|
The following is being investigated:
|
In progress, Testing a code to remove all empty _qc variables from the DAC files. |
This sounded like it was finished recently, and that NDBC was able to test and update their code accordingly. Can this be closed? |
The legacy _qc variables still present in the system datasets are presumed to be from the providers' originally submitted files and will continue to exist in the system. Issue #372 has been opened to verify this. |
The original DAC NetCDF specification provided a set of reserved variables that could be used by the data providers to store the results of an aggregate qc algorithm for a geophysical variables. These reserved names are:
These variables appear to be hardcoded into the script that builds the ERDDAP catalog:
glider-dac/scripts/build_erddap_catalog.py
Line 516 in 22d6322
which resulted in all data sets containing these empty variables, regardless of whether they are variables that are included in the data provider files. Upon inspection of over 1600 data sets, it has been determined that these variables are not included in the vast majority (>99%) of user submitted data sets.
The following steps are suggested:
These variables will be replaced by a set of reserved variable names that will contain the results of QARTOD tests. A comprehensive discussion of this can be found in #268. The resulting aggregate flags provided by the QARTOD test suite will be used by NDBC to determine suitability for release to GTS as described in #277.
The text was updated successfully, but these errors were encountered: