#  Executive Summary

The updated PLANMAP Data Management Plan (DMP) is provided. Map-wide metadata
structure and fields for PLANMAP mapping products are described and
exemplified. The long-term data repository venues for PLANMAP products are
listed and specified. Delivery file formats are updated, as reflected by
deliverables. Described aspects in this DMP include: beneficiaries producing
data, adherence to FAIR principles, data types, formats and standards,
metadata, documentation, intellectual property and data storage, archiving and
curation during and after the project.

#  Introduction

PLANMAP will both use and produce data. Different data categories can be
distinguished in the framework of PLANMAP:

**Base mapping data:**

  * **A)** Individual higher-level data products derived from raw experiment data (which are archived on PDS or PSA), e.g. map-projected individual images or custom calibrated cubes (e.g. CTX, OMEGA, CRISM) 

  

  * **B)** Custom processed or mosaicked data from multiple data products (i.e. derived hyperspectral summary products, multi-image mosaics) available in public archives or repositories (e.g. PSA, PDS, USGS) 

  

  * **C)** Individual higher-level data products already produced by experiment teams and available from PDS/PSA archives (e.g. HRSC) 

  

  * **D** ) Custom processed or mosaicked data with from multiple data products (i.e. derived hyperspectral summary products, multi-image mosaics) produced by the consortium 

  

**Integrated mapping products:**

  * Intermediate temporary mapping products (for scientific discussion and sharing within the consortium) o Raster imagery/data o Vector mapping data 

  

  * finished geological maps (See _D2.1 (Mapping Standards)_ , Rothery et al, 2018, 

  

_D2.2-public_ (Morphostratigraphic maps, Rothery et al., 2019) o Standard
USGS-like geological maps

  * Integrated geo-spectral and geo-stratigraphic maps o Geo-structural maps o Geo-modelling maps o Landing site and traverse maps o In-situ integrated maps o Digital outcrop models o Subsurface models 

  

  * 3D models for Virtual Reality environments (from one or more of the above categories) 

  

The fate of datasets and data products belonging to these categories is
different. Individual data products (A B, C) are preserved for the long-term
in appropriate archives. Their eventual reduction and reprocessing is
reproducible, with well-known open source tools, and supported for the long
term by robust institutions and agencies (e.g. USGS/NASA). Intermediate
mapping products are instrumental to producing final, released and/or
published PLANMAP digital mapping products (see section on Data Storage and
Management during the project) and their long termstorage is not planned, but
documentation, in the form of wiki or individual documents is going to be
preserved during the course of the project, and significant summaries and
excerpts will be included as deliverable text and annexes, and can also be
used as ancillary material attached to scientific publications.

The current long-term archiving and availability of PLANMAP data is as follows
(please refer to relevant subsections below):

  * All Raster, vector and layout (pdf) mapping data o Short-term: on the PLANMAP data archive on _https://data.planmap.eu/_ o Long-term: on the ESA PSA DOI-granting guest storage facility on _https://www.cosmos.esa.int/web/psa/psa_gsf_

  

  * Additional ancillary geologic models and specific 3D products o Short-term: on the PLANMAP data archive on _https://data.planmap.eu/_ o Long-term on the Univeristy of Padova DOI-granting data repository on _http://researchdata.cab.unipd.it_

  

  * Additional ancillary specific compositional products o Short-term: on the PLANMAP data archive on _https://data.planmap.eu/_ o Long-term on the INAF DOI-granting data repository 

  

#  Scope of the document

The present document updates the type of data, their characteristics and their
use, archiving and preservation plans throughout the PLANMAP project.
Intellectual property rights are also clarified, as well as specific per-
partner data use and responsibilities. The document outlines the basic data
management directions that are going to be updated throughout the project and
issued at discrete steps.

#  Beneficiaries using data

All beneficiaries will use data, in either individual or - in most cases -
combined forms. Data access to archived (NASA/ESA) mission data is free for
anyone. Some data will have temporary team-only access (during an embargo of
up to several months), such as mapping data used by PLANMAP researchers (see
section on Data Storage and Management during the project)

#  Beneficiaries producing data

All beneficiaries will produce either derived data (higher-level data
products) or new data derived by both human and computer/algorithm-assisted
mapping.

In particular, beneficiaries are set to produce these data categories (see
Annex A, B):

  * UNIPD: 

    * mosaics and higher level products derived from planetary archives o vector mapping products (geologic/geomorphologic maps) o 3D models 

  

    * (subject to increase/expansion) 

  

  

  * OU 

    * mosaics and higher level products derived from planetary archives o vector mapping products (geologic/geomorphologic maps) o (subject to increase/expansion) 

  

  

  * WWU 

    * mosaics and higher level products derived from planetary archives o vector mapping products (geologic/geomorphologic maps) o (subject to increase/expansion) 

  

  

  * INAF o mosaics and higher level products derived from planetary archives o (subject to increase/expansion) 

  

  * CNRS o 3D and virtual reality models o digital outcrop maps 

    * vector mapping products (geologic/geomorphologic maps and models) o (subject to increase/expansion) 

  

  

  * JacobsUni o mosaics and higher level products derived from planetary archives 

    * vector mapping products (geologic/geomorphologic maps) o (subject to increase/expansion) 

  

  

#  Adherence to FAIR principles

Data produced by PLANMAP will impact future robotic and space exploration,
mainly through mature, finished, published mapping products. Underlying data
and special mapping products will be of scientific use also before and beyond
that. Accessibility to the data will be provided in three different forms:

Findable data:

  * Longer-term discoverability will be guaranteed via connected Institutional repositories (ESA, UNIPD, INAF), VESPA sharing and inclusion in planetary data archives that are accessible and commonly used by the community. 

  

  * Shorter-term discoverability will be supported by the PLANMAP web-map and data access Accessible data: 

  

  * Geological mapping products will have multiple level of accessibility, with variable scale and complexity, from individual units to finished products and thematic maps Interoperable data: 

  

  * OGC standards for CRS and formats will be adopted 

  

  * Data discovery interoperability will be granted via the use of state-of-theart VESPA EPN-TAP (Virtual European Solar and Planetary Access EuroPlanet Table Access Protocol) for data search and query. 

  

Re-usable data:

  * Raw data will be used and processed/reduced, with embedded re-usability upstream with respect to PLANMAP 

  

  * Custom base-map data (e.g. mosaics) and partial mapping products and processed/derived datasets underlying geological mapping products (standard, non-standard, integrated, etc.) will be usable by others, also in the future, regardless of the final geological mapping products. 

  

  * Integrated and/or final mapping products will be re-usable directly or indirectly, with access to combined information content or individual layers (See _D2.1 (Mapping Standards),_ _D2.2-public_ ) with relevant topologies (units, contacts, etc.). 

  

#  Data types, formats and standards

PLANMAP uses existing datasets and data products and creates new products
deriving from combination or derivation of existing, processed data products,
as well as from completely new mapping (e.g. units), see _D2.1 (Mapping
Standards)_ (Rothery et al., 2018).

#  Data

**Raw data**

Planetary archives, PDS3, PDS4 imagery and cubes.

##  Base mapping data

OGC-compliant data already available from external entities (e.g. USGS) or
base mapping data produced by PLANMAP partners, some in PDS standards/formats.

##  Integrated mapping products

Integrated mapping products with individual layers are being produced in
OGCcompliant formats, both raster and vector, as well as with suitable 3D
formats (See Annex A). All individual layers/components of maps are in
geospatial format and with CRS suitable for the specific mapping project: in-
situ, local (mostly non-standard, see _D2.1 (Mapping Standards)_ ), regional
or global (both standard and non-standard).

#  Metadata

The aim of including metadata is to allow reproducibility by providing
information about the processing steps performed. Map-wide metadata including
both geometric and bibliographic information are provided for each map (e.g.
as accessible on _https://data.planmap.eu/_ ).

##  Raw data

Metadata from processed raw data are the same as those from archived data.
SPICE kernel version and software used (e.g. USGS ISIS) should be recorded.

Isis Cube labels (i.e. recording cumulative processing steps and used
ancillary data, metadata, CRS and alike). The information is going to be
recorded in processing labels and as temporary output in ASCII format.

##  Base mapping data

Projection, cubes and images used, type of control network used, and relevant
additional information available from original derived data producers (e.g.
USGS, ESA, academic institutions or local PLANMAP base mapping data producers
or groups) will be recorded.

##  Integrated mapping products

Metadata for integrated mapping products will be both map-related and sub-map
(i.e. geological unit)-related.

Map-related metadata include, as a minimum:

  * Used datasets and products 

  

  * Mapping individuals 

  

  * CRS 

  

  * Summary of used tools and documented workflow 

  

Unit-related data/metadata include, as a minimum, recorded and updated during
the mapping processes, see also _D2.1 (Mapping Standards)_

  * Individual products and layers used to determine unit extent and contacts 

  

  * Eventual interpolation/extrapolation of data underlying mapped unit outline 

  

  * Qualitative assessment on uncertainties involved in the unit determination 

  

Authors of the maps, programs, processing and basic info to allow
reproducibility of the underlying workflow is included and added to the
documentation. Also, geocoding of units (i.e. associating toponyms to
locations and mapped surface units) will be produced in order to ease search
of at least individual maps as well as individual units and their occurrence
within maps (see e.g. _http://geometrics.jacobsuniversity.de/_ , Rossi et al,
2018).

##  Map types

PLANMAP map-types, as per DoA, include:

  * **S** = Stratigraphic 

  

  * **C** = Compositional 

  

  * **M** = Morphologic 

  

  * **G** = Geo-structural 

  

  * **I** = Integrated 

  

  * **D** = Additional DOM-specific mapping products for individual or multiple lander/rover-imaged outcrops can be included 

  

##  Map-level metadata

Complementing metadata related to individual units, each map of PLANMAP
include several map-wide field, exemplified below:  
  
<table>  
<tr>  
<th>

**Field**

</th>  
<th>

**Field description (and example entries)**

</th> </tr>  
<tr>  
<td>

Map name (PM_ID)

</td>  
<td>

PM-MER-MS-H02_3cc_01

</td> </tr>  
<tr>  
<td>

Target body

</td>  
<td>

Mercury

</td> </tr>  
<tr>  
<td>

Title of map

</td>  
<td>

Geologic Map of the Victoria Quadrangle (H02), Mercury

</td> </tr>  
<tr>  
<td>

Bounding box - Min

Lat

</td>  
<td>

-22.5° 
</td> </tr>  
<tr>  
<td>

Bounding box - Max

Lat

</td>  
<td>

65°

</td> </tr> </table>  
<table>  
<tr>  
<th>

Bounding box - Min Lon (0-360)

</th>  
<th>

270°

</th> </tr>  
<tr>  
<td>

Bounding box - Max Lon (0-360)

</td>  
<td>

360°

</td> </tr>  
<tr>  
<td>

Author(s)

</td>  
<td>

Valentina Galluzzi; Laura Guzzetta; Luigi Ferranti; Gaetano di Achille; David
A. Rothery; Pasquale Palumbo

</td> </tr>  
<tr>  
<td>

Type

</td>  
<td>

Released

</td> </tr>  
<tr>  
<td>

Output scale

</td>  
<td>

1:3M

</td> </tr>  
<tr>  
<td>

Original Coordinate Reference System

</td>  
<td>

Lambert conformal conic

Center longitude: 315°

Standard parallel 1: 30°

Standard parallel 2: 58°

Datum: 2440 km (non-IAU, MESSENGER team datum)

</td> </tr> </table>  
<table>  
<tr>  
<th>

Data used

</th>  
<th>

MESSENGER MDIS BDR v0 uncontrolled basemap (166

m/pixel)

MESSENGER MDIS 2013 complete uncontrolled basemap (250 m/pixel)

MESSENGER MDIS uncontrolled mosaics v6, v7, v8 (250 m/pixel)

MESSENGER MDIS partial mosaic (USGS) (200 mpp)

MESSENGER MDIS 2011 albedo partial mosaic (USGS) (200 m/pixel)

Mariner 10 + MESSENGER flyby uncontrolled basemap (USGS) (500 m/pixel)

MESSENGER MLA DTM (665 m)

MESSENGER MDIS M2 flyby stereo-DTM (DLR) (1000 m)

</th> </tr>  
<tr>  
<td>

Standards adhered to

</td>  
<td>

Mapping scale: Tobler (1987); Output scale: USGS; Symbology: USGS FGDC and
other new symbols

</td> </tr>  
<tr>  
<td>

DOI

</td>  
<td>

10.1080/17445647.2016.1193777

</td> </tr>  
<tr>  
<td>

Aims

</td>  
<td>

Morpho-stratigraphic analysis of Mercury's units and BepiColombo target
selection.

</td> </tr> </table>  
<table>  
<tr>  
<th>

Short description

</th>  
<th>

Mercury’s quadrangle H02 ‘Victoria’ is located in the planet’s northern
hemisphere and lies between latitudes 22.5° N and 65° N, and between
longitudes 270° E and 360° E. This quadrangle covers 6.5% of the planet’s
surface with a total area of almost 5 million km2. Our 1:3,000,000-scale
geologic

map of the quadrangle was produced by photo-

interpretation of remotely sensed orbital images captured by the MESSENGER
spacecraft. Geologic contacts were drawn between 1:300,000 and 1:600,000
mapping scale and constitute the boundaries of intercrater, intermediate and
smooth plains units; in addition, three morpho-stratigraphic classes of
craters larger than 20 km were mapped. The geologic map reveals that this area
is dominated by Intercrater Plains encompassing some almost-coeval, probably
younger, Intermediate Plains patches and interrupted to the northwest, north-
east and east by the Calorian Northern Smooth Plains. This map represents the
first complete geologic survey of the Victoria quadrangle at this scale, and
an improvement of the existing 1:5,000,000 Mariner 10-based map, which covers
only 36% of the quadrangle.

</th> </tr>  
<tr>  
<td>

Related products

</td>  
<td>

Geologic Map of the Hokusai Quadrangle (H05), Mercury

Geologic Map of the Shakespeare Quadrangle (H03), Mercury (pre-Planmap)

Geologic Map of the Kuiper Quadrangle (H06), Mercury (prePlanmap)

</td> </tr> </table>  
<table>  
<tr>  
<th>

Units Definition (polygon styling)

</th>  
<th>

Smooth Plains, sp, 255-190-190

Northern Smooth Plains, spn, 245-162-122

Intermediate Plains, imp, 245-122-122

Intercrater Plains, icp, 137-90-68

Crater material-well preserved, c3, 255-255-115

Crater material-degraded, c2, 92-137-68

Crater material-heavily degraded, c1, 115-0-0

Crater floor material-smooth, cfs, 255-255-175

Crater floor material-hummocky, cfh, 205-170-102

</th> </tr>  
<tr>  
<td>

Stratigraphic info

</td>  
<td>

This map has an associated database of craters larger than 5 km used for basic
crater frequency analysis for N(5), N(10), and N(20).

</td> </tr>  
<tr>  
<td>

Other comments

</td>  
<td>

Since the mapping scale (~1:400k) was much higher than the output scale (1:3M)
the polylines of the map were not smoothed.

This map is currently being updated to fit the new controlled MESSENGER's end-
of-mission basemaps.

A post-release boundary merging was done with the H03 and H05 quadrangles.

This map uses a legend also for feature labels.

</td> </tr>  
<tr>  
<td>

Heritage used

</td>  
<td>

former Mariner 10 map by McGill and King (1983)

</td> </tr>  
<tr>  
<td>

Link to other repositories

</td>  
<td>

(crater database link)

(shapefiles database link)

</td> </tr>  
<tr>  
<td>

Acknowledgements beyond Planmap

</td>  
<td>

This research was supported by the Italian Space Agency (ASI) within the
SIMBIOSYS project [ASI-INAF agreement number I/022/10/0]. Rothery was funded
by the UK Space Agency (UKSA) and STFC.

</td> </tr> </table>

Table 1: Exemplary map-wide metadata for PLANMAP products, implemented for a
PLANMAP in-kind contribution (Geologic map by Galluzzi et al., 2016) see
_https://data.planmap.eu/pub/mercury/PM-MER-MS-H02_3cc_01/_

##  Documentation

Documentation of PLANMAP will be available on the project wiki space (
_https://wiki.planmap.eu/display/planmap)_ , which will be kept functional
after project-end based on best-effort and availability of resources. The
internal wiki space is used for both internal project coordination and
technical, scientific documentation. The latter, in evolved form, will be also
shared via the project public wiki space (
_https://wiki.planmap.eu/display/public_ ).

The types of documentation in the PLANMAP wiki include:

  * Summary of relevant activities per WP 

  

  * Procedures and workflows 

  

  * Mapping use case description 

  

  * Best practices and recommendations 

  

  * Tutorials on data handling and mapping 

  

  * Other documents 

  

#  Software

The software used to access and analyze PLANMAP data will be based on Open
Standards, in particular OGC standards. Both Open Source and proprietary
software (such as QGIS, ArcGis, and such like) will therefore be suitable for
accessing PLANMAP data. A particular case is constituted by the software that
is employed for 3d geological modeling, for which open source alternatives
rarely exist. For the choice of the software package two criteria will be
considered: a) the feasibility for the task that will be undertaken b) the
academic licensing scheme that is adopted. Under the same feasibility
conditions, software packages granting low-cost/affordable licensing schemes
for academic purposes will be favored.

The consortium will use a wide range of publicly available Open Source and
commercial tools to work and perform mapping tasks. Additionally algorithmic
and programmatic methods that add value to interactive human-computer mapping
will also use, as far as possible, Open Source tools, packages and libraries.

Software, tools and scripts or snippets developed throughout the project will
be shared both internally and externally via the PLANMAP GitHub organization
and relevant repositories ( _https://github.com/planmap-eu_ ). Some
repositories might be private, with access restricted to beneficiaries, during
the early phases of the project. Ultimately, all will be made public and will
be made available indefinitely after the end of PLANAMP.

**Data exploitation, accessibility and intellectual property**

Intellectual property rights on individual science outputs will be held by the
scientific collaborators and publishing venue/journal (e.g. individual
papers). Data and maps published on the PLANMAP data archive (ESA Guest
Storage facility, INAF, UNIPD or other institutional data repositories) and
their long-term evolution are cited either via their dataset DOI or via
relevant linked publications.

#  Data and metadata

Produced base mapping data are provided as CC-BY (attribution).

Published maps (of any kind) are going to be provided, free to use, with CC-BY
(attribution).

Acknowledgment of the PLANMAP EC H2020 Space project is requested from those
using PLANMAP-derived data. A relevant acknowledgement message will be
included in the documentation provided to ESA, as well as within the global
metadata of VESPA-shared datasets.

#  Documentation

Documentation licensing will follow Creative Commons CC-BY-4.0 (
_https://creativecommons.org/licenses/by/4.0/_ ). Documentation will be also
available, complementing or copying information on the public wiki space, on
GitHub and possibly other public repositories.

At the end of the project the entire body of documentation will be
consolidated and available both on the PLANMAP public (
_https://wiki.planmap.eu/display/public_ ) wiki and Github (
_https://github.com/planmap-eu_ ).

#  Software

Software developed by PLANMAP partners is going to be open source, with the
possible exception of specific software involving SMEs (e.g subcontracted
within virtual-reality tasks). GPLv3 is recommended, or any other license
covered by the Open Source initiative (
_https://opensource.org/licenses/category_ ).

Specific licensing for WP involving SMEs and potential exploitation beyond the
project of pre-existing or specific technological aspects WP5 will be
established and documented.

Software, tools and scripts produced by PLANMAP will be available as soon as
they are considered usable, on the public GitHub organisation (
_https://github.com/planmap-eu_ ). Private repositories will be used during
the course of the project, but will cease to exist at its end and all will be
made public.

#  Data/Software citation

Archived data used that comes from mission archives will follow the custom of
quoting experiment description papers and eventual relevant follow-up papers
(e.g. Malin et al., 2007; McEwen et al., 2007; Neukum et al., 2004; Jaumann et
al., 2007).

Datasets from NASA/ESA archives (PDS, PSA) follow the citation requirements of
those archives. In the case of NASA public domain data, the experiment-
description papers (e.g. Malin et al., 2007) would be cited in scientific
publications. ESA data follow similar citation styles (suggested citations are
included in the PSA entry pages).

Datasets produced by the PLANMAP consortium will be possibly quoted via:

  * Relevant peer-reviewed publications or published maps indicated in the dataset metadata (similar to PSA/VESPA) 

  

  * Dataset-specific DOI, i.e via OpenAIRE/Zenodo/GitHub for relevant datasets 

  

  * Eventual additional DOI-generating data services that might become available during the project lifetime 

  

#  Data storage and management during project

During day-to-day operations and technical/scientific activities of the
consortium, data will be stored on each partner's premises as well as, when
relevant, on shared network resources (such as cloud, FTP and web mapping data
access services). In principle, data will be made publicly available as soon
as possible during the project, respecting publication embargoes.

#  Data curation, archiving, preservation and security Data curation

Base data and maps (See Annex A) undergo archiving review by the archive
maintainers (PDS, PSA). If any issue is encountered (e.g. missing or
problematic labels, metadata and/or eventual problems with data themselves)
the PLANMAP consortium will share those information with respective archive
data publishers (PDS, PSA).

Mapping is an iterative, interactive process that will go through a few levels
of interactive, informal and formal scientific review within the PLANMAP
partners and consortium. Before a final map is produced (and its related
scientific publication is submitted), preliminary versions will be shared on
the PLANMAP web page, wiki and web-mapping data access page (
_https://maps.planmap.eu/_ and its file-based access site on
_https://data.planmap.eu/_ ).

In case underlying base mapping data require or are subject to improvements
that will affect the mapping, newer versions will be used and posted and
metadata updated.

#  Data preservation

Input data (based data and maps) are preserved by the respective archives and
not under PLANMAP responsibility.

Custom higher-level data imagery, cubes, virtual environments and 3D models
produced by PLANMAP partners during the course of the project will be
preserved on PLANMAP storage services. After the project data will be shared
(See Data Sharing subsection), optimally with some redundancy and in different
geographic locations, for longer-term availability.

#  Data security

The PLANMAP data processed, produced and analysed are not sensitive. No
specific security measures are planned. Data recovery, in case of storage
failures will be optimised by the use of central backup and local copies
across PLANMAP partner institutions.

#  Data sharing

Data sharing will be performed via 4 possible channels:

  * Individual partners. E.g., on own web site or repositories using industry standards for geodata (e.g. web-GIS) 

  

  * PLANMAP consortium, via web-gis and data-access web page, linked form the PLANMAP web page 

  

  * ESA PSA, upon delivery of data and mapping products 

  

  * VESPA, via distributed VO-compliant systems for integrated mapping products and, in the future, potentially sub-map, mapping unilt-level access (e.g. individual mapping units). 

  

##  EPN-TAP VESPA-based sharing on premise

VESPA-shared data contain data-product-level metadata pointing to actual data
sources. The release of data (see DoA) is planned in steps, to conclude by the
end of the project.

**Exemplar metadata for mapping products to be released via VESPA:**

A set of mandatory, documented metadata for VESPA services exists (
_https://voparisconfluence.obspm.fr/display/VES/Implementing+a+VESPA+service_
), plus optional ones. Those are mostly related to data-products (in PDS
sense) with some datasetwide. Individual unit granularity is not yet covered
by VESPA technical capabilities.

New developments of VESPA (currently not implemented, but envisaged for future
VESPA developments within the lifetime of PLANMAP) should allow for
metadatabased discovery and search that could extend the geographic data
search and experiment metadata search with feature/unit data/metadata search.

##  ESA PSA data deliveries

Individual used data products already existing in planetary archives (PDS,
PSA) will not be released to PSA (already in PDS in either raw or processed
form).

**Exemplary metadata for mapping products to be released via PSA:**

Release to PSA of non-PDS data geological mapping data, with relevant
documentation of a minimum of:

  * target body 

  

  * geographic extent (bounding box) of mapping product 

  

  * CRS 

  

  * additional fields as described in the Map-wide metadata table in the above sections. 

  

Data exchange formats for archived data will include:

  * For raster data = preferentially Geotiff 

  

  * For vector data = preferentially OGC/Geopackage 

  

  * Additional files or the same version of release raster files also provided in different formats might include eg. ISIS3 cube (.cub) format, Envi (.img + .hdr) or alike. 

  

A copy of the data in either geotiff (raster) and Geopackage (vector) will be
provided in any case, where relevant.