Consensus

Roy Williams roy at cacr.caltech.edu
Fri Dec 10 14:10:53 PST 2010


> IVOA is now defining a common understanding of TimeSeries, why should
> this differ from the VOEvent version of the same data-type?


Mike.... Not sure if my earlier message made it, so I will repeat it. I 
think the time series below is not very different from the iVOA common 
understanding ...Roy

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

There is an alternate representation of time series in the VOEvent2 
standard, through the Table element, which is based loosely on the 
VOTable structure. But specifically, it could be used for a time series. 
 From Doug Tody's recent document on representing time series, I have 
taken some utypes, and come up with the following very simple timeseries 
that can be used in VOEvent2 (below).

Cheers
Roy


<Param name="zeropoint"
        utype="CoordSys.TimeFrame.Zero"
        value="51234.0"/>
<Param name="band"
        utype="CoordSys.Band.GenID"
        value="R"/>
<Param name="timeunit"
        utype="Char.TimeAxis.Unit"
        value="day"/>
<Table>
   <Field name="Time"
          utype="Char.TimeAxis.Coverage.Location.Value"
          unit="day"
          ucd="time.epoch"/>
   <Field name="Rmag"
          utype="Data.FluxAxis.Value"
          unit="mag"
          ucd="phot.mag;em.opt.R"/>
   <Data>
     <TR><TD>1.635</TD><TD>16.78</TD></TR>
     <TR><TD>1.934</TD><TD>15.87</TD></TR>
     <TR><TD>3.456</TD><TD>14.99</TD></TR>
   </Data>
</Table>


More information about the voevent mailing list