The goal of this document is to define the requirements to provide an access to VESPA in several data analysis and visualization tools (AMDA, 3DView, CASSIS, etc), i.e. the VESPA clients. These clients will use a generic library to handle the basic aspects of the EPN-TAP protocol. This library is specified in Specification Document (in progress) . The following paragraphs are dedicated to the implementation in each tool.



According to 4 - EPN-TAP queries

scene = dataproduct_type=sp (spectrum)  [ AND Spectral Range [AND   Target Name AND/OR Time Range Spectral Range AND/OR  Species]]

It is important to notice that CASSIS can  only read the spectrum data.

The scene depends on metadatas found in spectra already displayed.

If there is no spectrum  displayed, then there is no scene.

But the user can specify one or several parameters described before
The return of the query should be  all the url of the spectra selected



scene => target + time interval
or scene => target + time interval + surface area on target

Access to VESPA could be provided through a window called "Remote Data (VESPA)" similar to "Remote Data (IMPEx)". This would open the VESPA window in 3DView with "target_name", "target_class" and "time interval" already selected. It must be possible to modify (extend or shorten) the time interval.

It must be possible to query with restrictions regarding the surface of objects (latitude/longitude on a planet). To be used with "2D Polar view" and Mercator maps. On such maps it should be feasible to define a rectangular region (lon/lat) which could feed into the "location" parameters of the TAP request 

A warning message must be generated when the user tries to open the VESPA window before the selection of a scene.


scenario #1 : scene => target + time interval

Data from one or more instruments on one or more spacraft over a time interval are plotted. From the "plot" window, a button allows to open a VESPA window. The left part of the window is dedicated to the contents of the query, and the right part to the results of the query, which must be displayed by product type. Users may choose other classifications. The left part contains the  target and time interval which were previously selected for the plot.

scenario #2 : access from the hierarchy of resources

The VESPA window may be opened from the hierarchy of resources, by a right click on an object (spacecraft or celestial body). In this case, there is no time range selected. The only selected parameters are target_name and target_class. This option would be added to the "Close All" option which is already implemented (see figure below)


  • No labels


  1. Here's the T117 use case (Titan flyby by Cassini) which relates 3Dview, Topcat and VESPA through a "planetary region" query T117_usecase.pdf

    1. many thanks. It's also linked from EPN link with GIS (to the page, as probably) on the long run it is better to upload as attachment and not only in comment? Then I could link to the section with it directly (and more permanently)

      1. You're right; I'll put it in the 3Dview section above

  2. Do we need an IDL one? It's easy in fact - the only boring part is to write the query.

  3. what about a python/ipython/jupyter one? using but also training-wise, notebooks could be effective.

  4. There s also a Google Sheet Add-On I created that can be used to access any (preferably GAVO DaCHS based) data service. The preview of the tool can be found here >>
    A short tutorial describing basic features and usage can be found here >>

    I have also submitted it so it should be available "officially" in Google's Add-On store soon...however, the review process can be a bit hang in there...(smile)