This message came from the CF Trac system. Do not reply. Instead, enter your
comments in the CF Trac system at http://kitt.llnl.gov/trac/.
#118: Add an attribute in Appendix F to identify the geoid
-----------------------------+------------------------------
Reporter: jonathan | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
\
\
\
\
\
\
Comment (by markh):
I recognise the need for the capability to define vertical datum instances
for vertical coordinates to reference.
Generally a Geoid is used to define a 3D coordinate reference system, not
just the vertical aspect. I assume that in the majority of cases we would
want to define ''altitude'' with respect to a geoid which other
coordinates are already defined with respect to.
* Are there use cases where we need to define altitude with respect to a
datum which other coordinates are not defined with respect to?
* Is it valid OGC-WKT to define a WKT string which only defines a
''VERT_CS''?
Given that we are introducing well known text support for grid_mapping
instances in @CF-1.7, can we just use this mechanism, rather than
producing an additional set of CF geoid names which will require
maintenance by the community?
\
\
\
--
Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/118#comment:4>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
This message came from the CF Trac system. To unsubscribe, without
unsubscribing to the regular cf-metadata list, send a message to
"[email protected]" with "unsubscribe cf-metadata" in the body of your
message.
