#  Introduction

The major aim of the GeoTwinn project is to significantly strengthen Croatian
Geological Survey (HGI-CGS)’s research potential and capability. HGI-CGS will
benefit from a range of research tools, technologies, software and methods at
the disposal of GEUS and BGS-UKRI. The project will also develop active
collaboration and partnership between people; involving talented scientists
within HGI-CGS and highly productive scientists within GEUS and BGS-UKRI, who
in a number of cases are world-leading experts in their field. Two-way
scientific exchanges and training programs will support HGI-CGS to strengthen
research in four important geoscience subject areas, which are at the core of
most world-leading geological surveys and geological research institutes:

  1. 3D geological surveying and modelling; 

  

  2. Advanced groundwater flow and contaminant transport modelling; 

  

  3. Geological hazards; 

  

  4. Geothermal energy. 

  

  

GeoTwinn, being Twinning project under Coordination and Support Action
programme, **will not collect new data** . The training programs will mainly
use existing data already at disposal to HGI-CGS. Data issued from other
providers (INA, City of Zagreb, etc.) will be used as requested by the owners.
All results from the GeoTwinn project will be integrated in the Digital
Academic Archives and Repositories (  _DABAR_ )  , under open access licence.
As defined in  _Guidelines on FAIR Data Management in Horizon 2020_ ,
GeoTwinn will ensure that all data produced through the project actions are
findable, accessible, interoperable and reusable (FAIR).

This document is considered to be a living document; therefore it will be
continuously updated during the project.

#  Data summary

What is the purpose of the data collection/generation and its relation to the
objectives of the project?

The GeoTwinn project aims to deliver a coordinated and targeted programme of
training, knowledge exchange and collaboration, involving world-leading
experts, to embed cutting-edge research techniques, tools and knowledge within
HGI-CGS, leading to a significant and measurable improvement in their
geoscientific research capability. The data collected for the project will
enable learning of data storage and manipulation, which will enable building
of complex geological models. Namely, the training sessions are based on real
data, enabling development of representative geological models.

What types and formats of data will the project generate/collect?

Data of diverse types will be collected and produced at all stages of the
project. Workflows for data manipulation and storage will be developed
according to the planned deliverables. Types, formats, origin and estimated
size of data are listed below ( **Table 1** ).

Most of the data used for training will mainly originate from HGI-CGS.

**Table 1** : Types and formats, origin of the data and estimated size of data
used/produced in GeoTwinn per each WP (*Common typical geological import
formats, but not limited to; **Common typical geological export + custom
formats, but not limited to)  
  
<table>  
<tr>  
<th>

**WP**

</th>  
<th>

**Software used**

</th>  
<th>

***Input formats**

</th>  
<th>

****Output formats**

</th>  
<th>

**Origin of the data**

</th>  
<th>

**Size of the data**

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

**1.1**

</td>  
<td>

GeoVisionary

</td>  
<td>

*.mxd, *.mve, *.sess, 

*.xml, *.xls, 

*.dxf, *.dat*.dat, *.txt, *.csv, *.xyz, *.tsv 

*.dat, *.txt, *.csv, *.asc*.dat, 

*.cps, *.cps3, *.dat, *.grd, *.flt, *.* 

*.dem *.tif *.tiff *.jpg *.jp2 *.gif *.img *.png *.adf *.dt0 *.bmp *.bt *.ntf *.ter 

*.hgt *.dim *.dt *.ecw *.ers *.fits *.lan *.gis 

*.nat *.vrt *.bag *.blx *.xlb *.grb *.kap *.adf *.mpr *.xpm *.doq*.shp *.kml *.tab *.adf *.e00 *.ntf, *.map, *.dat, *.ecl, *.GRDECL, *.DATA, *.GRID, *.EGRID, 

*.mve, *.int, *.off, *.OFF, *.db, *.ihf, *.idf, *.gp, *.pl, *.mx, *.ts, *vs,*so, *.wl, *.gpx, 

*.dat, *.p701, *.flt,*.dat, *.asc*.ext, *.obj, *earth, *.dat, *.bin*.segp, *.segy, *.sgy, *.seg, *.sg, *.dat, *.vrml, *.wrl, *.iv, *.3ds, 

*.dat, *.dat, *.zmap, *.3di, *.lin, *.flt, 

