<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1">Will anybody from IVOA attend the Planetary Data
Workshop?</font></p>
<p><font size="+1">
<a class="moz-txt-link-freetext" href="https://www.hou.usra.edu/meetings/planetdata2019/">https://www.hou.usra.edu/meetings/planetdata2019/</a></font></p>
<p><font size="+1">Both groups would benefit!</font></p>
<p><font size="+1">Rob</font></p>
<p><font size="+1">PS - if this reply is held for moderation, could
somebody please add my LPL email to the SSIG?</font></p>
<p><font size="+1">Thanks!<br>
</font></p>
<p><font size="+1">--</font><br>
</p>
<div class="moz-cite-prefix">On 2/12/19 4:12 AM, Pierre Fernique
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5d43bcf3-e2b7-583d-0007-6b1d01d5d070@astro.unistra.fr">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p><br>
</p>
<p>Dear Ssig, Apps and VESPA members<br>
</p>
<p>As you probably saw, we have more and more Solar System
resources available in the VO.<br>
This is a really good news (notably hanks to Europlanet effort)<br>
</p>
<p>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 :</p>
<ol>
<li>How to build correctly the data discovery tree ? Concretely,
how to move the good TAP, CS and other services to the Solar
System branch ?</li>
<li>How to handle the incompatible projections (sky resources
over planets, or the opposite, or Mars data over Io, etc...) ?</li>
</ol>
<p>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.<br>
</p>
<p>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.</p>
<p><b>So the question : How to characterize Solar System resources
in the VO ? </b><br>
</p>
<ol>
<li>For the VO registry, do we have to invent a dedicated field
such as <obsbody>mars</obsbody> ?</li>
<li>For TAP tables, how to specify that this table concerns this
body, or the sky ?</li>
<li>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 ?<br>
</li>
</ol>
<p>Reactions ? Suggestions ? Do we have time to discuss this point
during Paris Interop ?<br>
Cheers<br>
Pierre Fernique<br>
</p>
<p><br>
</p>
<p><img src="cid:part1.59D38F0B.4FF07ABC@lpl.arizona.edu" alt=""
class=""></p>
</blockquote>
</body>
</html>