I am a GDAL/PROJ user, so from my biased perspective life would be much easier from the WKT form :). Additionally, since WKT is already a standard from the OGC geospatial community, most geospatial software should be able to support it.
> The WKT model of metadata is different from the CF one. ... That would be a > big job. Correct. That is why I propose the CRS WKT take precedence. The CF grid mapping parameters only provides support for a limited subset of projection parameters. (Ref: https://cf-trac.llnl.gov/trac/ticket/69): > 3.2. Because the conceptual model for coordinate reference systems is both > large and complex it is considered impractical to devise CF attributes for > all of the potential CRS properties which might need to be encoded as > metadata attributes in netCDF files. Consequently there is a requirement for > such CRS properties to be specified in a compact notational format, > preferably a format that is already in widespread use, either as a de facto > or de jure standard. So, in this proposal, if the CRS WKT exists and can be read in, the CF projection parameters should be ignored entirely and no checks made between the two. However, the CF projection parameters are there for both backwards compatibility as well as for programs that do not support the WKT form of the projection. > To give WKT precedence, we would have to require all CF-compliant > applications to be able to parse WKT. That's a big expectation, which I think > is unrealistic in practice. I should clarify that in this proposal that `CRS WKT` can remain *optional*. However, when it does exist and your program can read it in, I propose that it should take precedence. As a side note, with the GDAL Barn changes (https://gdalbarn.com/), reading in a WKT is much more practical with PROJ as a dependency. It also provides support for WKT2. Additionally, GDAL can easily support the WKT form of the projection which enables all the dependent software to read in the projection. -- 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-569330268 This list forwards relevant notifications from Github. It is distinct from [email protected], 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 [email protected].
