Re: [CF-metadata] string valued coordinates

2014-11-07 Thread Jonathan Gregory
Dear Jim > I think deprecation for variables with a flag_values attribute is > going to far. We have quite a few variables where the values are > numeric and have units, but we encode specific error conditions with > values (outside the valid range) using flag_values and > flag_meanings. OK. Woul

Re: [CF-metadata] string valued coordinates

2014-11-07 Thread Schultz, Martin
Dear Jonathan, Deprecating the units attribute for string and char variables (perhaps int, too?) sounds like a good idea. Yet, I would still second Marc to at least allow for a "None" value in the units attribute - as far as I understand this wouldn't break the compatibility. But, in

Re: [CF-metadata] string valued coordinates

2014-11-07 Thread Hedley, Mark
Hello Jim et al I have followed your path and I agree with your analysis It looks like my assumption, and a whole part of my discussion thread, is based on a piece of code in a third party udunits wrapper which is not part of udunits. Hence I have been muddying the issue with an interpretation

[CF-metadata] standard_name: 'ensemble', was RE: realization | x of n

2014-11-07 Thread Kettleborough, Jamie
Hello, Is it worth introducing the new standard name 'ensemble' which is an alias for 'realization'? (Have we talked about this before?) Initially we used 'realization' to try to be more general than model studies (i.e. samples from distributions produced by statistical techniques) but 1.

Re: [CF-metadata] realization | x of n

2014-11-07 Thread John Graybeal
Modified to fit Mark's use case, I think suitable text is: name: original_ensemble_size description: The number of member realizations in the originally constituted ensemble. This provides context for any specific realization, for example orienting a member relative to its original group (even

Re: [CF-metadata] Classification of a "trajectory" with asynchronous time coordinates

2014-11-07 Thread Mike Godin
Hi Jim, Actually, the latitude, longitude, and z values are not sampled at different rates (I showed them as such for an extreme example, and in some decimation schemes they end up being asynchronous), but in reality the science data are collected asynchronously from each other and the coordina

[CF-metadata] SeaDataNet and ADCP data

2014-11-07 Thread Lowry, Roy K.
Dear All (especially John Caron), We're currently extending the SeaDataNet NetCDF standard - a profile of CF1.6 - to cover vessel-mounted ADCP and other profileTrajectory data (e.g. towed thermistor chains). Two issues have arisen. 1) For a ship, VMADCP have profiles of current parameters for e