Re: [CF-metadata] Temporal nitpicks.

Hi all, NetCDF-Java has no issues with T or no T in an ISO time string. Sean On Friday, September 23, 2016, Ethan Davis wrote: > Hi Chris, > > >> I'm going to venture a guess that the netcdf Java libs can [handle the >> "T"] (anyone know for sure?) > > > Yes, the netCDF-Java

Re: [CF-metadata] Temporal nitpicks.

Hi Chris, > I'm going to venture a guess that the netcdf Java libs can [handle the > "T"] (anyone know for sure?) Yes, the netCDF-Java library can parse date/time strings with the "T". Ethan On Fri, Sep 23, 2016 at 1:26 PM, Chris Barker wrote: > On Thu, Sep 22, 2016

Re: [CF-metadata] Temporal nitpicks.

I totally agree. Don't deprecate anything but definitely encourage ISO 8601:2004(E) with the caveat of requiring an offset-from-Z indicator. Cheers, Ethan On Fri, Sep 23, 2016 at 9:38 AM, Bob Simons - NOAA Federal < bob.sim...@noaa.gov> wrote: > Seth McGinnis said: > "I hesitate to support

[CF-metadata] Temporal nitpicks.

Seth McGinnis said: "I hesitate to support encouraging the use of the T because in my experience, approximately 0% of existing NetCDF files have it." a) We aren't advocating forbidding the older formats / saying that files with those time formats will become invalid. This is a question of what we

Re: [CF-metadata] Temporal nitpicks.

...@cgd.ucar.edu>> on behalf of Bob Simons - >> NOAA Federal <bob.sim...@noaa.gov <mailto:bob.sim...@noaa.gov>> >> Date: Thursday, September 22, 2016 at 2:14 PM >> To: CF Metadata <cf-metadata@cgd.ucar.edu >><mailto:cf-metadata@cgd.ucar.edu>> >

Re: [CF-metadata] Temporal nitpicks.

ta <cf-metadata@cgd.ucar.edu <mailto:cf-metadata@cgd.ucar.edu>> > Subject: Re: [CF-metadata] Temporal nitpicks. > > I vote to encourage the use of the T between date and time. > * The T is the official method to connect the date and the time in the > various ISO 8601 sta

Re: [CF-metadata] Temporal nitpicks.

I hesitate to support encouraging the use of the T because in my experience, approximately 0% of existing NetCDF files have it. There is benefit in encouraging alignment with a separate standard, but it comes at the cost of increasing the amount of disagreement in the set of all CF-compliant

Re: [CF-metadata] Temporal nitpicks.

<mailto:bob.sim...@noaa.gov>> Date: Thursday, September 22, 2016 at 2:14 PM To: CF Metadata <cf-metadata@cgd.ucar.edu<mailto:cf-metadata@cgd.ucar.edu>> Subject: Re: [CF-metadata] Temporal nitpicks. I vote to encourage the use of the T between date and time. * The T is the

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

f-metadata@cgd.ucar.edu<mailto:cf-metadata@cgd.ucar.edu>> Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3 I think #1 is a great idea as it has been a practice in a number of satellite missions. #2 I am not too fond of. Best practice says that wh

Re: [CF-metadata] Temporal nitpicks.

+1 for the "T" in the time string. On Thu, Sep 22, 2016 at 3:14 PM, Bob Simons - NOAA Federal < bob.sim...@noaa.gov> wrote: > I vote to encourage the use of the T between date and time. > * The T is the official method to connect the date and the time in the > various ISO 8601 standards, notably

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

ading.ac.uk<mailto:j.m.greg...@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] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

On Thu, Sep 22, 2016 at 12:06 PM, Jim Biard wrote: > So I went and dug into the source code for UDUNITS and UDUNITS-2. Both > versions of UDUNITS allow a wide variety of epoch date/time formulations > with and without space delimiters between just about any of the components,

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

On Thu, Sep 22, 2016 at 9:45 AM, Chris Barker wrote: > I think UDUnits does not use a T but maybe it will accept it. > UDUNITS accepts the "T" and can print it. Regards, Steve Emmerson ___ CF-metadata mailing list

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

; > > To: Nan Galbraith <ngalbra...@whoi.edu> > > CC: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu> > > Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, > Vol > > 161, Issue 3 > > > > On Tue, Sep 20, 2016 at 5:4

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

Chris Barker <chris.bar...@noaa.gov> > To: Nan Galbraith <ngalbra...@whoi.edu> > CC: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu> > Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol > 161, Issue 3 > > On Tue, S

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

: CF-metadata <cf-metadata-boun...@cgd.ucar.edu> on behalf of Chris Barker <chris.bar...@noaa.gov> Sent: 21 September 2016 20:52 To: Nan Galbraith Cc: cf-metadata@cgd.ucar.edu Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3 On Tue, Sep 20, 201

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

On Tue, Sep 20, 2016 at 5:45 AM, Nan Galbraith wrote: > Can we recommend the use of ISO-compatible date strings, with > the caveat that time zone should always be included? > Yes, we really should do that (though it's an offset that is specified, not a time zone) It's

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

Just FYI, the UDUNITS-2 package accepts ISO 8601-compliant timestamps like the following: 2016-01-01T05:04:03-0600 2016-01-01T05:04:03Z Regards, Steve Emmerson ___ CF-metadata mailing list CF-metadata@cgd.ucar.edu

Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

Chris, That's a completely valid suggestion. We have to consider implications for backwards compatibility. Among other things, UDUNITS would need to change their convention, since CF follows UDUNITS in this matter, as with all other units. There's nothing that says we can't make changes. I

[CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161, Issue 3

Jim and Chris B, I would like to weigh in here, please? Adhering to UDUnits has merits, but once one adopts ISO8601-like notations, as there is no way of specifying otherwise, people assume it *is* ISO8601 and therefore a string without a time zone marker indicates local time (whatever that