OG1 compliance

[jklymak]

Theoretically, there is nothing stopping pyglider from outputting OG1.0 compliant netcdf with the appropriate metadata yaml.

Practically, there are probably some assumptions made in pyglider that make that hard/impossible. Let's start tracking those here, and then we can break into separate todos.

ping @callumrollo

[richardsc]

Ping @clayton33

[clayton33]

I've been creating near-compliant OG1.0 netcdf's for a while now. I say near because I actually have no idea if they actually are, most of the metadata information is there, I think. From my experience it comes down to incorporating all the necessary metadata elements in the metadata yaml file. Once processed via pyglider I run a script on all my files to re-name any variables that pyglider requires (e.g. pressure, temperature, etc.). In my yaml, under the variables that requires a name change I have something called replaceName, my script looks for that, and changes the name in the netcdf file. All other variables have the OG1.0 compliant name.

Here's a link to the post processing script I run on our processed SeaExplorer data files, https://github.com/DFOglider/utils/blob/main/processingScripts/postProcess_SeaExplorer_delayed.py.

And an example of one of our metadata yaml files, https://github.com/DFOglider/deploymentYaml/blob/main/GLI2025SEA032M98.yaml.

[jklymak]

Ok so it seems the that pyglider could/should be flexible enough to handle other names for temperature pressure etc.