Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread John Caron
On 10/22/2010 9:46 AM, Julia Collins wrote: Hello, Benno's comment provides a convenient entry point for me to describe a recent problem. On Fri, 22 Oct 2010, Benno Blumenthal wrote: Note: if the time zone is omitted the default is UTC, and if both time and time zone are omitted the default is

Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread John Graybeal
I can't imagine this change having any traction for the coordinate variable of time, as some of the answers show. However, if one thinks about non-coordinate variables, standard_names of local_time and sidereal_time seem arguably useful. Even allowing for Roy's perfectly valid arguments agai

Re: [CF-metadata] time as ISO strings

2010-10-22 Thread Jeff deLaBeaujardiere
Hello- I don't think I have any standing to vote on CF matters, but I just wanted to say that I quite agree with Steve Hankin's viewpoint. I personally like ISO8601 date/time strings for text display, but agree that under-the-hood encodings such as CF "days since T" or Unix "seconds since the

Re: [CF-metadata] time as ISO strings

2010-10-22 Thread Seth McGinnis
I agree completely. Using ISO date strings as an encoding for time coordinates sounds terrible to me, doubly so if you consider that they would have to be not-quite-ISO in order to accommodate non-Gregorian calendars. That said, I also agree that it would be great if netcdf tools all knew how to

Re: [CF-metadata] Interpretation of unspecified time zone (was: New standard names for satellite obs data (timeas ISO strings))

2010-10-22 Thread Lowry, Roy K
Hi again, I must admit that your data is very different to the types of data I work with and I don't fully understand issues with composite images. Typical data for me are time series where a series of parameters, including position are logged every 30 seconds or so as a ship sails along. Year

Re: [CF-metadata] Interpretation of unspecified time zone (was: New standard names for satellite obs data (timeas ISO strings))

2010-10-22 Thread Benno Blumenthal
It is not really a problem to represent this in CF, just less than pretty. time becomes a function of more than one dimension. So, if by "local time" you mean that time is such that noon local time has the sun directly overhead, i.e. local time before the railroads established time zones, then we

Re: [CF-metadata] Interpretation of unspecified time zone (was: New standard names for satellite obs data (timeas ISO strings))

2010-10-22 Thread Julia Collins
Hi, On Fri, 22 Oct 2010, Lowry, Roy K wrote: I wonder how many existing CF data files would have the meaning of their time channel changed were this suggestion to be adopted. I am sure many. In some cases it might even make them accurate. :-) At some level, it's a tradeoff between "breaking" e

Re: [CF-metadata] point observation data in CF 1.4

2010-10-22 Thread Christopher Barker
On 10/18/10 1:32 AM, Bryan Lawrence wrote: That's the narrow technical perspective. The "social" question is whether there is a significant benefit to the community from defining is a single approach that is general enough to handle the necessary range of model-generated tracer particle clouds.

Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread Lowry, Roy K
Dear All, I wonder how many existing CF data files would have the meaning of their time channel changed were this suggestion to be adopted. If I were Julia I would be reworking my data so that the time channel was true UT. I've had so many problems in the past with local time co-ordinates.

Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread Julia Collins
Hello, Benno's comment provides a convenient entry point for me to describe a recent problem. On Fri, 22 Oct 2010, Benno Blumenthal wrote: Note: if the time zone is omitted the default is UTC, and if both time and time zone are omitted the default is 00:00:00 UTC. To clarify, this is the time

Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread Benno Blumenthal
On Fri, Oct 22, 2010 at 6:27 AM, Jon Blower wrote: > Hi Roy, > > Yes, but *only* if the ISO string contains time information.  If it only > contains a date (e.g. "2009-09-01") you can't add a time zone as I understand > it.  Furthermore, there's no default to UTC - in fact the default is local

Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread Lowry, Roy K
Sorry, didn't read your original message thoroughly enough. Must stop doing e-mail before waking up properly. Cheers, Roy. -Original Message- From: Jon Blower [mailto:j.d.blo...@reading.ac.uk] Sent: 22 October 2010 11:28 To: Lowry, Roy K Cc: cf-metadata@cgd.ucar.edu Subject: RE: [CF-m

Re: [CF-metadata] New standard names for satellite obs data (timeas ISO strings)

2010-10-22 Thread Jon Blower
Hi Roy, Yes, but *only* if the ISO string contains time information. If it only contains a date (e.g. "2009-09-01") you can't add a time zone as I understand it. Furthermore, there's no default to UTC - in fact the default is local time. (And I'm not sure your syntax is right - I think you us

Re: [CF-metadata] New standard names for satellite obs data (time as ISO strings)

2010-10-22 Thread Lowry, Roy K
Hi Jon, Full ISO8601 does carry time zone expressed in hours relative to UT in the syntax Zx where x is the offset from Zulu at the right-hand end of the string. Cheers, Roy. -Original Message- From: cf-metadata-boun...@cgd.ucar.edu [mailto:cf-metadata-boun...@cgd.ucar.edu] On Behalf