AbstractGeographical information systems (GIS) are becoming increasingly used for planetary science. GIS are computerised systems for the storage, retrieval, manipulation, analysis, and display of geographically referenced data.Some data stored in the Planetary Science Archive (PSA)[1] have spatial metadata associated to them. To facilitate users in handling and visualising spatial data in GIS applications, the PSA should support interoperability with interfaces implementing the standards approved by the Open Geospatial Consortium (OGC). These standards are followed in order to develop open interfaces and encoding that allow data to be exchanged with GIS Client Applications (e.g. OpenLayers, Cesium...). Access to this data for use in applications can be provided through OGC Web Service (OWS) implementations.An existing open source server is GeoServer, an instance of which has been deployed for the PSA, that uses the OGC standards to allow the sharing, processing and editing of data and spatial data through the Web Map Service (WMS) and Web Feature Service (WFS) standards. On the back-end side, a PostgreSQL/PostGIS instance allows the spatial queries.The final goal is to enhance the PSA (accessible through ) further as a portal which enables science exploitation of ESA's planetary missions datasets. This can be facilitated through the GIS framework, offering interfaces (both web GUI and scriptable APIs) that can be used more easily and scientifically by the community, and that will also enable the community to build added value services on top of the PSA.IntroductionSome of the current operational ESA planetary missions, such as Mars Express, ExoMars 2016, and BepiColombo, as well as other future missions such as ExoMars 2020, Juice, etc. will benefit of a GIS tool to visualize their targets (Mars, Mercury, Jupiter…) allowing spatial queries to retrieve geometrical information like features, footprints, rover path tracking, rover drill sites, etc.GIS ArchitectureThe PSA relies on 3-tiered system for the GIS architecture (see Figure 1). The database layer is composed of a PostgreSQL database with the PostGIS extension to store the spatial information. The server layer uses GeoServer as a map server to provide WMS/WFS responses (e.g. GeoJson, kml…) to the web application’s requests (implemented on the Vaadin framework). Finally, the client layer (browser) runs the OpenLayer Javascript library to render the map.Other external GIS tools like QGIS might be used to get the PSA spatial data from either the GeoServer or the database. Figure 1: GIS architecture diagram for the PSAViews ConsistencyThe PSA provides different views to show the same planetary data. These views are integrated and synchronized to each other to visualize the information as the data type requires. All of them use the filter menu to search by a given criteria and offer similar features such as sorting, pagination, downloading and product detailed info. Once a query is executed on a view, the information is automatically loaded when changing views. The map view is integrated in the current PSA (see Figure 2) as the other views (Table, Image) giving other perspective of displaying results when it comes to search for spatial data. Figure 2: Views Consistency in the PSAGIS ApplicabilityGIS technology on the PSA will offer a common way to filter (by mission, instrument, target, dates, geometry…) and search for spatial data, even for legacy missions, thanks to the homogenization of the geometrical information with per-product spatial metadata computed in a consistent way via SPICE.PSA will provide spatial data retrieval of both versions of the NASA Planetary Data Systems archival formats, PDS3 and PDS4, based on a criteria search, and, the possibility of selecting PDS3/PDS4 products from a particular region of interest (ROI) (see Figure 3). Figure 3: Query by ROI and footprint selectionPSA also provides other useful GIS tools such as switching projections for better visualization and analysis of footprints over the poles (see Figure 4) as well as switching between different base maps of Mars for better visualization, enabling/disabling layer feature, overlapping footprint selection by popup and a grid/graticule layer.Figure 4: Footprints over the Mars North Polar projectionPSA also allows the user to add customized and external data through a GeoJSON file uploader tool (see Figure 5).Figure 5: GeoJSON data uploader featureAcknowledgementAlthough the whole PSA team has somehow been involved in this GIS implementation, I would specially like to thank Francisco Raga for his huge contribution in many of the presented GIS features.References[1] Besse, S. et al. (2017) Planetary and Space Science, , ESA's Planetary Science Archive: Preserve and present reliable scientific data sets.

IntroductionThe Planetary Science Archive (PSA) of the European Space Agency (ESA) has recently released a new user interface and APIs to access ESA's planetary data. These updates, along with data migration activities, aim to keep the mission data relevant and usable over the long term. This is critical when the time between missions to a given body can be decades. [JO1] PDS3 migrationThe PSA currently supports 10 missions ranging from Giotto[JO2] , ESA's earlier deep-space probe in the 1980s, to the JUICE mission to the Jupiter system, launched last year. Early missions, as well as Mars Express - still going strong[JO3] after 20 years, provided data in PDS3 format. Newer missions have adopted PDS4 format and an operational archive approach where data are delivered regularly. This newer format brings many benefits, not the least a standard set of tools to allow users to open any data product. To ensure the longevity of the PDS3 data, an activity to migrate the legacy products has been started this year. This is particularly important to ensure, for example, that data from Venus Express are in the most usable form possible prior to EnVision. The key challenge in this activity is how to maintain data access for users coming from the world of PDS3, with its associated tools and codes, and that of PDS4.User interfaceAs a single repository for ESA's planetary data, the PSA has evolved its user interface (UI) over the years, always keeping multi-mission search at its core. Late last year a new version of the UI was released, offering a refreshed and responsive design. New functionality planned for late 2024 is the map-based display and selection of data products at Mercury, in preparation for the arrival of BepiColombo late next year. The figure below shows an example of visualising footprints from the CaSSIS instrument on the ExoMars Trace Gas Orbiter in the most recent version of the PSA. In addition, integration with the ESA Datalabs project is ongoing and support for PDS4 data is being added this year; whilst not yet fully public, this platform allows users to work with PSA data in a browser without having to download it. Finally, for those users who still need to download large amounts of data, a more streamlined approach will be rolled out by serving lists of URLs and pre-baked scripts rather than traditional compressed archives.Data accessUsers have the possibility to download data in several ways, from the UI, from a secure FTP system offering access to both public and private data, and via several APIs. Programmatic download of individual products has long been possible, but the most recent version offers download based on an ADQL query. This means that users can leverage complex criteria to select data which are packaged and downloaded. In addition, ingesting metadata into the PDS registry and API means that users can query on arbitrary metadata and pass the list of returned identifiers to the PSA to retrieve these products.New missionsCurrently the PSA supports 10 planetary missions and over one hundred instruments including remote sensing, in-situ, and laboratory-type instruments. In the coming years we hope to see data from future missions including Rosalind Franklin, HERA, Comet Interceptor, EnVision, PROSPECT and Mars Sample Return. In addition to these missions, a new challenge is the increasing number of payload opportunities on commercial missions, e.g. from the NASA CLPS programme, where data from ESA contributions need to be archived. A training session in November 2024 will give hands-on experience to many of the new data providers in how to produce archive products for the PSA.Community feedbackThe PSA exists first and foremost for the scientific community, and we appreciate your feedback on how things could be improved, missing functionality etc. As well as finding the PSA team at conferences and meetings you can reach out to the PSA Users’ Group who represent your needs also. We would love to hear how we could help you do more with these data, so please get in touch!

