Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Pierre Le Sidaner, Nicolas AndréBaptiste Cecconi, Vincent Génot, Laurent Beigbeder, Jean-Michel Glorian, Jean-Christope Malapert, Myriam Bouchemit, Joelle Durand


JCMalapert: We should work on specific cases, from the client to derive specifications of protocol and interfaces. 

Laurent Beigbeder and Jean-Michel Glorian: want to define how their tools (3Dview and CASSIS) will query VESPA, what result they would show to the user, how they handle data they don't know how

Baptiste Cecconi: On the VESPA portal, when we can find AMDA results. If the user wants to send it to AMDA via SAMP, AMDA should understand that the data shall not be downloaded from AMDA, but should be used directly from the database. Decide on what to do? E.g.: display a "plot manager" with the dataset parameters and the time interval.


Baptiste Cecconi: This is agreed. EPNcore is built to provide a data model that describes data product coverage useful for data discovery. EPN-TAP is an implementation of EPNcore with TAP. There may be other protocols that will use EPNcore in the future, this is to be studied. Furthermore: EPN-TAP is a generic data discovery protocol for planetary sciences, it does not replace dedicated interfaces adapted to specific thematics and use cases (for instance GIS), but it can be used to discover what data exist relative to a scene (in a GIS tool or in 3Dview), or in a spectral range (in CASSIS). The EPN-TAP protocol can be used two ways: a context data discovery protocol (querying all services with parameters pre selected depending on the tool display), or direct access to known resources when suitable (for instance, access to APIS images for 3Dview).