On Thu, 20 Jul 2006, Mark Taylor wrote:
> 2. The UCDs in the Vizier table are in what are syntactically
> comment lines according to SSN/75, so it looks to me like this
> is human-readable-only metadata. It may in fact be
> cds-readable, but I don't know if the relevant format is
> documented, or whether it's a good idea to support it.
>
but they are parseable and easy to spot. Does Aladin make use of this
information? Maybe CDS should be contacted to see whether this is an
extension that they are intending to provide to allow tools such as TOPCAT
to use a wider set of data.
[it would be trivial to add support for the retrieval part as well given
a skycat.cfg file]
> I should think the best thing for me to do (at least in the first
> instance) is to provide TST support which matches the variant(s)
> that GAIA uses/understands. Peter, is that defined by SSN/75.1
> including CURSA extensions, or is there some other reference
> I should work from?
>
Presumably GAIA is controlled by the TST format expected by SkyCat itself
as implemented by ESO so if we start extracting UCDs from the TST files we
may need to patch SkyCat - it sounds like ESO are accepting patches again.
(and maybe also by the JSky TST classes - yes the ESO Jsky code already
does all the retrieval and TST parsing but probably won't handle UCDs at
the moment)
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|