. IntroductionThe ESA-Roscosmos ExoMars 2022 Mission [1] will deliver the Rosalind Franklin Rover and Kazachock Surface Platform to the Oxia Planum landing site on Mars [2, 3]. The launch window opens on 20 September 2022 with a corresponding Mars arrival on 10 June 2023. The Rover’s mission objectives are to search for signs of life and characterise the shallow subsurface. During its 211 sol nominal mission ‘Rosalind Franklin’ will accomplish its objectives using its ‘Pasteur’ Payload of 9 instruments, plus a drilling system capable of extracting samples from down to 2m for analysis.2. Mission StatusTests and reviews to confirm overall spacecraft readiness are proceeding, including a campaign of High Altitude Drop Tests (HADTs) on the parachute system. Activities at the Rover Operations Control Centre (ROCC) —located at ALTEC, Turin (IT)— are ramping up. Software systems used during the mission for planning are being tested and refined, and the Control and Science Teams are working together to train for the day-to-day operations environment.3. Spacecraft ControlThe ROCC can be considered an Activity Plan factory for the Rosalind Franklin rover. The ROCC is designed to support ESOC (European Space Operations Centre) during the launch, LEOP (Launch and Early Orbit Phase), when conducting periodic checkouts of the rover and instruments in interplanetary cruise, and to perform rover mission operations on Mars. A partner facility in Moscow, the Surface Platform Payload Operations Control Centre (SPOCC), controls the Kazachok Surface Platform.The Science Team and the rover Control Team work together at the ROCC (including by remote connection) to conduct two parallel and connected processes. The Strategic process, performed during office hours, is the top-level process to plan rover activities. It proceeds via daily structured work and meetings. Strategic planning aims to achieve the rover mission objectives and maximize scientific return, and it is dynamic; adjusting to new scientific findings and interpretations. Strategic planning is done on 3 timescales: short term (next sol), medium term (within the current mission phase), and long-term (the next major mission phase plus objectives that could be addressed further in the future).The Tactical process is the sequence of events triggered by the downlink of rover data to ROCC following an orbiter pass. It ends with uplink of validated activity plans to the rover for execution. Tactical planning is done on a schedule synchronised with downlink and uplink via Mars orbiters.Figure 1: Illustration of scheduling strategic and tactical processes.4. Strategic PlanThe Strategic Plan provides traceability from the top-level mission science objectives to individual rover activities. It provides the scientific context and background for how the mission science is organised. The Rover Science Operations Working Group (RSOWG) is building the Strategic Plan for the rover via 3 main tasks:Define scientific questions elaborated from the mission objectives. From these questions, construct corresponding hypotheses that are testable by rover instruments at the Oxia Planum landing site. Prepare preliminary instrument command sequences and potential targets to test the hypotheses. Upon landing, the Strategic Plan will be ‘initialised’ at the landing point by the Science Team. They will interpret new data, assess locations to perform initial activities, and set long-term objectives.5. Science TargetsThe ‘Science Target Scheme’ has been conceived for use in daily science operations in order to harmonize the description of the places and features observed by the Rosalind Franklin rover during the mission, and the links between them. It is integrated into software tools running at the ROCC, and the data submitted to ESA’s Planetary Science Archive (PSA). It is a hierarchical schema of 10 classes representing objects at spatial scales relevant to Rover science, from areas identified in orbital data, down to spots on crushed samples analysed by instruments in the Rovers’ Analytical Laboratory Drawer, ALD [see 1]. A concept showing use of several target types used during the Post-Landing-To-Egress (PLTE) mission phase is shown in Figure 2.Figure 2: Concept for use of science targets in the PLTE mission phase (expected to last ~10 sols).6. Team SimulationsDuring 2021-2023 a programme of simulations is being performed for training and certification of the team for operations. A subset of simulations in the programme are planned and run by the RSOWG. These allow the Science Team to test and refine their processes, for example to perform decision-making in the time-limited operations environment, and to rehearse several designated roles (e.g. Journal Keeper, Long Term Planner). RSOWG simulations are planned by a dedicated Simulations Planning Group composed of science, project and industrial team representatives. They use inputs from all Rover instrument teams, and lessons learned from analogue campaigns [e.g. 4] and other information, to design the scenarios determined to be most fruitful for maturing scientific processes.7. ‘Micro’ and ‘Macro’ working groupsThe RSOWG has chartered the ‘Micro’ and ‘Macro’ sub-working groups with a broad mandate to prepare for and optimise aspects of science operations at those spatial scales. For example, the Micro group works on the protocol for assessment of sample analyses, and builds knowledge of sample types using terrestrial analogues. While the Macro group, for example, provides a detailed morphostratigraphic map of the landing site as input to building the strategic plan [5], and prepares the geospatial data layers used in operations. Both groups also work together on important topics that span orbital to sample spatial scales, such as interpreting orbital spectroscopic and geomorphological data to set and refine mineralogical expectations for mission samples.AcknowledgementsThe authors wish to sincerely thank the ExoMars 2022 Science Team and Industrial Teams for their continuing tireless efforts to ensure readiness for operations.References[1] Vago, J. L. et al., (2017) Astrobiology 17 (6–7), 471–510, doi:10.1089/ast.2016.1533[2] Quantin-Nataf, C. et al., (2021) Astrobiology 21 (3), doi:10.1089/ast.2019.2191[3] Mandon, L. et al., (2021), Astrobiology 21 (4), doi:10.1089/ast.2020.2292.[4] Balme, M. R. et al., (2019) Planet. Space Sci. 165, 31–5.[5] Sefton-Nash, E. et al., (2021) in LPSC 52, #1947.

