Solar System resources in the VO

Rob Seaman seaman at lpl.arizona.edu
Tue Feb 12 14:04:43 CET 2019


Will anybody from IVOA attend the Planetary Data Workshop?

    https://www.hou.usra.edu/meetings/planetdata2019/

Both groups would benefit!

Rob

PS - if this reply is held for moderation, could somebody please add my
LPL email to the SSIG?

Thanks!

--

On 2/12/19 4:12 AM, Pierre Fernique wrote:
>
>
> Dear Ssig, Apps and VESPA members
>
> As you probably saw, we have more and more Solar System resources
> available in the VO.
> This is a really good news (notably hanks to Europlanet effort)
>
> But for client point of view, and notably Aladin, it is more and more
> difficult to display and use correctly these new resources as there is
> presently no standard way to specify the celestial body concerned by
> each of these resources. Actually, in Aladin, we are face to two issues :
>
>  1. How to build correctly the data discovery tree ? Concretely, how
>     to move the good TAP, CS and other services to the Solar System
>     branch ?
>  2. How to handle the incompatible projections (sky resources over
>     planets, or the opposite, or Mars data over Io, etc...) ?
>
> I progressed a little. For the first point, I made a very bad hack
> based on the ivoid. We're lucky, most solar system resources use
> EPN-core + DACHS server... and DACHS automatically uses an ivoid
> containing the substring "/epn". By magic, 35 resources are now placed
> in the Solar System branch. I also had to manually add 3 others
> resources ( jacobsuni/tap, pvol/tap and  vo-plasma.oeaw.ac.at/tap).
> The result is not bad (see below) but this method is clearly
> debatable. And there is no distinction between planets.
>
> For the second point, I have not found a solution. Only Solar System
> HiPS maps have a dedicated keyword for each body. But  as it is not
> the case for other resources of the Solar System, I can not presently
> use this keyword.
>
> *So the question : How to characterize Solar System resources in the
> VO ? *
>
>  1. For the VO registry, do we have to invent a dedicated field such
>     as <obsbody>mars</obsbody> ?
>  2. For TAP tables, how to specify that this table concerns this body,
>     or the sky ?
>  3. How to handle the list of celestial bodies ? Do we have to provide
>     a list (mercury, venus, earth, moon, mars, io,...) somewhere in
>     the VO ?
>
> Reactions ? Suggestions ? Do we have time to discuss this point during
> Paris Interop ?
> Cheers
> Pierre Fernique
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20190212/71927f24/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cgpjigkioblcbnll.png
Type: image/png
Size: 721130 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20190212/71927f24/attachment-0001.png>


More information about the apps mailing list