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/.
#107: CF Data Model 1.7
-----------------------------+------------------------------
Reporter: markh | Owner: cf-conventions@…
Type: task | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
\
\
\
\
\
\
Comment (by biard):
Hi.
I find the phrases "vertical coordinates which are not geolocated" and
"horizontal coordinates which are not geolocated" to be confusing. It
seems to me that the georeference construct is documenting the
geolocation, not creating it. In addition, latitude/longitude coordinate
systems must also be georeferenced. There are, in fact, differences
between the latitude/longitude coordinates defined by different coordinate
reference systems (CRSs). The geographic community has pretty much
unified on global latitude/longitude systems and ellipsoids in recent
times, but you can't make that assumption with older CRSs.
It is possible to define a projected CRS without reference to
latitude/longitude at all. It could be done with a Cartesian CRS such as
Earth Centered Fixed (ECF). All the ones I know of are layered on a
latitude/longitude CRS, but I don't think you should assume layering
implies that a latitude/longitude CRS has special status.
I get the feeling that your effort to put formula_terms and grid_mapping
together in one construct definition may be what's making things awkward.
I'd write more, but I can't get to the CF pages to check on something I
needed to look at in order to proceed. More later.
\
\
\
--
Ticket URL: <http://kitt.llnl.gov/trac/ticket/107#comment:56>
CF Metadata <http://kitt.llnl.gov/>
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.