This 1:30,000 scale geological map describes Oxia Planum, Mars, the landing site for the ExoMars Rosalind Franklin rover mission. The map represents our current understanding of bedrock units and their relationships prior to Rosalind Franklin's exploration of this location. The map details 15 bedrock units organised into 6 groups and 7 textural and surficial units. The bedrock units were identified using visible and near-infrared remote sensing datasets. The objectives of this map are (i) to identify where the most astrobiologically relevant rocks are likely to be found, (ii) to show where hypotheses about their geological context (within Oxia Planum and in the wider geological history of Mars) can be tested, (iii) to inform both the long-term (hundreds of metres to similar to 1 km) and the short-term (tens of metres) activity planning for rover exploration, and (iv) to allow the samples analysed by the rover to be interpreted within their regional geological context.

Asteroids (24) Themis and (65) Cybele have an absorption feature at 3.1 µm reported to be directly linked to surface water ice. We searched for water vapour escaping from these asteroids with the Herschel Space Observatory Heterodyne Instrument for the Far Infrared (HIFI). While no H2O line emission was detected, we obtain sensitive 3σ water production rate upper limits of Q(H2O) < 4.1 × 1026 mol. s−1 for Themis and Q(H2O) < 7.6 × 1026 mol. s−1 for Cybele. Using a Thermophysical Model (TPM), we merge data from Subaru/Comics and Herschel/SPIRE with the contents of a multi-observatory database to derive new radiometric properties for these two asteroids. For Themis, we find a thermal inertia Γ = 20+25-10 J m-2 s-1/2 K-1, a diameter 192 +10-7 km and a geometric V-band albedo pV = 0.07 ±0.01. For Cybele we obtain a thermal inertia Γ = 25 +28-19 J m-2 s-1/2 K-1, a diameter 282 ± 9 km, and an albedo pV = 0.042± 0.005. Using all inputs, we estimate that water ice intimately mixed with the asteroids’ dark surface material would cover < 0.0017% for Themis and < 0.0033% for Cybele of their surfaces, while an areal mixture with very clean ice (bond albedo 0.8 for Themis and 0.7 for Cybele) would cover < 2.2% for Themis and < 1.5% for Cybele, of their surfaces. While surface (& sub-surface) water ice may exist in small localized amounts on both asteroids, it is not the reason for the observed 3.1µm absorption feature.

IntroductionThe ExoMars Trace Gas Orbiter (TGO) was launched in 2016 and Science Phase started in April 2018. Apart from the failure of one sub-instrument, the spacecraft and payload remain healthy and in normal operations today. The mission approach to archiving the data had two significant differences from previous ESA missions archiving in the Planetary Science Archive (PSA): ExoMars was the first mission to archive the PDS4 standard data and it was the first to actively process and archive the mission raw data daily.During the pre-launch phase the planning for the ExoMars archiving was done in close coordination with the BepiColombo mission team who would also take the active archiving approach and use the PDS4 standard, hence we were able to achieve a common data structure and set of rules for our data providers. This set of PSA rules has been recorded the PSA Archiving Guide, which remains a living document used by all new ESA missions archiving in the PSA.Data StructuresOne of the most impactful decisions made for the PSA PDS4 archives was to create a single bundle for each instrument then separate collections by data type, such as document, schema, data etc. Science data is also subdivided by processing level, hence all raw data for a mission accumulates in one collection inside one bundle. This naturally has led to large accumulating collections and while data volumes have not presented any significant issues, sheer numbers of files, especially if stored in a flat structure, have led to the need to consider carefully the physical structure adopted.Another issue, was that early in the mission, the directory structures were not settled and to change the structure required the data products to be deleted then re-ingested with the new path. This has since been improved with internal tools to change a path internally. It's important to note that the storage layout adheres to a distinct schema from what the end user sees. Data offered to users (via ftp, web pages, or custom applications) is regulated by the distribution path value stored in a database, eliminating the need for physical file movement in case of future rearrangements.Bundle and Collection Versions: A major difficulty with the single accumulating bundle/collection approach faced early on, has been versioning. Initially the bundle/collection versions were incremented on every daily delivery, but it quickly became evident that maintaining a full record of each version was going to be more effort that it made sense to expend. The approach was modified to artificially increment on a monthly basis but this approach has also now been dropped with the current approach to only increment if there has been a significant change such as the ingestion of reprocessed data from the whole mission.Product Design: One choice which is made for all science products is whether to group data files together into a single product, or even a single file, or whether to produce smaller separate products. For the CaSSIS instrument on the TGO it was decided that the framelets making up the push broom image should be stored as separate images. However a CaSSIS observation typically has around 600 PDS4 framelet products at Raw level. Added to the fact that in a typical day CaSSIS typically has around 30 observations, and data gets re-processed, we now have an archive with tens of millions of CaSSIS products. This has caused 2 main issues. The first has been difficulty in maintaining database performance. The other issue has been the discovery and tracking of missing data due to issues with the initial data downlink, the data processing, validation and/or transfer and ingestion into the PSA. Putting all the framelets for each filter into one product per observation would reduce number of products but at the cost of a very long label e.g. including geometry information for each framelet, which potentially has different downsides.Filenames:One of the successful decisions made was to standardise file naming and at least for the science products to include filenames as part of the LID. The use of mission/instrument the bundle name plus the filename for the products has created a convention which keeps the LIDs in the PSA unique.A different issue encountered was in the use of time in the filename. As data for most instruments did not have an observation ID, it is necessary to use date/UTC to create a unique filename/LID. However, the spacecraft clock drifted by up to a few seconds, corrected later in SPICE, so when the Raw data underwent a full re-processing the filename and hence the LID also changed meaning we had two different LIDs associated with a single observation.PSA Dictionary: Another success, has been to develop a dictionary for the PSA, allowing the addition of cross-mission attributes which are not included in the PDS4 core model. For some attributes, such as mission phase, we additionally include schematron in individual mission dictionaries and this standardisation in the schema has aided the development of the PSA tables and UI.Summary: Design choices made before the launch of ExoMars in 2016 remain in place, and the active archives now include the BepiColombo and JUICE missions. The structure and conventions adopted are easy to follow and have generally been successful. Some PDS conventions such as versioning have not been compatible with an active archive approach hence the way PSA deals with these has evolved.

