IOOSProfilingGliders / Real-Time-File-Format

Information and templates describing the netCDF file format to be used as the real time exchange data file between IOOS glider operators, the glider data assembly center, and the National Data Buoy Center.
https://github.com/IOOSProfilingGliders/Real-Time-File-Format/wiki
1 stars 1 forks source link

QC flag variables for coordinate variables #6

Closed kerfoot closed 11 years ago

kerfoot commented 11 years ago

Not sure if this was an oversite on my part (or intentional), but I'd like to add QC flag variables for the 'time' and 'time_uv' variables. At a minimum, I need flag values of 'measured' and 'interpolated'. I'm not sure about the spray or seaglider, but the sampling configurability of the slocum glider allows for missing timestamp values which are allowed for coordinate variables. So I'd like to fill the missing values and use the _qc variables to denote this.

Any problem with interpolating missing values in the coordinate array?

dpsnowden commented 11 years ago

If you've verified that this is legal CF behavior then I see no reason not to do it. I would first check with the GROOM manual. If I recall they have a pretty clear way of specifying how a variable is created and that it is general enough to apply to all variables. Similar to the measured vs interpolated.

Another source of information we should probably include is the ACDD proposed variable attribute coverage_content_type. This attribute uses ISO 19115 code spaces to indicate how the variable was derived. Check out the discussion at the ACDD page.