I agree that it would be a good idea to add such an example. Thanks.
--
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/249#issuecomment-593550945
This list forwards
For horizontal coordinates, the CF `axis` attribute should be used to indicate
which axis is `X` and which `Y`, where `X` is "like" longitude and `Y` "like"
latitude. This correspondence can't really be more than a rough guide, for
reasons mentioned above. Doesn't the `axis` attribute meet the
I think that is all I have to offer for clarifying information on this issue. I
will close it now since it seems that :-1: is the consensus here on the
proposal.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #248.
--
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/248#event-3088905534
This list forwards relevant notifications from Github. It is distinct from
@ethanrd I like your verbiage. I think you could simplify it a bit by saying
In many situations, any integer type may be used.
When the phrase "integer type" is used in this document, it should be
understood to mean **`byte`**, **`unsigned byte`**, **`short`**, **`unsigned
short`**, **`int`**,
As far as the temporal axis goes, CF is quite strongly "future positive". It
would take a lot of work to change this. I expect that the paleoclimate people
would appreciate the ability to do "past positive" time coordinates that would
use a (currently non-existent) calendar appropriate to their
@snowman2 I am generally opposed to this proposal as it stands.
If we want to adopt some sort of convention about this sort of thing, I suggest
it be something like what I've written below.
For spatial coordinate systems, add an attribute named "fluffy" (this is a
placeholder name — I'm unable
@snowman2 It seems pretty clear that this is a UDUNITS issue, not a CF issue.
--
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/248#issuecomment-593486026
This list
@semmerson, you can go to http://www.epsg-registry.org/ and filter by the unit
of measure type. For example:
--
You are receiving this because you are subscribed to this thread.
@martinjuckes The NUG section does not make statements that take the form of
requirements. It is a subtle and strange component of English language usage in
standards and requirements documents. There are quite specific meanings applied
to certain words. They are:
* shall - It must be done or
@snowman2,
I'm the UDUNITS developer.
I've never heard of these units. Do you have a reference for them (other than
the GitHub repository)?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
# Title
Example for Independent Latitude, Longitude, Non-spatiotemporal Variable, and
Time Axes
# Moderator
@GeyerB
# Moderator Status Review [last updated: 20/03/02]
no update yet
# Requirement Summary
Analogue to chapter `5.1. Independent Latitude, Longitude, Vertical, and Time
Axes`, where
12 matches
Mail list logo