Previous research on Asteroids (24) Themis and (65) Cybele have shown the presence of an absorption feature at 3.1 μm reported to be directly linked to surface water ice. We searched for water vapor escaping from these asteroids with the Herschel Space Observatory HIFI (Heterodyne Instrument for the Far Infrared) Instrument. While no H2O line emission was detected, we obtained sensitive 3σ water production rate upper limits of Q(H2O)< 4.1×1026 molecules s−1 for Themis and Q(H2O)

Abstract With new missions being selected, missions moving to post-operations, and missions starting their journey to various targets in the Solar System, the European Space Agency’s Planetary Science Archive [1] (http://psa.esa.int) (PSA) is in constant evolution to support the needs of the projects and of the scientific community. What happened since last year? The past year has been good for the European Space Agency (ESA) Solar System missions and the PSA, with the successful flyby of Earth by the BepiColombo mission to Mercury. The ExoMars 2016 mission is performing nominally and is quickly delivering numerous scientific observations. As is common for ESA missions, access to the data is protected and reserved to members of the science team for the first months of the mission. Once the products are ready to go public, the PSA performs a scientific peer-review to ensure that the products to be made public are of excellent quality for all future users. During the first half of 2020, the PSA has successfully peer-reviewed the CaSSIS and NOMAD observations. Those products are now being made public on a systematic basis once the proprietary period elapses (generally between 6 and 12 months). Early in 2020, filters to search data with geometrical values (i.e., longitude, phase angle, slant distance, etc.) were enabled. For now this service works for Mars Express and Rosetta, but will be soon extended to other missions. One of the main new services provided to the scientific community in 2020 is the Guest Storage Facility (GSF), which allows users to archive derived products. Products such as geological maps, Digital Terrains Models, new calibrated files, and others can be stored in the GSF in the format most used by the users. Contact us to preserve your science! Finally, by the end of 2020 users of the PSA will have access to new services based on Geographical Information Systems. You can contribute to the PSA! At the PSA we constantly interact with our users to ensure that our services are in line with the expectations and needs of the community. We encourage feedback from community scientists through: * PSA Users Group: A group of scientific experts advising the PSA on strategic development; * Direct interactions: Scientists from the PSA are available and eager to receive your comments and suggestions; * ESA missions: If you are part of a mission archiving its data at the PSA, tell us how your data should best be searched and used. Acknowledgement The authors are very grateful to all the people who have contributed over the last 17 years to ESA's Planetary Science Archive. We are also thankful to ESA’s teams who are operating the missions and to the instrument science teams who are generating and delivering scientific calibrated products to the archive. References [1] Besse, S. et al. (2017) Planetary and Space Science, 10.1016/j.pss.2017.07.013, ESA's Planetary Science Archive: Preserve and present reliable scientific data sets.

Introduction: The Planetary Science Archive (PSA)[1] of the European Space Agency (ESA) has, over the past year, incorporated new interfaces for accessing the data. These new interfaces (an improved SFTP[2], the PSA PDS[3] API[4] and ESA Datalabs[5]), along with enhancements to the existing ones (TAP/EPN-TAP[6] and UI[7]), have considerably contributed to expand the interoperability mechanisms of the archive. Here we describe various use cases (for both PDS3[8] and PDS4[9] data formats) in which all or part of these interfaces are used, showing different ways to obtain results from the same source archive.Example Overview: The use case will simply be to access some PDS3 and PDS4 products by their logical identifier. These are the missions and instruments we will use for this (both Martian missions). Mission Format Instr. Product identifier Mars Express PDS3 HRSC MEX-M-HRSC-3-RDR-EXT9-V4.0:DATA:HO799_0000_S23.IMG ExoMars TGO PDS4 ACS urn:esa:psa:em16_tgo_acs:data_raw:acs_raw_hk_nir_20180613t180000-20180613t235959::1.0 Depending on the interface, the result will be either the download of the data product or the associated metadata (bundles/datasets, collections, label files, etc.)GUI: The PSA Graphical User Interface (PSA GUI), which has been recently refurbished using the Angular framework, offering a modern and responsive design, allows the user to visualize data in a friendly way and search for PDS3 or PDS4 products via a rich set of filters. For our use case, we will use the Product ID field to search by the logical_identifier parameter (last version will be given by default).Figure 1: Getting a PDS3/4 product in the PSA GUI and displaying it in the Mars map view.TAP/EPN-TAP: The Table Access Protocol (TAP) service, running as a web application, allows searching PDS3 or PDS4 data by means of ADQL[10] queries. This service is used as back-end for the GUI shown before; in addition, it can be accessed directly through a browser, programmatically (with Bash, Python, etc.) or from a client application such as Topcat. For the PDS3 use case, we will use the EPN-TAP service (Europlanet extension based on TAP) via the curl command: $ curl -X 'GET' \ 'https://psa.esa.int/psa-tap/tap/sync?LANG=ADQL&REQUEST=doQuery&FORMAT=json&QUERY=select%20*%20from%20%20psa.epn_core%20where%20(obs_id=%27MEX-M-HRSC-3-RDR-EXT9-V4.0%3ADATA%3AHO799_0000_S23.IMG%27)' \ -H 'accept: *' This returns a JSON file with expected metadata such as mission, instrument, bundle, collection, target, geometrical information, processing level, download path, etc.SFTP: The new SFTP service, based on CrushFTP[11], provides a rich web client to download data, as well as a standard SFTP access. It uses a virtual volume behind the scenes, to get the available public/private data using the FUSE[12] technology. In this interface, the user may explore the structure of missions, datasets/bundles up to the desired level. For the use case, we will run the URL in the browser to get the same PDS3 product as before: https://psaftp.esac.esa.int/#/MARS-EXPRESS/HRSC/MEX-M-HRSC-3-RDR-EXT9-V4.0/DATA/O799/HO799_0000_S23.IMGThis will result in the download of the selected product to the user’s machine.Figure 2: Accessing a PDS3/4 product and browsing its contents with the PSA new SFTP. PDS API: The PDS API implemented by NASA makes use of the PDS4 harvester to access PDS4 data of the PSA (although PDS3 data is not yet available in PDS, the PDS3 to PDS4 migration activity of the PSA coming up soon will cover the retrieval of these datasets). The API can be accessed from a browser (Swagger[13]), command line, Jupyter notebook[14], etc. This API allows the user to search for PDS4 products and their references by their lidvid (logical identifier and version id), collections, specifying the returned fields and filtering by any of the metadata contained in their label files. This ability to query arbitrary meta-data makes it very powerful.To get the example PDS4 product via the PDS API we would just use the following URL:https://pds.nasa.gov/api/search/1/products/urn:esa:psa:em16_tgo_acs:data_raw:acs_raw_hk_nir_20180613t180000-20180613t235959::1.0Figure 3: Getting metadata of a PDS4 product through the PSA PDS API (via Swagger API).The response body includes product’s information such as the mission, instrument, observation dates, targets, etc. It also includes the PSA label (XML file) URL, which links to our PSA FTP repository.Various response formats are supported, including CSV, XML, JSON and the original PDS4 label.ESA Datalabs: Finally, this new framework allows the user to work with planetary data without needing to download it. In the example, a Jupyter Notebook is used to access and display the MEX HRSC product. For reading PDS3 data, the PDR[14] Python library is used.Figure 4: Getting and plotting a PDS3 product with ESA Datalabs.Acknowledgments: We are grateful to the PSA development team for their invaluable assistance in creating and refining the PSA software. We also thank our advisors and supporters for their guidance and encouragement throughout the process.References:[1] S. Besse et al. (2018), ESA's Planetary Science Archive: Preserve and present reliable scientific data sets, Planetary and Space Science, Volume 150, p. 131-140.[2] Secured FTP: https://psaftp.esac.esa.int/[3] Planetary Data System: https://pds.nasa.gov/[4] PDS PSA: https://pds.nasa.gov/api/search-psa/1/[5] ESA Datalabs: https://datalabs.esa.int/[6] TAP/EPN-TAP: https://psa.esa.int/psa-tap/tap/[7] PSA User Interface: https://psa.esa.int[8] PDS3 Archiving Guide:https://www.cosmos.esa.int/documents/772136/977578/ESDC-PSA-TN-0008.pdf[9] PDS4 Archiving Guide:https://www.cosmos.esa.int/documents/772136/977578/ESDC-PSA-TN-0002+Iss2Rel5-5.pdf[10] Astronomy Data Query Language (ADQL): https://www.ivoa.net/documents/ADQL/20180112/PR-ADQL-2.1-20180112.html[11] CrushFTP: https://www.crushftp.com/index.html[12] FUSE: https://github.com/libfuse/[13] Swagger: https://swagger.io/[14] Jupyter Notebook: https://jupyter.org/[15] PDR python library: https://github.com/millionconcepts/pdr

Introduction: The present abstract is intended to show the current ESA’s Planetary Science Archive (PSA) [1] in terms of architecture/infrastructure and the future interfaces and technologies which will be used in the next generation archive. These improvements range from a new graphical user interface developed in Angular to a TAP+ (Table Access Protocol) service as a single access to the data, through a new way of releasing new versions of the PSA more frequently to the scientific community. The PSA development team expects to release this new generation of the PSA this summer 2022. PSA current architecture: The PSA architecture and the technologies involved in its development have only undergone incremental updates in the last 6 years, and are now seen as somewhat obsolete. The front-end has been implemented using the Vaadin framework, which was initially a good strategy, but over time became onerous to maintain (e.g., dealing with JavaScript libraries, wasting time in wrapping some required extensions in Java). Also, from the back-end point of view, there are many interfaces/libraries to access the database (JDBC, PDAP, Data Distribution, etc) forcing us to double the effort when changing the API (see Figure 1: PSA current architecture) In addition, the PSA release approach has not followed a truly Agile approach, taking too long in releasing operationally. This is mainly due to the fact there is no a fully CI/CD strategy to be executed in the environments, leading to very manual release process with manual interventions. Also there are additional problems such as the synchronisation of the repositories when releasing, which strongly depends on the IT department. Figure 1: PSA current architecture New interfaces, technologies and infrastructure at PSA: After one year and half of development, the PSA development team has been able to achieve several goals on the roadmap to a new archive. Mainly, we will rely on a new graphical user interface implemented under the Angular framework (see Figure 2: Future PSA Graphical User Interface). There have been various reasons to migrate to this new technology: Faster development for maps visualisation and 3D interfaces, alignment within the ESDC department in a common front-end framework and also, the discontinuation of Vaadin 8 from March 2022 on. This future GUI will have a modern look and feel, with some relevant changes in line with the new ESA branding. Specially on the home view, where there are now card layouts to access the data from missions/instruments, targets and maps and a prototype traverse view for the ExoMars Rover mission, among other features. This new Angular framework has definitely sped the development up when modifying some JavaScript libraries, creating some end-to-end tests on top through Cypress, etc. This will also increase the performance on the client side consequently improving the user experience. In addition, this implementation is also mobile and tablet friendly/responsive. Figure 2: Future PSA Graphical User Interface Also, the new PSA will count on a single access point to the data through TAP+ (even private data) to homogenise the access by offering a single API, instead of using different interfaces/protocols (JDBC, PDAP, etc.) to access the information. In addition to these new interfaces, the PSA is making a huge effort to set up an infrastructure to support a faster deployment cycle in order to be more agile according to the scrum methodology. This implies integrating and deploying the software (after checking metrics in Sonar, passing the end-to-end tests, etc.) as nightly builds into a safe environment (pre-production) so that the Archive Scientists can test the latest features which, once approved, will go to the operational environment. This follows mostly a DEV-OPS infinite loop but having a middle environment (PRE) in which the scientists can safely test the features. Conclusion: The current PSA development team along with the Science Lead and all of the Archive Scientists are working together to produce a new generation of the planetary archive, with these features: * a more modern and responsive GUI based on a stable and well-known technology * a single access route to the data with authentication and authorization for private products (TAP+) * a new infrastructure of environments which allow a more efficient CI/CD so that the features can be validated earlier, allowing the PSA to offer releases in the operational environment more frequently. References: [1] Besse, S. et al. (2017) Planetary and Space Science, 10.1016/j.pss.2017.07.013, ESA's Planetary Science Archive: Preserve and present reliable scientific data sets. Acknowledgments: The authors would like to thank everybody, especially the PSA development team, who have contributed to the development of the PSA in the recent years and the incoming new generation of the archive.

Introduction Studies are underway to provide solutions to bring the Rosalind Franklin rover to Mars (Figure 1). Complementing the ExoMars 2016 mission involving the Trace Gas Orbiter and Schiaparelli spacecraft [1, 2], the second ExoMars mission’s science objectives are to search for signs of past and present life, and to investigate the subsurface water/geochemical environment as a function of depth [3, 4]. We report on work by the Science Team to finalise preparations that would have been needed for a launch in 2022, and that remain essential for readiness at a future launch date. Figure 1. Rover Science Operations Working Group (RSOWG) The ExoMars RSOWG was chartered in 2019 to advance the state of preparation for Rover science operations within the science team. Sub-groups are tasked with addressing specific needs: RSOWG-Micro address topics regarding the spatial scale of the samples that will be extracted from down to 2m by the rover’s drill, their analogues, and plans for their analyses. Notable recent work by the Micro sub-group has included (i) Recommending a sequence of rover activities following commissioning, named ‘Science.0’. The goal of the Science.0 activities is to prime the rover’s analytical laboratory and characterise its initial state prior to commencing analysis to search for biosignatures on Mars samples. (ii) Running a process to propose, select and analyse a set of ‘Mission Reference Samples’ – a suite of analogue samples most relevant to the landing site and mission objectives to be characterized by ground models of the MicrOmega [5], RLS [6] and MOMA [7] instruments. RSOWG-Macro address topics using the wealth of remote sensing data amassed by orbiter missions, and at rover to regional spatial scales. In 2020-2021 the Macro group performed a group mapping exercise of the Oxia Planum landing site [8] to develop understanding of the site’s stratigraphy and geological history [9]. A related output has been the publication of a corresponding Geographic Framework [10], to be used during simulations and operations. Other RSOWG-Macro activities have included defining how to initialise the mission’s ‘Strategic Plan’ upon landing, building a version-controlled repository of orbital data products, and establishing conventions for naming features and places at the landing site. The RSOWG Simulations Planning Group comprises a team of ‘Simulation Officers’, nominated from Pasteur Payload Teams, ESA and industry. In 2021 they were tasked with designing and leading a series of ‘RSOWG Simulations’, an early series of team simulations that were intended to rehearse and refine strategic science processes. Scenarios, entitled ‘After Landing’, ‘Site Survey’, ‘Opportunistic science trade-off’ and ‘ALD Analyses’, required science data interpretation, rover activity planning, and decision making at strategic level, and used data from all 9 Pasteur Payload instruments. Lessons learned from early simulations, inform planning of future simulations and exercises, including those prepared by the Rover Operations Control Centre (ROCC – Turin, Italy) for training and certification of team members for operations. During 2022 and beyond, RSOWG are focussing on maturing the mission’s ‘Strategic Plan’, which provides traceability from the Rover mission science objectives to individual rover and instrument activities, taking into account the realities of the landing site. The RSOWG is tasked to form the Strategic Plan by 1) identifying questions that stem from the Rover mission science objectives and organizing them into scientific priorities, 2) defining hypotheses that should be tested using rover instruments, and 3) identifying targets and ‘skeleton’ plans of activities that could be performed by the rover and its instruments that would address specific groups of hypotheses. Plans, People, and Processes Some aspects of science operations preparations lie outside the responsibility of RSOWG, and are complementary to the industry-led development and testing of systems and rover operations at the ROCC. The ‘Science Operations Plan’ was developed to ensure that daily science operations processes in Tactical and Strategic planning cycles (Figure 2) are complete, robust, transparent, efficient, and collegiate. The plan complements ground and flight control procedures, and covers science team organization, communication, journaling, science-specific tools, and designated roles. Figure 2: Illustration of Tactical planning (synchronized with orbiter overflights) and Strategic Planning (office hours) shifts as they relate to UTC and Local Mean Solar Time at Oxia Planum. The 'Strategic Plan' guides and governs the decisions made during planning cycles. The rover long-term data archive, hosted on the ESA Planetary Science Archive (PSA) [11], will contain not only data from science instruments in the Pasteur Payload, but also data regarding the Rosalind Franklin rover’s journey through Oxia Planum. This is achieved via the ‘Science Target Scheme’, which prescribes data structures and links between them for a hierarchy of target classes from landing site to sample analysis scales. The Sample Analysis Protocol (SAP), in preparation, builds on the ExoMars Biosignature Score (EBS) [3], and is intended define the investigations and metrics for establishing and reporting whether a location on Mars has hosted microbial life, past or present. Finally, analyses and bespoke tools support needs in areas such as staffing, sequence optimisation for rover activities, and ‘trade-sheets’ [12] to aid decision-making for science targets. Acknowledgments We thank the ExoMars Pasteur Payload, Science, and Industrial Teams, for their profound continuing efforts to prepare the first European Mars rover mission that will search for signs of life on Mars. References [1] Vago, J. L. et al., (2015) Sol. Syst. Res. 49 (7), 518–528. [2] Svedhem, H. et al., (2020) 14th Eur. Sci. Congr. 2020, held virtually, 21 Sept. 2020 - 9 October, 2020. Abs. EPSC2020-802. [3] Vago, J. L. et al., (2017) Astrobiology 17 (6–7), 471–510. [4] Thomas, N. et al., (2017) Space Sci. Rev. 212 (3–4), 1897–1944. [5] Bibring, J.-P. et al., (2017) Astrobiology 17 (6–7), 621–626. [6] Rull, F. et al., (2017) Astrobiology 17 (6–7), 627–654. [7] Goesmann, F. et al., (2017) Astrobiology 17 (6–7), 655–685. [8] Sefton-Nash, E. et al., (2021) in 52nd Lunar Planet. Sci. Conf. [9] P. Fawdon, et al. (2022) in Lunar Planet. Sci. Conf., LPI. [10] Fawdon, P. et al., (2021) J. Maps 17 (2), 762–778. [11] Lim, T.-L. et al., (2021) in 5th Planet. Data Work. Planet. Sci. Informatics Anal., Vol. 2549. [12] Torres, I. et al., (2022) '“Trade-Off” Tools to Quantify Biosignature Potentials for Future ExoMars Rover Mission Operations', This Conference.

