Hi @taylor13, Your point is valid. I guess there would be two alternative solutions:
1. We remove _'or exceed'_ from the sentence _'For the coordinate reconstitution process, the floating-point arithmetic precision should match or exceed the precision specified by computational_precision attribute.'_ That would be the closets we can get to _reproducible and of predictable accuracy_ . It would leave no choice to be made by the users uncompressing the coordinates and all users would get the same results. 2. We keep _'or exceed'_ and adapt the wording along the lines of what you propose. Personally, I think that ensuring _that the results of the coordinate reconstitution process are reproducible and of predictable accuracy_ is very valuable, and my preference would be option 1. I believe that if a data creator has judged that `computational_precision = "32"` is sufficient and appropriate for the data product, it would typically also imply that there is only a limited scope for real improvements on the user side by going to 64-bit floating-point arithmetic. That would also support option 1. What do you think? Anders -- 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-867659527__;Iw!!G2kpM7uM-TzIFchu!jqrMRPJgMCXBzWMK_C5wnS042F_1saeuKGKITvXgUfZ3CMnaNQLN8SlQRGCB0hCUss9SEdEuAHw$ 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.
