I am removing the part about the standalone WKT to be discussed in another issue.
Proposed WKT string statement modifications (modifications in italics): >There will be occasions when a given CRS property value is duplicated in both >a single-property grid mapping attribute and the crs_wkt attribute. In such >cases the onus is on data producers to ensure that the property values are >consistent. There will be occasions when a given CRS property value is >duplicated in both a single-property grid mapping attribute and the crs_wkt >attribute. In such cases the onus is on data producers to ensure that the >property values are consistent. *If both a crs_wkt and grid mapping attributes >exist, it is assumed that they do not conflict. As such, information from >either one (or both) may be used to represent the CRS of the file, recognizing >that the grid mapping parameters should always be completed as fully as >possible.* ~~However, in those situations where two values of a given property >are different, then the value specified by the single-property attribute shall >take precedence. For example, if the semi-major axis length of the ellipsoid >is defined by the grid mapping attribute semi_major_axis and also by the >crs_wkt attribute (via the WKT SPHEROID[…] element) then the former, being >the more specific attribute, takes precedence. Naturally if the two values are >equal then no ambiguity arises.~~ -- 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-586056569 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.