Thank you @taylor13 for the proposals and @davidhassell for the implementation details.
I fully agree with your point 1, 2 and 3. There is possibly one situation that might need attention. If the coordinates subject to compression are stored in decimal64, typically we would require the computations to be decimal64 too, rater than decimal32. We could deal with that either by: A. Using the scheme proposed above, requiring the data creator to set the `computational_precision` accordingly. B. Requiring that the interpolation calculation are never carried out at a lower precision than that of the coordinates subject to compression, even if the `computational_precision` is not set. Probably A would be the cleanest, what do you think? -- 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-840817684__;Iw!!G2kpM7uM-TzIFchu!j-pO09g70M-pQckNVKXy6kW6_dkAhOtnQbeVFsFkbJ0RkqiZV1xGBP2CQpyiOHJEaF4MtDrBfkA$ 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.