Introduction: The present abstract is intended to show the current ESA’s Planetary Science Archive (PSA) [1] in terms of architecture/infrastructure and the future interfaces and technologies which will be used in the next generation archive. These improvements range from a new graphical user interface developed in Angular to a TAP+ (Table Access Protocol) service as a single access to the data, through a new way of releasing new versions of the PSA more frequently to the scientific community. The PSA development team expects to release this new generation of the PSA this summer 2022. PSA current architecture: The PSA architecture and the technologies involved in its development have only undergone incremental updates in the last 6 years, and are now seen as somewhat obsolete. The front-end has been implemented using the Vaadin framework, which was initially a good strategy, but over time became onerous to maintain (e.g., dealing with JavaScript libraries, wasting time in wrapping some required extensions in Java). Also, from the back-end point of view, there are many interfaces/libraries to access the database (JDBC, PDAP, Data Distribution, etc) forcing us to double the effort when changing the API (see Figure 1: PSA current architecture) In addition, the PSA release approach has not followed a truly Agile approach, taking too long in releasing operationally. This is mainly due to the fact there is no a fully CI/CD strategy to be executed in the environments, leading to very manual release process with manual interventions. Also there are additional problems such as the synchronisation of the repositories when releasing, which strongly depends on the IT department.

Abstract The European Space Agency’s (ESA) Mars Express (MEX) mission to Mars has been returning valuable scientific data for ~18 years. This data is available to the public for free via the Planetary Science Archive (PSA), which houses the raw, calibrated, and higher-level data returned by the ESA’s planetary missions, including data provided by the various MEX instrument teams. The High Resolution Stereo Camera (HRSC) has provided several types of datasets throughout the mission, and its images have proven popular not only among scientists but also the public for the spectacular images of the red planet. A new version (version 4.0) of the radiometrically calibrated HRSC data has been made available which covers the entirety of the mission’s operation up to now. This new version utilizes an updated calibration, which is especially important for later images as it improves the adjustments for the aging of the instrument [1]. In addition to the new calibration, the data is now split into mission phases. Previous versions of the radiometrically calibrated data incorporated all observations into a single dataset, which led to increasing lag in some access methods as the dataset continued to grow in size and number of files. All this data and more can be accessed at the PSA at: https://archives.esac.esa.int/psa/ Introduction MEX was inserted into Mars orbit in December 2003, though several instrument test observations also exist from the cruise phase of the mission, prior to arrival at Mars. Thus, this long-lived Mars mission covers 18+ years of data with its 7 instruments. Later in the mission’s lifetime, the camera used for the Beagle 2 lander separation was reactivated and used for public outreach. Over time, the camera began to be used for scientific observations as well, making MEX an unusual mission in that it now has more scientific instruments in operation than it was launched with. The PSA user interface The ESA’s PSA uses the Planetary Data System (PDS) format developed by NASA to store the data from its various planetary missions. In the case of MEX, the data is stored in the PDS3 format, which primarily uses ASCII files to store and describe the data. Newer missions, from ExoMars onward use the PDS4 data standard, which uses XML files. There are three primary ways in which to find the data. One is the FTP area, which houses all the public data in the PSA. Here, there are no advanced search capabilities, but it does provide access to all the supporting files and documentation for the various datasets. When first searching for new data, users would benefit from using the Table View search interface [2]. Here the user can search using various parameters, such as mission name, target, instrument name, processing level, observation times, etc. The Table View is also linked to the Image View, where users can view the browse images provided by the PI teams. The Table View interface also has a section for “Free Search”, allowing one to use Contextual Query Language (CQL) to search over additional parameters. Finally, there is also a Map View for viewing the footprints of data from those instruments where such calculations can be of some utility. These various search methods rely in part on the metadata provided by the instrument teams in the labels associated with each of the data products, though the Map View also benefits from a homogenized approach to calculating geometrical parameters for all data across various missions. Conclusion The redelivery of the HRSC data provides an improved dataset with newer calibration factors applied. This data can be freely accessed at the ESA’s PSA, at https://archives.esac.esa.int/psa/. There are multiple ways of browsing the HRSC and other instrument teams’ data, including from other planetary missions, which will be explained in this poster. The development of the PSA’s user interface is an ongoing project, and we welcome feedback from the community for suggestions on new ways to search this wealth of data. Feedback and suggestions can be sent to psahelp@cosmos.esa.int. Acknowledgements The MEX Archive Scientist and the entire PSA team would like to extend their thanks to the HRSC team for their effort in updating previous deliveries and continuing to deliver new data from Mars to the public via ESA’s PSA. Our thanks go also to the European taxpayers, whose contributions to the European Space Agency enable the gathering and dissemination of this scientific knowledge, and preserving it for future generations of scientists to work on. References [1] Gwinner, K. et al.: The High Resolution Stereo Camera (HRSC) of Mars Express and its approach to science analysis and mapping for Mars and its satellites, Planetary and Space Science, Vol. 126, pp. 93-138, 2016. [2] Besse, S., Vallat, C., Barthelemy, M., Coia, D., Costa, M., De Marchi, G., Fraga, D., Grotheer, E., Heather, D., Lim, T., Martinez, S., Arviset, C., Barbarisi, I., Docosal, R., Macfarlane, A., Rios, C., Saiz, J., and Vallejo, F.: ESA’s Planetary Science Archive: Preserve and present reliable scientific data sets, Planetary and Space Science, Vol. 150, pp. 131-140, 2018.

