nvs-vocabs / r01 Goto Github PK

The controlled vocab for DATA_TYPE is set in Reference Table 1. One of the controlled values (ID=META) has a different label definition in the NVS R01 vocab ("Argo metadata") compared to that in the Argo User's Manual, V3.41, page 71: "Argo meta-data". From a cursory look at some Argo wmoid_meta.nc files, it appears that the Argo User's Manual encoding is used in netCDF files, i.e.,

DATA_TYPE = "Argo meta-data " ;

https://vocab.nerc.ac.uk/collection/R01/current/
(Note the additional hyphen in Argo User's Manual version.)

The two definition should be reconciled to achieve machine-readable parsing of CDL and JSON files based on the vocabulary.

There is, I suppose, a separate issue here that some metadata fields in Argo netCDF files are encoded using labels ("Argo meta-data") as opposed to IDs ("META"), while other fields (e.g., "PLATFORM_FAMILY") are encoded using IDs. Not sure how to raise that issue....

Thanks,

Eric Rehm
Sea-Bird Scientific

Deprecate the B-Argo trajectory (BTRAJ) concept, to reflect the information in Reference Table 1 (data type) of the Argo User Manual.

Argo Auxilary Files also have a metafile, i.e., wmoid_meta_aux.nc.

For the DATA_TYPE field, it is currently populated with "Argo auxiliary meta-data", e.g.,

DATA_TYPE = "Argo auxiliary meta-data " ;

This label is not in Argo User's Manual Reference Table 1, p. 71 or the NVS R01 Vocabulary.

Eric Rehm
Sea-Bird Scientific