-
Notifications
You must be signed in to change notification settings - Fork 0
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
special_feature metadata file variable #32
Comments
Here are the SPECIAL_FEATURES entries from Coriolis DAC for BGC experimental sensors <style> </style>
|
Thanks Thierry.
It depends what is expected by 'machine parsing' then. What would be expected from the parsing at OceanOPS? We can include the special features in the official notification as well, the question is do we do that in any case, or just if it's compliant (ie contains 'AUX')? |
Just a reference to an older discussion on SPECIAL_FEATURES etc.: #8 |
In this "Auxiliary directory" page, it is mentioned: For a float, the list of sensors comes from PARAMETER and SPECIAL_FEATURES containing"AUX". |
Thanks. So:
My only question now is about this:
"AUX" will indicate relevant value in the string, but it can be something else than a sensor? Am I wrong? |
Personally I do not like upper case strings. So let's decide that "AUX" is not case sensitive (AUX, aux, ... are valid). |
In the NetCDF user's manual, it is mentioned :
This vocabulary captures the possible SPECIAL_FEATURES in a float’s characteristics.
Additional float features can be specified here such as algorithms used by the float.
The SPECIAL_FEATURES variable in a float metadata file must be filled by the DAC, to indicate there are AUX data files (see https://argo.ucsd.edu/data/auxiliary-directory).
Actually, it should not be a fixed vocabulary.
Today, for floats having experimental sensors it is required that :
The SPECIAL_FEATURES string must include the substring ‘AUX’ for machine parsing
Is that syntax sufficient ? Yes in my opinion.
Action : in Argo User's manual, replace This vocabulary captures with This variable captures
The text was updated successfully, but these errors were encountered: