best practice.
-CHB
> From: JPL
> Date: Thursday, September 22, 2016 at 2:13 PM
> To: Chris Barker , Jonathan Gregory <
> j.m.greg...@reading.ac.uk>
>
> Cc: "cf-metadata@cgd.ucar.edu"
> Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Diges
PM
To: Chris Barker mailto:chris.bar...@noaa.gov>>,
Jonathan Gregory mailto:j.m.greg...@reading.ac.uk>>
Cc: "cf-metadata@cgd.ucar.edu<mailto:cf-metadata@cgd.ucar.edu>"
mailto:cf-metadata@cgd.ucar.edu>>
Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Di
o:cf-metadata@cgd.ucar.edu>"
mailto:cf-metadata@cgd.ucar.edu>>
Subject: Re: [CF-metadata] Temporal nitpicks. Was: CF-metadata Digest, Vol 161,
Issue 3
On Thu, Sep 22, 2016 at 5:53 AM, Jonathan Gregory
mailto:j.m.greg...@reading.ac.uk>> wrote:
Dear Chris et al.
I may have missed it - ar
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,
> with and without l
Hi.
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, with and without leading zeros, with and without a 'T'
between the da
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
CF-metadata@cgd.ucar.edu
http://mail
- no idea about any other
parsing libs.
-CHB
> Best wishes and thanks
>
> Jonathan
>
> - Forwarded message from Chris Barker -
>
> > Date: Wed, 21 Sep 2016 12:52:48 -0700
> > From: Chris Barker
> > To: Nan Galbraith
> > CC: "cf-metadata@cgd.uca
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, 2016 at 5:45 AM, Nan Galbraith wrote:
>
> > Can we recommend the use of ISO-compatible date strings
___
From: CF-metadata on behalf of Chris Barker
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, 2016 at 5:45 AM, Nan Galbraith
mailto:ngalbra...@whoi
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 unfortunate that ISO defau
Can we recommend the use of ISO-compatible date strings, with
the caveat that time zone should always be included?
It's unfortunate that ISO defaults to local time, and that seems to be
non-negotiable.
This is what we use in the OceanSITES implementation of CF. Obviously,
it won't solve everyon
On Thu, Sep 15, 2016 at 5:40 AM, Jim Biard wrote:
> 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.
>
As l
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
http://mailman.cgd.ucar.edu/mailman/l
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
wa
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 is
15 matches
Mail list logo
