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 - Solar? Mean Solar? Sidereal? National legal?)

There is work just starting in the OGC/ISO pipeline on how to indicate a 
non-Gregorian calendar using ISO8601 like notation, for the WKT communities.

Personally, I would advocate ISO8601 strict adherence, as most of the 
recommended best practices and profiles, such as RFC3339, are generally strict 
subsets of ISO 8601.

Chris 


-----Original Message-----
From: CF-metadata [mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf Of 
cf-metadata-requ...@cgd.ucar.edu
Sent: Wednesday, September 14, 2016 10:02 PM
To: cf-metadata@cgd.ucar.edu
Subject: CF-metadata Digest, Vol 161, Issue 3

Send CF-metadata mailing list submissions to
        cf-metadata@cgd.ucar.edu

To subscribe or unsubscribe via the World Wide Web, visit
        http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
or, via email, send a message with subject or body 'help' to
        cf-metadata-requ...@cgd.ucar.edu

You can reach the person managing the list at
        cf-metadata-ow...@cgd.ucar.edu

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of CF-metadata digest..."


Today's Topics:

   1. nitpick in time axes example (Chris Barker)
   2. Re: nitpick in time axes example (Jim Biard)


----------------------------------------------------------------------

Message: 1
Date: Wed, 14 Sep 2016 12:34:11 -0700
From: Chris Barker <chris.bar...@noaa.gov>
To: "cf-metadata@cgd.ucar.edu" <cf-metadata@cgd.ucar.edu>
Subject: [CF-metadata] nitpick in time axes example
Message-ID:
        <CALGmxE+S80kd1CnD-55btZZhz=vko-bbbps-bv2w2a-bu0w...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I see in teh doc:

Example 4.4. Time axis

double time(time) ;
  time:long_name = "time" ;
  time:units = "days since 1990-1-1 0:0:0" ;

IIUC, ISO 8601 requires two digits for the time pieces [1], so that should
be:

"days since 1990-1-1 00:00:00"


The parser I use isn't picky about this, but maybe some are?

BTW, as it's an example, we should probably throw a time offset on there,
too:

"days since 1990-1-1 00:00:00Z"


or

"days since 1990-1-1 00:00:00+00:00"


[1] at least according to wikipedia:
https://en.wikipedia.org/wiki/ISO_8601#Times


-Chris


-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

chris.bar...@noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20160914/614bb5f3/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 14 Sep 2016 17:01:34 -0400
From: Jim Biard <jbi...@cicsnc.org>
To: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] nitpick in time axes example
Message-ID: <88f473d3-243e-0219-cfa8-ac975f510...@cicsnc.org>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Chris,

CF has consistently maintained adherence to the UDUNITS definition for the 
reference time string, and that is different from ISO. (See CF Section 4.4
<http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#time-coordinate>)
As stated at the top of the section, Z is not used in the case of UTC and there 
is a space before any time zone offset. Example 4.4 is written that way 
specifically to make it clear that single-digit numbers are legal.

Grace and peace,

Jim


On 9/14/16 3:34 PM, Chris Barker wrote:
> I see in teh doc:
>
> Example 4.4. Time axis
> double time(time) ;
>    time:long_name = "time" ;
>    time:units = "days since 1990-1-1 0:0:0" ; IIUC, ISO 8601 requires 
> two digits for the time pieces [1], so that should be:
>
> "days since 1990-1-1 00:00:00"
>
> The parser I use isn't picky about this, but maybe some are?
>
> BTW, as it's an example, we should probably throw a time offset on 
> there, too:
>
> "days since 1990-1-1 00:00:00Z"
>
> or
>
> "days since 1990-1-1 00:00:00+00:00"
>
> [1] at least according to wikipedia: 
> https://en.wikipedia.org/wiki/ISO_8601#Times
>
>
> -Chris
>
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> chris.bar...@noaa.gov <mailto:chris.bar...@noaa.gov>
>
>
> _______________________________________________
> CF-metadata mailing list
> CF-metadata@cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

--
CICS-NC <http://www.cicsnc.org/> Visit us on
Facebook <http://www.facebook.com/cicsnc>       *Jim Biard*
*Research Scholar*
Cooperative Institute for Climate and Satellites NC <http://cicsnc.org/> North 
Carolina State University <http://ncsu.edu/> NOAA National Centers for 
Environmental Information <http://ncdc.noaa.gov/> /formerly NOAA?s National 
Climatic Data Center/
151 Patton Ave, Asheville, NC 28801
e: jbi...@cicsnc.org <mailto:jbi...@cicsnc.org>
o: +1 828 271 4900

/Connect with us on Facebook for climate 
<https://www.facebook.com/NOAANCEIclimate> and ocean and geophysics 
<https://www.facebook.com/NOAANCEIoceangeo> information, and follow us on 
Twitter at @NOAANCEIclimate <https://twitter.com/NOAANCEIclimate> and 
@NOAANCEIocngeo <https://twitter.com/NOAANCEIocngeo>. /


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20160914/8af43717/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CicsLogoTiny.png
Type: image/png
Size: 15784 bytes
Desc: not available
URL: 
<http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20160914/8af43717/attachment.png>

------------------------------

Subject: Digest Footer

_______________________________________________
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata


------------------------------

End of CF-metadata Digest, Vol 161, Issue 3
*******************************************
_______________________________________________
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

Reply via email to