Hi Aleksander,
Interesting. That is not what I was expecting, so it may be a good idea to make the std_name capture your concept more precisely.
Are you thinking about two instruments on the same platform? different platforms?
If more than one satellite, do they need to be in the same orbit?
If one satellite, does this depend on the scanning pattern and timing, and whether or not one of the instruments gets turned off for a while?
Is this something that will vary with every point in space and time, since sometimes satellite tracks cross before the orbit repeats, and/or scan patterns can change?
Best wishes,
Philip
-----------------------------------------------------------------------
Dr Philip Cameron-Smith, pjc at llnl.gov, Lawrence Livermore National Lab.
-----------------------------------------------------------------------
> -----Original Message-----
> From: CF-metadata [mailto:cf-metadata-bounces at cgd.ucar.edu] On Behalf Of
> Aleksandar Jelenak - NOAA Affiliate
> Sent: Monday, January 14, 2013 9:09 AM
> To: cf-metadata at cgd.ucar.edu
> Subject: Re: [CF-metadata] New Standard Names for Satellite Data
>
> Hello Philip,
>
> On Fri, Jan 11, 2013 at 2:53 PM, Cameron-smith, Philip
> <cameronsmith1 at llnl.gov> wrote:
> >> 5) time_interval
> >> An interval of time.
> >> Units: s
> >
> > Can you clarify what you want for time_interval that cannot be encoded with
> the existing CF?
>
> I want to store time intervals between collocated observations made by two
> satellite instruments. The duration between the collocated obs is important
> property when selecting data for further cal/val analysis.
>
> -Aleksandar
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Received on Mon Jan 14 2013 - 13:34:14 GMT
