<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I Marco, <div><br></div><div>if I understand well, you have 3 dynamic-spectra (each having 6 spectral channels).</div><div>The <a href="http://www.ivoa.net/rdf/product-type#dynamic-spectrum">http://www.ivoa.net/rdf/product-type#dynamic-spectrum</a> data product should applicable. </div><div><br></div><div>In epncore, this should be no problem to describe the spectral axis. Nothing prevents to have sparse spectral axes in the datasets. </div><div><br></div><div>Cheers</div><div>Baptiste</div><div><br><div><br><blockquote type="cite"><div>Le 24 mars 2025 à 09:47, Markus Demleitner via semantics <semantics@ivoa.net> a écrit :</div><br class="Apple-interchange-newline"><div><div>Hi Marco,<br><br>On Fri, Mar 21, 2025 at 06:26:59PM +0100, Molinaro, Marco via semantics wrote:<br><blockquote type="cite">for a "heritage data" project we have a set of observations<br>that consist of time series of nearly monochromatic RHCP & LHCP<br>radio fluxes of the full disk Sun.<br><br>Unfortunately the files they are stored in (FITS bintables)<br>contain:<br>- the 6 individual observational frequencies, sparse from 237Mhz to 2.7GHz<br>- for each of them 3 time series: LHCP, RHCP and the sum of them (full flux)<br><br>This leads us to describe them, no matter if in obscore or epncore,<br>as 6 separate time series records referencing the same FITS dataset,<br>because we are unable to describe the sparse "em" axes.<br></blockquote><br>Well, as long as the time axis is sampled uniformly, there is nothing<br>that would keep you from having just one time series with 18 columns,<br>and I believe clients like SPLAT would do a reasonable job displaying<br>them.<br><br>If the time axis is not sampled uniformly over all frequencies, I<br>think I'd go for per-frequency time series with one column each for<br>the three observation modes.<br><br>All that is based on what I think will make this data easy to work<br>with with generic VO tools, completely independently of the<br>underlying physics and in particular community practice. Therefore:<br><br><blockquote type="cite">Or maybe Radio, HE, TD IGs have some insight on this.<br></blockquote><br>I'd frankly ask Solar System first (and its vice chair already<br>confesses he can't help here). I'd say *if* there's some dominant<br>practice in the community, whatever format that calls for is what I'd<br>serve up by default; and then I'd attach a datalink that yields<br>SDM-compliant tables with Ada blocks (:-)<br><http://ivoa.net/documents/Notes/LightCurveTimeSeries/index.html><br>for interoperability beyond that community.<br><br>Consider this as not much more than my 2 cents, though.<br><br> -- Markus<br><br></div></div></blockquote></div><br></div></body></html>