*.dat, *.out, *.krg, *.xyz 

</td>  
<td>

*.mxd, *.mve, 

*.sess, 

*.dat, 

*.txt,*.csv, 

*.asc*.dat, 

*.txt,*.csv, 

*.asc*.dat, 

*.txt,*.csv, *.asc 

*.dat, *.tif *.tiff *.jpg *.jp2 *.gif 

*.img *.png, 

Grids and

Mesh surfaces, seismic and

well formats, 3D pdf, etc.

</td>  
<td>

HGI-CGS, City of Zagreb, Croatian

Hydrocarbon

Agency

</td>  
<td>

Up to 10 Gb, possible

more

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

SIGMA

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

SKUA-GOCAD

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

NERC-BGS

GROUNDHOG DESKTOP

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

Midland Valley MOVE

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

**1.2**

</td>  
<td>

Landmark

DecisionSpace

\+ OpenWorks

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

**2.1**

</td>  
<td>

ArcGIS

</td>  
<td>

Raster, shp, dxf, pdf, xls, csv, dat, txt, asc, dem, tif, tiff, jpg

</td>  
<td>

Raster, shp, mxd, pdf, tif, tiff, jpg, txt, asc, dat, csv, pdf, xls, gpr

</td>  
<td>

HGI-CGS, DHMZ,

Hrvatske vode,

Zagrebac ki holding,

Vodovod i odvodnja

(VIO),

Zapres ic , VG

Vodoopskrba,

ZGOS

</td>  
<td>

<100 Gb

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

GMS

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

**2.2**

</td>  
<td>

R, ArcGIS

</td>  
<td>

Txt, csv, xls, raster, shp

</td>  
<td>

Txt, csv, xls, pdf, raster, shp, pdf

</td>  
<td>

HGI-CGS,

Freely available data

</td>  
<td>

1-10 Gb

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

**3**

</td>  
<td>

Socet Set

</td>  
<td>

Raster, shp

</td>  
<td>

Raster, shp, pdf

</td>  
<td>

HGI-CGS, safEarth,

Freely available data

</td>  
<td>

<100 Gb

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

Geovisionary

</td>  
<td>

Raster, shp

</td>  
<td>

Raster, shp, pdf

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

ArcGIS

</td>  
<td>

Raster, shp

</td>  
<td>

Raster, shp, pdf

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

R

</td>  
<td>

txt, csv, xls

</td>  
<td>

txt, csv, xls, pdf

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

Matlab

</td>  
<td>

txt, csv, xls

</td>  
<td>

txt, csv, xls, pdf

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

**4**

</td>  
<td>

PhreeQC

</td>  
<td>

Excel (.xlsx)

</td>  
<td>

Excel (.xlsx)

</td>  
<td>

DARLINGe project,

HGI-CGS

</td>  
<td>

<100 Gb

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

FEFLOW

</td>  
<td>

Raster, shp, dxf, pdf, xls, csv, dat, txt, asc, dem, tif, tiff, jpg

</td>  
<td>

fem, dac, mxd, raster, shp, pdf

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

ArcGIS

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

Will you re-use any existing data and how?

Being Coordination and Support Action project, GeoTwinn training procedures
will rely on **existing or generated data exclusively** .

Knowledge and data produced within this project is also expected to be the
basis for further research activities beyond this project in the host
organisation. The continued collaboration between the partner organisations
and their wider international research networks is also expected.

What is the origin of the data?

Origin of data is shown in the **Table 1** .

What is the expected size of the data?

The expected size of data for each WP is shown in the **Table 1** .

To whom might it be useful ('data utility')?

The project outputs mainly target project partners, scientific and other
communities, including universities and research institutes.

#  FAIR data

##  Making data findable, including provisions for metadata

Are the data produced and/or used in the project discoverable with metadata,
identifiable and locatable by means of a standard identification mechanism
(e.g. persistent and unique identifiers such as Digital Object Identifiers)?

Metadata for the GeoTwinn will be made available through HGI-CGS repository
within DABAR (Digital Academic Archives and Repositories) system which can be
found at  _https://repozitorij.hgi-cgs.hr_ .

_DABAR_ provides technological solutions that facilitate maintenance of higher
education and science institutions' digital assets. DABAR provides a
possibility of open access publishing and increasing the visibility of the
content and the institution itself, reliable long-term data storage and
implements and promotes standard data exchange protocols (OAI-PMH).