The European Space Agency’s Planetary Science Archive (PSA) is the home for all scientific data from ESA’s planetary missions. Adopting the NASA PDS standard (version 3 and 4) it is designed to make the data, meta-data and knowledge on how to use them available to the scientific community. As a multi-mission archive, the PSA supports (or will soon support) over ten missions and their associated instruments, with this number expected to grow significantly in the coming years. The PSA has a long legacy of successfully preserving and distributing mission data to the community, and offers several services to fulfil this, including tabular, image-based and map-based interfaces, several APIs and traditional FTP. However, the entry barrier for new users is quite high, and moving forward there are new data access requirements coming from scientists wanting to perform more complex queries, run machine learning algorithms and so on. This presentation will describe the current infrastructure, recent updates and plans for the next few years which will try to address these changing needs. In particular, the following key developments are foreseen: * implementation of a new user interface, with a streamlined and more user-friendly design, which will also work well on mobile, and touchscreen displays, * improvements to APIs to include more data (specifically instrument geometry), and to incorporate the new PDS API which will allow access to any meta-data in the data products, leveraging the full value of the effort put in by instrument teams and archive scientists to curate them, * integration with ESA DataLabs, a project designed to “bring the code to the data” and allow data processing and analysis to be done in an interactive online environment hosted close to the data repository and allowing big data workflows without having to download the products, * publication of data tutorials based on open-source tools and libraries, to give new users a “quick start guide” to using data from a given instrument, and * a much higher frequency release cadence, responding to the needs of the scientific community in a timely manner. Finally, community input is sought on other improvements which could be made, and which use cases are not fulfilled by the current infrastructure.

