_If the CRS cannot be represented using the grid mapping parameters, using only
the crs_wkt attribute is considered valid._
Sorry, but to my untrained eyes this essentially means software that purports
to be CF compliant will have to be able to deal with WKT. It is very simple,
I have a
Just to be clear, this proposal does not propose to remove or override the
`grid_mapping` parameters. It's main goal is co-existence with the CRS WKT.
Proposed WKT string statement modifications (modifications in italics):
> The crs_wkt attribute is intended to act as a supplement to other
>
> Are there any applications that actively read in and use the CF grid mapping
> parameters?
Not sure if I'm answering the right question here, but
[Iris](https://github.com/SciTools/iris) ***definitely does*** explicitly
interpret CF grid-mapping terms : we have explicit code for translating
I would suggest maybe going a little slow on this one, because my guess is
many people are not following this discussion, so they will not be able to
respond. I have no idea what for example Panoply does, the Coastwatch tools,
Thredds, Seadas, and some others I can think of, and we
GDAL is one more than I was aware of. I'm not aware of any others.
--
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-572632771
This list forwards
@snowman2 Are there any applications that actively read in and use the CF grid
mapping parameters?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
One minor addition:
*"If the CRS cannot be represented using the grid mapping parameters, using
only the CRS WKT is allowed. However, some applications will not be able to
read in the CRS WKT form."*
--
You are receiving this because you are subscribed to this thread.
Reply to this email
