# Moderator
@davidhassell
# Requirement Summary
Ensure internal consistency and correctness of figure numbering, formulas,
terms, examples
# Technical Proposal Summary
This issue addresses:
- Correction of typos in formulas;
- Correct figure numbering and change all figure numbering to consist
Dear @JonathanGregory ,
We have just discussed the matter of the cell bounds interpolation and the
question you [raised
@AndersMS pushed 1 commit.
b10fb673c6289bfe7585b33b7c5056b2c43abc90 Clarify conditions for bounds
interpolation
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
Dear @JonathanGregory,
Once again, thank you very much for your thorough review and valuable comments,
which significantly improved the proposal.
Cheers
Anders
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Dear @JonathanGregory ,
Regarding the interpolation of bounds, [you
asked](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/327*issuecomment-886687324__;Iw!!G2kpM7uM-TzIFchu!gwecS-gI9rNIndTP8rqMcB6mXYSV_fxclkyOlS4CO2hI_NE9xWHxmdM2h4s2mto-MGJkkxsi9oo$
):
> Are
@JonathanGregory, @davidhassell, @erget
A special character had sneaked into the formulas `cos() `and `sin()`. I have
removed it c989276 and the boxes are gone in my preview.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
@AndersMS pushed 3 commits.
7802b6ec8d3f33237472a81ed106b5ca74662e02 Move coordinate_interpolation to
correct alphabetic position in table
d28dfd1a4dfb3fe42ef3ed702d61cca05d8c8cdd Increase column width in Common
Conversions and Formulas
c9892766a85437d6ea88034741244f411a9def8e Remove special
@AndersMS pushed 2 commits.
b2bb0176c7be721fe6e4e9c42264cb66fe476abc Corrections of typos
b6cd5e6ceb6e7cdbc1af2debe884d16263748923 Correct Futhermore -> Furthermore
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__ht
@AndersMS commented on this pull request.
> @@ -606,7 +606,7 @@ For the reconstituted coordinates, cell bounds are stored
> separately for each co
for the example of 2D bounds. Since the cell bounds are contiguous, bounds
points of adjacent cells will coincide and so the full set of
@AndersMS pushed 1 commit.
be8f18da851a6835a7de60695ac0ae6dc5d1c9d6 Minor editorial corrections
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 2 commits.
09b107edb7af0b90e333a46d052e34d716e21790 Reword and move to end of chapter the
section on computational precision, update all examples to have
computational_precision attribute
2711322ced19d5597f3fa69fc0941bdce8eb7c55 Correct section link
--
You are receiving
@AndersMS pushed 1 commit.
bf952344788260709394d0cda74aa5ee3d70dff0 Editorial, heading capitalisation
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 2 commits.
4cc00cb90b8250417fd9eb7b1a832551d22492aa Change cartesian to 3d cartesian
(Change 27)
d9436e48c4b6aabb87b6bcc9ba3dd4ec61c37377 Rename [bi_]quadratic_remote_sensing
to [bi_]quadratic_latitude_longitude (Change 27)
--
You are receiving this because you
@AndersMS pushed 4 commits.
ec65f107617d4ae9a2bad371f279061971755724 Change font in Common Conversions and
Formulas table
06dac3aeb6d8b6dd9b8356258193b3923aa03b3f Revert change 5f9ad9a (Change 23)
a30c58f4e34e5b1b76c823ccadbb0dd386dcff25 Improve wording of bounds
interpolation tie point
Dear @JonathanGregory,
Just to let you know that I just updated my reply to **Reply to
Comment/Proposed Change 23**
Dear All,
Here are the links to the easy-to-read versions including all the above changes:
- [Chapter
Dear @JonathanGregory ,
Thank you for your rich set of comments and suggestions. I have provided
replies below, in the same format we used for the first set of comments.
Several of the replies I have already implemented in the document and indicated
the corresponding commit. For others, the
@AndersMS pushed 1 commit.
303aaa440351b05a7ff52d4329426d81a5c1e7bc Add "s" to "each of the interpolated
dimension" in Appendix J
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-conve
@AndersMS pushed 1 commit.
4efef82a424181cfc477bdb1b07fc83026f2c949 Move "Common Conversions and
Formulas" in front of "Interpolation Methods" in Appendix J
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/
@AndersMS pushed 1 commit.
ea474a57a803015fdf166fcea420746620774daa Rename cofficeint "c" to "w" in
Appendix J to avoid confusion with point C
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://gith
@AndersMS pushed 1 commit.
0116283e6cda5d94e3ccf3ff2731d8fd2fda8515 Change "equivalently" to "similarly"
in explanation of s1 and s2 in App J
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.
@AndersMS pushed 1 commit.
5f9ad9ac3616131cd3263f2eaa7d2781ff088df8 State tht for linear interpolation,
the coordinates of the interpolated points are evenly spaced.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https
@AndersMS pushed 1 commit.
0fdc7e448cb9798814c40c0b490ab8df35b7fc3e Move Figure 1 and 2 in Appendix J
futher down
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
1002806c944e105644cdc6afc35128738ac676c0 Include interpolation argument s in
figure 1 and 2
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326
@AndersMS pushed 1 commit.
f6f48fbea3b4780cb439a00dced0ee770592418f Introduce section numbering and
remove table captions in Appendix J
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
@AndersMS pushed 1 commit.
ca816180507dee3cd7633836e85c64f3356b514b Correct "target dimension" to
"interpolated dimension" (Change 17)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.
Dear @JonathanGregory ,
I am still a bit new to documents on GtiHup, but these two links does the job
in my browser:
- [Chapter
@AndersMS pushed 1 commit.
d033feeb798aa4c63e3d0d8ce04d27809dde2d0f Change "iz" (interpolation zone) to
"is" (interpolation subarea) in App J (Change 3)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__h
Dear @JonathanGregory,
Appendix J is now ready for your review.
The only remaining open issues is now that we will do one more iteration on the
section on Computational Precision for Chapter 8 - we will publish it here
within the next days.
Best regards,
Anders
--
You are receiving this
@AndersMS pushed 1 commit.
ecdaf926c5b6ba87045d47f5dabffe25715429c8 Correct numbering mistake in Appendix
J
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
a285b42869c278d948ec387a47e74e64e4ed07f4 Correct spelling mistake in Appendix J
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
0ef79f53ef5b0713969fa9d2b400a4c5205f3c13 Update Appendix J with new terms and
names
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
0c5b732cbbf7d2ddc006e3708813e7c70a722e16 Require tie points to be numeric type
and have no missing values
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
@AndersMS pushed 1 commit.
3ea5989193f8dc3dd7bc14db8b047fc19d8234f0 Update <> names and figure
names to new terms
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326
Dear All,
Just to let you know that as agreed during the discussion of the new
"Interpolation of Cell Boundaries" section (f3de508) I have added a the
following sentence in the "Interpolation Parameters"
section (2ce5d66):
> Interpolation parameters are not permitted to contain absolute
@AndersMS pushed 1 commit.
2ce5d66afbb3a93ee1cc4497d0ead05f38d1aee5 Constrain interpolation parameters to
support bounds interpolation
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
Dear team,
Following our meeting this afternoon, I propose the following new paragraph at
the end of the section "Tie Points and Interpolation Subareas":
> Tie point coordinate variables for both coordinate and auxiliary coordinate
> variables must be defined as a numeric data type and are not
@AndersMS pushed 1 commit.
f3de5085b4cec59515b0306b5dae2d4280d4a74d Rewrite section Interpolation of Cell
Boundaries (Change 15)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions
@AndersMS commented on this pull request.
> +Note that the value of `s` varies from `0.0` at the tie point `A` to `1.0`
> at tie point `B`. For example, if `ia = 100` and `ib = 110` and the index in
> the target domain of the coordinate value to be reconstituted is `i = 105`,
Dear All,
Regarding the wording of the section on computational precision attribute, I
have reservations with respect to the direction it has taken and I suggest we
discuss the matter during our meting this afternoon.
It is essential to the value and usability of the of the _Lossy Compression
@AndersMS pushed 1 commit.
cb91ac0e6885b578c2afefe8439f87b8ccaec2b8 Update ch08.adoc
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
5ddda3be5c4de9e0914bc8eb42c4c65dd81ae95d Update ch08.adoc
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
daaa3e0390a8f029ef56b67258c1f2586edde967 Remove paragraph "A single
interpolated dimension may be associated with multiple " no longer relevant
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldef
@AndersMS pushed 1 commit.
98075185eff417f6b666209709441f01f8935498 Combine the tie_point_dimensions and
tie_point_indices attributes (Change 1)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention
@AndersMS pushed 1 commit.
db15c0151696dfcfea3c4f4da2e82fcffbcca6b5 Add new section 8.3.9, "Computational
Precision"
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-convention
Hi @davidhassell and @oceandatalab,
I also support the `computational precision` paragraph by @davidhassell
presented here
Dear All,
As proposed
[above](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/327*issuecomment-872151596__;Iw!!G2kpM7uM-TzIFchu!i2lqlelli9HNPJ8B2iYj8zTfVVqAhReHwOARRaVVBHVvLhBGBN3dSzLqichBRORcq_I9wjOrnsg$
) I will go ahead and change all occurrences and forms
@AndersMS pushed 1 commit.
5ff42831af6d9e045e6f4f862d14b73f34826c5a Clarify interpolation subarea size
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
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
@AndersMS pushed 1 commit.
2becd52c5f81920fa24b495de50a17cb0f488c5f Improve wording of Tie Point Index
Mapping (Change 8)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull
@AndersMS pushed 1 commit.
376fd271d9314aea350c79773063acc7601327b8 Update Example 8.6 to correctly
specify one dimension interpolation for X and Y
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf
@AndersMS pushed 1 commit.
839b49c63365a2f27a5bf47434def05636feaee3 Improve description of
non-overlapping interpolation subareas
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions
@AndersMS pushed 1 commit.
577fbcc7996d85157ebd5d829240b121c8ca2a76 Improve description of
non-overlapping interpolation subareas
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions
@AndersMS pushed 2 commits.
e5feea3947e9958b79ba26da642a2fd1da66921b Combine the tie_point_dimensions and
tie_point_indices attributes (Change 1)
35019927e4218044d09d1cc6a61cf727dc4cf58f Update figures to match new terms
--
You are receiving this because you are subscribed to this thread
Dear All,
Considering that we have now renamed the term _tie point interpolation
dimension_ to _subsampled dimension_, should we possibly change the title
**Lossy Compression by Coordinate Sampling**
to
**Lossy Compression by Coordinate Subsampling**
and the replace the occurrences of
@AndersMS pushed 1 commit.
db0eb4e0a75f20d0733996ab8579b26404b148fb Rename terms to: subsampled
dimension, interpolated dimension and non-interpolated dimension
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https
Dear @JonathanGregory
That's an interesting suggestion, than you. We will discuss it in the group
tomorrow.
Best regards,
Anders
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Dear @JonathanGregory
Dear Jonathan,
Thank you for the fedback.
- yes, we had a sentence saying that the size of a tie point interpolation
dimension must be less than or equal to the size of the corresponding
interpolated dimension. I actually deleted it, since it is a consequence of
other
I have removed the paragraph "The same interpolation variable may be multiply
mapped " as proposed
@AndersMS pushed 1 commit.
485d3b8a762d074844611b96fbfd5bbedb228d22 Remove paragraph "The same
interpolation variable may be multiply mapped " no longer relevant
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/
Dear All,
I believe the following paragraph from our chapter 8 is no longer relevant,
after we have moved all the dimension related attributes from the data variable
to the interpolation variable.
The tie point variables `lat` and `lon` spanning dimension `tp_dimension1` and
tie point
Hi again @JonathanGregory
Just to add the figures have not yet been updated, I think we will do this when
all text changes have ben agreed.
Anders
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Dear @JonathanGregory
We have progressed with preparing the replies to your proposals. Although there
are still a couple of open points, we thought it would be useful to share what
we already have.
We have numbered your proposal as Proposed Change 1-16 and treated each of
these separately
@AndersMS pushed 1 commit.
5cfae45cdb53b3901e7e2dddeacc4a355c9bfbf2 Improve wording of "An interpolation
subarea must span..." (Change 11)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-con
@AndersMS pushed 1 commit.
d6d7ea3d3fffbc05e1479feee36d3780181c912a Rename "terms to continuous area" and
"interpolation subarea" (Change 5)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.
@AndersMS pushed 1 commit.
f439ee5c9485f5945b00d011162f86b2b1dd4eb9 Reduce number of data variables in
Example 8.5 (Change 16)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions
@AndersMS pushed 1 commit.
aceb9873714a6cf5995c1fe916558bb86de502a3 Improve sentence "The bounds of a tie
point must be the same..." (Change 14)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-
@AndersMS pushed 1 commit.
ba4a65e5fa45c8e11c6ae4b6f4f2551279189af3 Reword text about the dimensions of
interpolation parameter (Change 13)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
@AndersMS pushed 1 commit.
fdeef671ca195f49965f3d38404f6f4367995178 Correct sentence "must be a
subset of zero or more of the ..." (Change 12)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://git
@AndersMS pushed 1 commit.
d715552465cae76bbb912e72f10d2620d7398592 Improve sentence "An interpolation
zone must span at least two points..." (Change 11)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://git
@AndersMS pushed 2 commits.
3d4348f5904bc6a105bf0e853b9cafee9f4ae3e0 Update sentence: "A single
interpolation dimension may be associated..." (Change 9)
7ab0c4f73f4813ebed8dc98779bb6a5d665d2fbf Reword section "Interpolation and
non-interpolation dimension" (Change 10)
-
@AndersMS pushed 1 commit.
971bfbec0577a2efb7c1a32fc872894e2ee1a86c Remove sentence "This form of
compression may also be..." (Change 7)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-con
@AndersMS pushed 1 commit.
27d17334e2348431a2c34326cf487be3201f15b6 Reword first paragraph of Section 8
(Change 6)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files
@AndersMS pushed 1 commit.
a6d37b4a9ad545b9e20c22f96f6082aec9dc2f0f Change term 'tie point variable' to
'tie point coordinate variable' (Change 4)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf
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
@AndersMS pushed 1 commit.
f8cd983c76e0a6fb2485144ad5aa699e2e42b30b Rename tie_point_dimensions attribute
to tie_point_mapping (Change 2)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
@AndersMS pushed 0 commits.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/pull/326/files/1c9ced889dfe11ff37b29750efc2ae01d90b7717..190fdffaae6c24c28633cc3e167c68df674a9a1f__
@AndersMS pushed 1 commit.
1c9ced889dfe11ff37b29750efc2ae01d90b7717 Add section in Chapter 8 on
Computational Precision including new reference
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention
Hi @JonathanGregory and @erget
We propose to change the firstagree with your proposed text. We have opened
this issue (Rework intro to Section 8: Accuracy & precision · Issue #330 ·
cf-convention/cf-conventions (github.com)) to address per-variable gzipping as
well as to verify that the usage
@AndersMS pushed 1 commit.
190fdffaae6c24c28633cc3e167c68df674a9a1f Reword section Interpolation and
Non-Interpolation Dimensions (Cahnge 10)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
@AndersMS pushed 1 commit.
ea5268bde8f55073fa626808b3fbfd81136b45f4 Rename attribute tie_points to
coordinate_interpolation (Change 2)
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf
Good idea David.
Should we perhaps use _computation_ instead of _calculation_ to match the
attribute name? Here I have updated the first two paragraphs and added an
example:
**8.3.8 Computational Precision**
"The accuracy of the reconstituted coordinates will depend on the degree of
Dear All,
Following a discussion yesterday in the team behind the proposal, we propose
the 'computational_precision` attribute to be optional. Here is the proposed
text, which now has a reference to [IEEE Std 754]. Feel free to comment.
Anders
**8.3.8 Computational Precision**
The accuracy
Dear @JonathanGregory
Thank you very much for your rich and detailed comments and suggestions, very
appreciated.
The team behind the proposal met today and discussed all the points you raised.
We have prepared or are in the process of preparing replies to each of the
points. However, before
Hi @taylor13 and @davidhassell,
Regarding the `computational_precision` attribute, it appears that we currently
have two proposals: Either an optional attribute with a default value or a
mandatory attribute.
I have written two versions of the new section 8.3.8, one for each of the two
Hi David,
Yes, I would be happy to update the PR. However, I still have one concern
regarding the `computational_precision `attribute.
In the introduction to _Lossy Compression by Coordinate Sampling_ in chapter 8,
I am planning to change the last sentence from
> The creator of the compressed
Hi David,
Fine, I take your advice regarding not having a default value. That is probably
also simpler - one rule less.
Anders
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Leaving out "base-2" is fine. Shortening the description further as you suggest
would also be fine with me.
I am wondering if we could change the wording to:
"The floating-point arithmetic precision should match or exceed the precision
specified by `computational_precision `attribute. The
Hi @taylor13 and @davidhassell,
I am not fully up to date on the data types, but following the links that David
sent, it appears that decimal64 is a base-10 floating-point number
representation that _is intended for applications where it is necessary to
emulate decimal rounding exactly, such
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
Hi @taylor13
Thank you very much or your
[comments](https://urldefense.us/v3/__https://github.com/cf-convention/discuss/issues/37*issuecomment-832780564__;Iw!!G2kpM7uM-TzIFchu!lLfxA-1u7BwCI_w6J1bYPrIbNQuDCLnaPErHAUz5vBwAAZn2Z7S69d6LTvuHUjDOgIwCD7NGM8M$
). We did have a flaw or a weakness in the
@AndersMS pushed 1 commit.
4088f637e3d76c0046e75255653a40703c4200d3 Replace expression for gsqr with
equivalent, but numerically more accurate version
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://urldefense.us/v3/__https://github.com/cf
# Title
Lossy Compression by Coordinate Sampling
# Moderator
@user
# Moderator Status Review [last updated: -MM-DD]
Brief comment on current status, update periodically
# Requirement Summary
The spatiotemporal, spectral, and thematic resolution of Earth science data are
increasing
Hi @davidhassell,
It was not my intention to propose only one domain variable per file, but to
suggest one domain variable per domain (so no copies) :-)
So the if
- there is only one domain variable per domain
and
- if domain variables are used in the file, all domains must have a domain
Hi @davidhassell and @JonathanGregory,
> As @JonathanGregory says, this is no problem. I don't think that this needs
> special mention, as this is has always been true of all types of variables.
>From a user point of view and for the ease of discovering the domains, it
>would appear
@davidhassell
A couple of comments on the proposed text:
Possibly it could be made clearer in the text that multiple domain variables
may exist in a file. The text uses the plural form in a few places, like in the
heading 5.8 Domain Variables, but mostly uses the singular form. The current
Dear @davidhassell ,
I also support this proposal. This will address some of the uses cases
discussed in [cf-convention/discuss#37, Standard way to define subsampled
coordinates,](https://github.com/cf-convention/discuss/issues/37), including
the need for tools to be able to pre-process
97 matches
Mail list logo
