New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes from trac 164 discussion #6

Merged
merged 4 commits into from Dec 19, 2017

Conversation

Projects
None yet
3 participants
@twhiteaker
Copy link

twhiteaker commented Dec 13, 2017

See http://cf-trac.llnl.gov/trac/ticket/164

  • Added link from trac ticket to this PR?

Applied via ​cf-convention#115

  • Updated "Revision History"? (Use the date you applied the changes.)
@@ -6,7 +6,7 @@

All CF attributes are listed here except for those that are used to describe grid mappings. See Appendix F for the grid mapping attributes.

The "Type" values are **S** for string, **N** for numeric, and **D** for the type of the data variable. The "Use" values are **G** for global, **C** for variables containing coordinate data, **D** for variables containing non-coordinate data, and **-** for variables with a special purpose. "Links" indicates the location of the attribute"s original definition (first link) and sections where the attribute is discussed in this document (additional links as necessary).
The "Type" values are **S** for string, **N** for numeric, and **D** for the type of the data variable. The "Use" values are **G** for global, **C** for variables containing coordinate data, **D** for variables containing non-coordinate data, **M** for geometry container variables, and **-** for variables with a special purpose. "Links" indicates the location of the attribute"s original definition (first link) and sections where the attribute is discussed in this document (additional links as necessary).

This comment has been minimized.

@davidhassell

davidhassell Dec 14, 2017

I've nothing against it - but why M?

This comment has been minimized.

@dblodgett-usgs

dblodgett-usgs Dec 14, 2017

Owner

I would guess it stands for "Mapping" ? Should we change it to "G" for geometry? Not a big deal either way right?

This comment has been minimized.

@twhiteaker

twhiteaker Dec 14, 2017

G was already taken for "global". I also wanted C for "container" but that was taken for "coordinate data". Then I thought "V" for geometry container Variable but that seemed too generic. So I went with M for geoMetry. I'm not enamored with it and am totally open to suggestions. If we can use two characters, we could do GC.

This comment has been minimized.

@dblodgett-usgs

dblodgett-usgs Dec 19, 2017

Owner

Fine by me!

@dblodgett-usgs dblodgett-usgs merged commit e3276e8 into dblodgett-usgs:master Dec 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment