|Stéphane Erard||One year on VESPA, a community-driven Virtual Observatory in Planetary Science||In the frame of the Europlanet-RI program (2009-2012), a prototype Virtual Observatory dedicated to Planetary Science has been set up. Most of the activity was dedicated to the definition of standards to handle data in this field. The aim was to facilitate searches in big archives as well as sparse databases, to make on-line data access and visualization possible, and to allow small data providers to make their data available in an interoperable environment with minimum effort. This system makes intensive use of studies and developments led in Astronomy (IVOA), Solar Science (HELIO), and space archive services (IPDA). |
A general standard has been devised to handle the specific complexity of Planetary Science, e. g., in terms of measurement types and coordinate frames . This standard is now a project study of IPDA. A procedure has been identified to install small data services, and hands-on sessions are organized twice a year at EGU and EPSC. A specific user interface (VESPA) has been developed at the Observatory of Paris (http://vespa.obspm.fr) using a resolver for target names. Selected data can be sent to VO visualization tools such as TOPCAT or Aladin through the SAMP protocol.
This effort is continuing in the Europlanet2020-RI programme started in Sept 2015 for 4 years. The programme provides support to new data services from the community (30 to 50 expected), and focuses on the improvement of the infrastructure. Future steps will include the development of a connection between the VO world and GIS tools, and integration of heliophysics, planetary plasma and mineral spectroscopy data.
The Europlanet 2020 Research Infrastructure project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 654208.
|Ludmila Kolokova||SBN-VESPA PDART Proposal|
The goal of this project is to develop a method for interfacing a PDS4 registry-based data service, as found at the PDS nodes, to the IVOA VESPA project portal and to deploy a prototype EuroPlaNet-Table Access Protocol (EPN-TAP) interface for the PDS Small Bodies Node (SBN) to demonstrate this method.
We propose to develop tools that will enable PDS4 registry-based data services, like those at the Small Bodies Node and other PDS nodes, to interface their data holdings to VESPA. This will facilitate the use of existing SBN PDS4 datasets by providing access to them through a Virtual Observatory portal designed to support planetary search parameters. It will enable and enhance future planetary science investigations by enabling users to retrieve SBN data in conjunction with correlated data from other sources, and by expanding the tools available for analyzing PDS4 data to include current and future VO tools.
In particular, this work will increase the accessibility and usability of PDS4 data, for which relatively few format-specific tools have been created, by providing conversion tools that will convert PDS4 format arrays and character tables into FITS file and VOTable structures, respectively, for which there exist a wide and growing variety of tools.
|Emily Law||PDS Roadmap Study||PDS has established a Roadmap Study Team (RST) to develop a Roadmap for the period 2017 to 2026. The purpose of this roadmap effort is to outline a strategy for moving forward in planetary data archiving under the auspices of a rapidly growing data volume (nearly 1 petabyte at present), new computing capabilities, tools, and facilities, and a growing community of planetary science investigators. This presentation will introduce and inform the roadmap activities in progress.|
The PDS4 Information Model and Interoperability
For diverse scientific disciplines to interoperate they must be able to exchange information based on a shared understanding. This shared understanding must be captured in a knowledge representation framework comprised of standards, methodologies, and tools for the purpose of creating a controlled vocabulary and a formal set of information requirements. In practice, this involves diverse and time- consuming activities including the adoption of standard reference models, knowledge acquisition, and the development of the information model, metadata and change management, and governance establishment. Finally, the resulting information model must have a positive impact on the community by being used. This presentation will provide an overview of the PDS4 Information Model, its impact on the development and management of the PDS, and its potential role in providing interoperability within the broader Space Science Community.
|Gangloff Michel||Interoperability standards at CDPP||The CDPP (French plasma physics data center (http://cdpp.eu) is engaged for nearly two decades in the archiving and dissemination of plasma data products from space missions and ground-based observatories, and involved in many interoperability projects or international organizations like SPASE, IVOA and IPDA. The work done in the frame of projects supported by the european commission (Europlanet/VESPA, IMPEx) , as well as the integration of SPASE in one of the analysis tools (AMDA) developed by the CDPP will be presented.|
|Jon Vandergrif||An Emerging Data Server Standard for NASA Heliophysics Time Series Data||The Heliophysics Data and Model Consortium (HDMC) is designing a standard API for serving time series data. The Heliophysics Application Programming Interface (HAPI) specification captures a minimum set of server-side functionality needed for a data provider to offer a standard, computer-friendly access mechanism to one or more datasets. There are 3 key capabilities in the HAPI spec: 1. list the datasets available; 2. describe one dataset (get a data header); 3. stream digital data for a given time range of one dataset. These capabilities are simple enough that even a small data provider could implement the spec without too much effort. A few example servers have been set up, and a development version of Autoplot has been created that can talk to a HAPI server. The API will be described, and a brief demonstration will be given to illustrate the server output and the type of data interoperability that this specification can enable.|
|Chuck Acton||SPICE Development Plans||Acton will summarize current NAIF thinking about further development of the SPICE system, and in so doing will entertain suggestions from the workshop participants.|