Re: [CF-metadata] Handling time when date is "missing"

Jay, You could use the variable time as a single value to establish the time (in complete CF date format) of the first observation Another multi dimension array can then be used to store the time offset (in hours or seconds etc.) of each measurement from variable time Or else convert the

Re: [CF-metadata] Temporal nitpicks.

less human readable) On 9/22/16, 3:43 PM, "CF-metadata on behalf of Seth McGinnis" <cf-metadata-boun...@cgd.ucar.edu on behalf of mcgin...@ucar.edu> wrote: >I have to disagree. Personally, I find the T a lot less readable than >separating them with a space. > >On 9/22/16 4

Re: [CF-metadata] Temporal nitpicks.

Just making the time stamp more human readable is important so I too am in favor of a ’T’ to separate the date and time ! From: CF-metadata > on behalf of Bob Simons - NOAA Federal

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

Sorry I misspoke. A ‘Z’ is required to identify the ISO8601 time stamp as GMT time. So I do agree with point #2 below….but adding a ‘Z’ seems to break the CF convention up to this point. From: JPL > Date: Thursday,

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 when offset is not specified implicitly GMT must be assumed. So I think specifying a ‘Z’ in ISO time stamp is only necessary when specifying a non zero