Re: [CF-metadata] Pre-proposal for "charset"

; a netCDF file, with no interest in CF, you wouldn't know that it was an >> array >> of strings, but if you are using it as a CF aux coord var, you do know >> that, >> so I don't think any further signal is needed - it would be redundant. >> >> Best wish

Re: [CF-metadata] Pre-proposal for "charset"

reg...@reading.ac.uk>> > CC: "cf-metadata@cgd.ucar.edu <mailto:cf-metadata@cgd.ucar.edu>" <cf-metadata@cgd.ucar.edu <mailto:cf-metadata@cgd.ucar.edu>> > Subject: Re: [CF-metadata] Pre-proposal for "charset" > > On Mon, Mar 6, 2017

Re: [CF-metadata] Pre-proposal for "charset"

sage from Chris Barker <chris.bar...@noaa.gov> - > Date: Mon, 6 Mar 2017 11:16:35 -0800 > From: Chris Barker <chris.bar...@noaa.gov> > To: Jonathan Gregory <j.m.greg...@reading.ac.uk> > CC: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu> > Subje

Re: [CF-metadata] Pre-proposal for "charset"

On Mon, Mar 6, 2017 at 9:47 AM, Jonathan Gregory wrote: > Yes, we can reopen the ticket. I think the _Encoding for char is a good > idea, > especially if it's an NUG convention. so let's do that part at least. > Are there any files out in the wild that DO use ND

Re: [CF-metadata] Pre-proposal for "charset"

From: Chris Barker <chris.bar...@noaa.gov> > To: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu> > Subject: Re: [CF-metadata] Pre-proposal for "charset" > > Hi all, > > I tried to post this note last week, in response to the TRAC ticket, but it >

Re: [CF-metadata] Pre-proposal for "charset"

Hi all, I tried to post this note last week, in response to the TRAC ticket, but it doesn't seem to have gone through. Sorry if this is a repeat. Note that it seems Bob has lost momentum on this one, and closed the ticket. However, the fact that the OP is dropping out doesn't mean it's still not

Re: [CF-metadata] Pre-proposal for "charset"

On Tue, Feb 28, 2017 at 12:30 PM, Jonathan Gregory < j.m.greg...@reading.ac.uk> wrote: > > I wasn't clear -- even if you know a CHAR array is supposed to be an > array > > For string-valued auxiliary coordinate variables (CF section 6.1) it's > explicitly stated that the trailing dimension in CDL

Re: [CF-metadata] Pre-proposal for "charset"

Dear Chris and Bob > I wasn't clear -- even if you know a CHAR array is supposed to be an array > of strings, you don't know which dimension is the "string" dimension, and > which is the array dimension. If you have a 3x4 array of length-5 strings, > what is your CHAR array dimension? either of

Re: [CF-metadata] Pre-proposal for "charset"

CF section 2.2 already clarifies that it is the "last" (AKA "rightmost") dimension that specifies the maximum number of characters and is collapsed to interpret the char array as a String array: > > An n-dimensional array of strings must be implemented as a character array > of dimension

[CF-metadata] Pre-proposal for "charset"

Federal <bob.sim...@noaa.gov> - > Date: Sat, 25 Feb 2017 08:16:57 -0800 > From: Bob Simons - NOAA Federal <bob.sim...@noaa.gov> > To: CF Metadata <cf-metadata@cgd.ucar.edu> > Subject: [CF-metadata] Pre-proposal for "charset" > > Jonathan a

[CF-metadata] Pre-proposal for "charset"

cf-metadata@cgd.ucar.edu > Subject: [CF-metadata] Pre-proposal for "charset" > Message-ID: <20170223162252.ga7...@met.reading.ac.uk> > Content-Type: text/plain; charset=us-ascii > > Dear Bob > > > CF section 9.5 says: "The variable carrying the cf_ro

Re: [CF-metadata] Pre-proposal for "charset"

gt; > To: Jonathan Gregory <j.m.greg...@reading.ac.uk> > CC: CF Metadata <cf-metadata@cgd.ucar.edu> > Subject: Re: [CF-metadata] Pre-proposal for "charset" > > Hello, > > I think that Jonathan is right about the CF-compliance of the example DSG > file. I t

[CF-metadata] Pre-proposal for "charset"

Dear Bob > CF section 9.5 says: "The variable carrying the cf_role attribute may > have any data type." > And that makes sense, because some profile_id might be an integer and > theoretically could be a single char. > >> Yes, I agree that on the basis of netCDF >> alone >> you can't tell whether

Re: [CF-metadata] Pre-proposal for "charset"

On Wed, Feb 22, 2017 at 10:56 AM, Chris Barker wrote: > > Another note: > > On Mon, Feb 6, 2017 at 3:08 PM, Bob Simons - NOAA Federal < > bob.sim...@noaa.gov> wrote: > >> * "HTML" - the chars are to be interpreted as an array of Strings with >> HTML content, using the

Re: [CF-metadata] Pre-proposal for "charset"

On Wed, Feb 22, 2017 at 10:38 AM, Bob Simons - NOAA Federal < bob.sim...@noaa.gov> wrote: > As for needing a different subject for the email: I'm lumping together 2 > new related attribute names: "charset=..." and "data_type=string|char" so > that the information stored in char variables in

Re: [CF-metadata] Pre-proposal for "charset"

Another note: On Mon, Feb 6, 2017 at 3:08 PM, Bob Simons - NOAA Federal < bob.sim...@noaa.gov> wrote: > * "HTML" - the chars are to be interpreted as an array of Strings with > HTML content, using the ISO-8859-1 charset. Non-ISO-8859-1 must be encoded > using the

Re: [CF-metadata] Pre-proposal for "charset"

..@reading.ac.uk> > To: cf-metadata@cgd.ucar.edu > Subject: Re: [CF-metadata] Pre-proposal for "charset" > Message-ID: <20170222181546.gd8...@met.reading.ac.uk> > Content-Type: text/plain; charset=us-ascii > > Dear Bob > > Thnaks for the helpful example. Yes, I

Re: [CF-metadata] Pre-proposal for "charset"

As for needing a different subject for the email: I'm lumping together 2 new related attribute names: "charset=..." and "data_type=string|char" so that the information stored in char variables in netcdf-3 files can be easily and unambiguously interpreted. You are correct. My proposal is for

Re: [CF-metadata] Pre-proposal for "charset"

imons - NOAA Federal <bob.sim...@noaa.gov> > To: CF Metadata <cf-metadata@cgd.ucar.edu> > Subject: Re: [CF-metadata] Pre-proposal for "charset" > > You requested a sample file which demonstrates the need for a "data_type" > attribute for char va

Re: [CF-metadata] Pre-proposal for "charset"

<bob.sim...@noaa.gov> - > Date: Wed, 8 Feb 2017 10:00:32 -0800 > From: Bob Simons - NOAA Federal <bob.sim...@noaa.gov> > To: CF Metadata <CF-metadata@cgd.ucar.edu> > Subject: Re: [CF-metadata] Pre-proposal for "charset" > > I think my original

Re: [CF-metadata] Pre-proposal for "charset"

I think my original pre-proposal has a significant flaw and needs to be revised. The problem is: charset needs to be specifiable for all char arrays, regardless of whether the values should be interpreted as Strings or individual chars. I see two basic solutions: 1) Two attributes, but a given