International GNSS Service (IGS), the European Permanent Network (EPN) and the
Slovenian national network SIGNAL could be used in GIMS.

GNSS auxiliary data must be used as well, i.e. satellite orbits, satellite
clocks, antenna phase center offsets/variations, etc. These will be collected
from various online repositories such as those of IGS.

#  SAR

For the SAR data analysis, the following data will be used: a digital terrain
model, land cover maps and optical orthoimages of the study area.

Besides the generation of the ground deformation products, the SAR raw data
will not be directly used for end users or other purposes. By contrast, the
derived products (quantitative results) can be used by different entities,
e.g. research institutions working in earth sciences, geological surveys
(national and regional), civil protection (national and regional), local
administrations, infrastructure owners, etc.

#  MEMS

Generally speaking, time series of raw inertial measurements of low-cost MEMS
sensors of essentially static nature are unlikely to be of interest to other
groups other than those working on comparable topics. However, negative
statements are not easily provable. Subsets of these time series around the
times of strong motion signals may be of higher interest and therefore the
amount of data to be stored and made available to other groups can be reduced
to periods of several minutes as opposed to the storage of full, uninterrupted
data sets.

The likelihood of further use of IMU data by other groups is unpredictable.

#  Geological Data

Geological maps and other existing geological data will be used to identify
the source of movements (i.e natural background, anthropogenic influence).

#  2\. FAIR data

Data should follow the FAIR logic, so they have to be findable, accessible,
interoperable and reusable (FAIR).

**MAKING DATA FINDABLE**

To allow project data to be findable, data produced in the GIMS project will
be discoverable with metadata.

The naming conventions will be as follows:

  * Raw data: 

    * GNSS observations: MMMMDDDS.YYo, where MMMM is a 4-character marker name, DDD is a 3-digit day-of-year (from 001 to 366), S is a session id (default: “0” for daily files, letters from “a” to “x” for hourly files), YY is a 2-digit year (e.g. “18” for 2018); 

  

    * SAR data: the naming convention of the European Space Agency archives  1  will be used; o IMU/MEMS data: the same naming convention as for GNSS observations will be used. 

  

  

  * Quantitative results: 

    * ground deformation maps: convention to be agreed with project partners; 

  

    * ground deformation time series: NNNWWWWD.snx, where NNN is 3-character network id, WWWW is a 4-digit GPS week number, D is a 1-digit day-of-week (from 0 to 6, with 0 = Sunday). 

  

  

Search keywords, and version numbers will not be used since they are not
consistent with the kind of data managed during the project.

Metadata will be created for quantitative results only, namely:

  * for ground deformation maps: 

    * number of SAR used images o covered period o SAR image dates 

  

    * basic information on the type of processing o information on the key processing parameters o quality index for deformation velocity values - for ground deformation time series: 

  

    * GNSS station marker name o GNSS processing technique o time series start date o time series end date 

  

    * maintenance information 

  

  

##  MAKING DATA OPENLY ACCESSIBLE

The following data accessibility policy will be followed:

  * Raw data: 

    * GNSS observations produced by GIMS units: openly available upon request; 

  

    * SAR data: Sentinel-1 raw data are publicly available; no intermediate data will be made public; 

  

    * IMU/MEMS data produced by GIMS units: simulated IMU raw data will be confidential; actual IMU raw data will be openly available upon request. 

  

  

  * Quantitative results: 

    * ground deformation maps: openly available after decision on a case-by-case basis; o ground deformation time series: openly available after decision on a case-by-case basis. 

  

  

Openly available data will be made accessible by deposition in an online
repository (e.g. Amazon S3). The appropriate tools and documentation to access
the data will be provided, if needed (e.g. Amazon S3 “AWS CLI” tool, that is
freely available).

The option of using Amazon S3 will be evaluated by the GIMS consortium. GReD
already has an Amazon AWS account, where a GIMS-specific repository could be
created and managed.

Access to openly available datasets will be provided upon request by the
interested party, by filling in a registration form on the GIMS website. The
registration form will include the following information:

  * Name/Institution of the requesting party 

  

  * Contact information (email address) 

  

  * Data type (GNSS observations / actual IMU raw data / ground deformation map / ground deformation time series) 

  

  * Time period (from date – to date) 

  

The GIMS consortium does not foresee the need of a data access committee.

Data processing software will not be made available as open source code, since
the GIMS project has a strong market uptake aim.

##  MAKING DATA INTEROPERABLE

Data produced in the GIMS project will adhere to widely adopted standard
formats, in particular facilitating the compatibility with available open
applications. In this respect, GIMS data are interoperable.

Standard and open formats will be chosen whenever possible. Otherwise, format
specifications will be defined and provided.

##  INCREASE DATA RE-USE

Openly available data will be licensed under a Creative Commons Attribution-
NonCommercialNoDerivatives 4.0 International (CC BY-NC-ND 4.0) license (
https://creativecommons.org/licenses/by-ncnd/4.0/)

The existing data from selected pilot areas for validation of GIMS provided
data cannot be re-use by third parties, if the owner of data is a private
company

Data will be made available for re-use after the end of the GIMS project
(November 2020) and they are intended to remain re-usable indefinitely.

Due to the innovative nature of the project, at the moment it is not possible
to define the final quality assurance processes yet.

#  3\. Allocation of resources

Person/months needed to adhere to FAIR guidelines are already included in the
planned GIMS effort.

Direct costs associated, for example, to Amazon S3 storage are eligible as
part of the Horizon 2020 grant.

Dr. Lisa Pertusini of GReD will be responsible for data management for the
GIMS consortium.

Long-term preservation of the project data and results will be valuable to
GReD in terms of exposure, thus GReD will consider the feasibility of
allocating the resources needed to do that.

**4\. Data security**

Amazon S3 guarantees state-of-the-art data security.

#  5\. Ethical aspects

GIMS project does not deal with personal data gathered through questionnaires
for research purpose. No ethical aspects are considered to be relevant within
this project.

#  6\. Other issues

No other issues arise with respect to GIMS data.

We do not make use of other national/funder/sectorial/departmental procedures
for data management.