The European Space Agency’s Planetary Science Archive (PSA) is the home for all scientific data from ESA’s planetary missions. Adopting the NASA PDS standard (version 3 and 4) it is designed to make the data, meta-data and knowledge on how to use them available to the scientific community. As a multi-mission archive, the PSA supports (or will soon support) over ten missions and their associated instruments, with this number expected to grow significantly in the coming years. The PSA has a long legacy of successfully preserving and distributing mission data to the community, and offers several services to fulfil this, including tabular, image-based and map-based interfaces, several APIs and traditional FTP. However, the entry barrier for new users is quite high, and moving forward there are new data access requirements coming from scientists wanting to perform more complex queries, run machine learning algorithms and so on. This presentation will describe the current infrastructure, recent updates and plans for the next few years which will try to address these changing needs. In particular, the following key developments are foreseen: * implementation of a new user interface, with a streamlined and more user-friendly design, which will also work well on mobile, and touchscreen displays, * improvements to APIs to include more data (specifically instrument geometry), and to incorporate the new PDS API which will allow access to any meta-data in the data products, leveraging the full value of the effort put in by instrument teams and archive scientists to curate them, * integration with ESA DataLabs, a project designed to “bring the code to the data” and allow data processing and analysis to be done in an interactive online environment hosted close to the data repository and allowing big data workflows without having to download the products, * publication of data tutorials based on open-source tools and libraries, to give new users a “quick start guide” to using data from a given instrument, and * a much higher frequency release cadence, responding to the needs of the scientific community in a timely manner. Finally, community input is sought on other improvements which could be made, and which use cases are not fulfilled by the current infrastructure.

