Re: [CF-metadata] [cf-convention/cf-conventions] Allow CRS WKT to represent the CRS without requiring reader to compare with grid mapping parameters (#222)

2020-07-09 Thread taylor13
Oh, I just saw that the crossed out "is". Sorry. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/222#issuecomment-656300980 This list forwards relevant notifications

Re: [CF-metadata] [cf-convention/cf-conventions] Allow CRS WKT to represent the CRS without requiring reader to compare with grid mapping parameters (#222)

2020-07-09 Thread taylor13
@snowman2 My poor brain can't seem to detect what exactly was tweaked. Could you please point to the specific change made? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [CF-metadata] [cf-convention/cf-conventions] Allow CRS WKT to represent the CRS without requiring reader to compare with grid mapping parameters (#222)

2020-07-09 Thread Alan D. Snow
Minor tweak: For example, if the semi-major axis length of the ellipsoid ~~is~~ defined by the grid mapping attribute semi_major_axis **disagrees with** the crs_wkt attribute (via the WKT SPHEROID[…​] element), the value of this attribute cannot be interpreted accurately. -- You are

Re: [CF-metadata] [cf-convention/cf-conventions] Allow CRS WKT to represent the CRS without requiring reader to compare with grid mapping parameters (#222)

2020-07-09 Thread taylor13
Yes, I think the intent of this is fine. I don't recall the text that precedes the revised text, but should the first sentence read: "If, *for a given property,* both crs_wkt and grid mapping attributes exist, the attributes must be the same and grid mapping parameters should always be

Re: [CF-metadata] [cf-convention/cf-conventions] Allow CRS WKT to represent the CRS without requiring reader to compare with grid mapping parameters (#222)

2020-07-09 Thread JonathanGregory
This issue doesn't have a moderator - I think that's why it's not progressed. I will moderate it. @snowman2's current proposal (https://github.com/cf-convention/cf-conventions/pull/282) is to replace However, in those situations where two values of a given property are different, then the

[CF-metadata] [cf-convention/cf-conventions] Broken link to NUG Definition of Coordinate Variables (#283)

2020-07-09 Thread Dalton Kell
Hello all, While searching for defining characteristics of a _coordinate variable_ versus a _geospatial variable_, I found this issue. I marked it as a defect. My search also brought me to related issue #174, which seems to not have been resolved yet. # Hyperlink to the NetCDF Users Guide