- Cahill Bg 370, Caltech, Pasadena, CA, USA
- Baptiste Cecconi (LESIA, Obs paris, Meudon, France), VESPA, CDPP
Stéphane Erard (LESIA, Obs Paris, Meudon, France), VESPA
- Jon Vandegriff (JHU/APL, Laurel, MD, USA), HDMC
- Santa Martinez (ESA/ESAC, Madrid, Spain), PSA
- Gangloff Michel (IRAP/CNRS, Toulouse, France), VESPA, CDPP
- Manuel Scherf (IWF/OeAW, Graz, Austria), VESPA
- Earl Maize (NASA/JPL, Pasadena, CA, USA), Cassini
- Barbara Streiffert, (NASA/JPL, Pasadena, CA, USA), Cassini
- Boris Semenov (NASA/JPL, Pasadena, CA, USA), NAIF
- Charles Acton (NASA/JPL, Pasadena, CA ,USA), NAIF
- Dan Crichton (NASA/JPL, Pasadena, CA, USA), PDS/EN
- Steve Hughes (NASA/JPL, Pasadena, CA, USA), PDS/EN
- Ludmilla Kolokova (UMD, College Park, MD, USA), PDS/SBN
- Pierre Le Sidaner (DIO, Obs. Paris, Paris, France), VESPA
- Cyril Chauvin (DIO, Obs. Paris, Paris, France), VESPA
- Emily Law (NASA/JPL, Pasadena, CA, USA), PDS/EN
- Sébastien Besse (ESA/ESAC, Madrid, Spain), PSA
- Jeremy Faden (UIowa, Iowa City, IA, USA) (remote)
- Inaki Ordonez-Etxeberria (EHU, Bilboa, Spain) (remote)
- Alfiah Rizky Diana Putri (UCL, London, UK) (remote)
Stéphane Erard: One year on VESPA, a community-driven Virtual Observatory in Planetary Science
- VESPA query portal: http://vespa.obspm.fr
- VESPA documentation: http://discussions.europlanet-vespa.eu
- VESPA main web page: http://www.europlanet-vespa.eu
- Europlanet-2020-RI web page: http://www.europlanet-2020-ri.eu
- Stéphane Erard presents the VESPA activity during the first year of the project.
- Q. Chuck Acton: Why is IPDA not displayed in slide 2?
A. The displayed database are not representative, they are just examples. However, the IPDA is not a database. It is an alliance that is workmen towards interoperability between space agency planetary archives.
- Q. Emily Law: Do you contribute to standard design in other the alliances?
A. Yes, we participate to IVOA, SPASE and OGC, with different people in the VESPA team. We always try to reuse instead of reinvent. Our action in the consortia is to adapt existing standard for planetary science applications. Examples: adding planetary coordinates at IVOA, adding FITS support in OGC, adding planetary bodies in ObservedRegion's SPASE data model.
- Q. Boris Semenov: Can we search for or share data collections in VESPA?
A. It is technically possible. However, the main usage of VESPA is to provide a link to individual data resources. A useful application of VESPA is to be able to display selected data products with standard tools. If data collections are provided, it might be difficult to display them easily.
Extra thoughts after the meeting: if the data collection can be linked with a scriptable URL (such as a GIS map service, or HAPI (see Jon Vandegriff presentation)), that would be useful. We will study this use case.
- Q. Dan Crichton: Who are the Chinese contacts you talked to at AOGS?
A. Stéphane will have a look and tell IPDA (done)
Ludmila Kolokova: SBN-VESPA PDART Proposal
- Ludmilla Kolokova presents a PDART proposal submitted earlier this year. The goal is to develop a method to interface PDS/SBN with VESPA.
- Why PDS/SBN and not PDS as a whole?
The PDS/SBN specificity is the diversity of objects. There is also many instruments hosts, including ground observatories and balloons, which are not usual for a NASA data center.
- Good opportunity to build the observatory/spacecraft catalog.
- LK shows the similarities between PDS4/SBN and EPNcore parameters. For some parameters the mapping should be easy. For others, it will imply some work on SBN's side:
- spectral parameters:
In SBN, filter names is used, or central wavelength and width. Spectral informations are in wavelengths, not frequency.
- targets and instrument names
This a complex task. The target names for a given object are not always unique in the SBN database, different targets may bear the same name (eg, Halley, Europe), some objects can belong to several target classes (eg, Chiron), and have changed target class (dwarf planets in particular). The same holds for instrument names and host names. However, the SBN has a lot of experience on that topic, and tools have been developed to work out the situation.
- spectral parameters:
- The MPC (Minor Planet Center) is now part of SBN.
- Some EPNcore parameter will have to be computed when building EPNcore (table or view) from PDS4 labels (e.g., ISO-8601 UTC times into Julian Day).
- The PDS4 is very flexible and it is possible to declare all EPNcore metadata in a "local discipline dictionary" (see Steve Hughes presentation). The project will be an opportunity to enhance PDS4 standards based on the work done on VESPA.
- The PDS4 labels will have to be ingested into an SQL (PgSQL) database.
- File transformation: to FITS or to VOTable.
- PDART proposal selection result: end of 2016. If selected, work starting in March 2017.
- Comment. Baptiste Cecconi: The PDS/PPI team has already developed a PDS4 "table" object to VOTable. Todd King may be contacted for this.
- Q. Sébastien Besse: Who is going to build the custom translators needed to share in VESPA (with EPNcore standard units)?
A. This is on the data provider's side. There is some work do be done. First version may be minimal, with improved description on a later step. This requires knowledge on the datasets. Stéphane Erard showed the concept of label metadata extraction to SQL table and then to EPNcore view.
Emily Law: PDS Roadmap Study
- VESPA RFI answer: NNH15ZDA012L. Preparation for the Development of a Community-Based Roadmap for Planetary Data Services
- Emily Law is presenting the PDS roadmap. Initially 6 broad topics were identified, including public access (this is new). RFI in Jan. 2016 received 24 responses.
- Result and draft roadmap to be presented at next LPSC (March).
Steve Hughes: The PDS4 Information Model and Interoperability
- PDS4 Information Model (220.127.116.11): https://pds.jpl.nasa.gov/pds4/doc/im/current/index_1700.html
- Steve Hughes presents the PDS4 standards (especially information model and interoperability layers)
- PDS4 is based on international standard (OAIS, ebXML...)
- Governance (standard definitions) has three layers: PDS (global), nodes (discipline) and missions. Very different from PDS3, where everybody had a say.
- Metadata are described in the information model. Local Data Dictionaries (LDD's) at discipline or mission level. It will be easy to build a mapping from PDS4 to EPNcore using this mechanism (EPNcore LDD). Several LDD can overlap, there can be a PSA LDD and a SBN LDD.
- Q.Baptiste Cecconi: Is there a mechanism to merge several LDD, so as to simplify the model?
A. If there is a lot of overlap, LDD may merged, or the concepts may be escalated up to the next governance level. Inclusion into general PDS level requires assessment by PDS Change Control Board.
- Q. Boris Semenov: How can the system be "backward compatible" if there are LDD changes?
A. This is related to the issue of PDS4 version 2.0. That will happen when all nodes have representative data collections dealing with a large fraction of the data types of their discipline. That may take several years. Until then, there is no commitment on "backward compatibility". So the advice is try out and comment now, so that your needs are in the system.
Michel Gangloff: Interoperability standards at CDPP
- CDPP web page: http://cdpp.eu
- CDPP AMDA tool: http://amda.cdpp.eu
- CDPP 3dview tool: http://3dview.cdpp.eu
- CDPP Propagation tool: http://propagationtool.cdpp.eu
- Gangloff Michel presents the CDPP and the recent developments in interoperability, as well as the CDPP tools: AMDA, 3Dview and PropagationTool. Description of the various european projects CDPP participated into EPN/VESPA, HELIO, IMPEx...
- Note on IMPEx: tools to display and compare data and simulation runs for planetary plasma. Project is over, but seeking new fundings.
- Description of the internal CDPP registry. It extends SPASE and includes EPNcore metadata.
- The Propagation Tool now includes the EPNTAPClientLib (see other presentation by Michel Gangloff), it connects to APIS this way.
- Presentation of a use case from 3Dview on a Titan flyby. It uses EPNTAPClientLib querying VESPA with the select scene on 3Dview. The data found this way (Titan atmospheric profiles) are displayed with TOPCAT.
- Q. Boris Semenov: How do you manage your spice kernels?
A. They are managed (regularly updated) and stored on server side. The clients are requesting times series of orbital and attitude parameters.
Jon Vandegriff: An Emerging Data Server Standard for NASA Heliophysics Time Series Data
- HDMC web site: http://hpde.gsfc.nasa.gov/hpde_hdmc_projects.html
- HAPI test server: http://datashop.elasticbeanstalk.com/hapi/data?id=CASSINI_1_MIN_CRUISE_MAG&time.min=2002-095&time.max=2002-095T00:05&include=header¶meters=BR,BT,BN
- Jon Vandegriff presents the HAPI (Heliophysics API) as defined by the HDMC. It is very generic, so it can be applied to planetary sciences too.
- Granule level not relevant for this type of data, they need to access individual measurements - similar to AMDA.
- Different formats => archives : API difficulties (each data center has its own).
- Goal is: clients should be easy to write as well.
- HAPI is independent from SPASE. It can be implemented in data center, in addition to usual interface. Uses JSON for output. Standardize time description (ISO-8601). Access to data: provide a datase_ID and time range only. Returns a CSV file.
- The API has 3 levels of query level: capabilities, catalog (list of datasets) and info (on a selected dataset).
- Example shown with virutal machine on amazon cloud service.
- Autoplot is HAPI compliant.
- Plan: add a element in SPASE for describing the HAPI URI template.
- Comment. Steve Hughes: It would be possible (nice?) to have a HAPI URL catalog in PDS4/PPI.
Michel Gangloff: A generic library for the management of the EPN-TAP protocol
- EPNTAP Client Library Specification: VESPA EPN-TAP Library specification
- EPNTAP Client Library Deliverable Document:
- CASSIS: http://cassis.irap.omp.eu
- A generic library for the management of the EPN-TAP protocol
- Registry search through the VOParis registry (REST interface, with JSON output) and the IVOA registry (RegTAP)
- Afterthought: EPN-TAP library docs and use cases to be reorganized on VESPA wiki
Charles Acton: SPICE Development Plans
- Chuck presents the NAIF/SPICE development plans
- Digital Shape Kernels: small bodies and planets. Transform tool available to go from a shape model (from a series of formats to DSK)
- WebGeoCalc: programmatic interface ready. Will be distributed to large institutes.
- Current developments for VOTable output and SAMP implementation
- Cosmographie: science oriented, scriptable. 3D shape support to be expected soon (end 2016)
- Very interesting meeting. This format (not a short and rigid session schedule) is better for discussions and interaction.
- Next opportunity: Pasadena IPDA in 2018 ? ESPC 2017 in Riga ? EPN/NA2 workshop ?
- Rename "Planetary Interop Workshop #1" and propose next one well in advance to make sure US people can get support.