Re: [CF-metadata] Add new integer types to CF?

It is I who is tired :) I recant the part about packed data. There may be reasons to keep it in a signed variable, but ability to pack negative numbers is not one. Thanks for thinking that through, MJ.Charlie--Charlie Zender, Earth System Sci. & Computer Sci.University of California, Irvine

Re: [CF-metadata] Add new integer types to CF?

Charlie, your unsigned proposal change looks good to me, except for one question. I must be very tired right now, but I don't understand why you are suggesting the prohibition on unsigned types for packed data: "Use of unsigned types to hold packed data is not permitted since they are

[CF-metadata] Add new integer types to CF?

People, CF explicitly supports types char, byte, short, int, float, and double. There are five "new" numeric types it could support: unsigned byte, unsigned short, unsigned int, int64, and unsigned int64. These new types are in netCDF3 (in the CDF5 encoding released in netCDF v. 4.4.0) and in

Re: [CF-metadata] grid cells with a varying number of cell bounds

The relevant section of the UGRID conventions seems consistent with this (except _FillValue is suggested). It goes on to say "...we may use in the future a ragged array, but here

Re: [CF-metadata] grid cells with a varying number of cell bounds

Hello Karl, Jonathan, Jim, I also support Karl's suggested changes, with the possible exception of insisting that the valid bounds values always precede the any missing data. Whilst that is surely the easiest case for software to deal with, and is an attractive restriction to me, it that may not

[CF-metadata] grid cells with a varying number of cell bounds

Dear Karl I agree, other views are needed; it would be especially useful to hear from Dave Blodgett and other proposers of the simple geometries. Although I agree that what you describe is not necessarily inefficient (and in the case you mention it would be more efficient than the simple

Re: [CF-metadata] grid cells with a varying number of cell bounds

Karl, I agree with you. I don't see a problem with the existing convention being tweaked to state that fewer vertices for a cell are indicated by missing values in the last elements. Jim [image: CICS-NC] Visit us on Facebook *Jim Biard*

Re: [CF-metadata] grid cells with a varying number of cell bounds

Dear Jonathan and all, Regarding the options for representing polygon cells with varying number of sides (see below), I agree that the "simple geometries" proposal can indeed handle this case. ( It of course could also handle the case when all grid cells have the same number of sides.) I

[CF-metadata] CF Conventions 1.7 is released

Dear Jeff Thanks for the announcement and for your own great and painstaking efforts over producing CF 1.7. It's great to have a new version at last. CF 1.6 was published in Dec 2011! When we changed to the new method of managing the document, we also agreed that in future we would have