<<

3rd Planetary Data Workshop 2017 (LPI Contrib. No. 1986) 7045.pdf

A COMMON MODEL TO HANDLE PDS3 AND PDS4 DATA. J. Saiz1, A. Macfarlane1, R. Docasal1, C. Rios1, I. Barbarisi1, F. Vallejo1, S. Besse1, C. Vallat1, C. Arviset1, 1ESA/ESAC, Camino Bajo del Castillo s/n, Urb. Villa- franca del Castillo, 28691 Villanueva de la Cañada, Spain, [email protected].

Introduction: ExoMars 2016 [1], launched on 14th References: March 2016, was the first ’s [1] ESA, ExoMars 2016 mission overview, (ESA) operational mission to make use of the latest http://exploration.esa.int/mars/46124-mission- release of the Planetary Data Standards (PDS4). overview; [2] ESA, ExoMars RSP mission overview, Following this, ExoMars Rover/Surface Platform http://exploration.esa.int/mars/48088-mission- (RSP), planned to be launched in 2020 [2], which aims overview/; [3] ESA, BepiColombo mission overview, to put a European rover and a Russian platform on the http://www.esa.int/Our_Activities/Space_Science/Bepi Mars surface, and BepiColombo [3], a joint ESA and Colombo_overview2; [4] Besse, S. et al., (2017) Plan- JAXA mission to Mercury, will produce their scientific etary and Space Science (submitted); [5] Macfarlane, data in PDS4 format as well. A. et al., (2017) Planetary and Space Science (submit- ESA’s Planetary Science Archive (PSA) [4] is the ted); [6] Salgado, J. et al. (2013), IPDA Planetary Ac- central repository to store products from all ESA cess Protocol; [7] Erard, S. et al. (2014) The EPN-TAP planetary missions. This archive is not only in charge protocol for the Planetary Science Virtual Observato- of preserving data from operational or future missions ry. following the PDS4 standard, like the aforementioned ones, but also from legacy missions that utilized the previous Planetary Data Standard PDS3: Giotto, Huy- gens, , SMART-1, the recently finished mission, currently in post-operations phase, and the still operational . Common data model: As part of the reengineer- ing of the PSA [5], an effort has been made to map the key metadata from PDS3 and PDS4 into a common data model with the intention of providing transparency to the services that make up the new PSA. These include the main web portal from where data coming from ESA planetary missions can be searched, viewed and downloaded, as well as machine access interfaces implementing the PDAP (Planetary Data Access Protocol) [6] and EPN-TAP (EuroPlanet-Table Access Protocol) [7]. The common mapping allows the PSA to support data deliveries from the pipelines of existing missions without the need to reprocess the PDS3 data, and in addition it simplifies the data deliveries from missions following the PDS4 standard. At the same time, the original PDS3 and PDS4 structures are also main- tained, thus permitting to retrieve them when required. Technologies involved: The implementation of this data model comprises a PostgreSQL database with PostGIS (a spatial and geographic extension for Post- greSQL) and a GeoServer instance (an open source utility to share geospatial data). The original PDS3 and PDS4 deliveries are stored in a file repository that is accessible with proper access rights from the different interfaces. All these enable a solution in which the user is not required to know in detail the underlying structure of the data formats.