Regarding the standard identification mechanism, every publish object will
have unique identifier which is called URN:NBN number.

All results produced in this project will be openly accessible for further
usage.

What naming conventions do you follow?

All repositories in DABAR have implemented an OAI-PMH interface. Supported
schemes are Dublin Core (DC) and Metadata Object Description Schema (MODS).

Will search keywords be provided that optimize possibilities for re-use?

Search key-words will be taken from thesauri of HGI-CGS repository and will be
provided for optimising the possibility of re-usage of the data.

Do you provide clear version numbers?

GeoTwinn will provide clear version numbers for all published documents.

What metadata will be created? In case metadata standards do not exist in your
discipline, please outline what type of metadata will be created and how.

To ensure that objects are searchable, every object placed in repository has
to be described using a prescribed set of metadata during upload. All
repositories in DABAR have implemented an OAI-PMH interface. Supported schemes
are Dublin Core (DC) and Metadata Object Description Schema (MODS) which
provide standards for our discipline.

##  Making data openly accessible

Which data produced and/or used in the project will be made openly available
as the default? If certain datasets cannot be shared (or need to be shared
under restrictions), explain why, clearly separating legal and contractual
reasons from voluntary restrictions.

All results of the analysis produced during this project will be made openly
available through the HGI-CGS repository which can be found at
_repozitorij.hgi-cgs.hr,_ or at the HGI-CGS webpage at  _www.hgi-cgs.hr_ .

Note that in multi-beneficiary projects it is also possible for specific
beneficiaries to keep their data closed if relevant provisions are made in the
consortium agreement and are in line with the reasons for opting out.

At this moment there is no reason for opting out of open access regarding
publishing any of the results generated by GeoTwinn project.

How will the data be made accessible (e.g. by deposition in a repository)?

All data will be made accessible by deposition in an open access repository
stated above.

What methods or software tools are needed to access the data?

No special methods or software tools will be needed for accessing the data
because the data will be placed on open access repository in open access
formats (xsd, xslt, etc.).

Is documentation about the software needed to access the data included?

Reports containing data produced by this project will provide list of software
needed for accessing the provided data.

Is it possible to include the relevant software (e.g. in open source code)?

At this point, it won’t be possible to include the relevant software in open
source code. But, all results will be published in open formats (xsd, xslt,
etc.) in an open access repository.

Where will the data and associated metadata, documentation and code be
deposited? Preference should be given to certified repositories which support
open access where possible.

Produced data and documentation regarding that data, will be deposited in a
HGI-CGS’s

repository that can be found at  _https://repozitorij.hgi-cgs.hr_ and which is
openly accessible.

Have you explored appropriate arrangements with the identified repository?

There is a possibility for our official HGI-CGS repository to be listed in
OpenDOAR. OpenDOAR (Directory of Open Access Repositories) is a controlled
directory of academic repositories with open access content. It is available
at  _http://www.opendoar.org/_ and encompasses various types of repositories.

If there are restrictions on use, how will access be provided?

Open access will be provided for all data produced through GeoTwinn project.

Is there a need for a data access committee?

At this point, we do not believe data access committee will be needed.

Are there well described conditions for access (i.e. a machine readable
license)?

Conditions for access are well described.

##  Making data interoperable

Are the data produced in the project interoperable, that is allowing data
exchange and re-use between researchers, institutions, organisations,
countries, etc. (i.e. adhering to standards for formats, as much as possible
compliant with available (open) software applications, and in particular
facilitating re-combinations with different datasets from different origins)?

As already mentioned, our repository in DABAR has implemented OAI-PMH
interface which supports following schemes: Dublin Core (DC) and Metadata
Object Description Schema (MODS) which will be used for describing general
data i.e. Title, Author, Coauthors, owner of the data etc.

GeoTwinn also considers using Open Geospatial Consortium (OGC) open standards
or INSPIRE (INfrastructure for SPatial InfoRmation in Europe) standards for
specific, geospatial data.  _OGC_ is an international, not for profit
organization, committed to making quality open standards for the global
geospatial community.

_INSPIRE_ is dealing with metadata in the domain of European Spatial Data
Infrastructure. The thematic, semantic background of INSPIRE is environmental
protection.

