Dear Sylvain (@oceandatalab) Thank you very much for your proposed wording of the Computational Precision text, which I think is a sound way to formulate the meaning and usage of the `computational_precision` attribute.
I like the detailed rationale you have provided and support having the `computational_precision` attribute of the interpolation variable mandatory. Possibly we could shorten the text slightly and still convey the message? Would the following possibly do the job? **8.3.8 Computational Precision** The accuracy of the reconstituted coordinates will mainly depend on the degree of subsampling, the choice of interpolation method and the choice of the floating-point arithmetic precision used in the interpolation method computations. The accuracy of the reconstituted coordinates may also depend on details of the interpolation method implementation and on the computer platform, meaning that the results of the coordinate reconstitution process may not be fully reproducible. However, to enable the data user to reconstitute the coordinates to a accuracy comparable to the accuracy intended by the data creator, the data creator shall specify the floating-point arithmetic precision used during the preparation and validation of the compressed coordinates by setting the interpolation variable’s `computational_precision `attribute to one of the following values: (table) "32": 32-bit floating-point arithmetic, comparable to the binary32 standard in [IEEE_754] "64": 64-bit floating-point arithmetic, comparable to the binary64 standard in [IEEE_754] As an example, a `computational_precision` = "64" would provide the guidance to the data user that using 64-bit floating-point arithmetic will reconstitute the coordinates with an accuracy comparable to the accuracy intended by the data creator. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/327*issuecomment-873017814__;Iw!!G2kpM7uM-TzIFchu!mfqlpwce8MY_Ko0Jwe3q7zB4yHaQ_q_SMgTIVH0HO93jdABT07IZuPql32A9HGlhcZSMtfZ2-KU$ This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
