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
A new version of the NetCDF file format checker should use the Argo vocabularies.
Argo vocabularies consists of reference tables described in RDF.
Here are the 28 reference tables as of December 9th 2021 (the few remaining one to come soon).
Note from a point raised during our 4th Argo Vocabulary Task Team meeting on the 16th of March 2022:
How shall the GDAC file checker implement edits to the Argo NVS collections? We initially thought of this possible solution:
Automatic implementation of concept addition to existing collections (e.g. a new sensor model added to R27)
Review of edits to existing concepts before implementation (as may cause legacy compatibility issues)
Other note from a point raised during our 4th Argo Vocabulary Task Team meeting on the 16th of March 2022:
Ongoing efforts to formalise the syntax of the information used to populate SPECIAL_FEATURES, which is an unconstrained netCDF variable in the metadata file which points to possible experimental sensors and data in the AUX directory for a float.
Once this work is complete, it was suggested that the GDAC file checker implements automatic checks on SPECIAL_FEATURES and send a warning to DACs that have content which does not comply with the agreed format/syntax.
A new version of the NetCDF file format checker should use the Argo vocabularies.
Argo vocabularies consists of reference tables described in RDF.
Here are the 28 reference tables as of December 9th 2021 (the few remaining one to come soon).
The text was updated successfully, but these errors were encountered: