@davidhassell -- I'm in support of this in concept and would be willing to
moderate the discussion. I will review the PR in detail soon.
Others, please review. Comments on detailed aspects of the PR can be in line,
but please put all general discussion here.
--
You are receiving this because
@dblodgett-usgs Thanks for moderating
--
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/301#issuecomment-696883791
This list forwards relevant notifications from Github.
# Introducing a CF domain variable
# Moderator
TBD
# Moderator Status Review [last updated: -MM-DD]
Brief comment on current status, update periodically
# Requirement Summary
The concept of a domain that describes data locations and cell properties is
not currently mentioned in the CF
See issue #301 for discussion of these changes.
# Release checklist
- [x] Authors updated in `cf-conventions.adoc`?
- [x] Next version in `cf-conventions.adoc` up to date? Versioning inspired by
[SemVer](https://semver.org).
- [ ] `history.adoc` up to date?
- [x] Conformance document up-to-date?
@peterkuma, I share your interest in standardizing the treatment of zero and
negative years. However, I am afraid your use case may not appropriate for
this task. My experience so far is that almost all climate-related obs and
model data sets that might use CF encoding are in the domain of
