Extra metadata - physical

[callumrollo]

Following a discussion with SeaExplorer data users, several additional pieces of metadata have been suggested:

glider mass and glider volume for flight model regression. This should be simple to add to the yaml at the metadata level. Not sure if we'd need a structure to include units as well, or have names like glider_mass_kg and glider_volume_m3

location of sensors this is a little more involved, but seemingly the location of the sensors on the glider can be important in post-processing. One suggested method was to define x, y, z of the sensors relative to some consistent point of the glider chassis. These could be added to each sensor in the glider_sensors structure of the yaml

[jklymak]

A question here would be how automated these extra meta data should be. If they will be needed for automatic processing then they should definitely be attributes. If they are just extra info, then they could be in a physical_config string parameter that has whatever they like in it.

I don't think there is a way to nest attributes in netcdf but maybe like you are saving the sensor config as yml there could be a similar yml for physical config?