Dear Jonathan and John, > > What does 9.1 actually mean by "monotonically increasing" > if the data > > can be stored in non-monotonic order? > > Ah yes, good point! Perhaps we should delete "with > monotonically increasing > times" in Table 9.1, and also "ordered" in the > trajectoryProfile definition.
Does CF really need to support unordered elements *within* a single[1] time series? e.g. Are there a significant number of real-time situations where the data from a single stream need to be written out of order to a CF file? So somewhat contrary to my previous statement, my current thinking is table 9.1 should keep the "monotonically" and "ordered" descriptions, and these should be clarified by further rules stating their ordered nature even when expressed as an aux coord var. [1] It's clear how it can help to support unordered elements *across* multiple time series - but that's taken care of by the indexed ragged array representation (9.3.4). Regards, Richard Hattersley AVD Iris Technical Lead Met Office FitzRoy Road Exeter Devon EX1 3PB United Kingdom Tel: +44 (0)1392 885702 Fax: +44 (0)1392 885681 Email: richard.hatters...@metoffice.gov.uk Website: www.metoffice.gov.uk _______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