Introduction: With new missions being selected, missions moving to post-operations, and missions starting their journey to various targets in the Solar System, the European Space Agency’s Planetary Science Archive [1] (http://psa.esa.int) (PSA) is in constant evolution to support the needs of the projects and of the scientific community. Geometry as a key input for users: While analysing the various services that the PSA already offers, geometrical information was lacking in many ways. Feedback received by the users and the PSA User Group pointed to improvements in this area. During the past years, the PSA structured its internal architecture to provide excellent services to the community. Through external partnership, we developed the GEOmetry GENerator that allows a consistent way of deriving geometrical information. This input provides a solid foundation to develop Geographical Information System (GIS) services into the PSA. At the end of 2020, the PSA released its 3D and 2D interfaces for Mars Express and Rosetta, providing a new generation of geometrical services. Although currently focused on Mars and comet 67P/C-G, our architecture enables a rapid growth to support in particular BepiColombo and JUICE. High level products through the Guest Storage Facility: One of the other new service provided to the scientific community recently is the Guest Storage Facility (GSF), which allows users to store derived products. Products such as geological maps, Digital Terrain Models, new calibrated files, and others can be stored in the GSF in the format most used by the users. The philosophy of the GSF service is to impose minimum requirements on the data producers, while delivering maximum usability to the end users. Various products related to Titan and Mars are available in the GSF. Products related to the Moon, comet 67P/C-G and other targets are in preparation. Contact us to preserve your science! Interact with the PSA and expect more in the years to come: The PSA aims to build on the previous development to further enrich its services. New GIS interfaces related to Phobos, the Moon and Mars are in development to facilitate the searching capabilities on those targets. In parallel to those major developments, new functionalities will be developed to support ESA missions, in particular ExoMars, Mars Express, and BepiColombo. At the PSA we constantly interact with our users to ensure that our services are in line with the expectations and needs of the community (despite massive disruptions in 2019 and 2020). We encourage feedback from community scientists through: * PSA Users Group: A group of scientific experts advising the PSA on strategic development; * Direct interactions: Scientists from the PSA are available and eager to receive your comments and suggestions; * ESA missions: If you are part of a mission archiving its data at the PSA, tell us how your data should best be searched and used. Acknowledgments: The authors are very grateful to all the people who have contributed over the last 18 years to ESA's Planetary Science Archive. We are also thankful to ESA’s teams who are operating the missions and to the instrument science teams who are generating and delivering scientific calibrated products to the archive. References: [1] Besse, S. et al. (2017) Planetary and Space Science, 10.1016/j.pss.2017.07.013, ESA's Planetary Science Archive: Preserve and present reliable scientific data sets.

Asteroids (24) Themis and (65) Cybele have an absorption feature at 3.1 mu m reported to be directly linked to surface water ice. We searched for water vapor escaping from these asteroids with the Herschel Space Observatory Heterodyne Instrument for the Far Infrared. While no H2O line emission was detected, we obtain sensitive 3 sigma water production rate upper limits of Q(H2O) < 4.1 x 10(26) molecules s(-1) for Themis and Q(H2O) < 7.6 x 10(26) molecules s(-1) for Cybele. Using a thermophysical model, we merge data from the Subaru/Cooled Mid-Infrared Camera and Spectrometer and the Herschel/Spectral and Photometric Imaging Receiver with the contents of a multi-observatory database to derive new radiometric properties for these two asteroids. For Themis, we find a thermal inertia Gamma = 20(-10)(+25) J m(-2) s(-1/2) K-1, a diameter 192(-7)(+10) km, and a geometric V-band albedo p(V) = 0.07 +/- 0.01. For Cybele, we obtain a thermal inertia Gamma = 25(-19)(+28) J m(-2) s(-1/2) K-1, a diameter 282 +/- 9 km, and an albedo p(V) = 0.042 +/- 0.005. Using all inputs, we estimate that water ice intimately mixed with the asteroids' dark surface material would cover <0.0017% (for Themis) and <0.0033% (for Cybele) of their surfaces, while an areal mixture with very clean ice (Bond albedo 0.8 for Themis and 0.7 for Cybele) would cover <2.2% (for Themis) and <1.5% (for Cybele) of their surfaces. While surface (and subsurface) water ice may exist in small localized amounts on both asteroids, it is not the reason for the observed 3.1 mu m absorption feature.