INSPIRE has not yet implemented mandatory new version of HRN ISO 19115: 2014
norms but this can be expected in short period of time (in year 2019).

In the way described above, we will assure all data produced by GeoTwinn
project will be interoperable.

What data and metadata vocabularies, standards or methodologies will you
follow to make your data interoperable?

GeoTwinn will use Open Geospatial Consortium (OGC) open standards, as well as
OAI-PMH interface which supports DC and MODS schemes, on DABAR.

Will you be using standard vocabularies for all data types present in your
data set, to allow inter-disciplinary interoperability?

In order to provide inter-disciplinary interoperability, we will use standard
vocabularies for all data types in our data sets.

In case it is unavoidable that you use uncommon or generate project specific
ontologies or vocabularies, will you provide mappings to more commonly used
ontologies?

In case of usage of uncommon or even generate project specific ontologies or
vocabularies, we will provide mapping to more commonly used ontologies.

##  Increase data re-use (through clarifying licences)

How will the data be licensed to permit the widest re-use possible?

The use of the DABAR is free of charge for any use, including public, private
and commercial use, according to the license.

All results produced in GeoTwinn will have Creative Commons Attribution (CC
BY) licence which will allow the widest re-use possible.

Any and all Intellectual Property Rights (IPR) in the geological data provided
by the DABAR are and shall remain the exclusive property of their respective
right holders.

When will the data be made available for re-use? If an embargo is sought to
give time to publish or seek patents, specify why and how long this will
apply, bearing in mind that research data should be made available as soon as
possible. Not applicable. The data will be re-usable from the moment they are
published.

Are the data produced and/or used in the project useable by third parties, in
particular after the end of the project? If the re-use of some data is
restricted, explain why.

All data produced by GeoTwinn project will be usable by any third parties,
especially after the end of the project.

How long is it intended that the data remains re-usable?

There is no period of time intended for the data to remain re-usable. Once
they will be published in open access on repository, they are planned to
remain publicly available.

Are data quality assurance processes described?

Not applicable. At this moment, DABAR doesn’t have descriptions regarding
quality assurance processes.

#  Allocation of resources

What are the costs for making data FAIR in your project?

At this moment, we cannot estimate total cost of making data FAIR in our
project.

How will these be covered? Note that costs related to open access to research
data are eligible as part of the Horizon 2020 grant (if compliant with the
Grant Agreement conditions).

The data will be published in open access free of charge, where possible. In
other cases authors of scientific publications will use green or gold open
access option. The costs will be partially covered from the budget of the
project.

Who will be responsible for data management in your project?

The lead partner (HGI-CGS) and its representative will be responsible for data
management. The management decisions should be approved by Coordination Board
of the project.

Are the resources for long term preservation discussed (costs and potential
value, who decides and how what data will be kept and for how long)?

The use of the DABAR is free of charge for any use, including public, private
and commercial use, according to the license. All data produced in GeoTwinn
will have Creative Commons Attribution (CC BY) licence which will allow the
widest re-use possible.

#  Data security

What provisions are in place for data security (including data recovery as
well as secure storage and transfer of sensitive data)? Is the data safely
stored in certified repositories for long term preservation and curation?

The data will be safely stored in certified repository (
_https://repozitorij.hgi-cgs.hr_ )  for long term preservation. As GeoTwinn
doesn’t use, collect or preserve any sensitive data, no sensitive data will be
stored on repository.

#  Ethical aspects

Are there any ethical or legal issues that can have an impact on data sharing?
These can also be discussed in the context of the ethics review. If relevant,
include references to ethics deliverables and ethics chapter in the
Description of the Action (DoA).

There aren’t any ethical or legal issues that could have any impact on data
sharing at this moment. For more information, we have prepared a document
regarding ethic issues, which is also one of the Deliverables for this project
(D7.1 POPD Requirement No. 1) and will be uploaded by the end of March 2019.

Is informed consent for data sharing and long term preservation included in
questionnaires dealing with personal data?

Statements regarding General Data Protection Regulation (GDPR) include
informed consent for data sharing and long term preservation.

#  Other issues

Do you make use of other national/funder/sectorial/departmental procedures for
data management? If yes, which ones?

No other national/funder/sectorial/departmental procedures for data management
have been used for purposes of creating this DMP.