Topic: LCE 16 – 2014 Understanding, preventing and … · · 2016-06-061 Topic: LCE 16 – 2014 Understanding, preventing and mitigating the potential environmental impacts and

1

Topic: LCE 16 – 2014 Understanding, preventing and mitigating the potential environmental impacts and risks of shale gas exploration and

exploitation

Project number: 640896

Project name: SHale gas Exploration and Exploitation induced Risks

Project acronym: SHEER

Start date: 01/05/2015 Duration: 36 months Deliverable reference number and title: D2.2 Report on data availability, data comprehensiveness and metadata. Special interest for: WP2 Compilation of the SHEER database, WP1, WP3-WP7, Scientific user community (including researchers from outside SHEER project), training and educational institutions Version: Due date of deliverable: M6 Actual submission date: M6 AUTHORIZED: Paolo Gasparini 05/11/2015 Dissemination Level PU Public

PP Restricted to other programme participants (including the Commission Services)

RE Restricted to a group specified by the consortium (including the Commission Services)

CO Confidential, only for members of the consortium (including the Commission Services) X

This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 640896.

2

Note about contributors The following organizations contributed to the work described in this deliverable: Lead partner responsible for the deliverable: IGF PAS Deliverable prepared by: Dorota Olszewska Monika Staszek Beata Orlecka-Sikora Grzegorz Lizurek Janusz Jarosławski Other contributors: KNMI Dirk Kraaijpoel Bernard Dost KeU Peter Styles Sam Toon AMRA Matteo Picozzi Partner responsible for quality control: RSK Deliverable reviewed by: Andrew Gunning

3

Acknowledgement The research leading to presented results has received funding from the EC HORIZON2020 Programme under grant agreement n° 640896.

4

Content Abstract 5 List of Figures 6 List of Tables 7 1 Introduction 8 2 SHEER data repository 10 3 SHEER data availability and comprehensiveness 18 3.1 LUBOCINO Shale Gas 19 3.2 PREESE HALL Shale Gas 20 3.3 BECKINGHAM SITE conventional hydrocarbon production 20 3.4 GRONINGEN FIELD conventional hydrocarbon production 21 3.5 GROSS SCHONENBECK geothermal energy production experiment 21 3.6 THE GEYSERS geothermal energy production 22 3.7 On-site monitoring in Wysin, Pomerania, Poland 24 Appendices 26 Appendix 1 The SHEER database inquiry filled by data providers 26 Appendix 2 Form of MAT file catalogue 35 Appendix 3 Form of MAT file Generic Data Format 41

5

Abstract

Keywords: database, data integration, inducing technology One of the deliverables of the SHEER project is the SHEER database where data from on-site monitoring of shale gas exploration – exploitation operations at the Wysin Site will be integrated. Moreover, the database will gather the data from several past case studies concerning various types of impacts from related technologies. Before the data is integrated its availability and data comprehensiveness should be verified. Therefore, it was necessary to verify the availability of data which was planned to be integrated and its completeness within each episode. It was also crucial to evaluate the data in terms of both additional processing and preparation and data format homogenization. Finally, data from six past case studies has been accepted for integration within SHEER Database.

6

List of Figures

Figure 1 Scheme of functionalities of Local Data Centre for SHEER database purpose. 11Figure 2 Screenshot of CIBIS service of Local Data Centre for SHEER data collection and

managing. This service enables to load, delate, copy and upload the data, validate and run conversion of the data, set or change source of the data.

12

Figure 3 Screenshot of CIBIS service of Local Data Centre for episode data configuration. 12Figure 4 Screenshot of CIBIS service of Local Data Centre for schemes. Metadata are created

for files and the directories using xml formats.13

Figure 5 Interface of Local Data Centre service for documents management. 13Figure 6 Structure of the data for episode. Green rectangle represents the episode and the blue

ones the directories. 15

Figure 7 Episode Quality Control Workflow 17Figure 8 Service for the presentation and data access to Gross Schoenebeck episode. 23Figure 9 Service for Gross Schoenebeck episode borehole trajectory visualisation. 23Figure 10 Service for Gross Schoenebeck episode integrated visualisation. 24

7

List of Tables

Table 1 SHEER database episodes 10Table 2 List of metadata fields. 14Table 3 Detailed description of episode metadata. 16Table 4 Detailed description of directory metadata 16Table 5 Detailed description of file metadata 16Table 6 Data planned to be integrated from past case studies 18Table 7 LUBOCINO Shale Gas data accepted for integration 19Table 8 PREESE HALL Shale Gas data accepted for integration 20Table 9 BECKINGHAM SITE conventional hydrocarbon production data accepted for

integration 20

Table 10 GRONINGEN FILD conventional hydrocarbon production data accepted for integration

21

Table 11 GROSS SCHONENBECK geothermal energy production experiment data integrated.

22

Table 12 THE GEYSERS geothermal energy production data accepted for integration 22

8

1 Introduction

One of the key objective of SHEER project is the compilation of database comprising already existing and new multidisciplinary data concerning the shale gas exploitation test sites, processing procedures, results of data interpretation and recommendation as well as other documents describing the state of the art. The database is planned to include also data from conventional hydrocarbon exploration and enhanced geothermal fields involving fluid injection used as a proxy. The complex relationships between human technological activity, such as the shale gas exploitation, on the environment, and the environment’s response require a holistic approach. An insight into these relationships can result only from cross-disciplinary studies of the interaction of technology and the natural environment. . It is obvious that a serious analysis of the environment’s response, that is the result, cannot be done without a simultaneous analysis of conditions of the technological activity, that is the cause. To reach the required comprehensiveness of the collected case studies, the time series – seismic waveforms, groundwater flow and water chemistry parameters, air pollution parameters as well as parameters determining the technological activity – should be complemented with relevant static geo-data. For such case, there are many issues that should be taken into account while designing the SHEER data repository, for example data collection, preservation, quality control, integration and availability. Moreover, whilst each research infrastructure is separately concerned with the integration of data within its domain, it is also important to find a robust means to integrate data across disciplines. Diversity of the research infrastructure in SHEER database requires to develop an over-arching structure for higher-level integration. The data should be also supplemented with descriptive and readable metadata. The multidisciplinary character of the problem undertaken in SHEER project means that the data to form the SHEER database will be inhomogeneous. Furthermore, even within the SHEER problem components, seismic, water, air, the past data are not supported by unique formats. We aim to homogenize and harmonize data from different fields (geophysical, geochemical, geological, technological, etc.) and create and provide access to an advanced database of case studies of environmental impact indicators associated with shale gas exploitation and exploration, which so far does not exist. To preserve and curate the data for long-term use we envision that after the project completion most of SHEER database will be transfer to IS-EPOS e-platform and made available according to the rules of access to TCS AH, which assumes an open access from in and out of research community. The IS-EPOS e-platform, (http://is-epos.grid.cyfronet.pl/) is a prototype of Thematic Core Service Anthropogenic Hazards of Working Group 10 “Infrastructure for georesources” of European Plate Observing System (EPOS) project. It serves to integrate research infrastructure of anthropogenic hazards due to exploration and exploitation of georesources: comprehensive data descriptions of case studies, software services and relevant written materials. Presently being a prototype, the IS-EPOS e-platform will be further developed by WG10 in the framework of EPOS implementation phase, which has already started in September 2015. Access to and sharing of the collected data are recognized by Project Consortium as essential for advancement of science. For this reason all acquired data: seismic, operational and environmental, will be standardized according to the policies of the EPOS WG10, applied in IS-EPOS e-platform and then in TCS AH.

9

The coordinated data management of multidisciplinary set of observational SHEER data will become much more efficient when the datasets are gathered into a database easily accessible by the project partners. Project Consortium decided that the SHEER database will be stored in the Local Data Centre (LDC) in the Institute of Geophysics Polish Academy of Sciences (IGF), which will take responsibility for the technical part of database management. We will establish the technical channels and facilities at IGF Local Data Centre for the acquisition, storage and distribution of datasets. Web-based interfaces will be added to simplify usage for project researchers. The SHEER database should also have the possibility to improve its capacity during the project. It means that the data advanced processing results developed within the other Work Packages of SHEER will be incorporated in the SHEER database. The first step in SHEER database designing process is to gather information about the type and formats of data planned to be uploaded to that base. Therefore, the following actions have been done:

- Revision of the data; The data providers were asked to fill in the SHEER database inquiries1 in order to evaluate the content and the quality of data for every episode.

- Determination of data accuracy and limitations; The SHEER database inquiries were analysed and types of data available and necessary for database compilation were defined. Evaluation of the datasets from the standpoint of their comprehensiveness and data completeness has been done.

- Homogenization of data formats; The SHEER database inquiries were analysed and data which needed additional processing and format changes was determined.

- Metadata preparation. Metadata were prepared following the XML standard format for metadata developed within the IS-EPOS2 project.

In the following chapters we present the result of the analysis of data availability and comprehensiveness as well as the rules for metadata creations. One of the case studies has been already integrated and in the deliverable we present its content. On the basis of the collected information on data we have designed the Local Data Centre with some functionalities to facilitate the process of data integration. This environment is described in the chapter 2.

1 Appendix 1:The SHEER database inquiry. 2 IS-EPOS “DIGITAL RESEARCH SPACE OF INDUCED SEISMICITY FOR EPOS PURPOSES” is co-financed from the funds of the European Regional Development Fund (ERDF) as a part of the Operational Programme Innovative Economy (OP-IE).

10

2 SHEER data repository

Following the EPOS WG10 nomenclature, the basic unit of the database is the episode. The episode is a comprehensive data description of a geophysical (e.g. deformation) process, induced or triggered by human technological activity in the field of exploration and exploitation of georesources, which under certain circumstances can become hazardous for people, infrastructure and/or the environment. The episode consists of a time-correlated collection of geophysical data representing the geophysical process, technological data representing the technological activity, which is the cause of this process and all other relevant geo-data describing the environment, in which the technological activity and its result or by-product, the geophysical process take place. List of the SHEER episodes is provided in Table 1. Table 1 SHEER database episodes

Inducing technology Name Case type WYSIN Shale Gas Present case study LUBOCINO Shale Gas Past case study

Unconventional hydrocarbon extraction

PREESE HALL Shale Gas Past case study BECKINGHAM SITE conventional hydrocarbon production

Past case study Conventional hydrocarbon extraction

GRONINGEN FIELD conventional hydrocarbon production

Past case study

GROSS SCHONENBECK geothermal energy production experiment

Past case study Geothermal energy production

THE GEYSERS geothermal energy production

Past case study

The Local Data Centre will collect the episodes and disseminate them, on a user’s request through dedicated web-interface. The main tasks of the LDC will be:

(1) to register infrastructure providers. LDC will be open for servicing of providers of research infrastructure; (2) to receive data from data providers by data download interfaces. Some episodes will include seismic data recorded continuously by LDC data download interfaces, other processed: triggered signals and seismic catalogues; (3) to convert provided analogue data into a relevant digital form; (4) to convert digital data formats to formats acceptable by TCS AH; (5) to prepare metadata for the received data; (6) to communicate with TCS AH if necessary.

The structure of LDC is presented in the Figure 1. The LCD has been constructed using CIBIS software – the system created to storage, manage, configure, verify and describe data in IS-EPOS project. CIBIS has separate modules to manage:

- Users (which allows to set privileges to the groups of users); - Episodes (which allows to group directories into episodes disregarding to which storage they

are assigned); - Storages (which allows to place directories physically in the server);

11

- Directories, with internal structure created on the basis of a data scheme (which allows not only to add files and directories but also to copy, download, compress, unpack, rename, move or view file contents. All versions of uploaded files are being stored in the system and it is possible to manage these versions.);

- Schemes (which is used to create structure trees inside directories and to define metadata rules and values);

- Configurations (which is used to manage validators and converters. Raw data can be easily converted to chosen format using created converters, e.g. ASCII to mseed converter. Format of integrated data can be easily validated using chosen validators. There is a possibility to add new converters or validators to the system.);

- Data for publication (which is used to set metadata values for selected directories basing on various schema and rules files, which are defined in ‘Schemes’ module).

Modules arranged for SHEER database are: - Storage, - Episodes according to SHEER proposal, - Schema supporting accepted data structure and rules for metadata, - Document repository.

The web-interfaces of the basic services of LDC for SHEER database purpose are presented in the Figures 2-5.

Figure 1 Scheme of functionalities of Local Data Centre for SHEER database purpose.

12

Figure 2 Screenshot of CIBIS service of Local Data Centre for SHEER data collection and managing. This

service enables to load, delate, copy and upload the data, validate and run conversion of the data, set or change source of the data.

Figure 3 Screenshot of CIBIS service of Local Data Centre for episode data configuration.

13

Figure 4 Screenshot of CIBIS service of Local Data Centre for schemes. Metadata are created for files and the

directories using xml formats.

Figure 5 Interface of Local Data Centre service for documents management. Interoperability with EPOS TCS AH is ensured by proper data formats of SHEER data and XML based metadata catalogue. Data in the SHEER database are gathered within the following sections:

- Data relevant for the considered hazards: o Seismic data (e.g. catalogue, signals, information about network); o Water quality data (e.g. physicochemical properties and analysis); o Air quality data (e.g. air properties and analysis); o Satellite data;

- Technological data (e.g. drilling data, fracture data) ; - Other geo-data:

14

The episode must consist of at least one type of data relevant for the considered hazards and geo-data and at least one type of technological data. The seismic data should contain at least seismological catalogue and signals. The catalogue should be prepared as Matlab file in especially organised format3. Corresponding signals (triggered seismograms or accelerograms) or waveforms (continuous data) should be delivered as SEED/miniSEED files (standard format of signals in seismology). The available data can be divided into two categories: data for further processing and data for presentation. The data for presentation provides background for displaying the results of calculations and is supported by GIS software and map-servers. According to the guidelines of the IS-EPOS, SHP format should be used for vector data and GeoTiff for raster data (e.g. scanned maps). These data are not used for calculations but need to be available for the system for visualization purposes. MapServer enables system to visualize all GIS data available in the database for each episode. The data for further processing should be loaded into Matlab/Octave and used for further calculations. Format of that data is GDF mat file4 (Generic Data Format prepared within IS-EPOS). Data prepared in this format can be easily converted to ASCII (CSV) format with homogenous structure. Table 2 List of metadata fields.

Metadata field required for

Metadata field Metadata field description

Episode Directory File Episode Name of episode x episodeOwner Provider of data x Description Long data content description Text Short data content description x Country Data origin localization (country) x Region Data origin localization (region) positionType Type of positioning of the data (point,

polygon) x

coordinateSystem Coordinate system of positioning of the data (e.g. WGS-84)

x

Longitiude Data origin localization (longitude) x Latitiude Data origin localization (latitude) x Start Start time of data End End time of data eventID ID number of seismic event itemType Type of the object (episode, directory, file) x x x Name Name of data file x x x Path Path to the data file x x x dataType Type of data (e.g. waveforms, catalogue,

…) x

inducingTechnology Technology impacting the environment x Type Type of date section (e.g technological,

…) x

3 Appendix 2: Catalogue mat file details 4 Appendix 3: GDF mat file details

15

The SHEER database metadata are prepared in accordance with the guidelines of the IS-EPOS project. Various metadata fields are required depending on the object type (episode, directory or file) (Table 2). Values of metadata are inherited down through the structure of data in the episode. For example, it is enough to set the value of metadata field ‘episode’ (the episode name) for episode and then all directories and files belonging to this episode will have the same value of metadata ‘episode’ as this episode. The detailed description of metadata structure is prepared separately for each object type: episode, directory and file. The structure of the data for every episode is presented in the Figure 6.

Figure 6 Structure of the data for episode. Green rectangle represents the episode and the blue ones the

directories.

16

The data is arranged in the tree structure as it is shown in Figure 6. The values of metadata are inherited down through this structure so information about the episode, like episode owner, country, region or inducing technology, is the same for all object types in the episode and is set only once in the episode metadata. The same rule applies to directories. Information about section type is set in directory metadata (‘type’) and is applied to all files within this directory. Detailed description of episode, directory and file metadata are presented in Tables 3-6. Table 3 Detailed description of episode metadata. Metadata Name Description and option Field is required Name Name of episode Yes Path Episode path Yes ItemType Type of object= episode Yes episodeOwner Owner of episode – one of: IGF PAS, KaU, KNMI, AMRA Yes description Long episode content description No text Short episode content description yes country Episode localization (country)– one of: Poland, United

Kingdom, Netrlands, Germany, USA/California yes

region Episode localization (region)– one of: Pomerania, Lancashire, Beckingham, Groningen, Gross Schoenebeck, The Geysers

No

positionType Type of positioning of the episode – one of: point, polygon yes coordinateSystem Coordinate system of positioning of the episode (e.g. WGS-

84) yes

longitude Episode localization (longitude) yes latitude Episode localization (latitude) yes start Start time of episode No end End time of episode No inducingTechnology Technology impacting the environment – one of:

conventional hydrocarbon extraction, unconventional hydrocarbon extraction, geothermal energy production

yes

Table 4 Detailed description of directory metadata Metadata Name Description and option Field is required name Name of directory yes path Directory path yes itemType Type of object = directory yes text Short directory content description No description Long directory content description No type Type of data section - one of: Data relevant for the

considered hazards, seismic, water quality, air quality, satellite data, technological data, geodata

yes

Table 5 Detailed description of file metadata Metadata Name List of options Field is required name Name of file yes path File path yes itemType Type of object = file yes text Short file content description no describtion Long file content description no dataType Type of data yes start Start time of data no end End time of data no

17

eventID ID number of seismic event no The comprehensive web services allow speeding up the data integration process and reducing/minimizing the possible mistakes while incorporating diverse heterogeneous datasets through quality control. The Figure 7 illustrates the proposed data quality control workflow.

Figure 7 Episode Quality Control Workflow

18

3 SHEER data availability and comprehensiveness

The SHEER data sources belong to 4 categories: 1) an unique data set from shale gas operation sites in Lubocino (Poland) and Preese Hall

(UK); 2) conventional oil and gas production sites (Groningen site in the Nederland, Beckingham

site in UK); 3) sites where stimulation for geothermal energy production and geothermal experiments

took place. They will be included to SHEER database due to their close analogies to the mechanisms of shale gas stimulation and induced seismicity problems and can be used as proxy;

4) An unique component of the SHEER database will come on the monitoring activity performed during the project in one active shale gas exploration and exploitation site in Wysin, Pomerania, Poland. In the framework of the site monitoring in Wysin the seismicity, water conditions and air pollution in the direct vicinity of newly drilled wells with horizontal stimulation will be monitored. The monitoring will begin in the pre-operational period to determine the key baseline of the monitored parameters. An impact of both the exploratory vertical drillings and the horizontal fracking will be followed. The monitoring will be continued after termination of the exploration and appraisal operation in order to assess experimentally protracted environmental effects.

The past case studies data planned to be integrated within the SHEER database according to the proposal of the SHEER project are summarized in Table 6. Table 6 Data planned to be integrated from past case studies

Section Type Data relevant for the considered hazards

Episode Name

Seismic data

Water quality

data

Air quality data

Satellite data

Technolo-gical data

Other geo-data

LUBOCINO Shale Gas X X X X X PREESE HALL Shale Gas

X X X X

BECKINGHAM SITE conventional hydrocarbon production

X X X

GRONINGEN FIELD conventional hydrocarbon production

X X

GROSS SCHONENBECK geothermal energy production experiment

X X X

THE GEYSERS geothermal energy production

X X X

19

During the first phase of the SHEER project the SHEER database inquiries was sent to the data owners to collect information about the data availability and comprehensiveness. The analysis included:

- availability verification of data planned to be integrated; - completeness verification of episode data (mandatory availability of data relevant for the

considered hazards and technological data); - completeness verification of seismic data (mandatory availability of catalogue and signals); - assessment of available data in terms of additional processing and preparation; - assessment of available data formats in terms of format homogenization.

The summary for each episode concerning data availability and further processing as well as preparation or format homogenization necessity is presented below.

Data providers are also obligated to prepare information about the observation network as an inventory.xml file (seiscomp standard). Ground subsidence as the satellite data will be collected for every episode in determined time window.

3.1 LUBOCINO Shale Gas

The owner of data actually did not agree to make seismic data available for SHEER project. Therefore, this episode consist only of water quality data and technological data - production parameters. Production parameters were prepared on the basis of PGING reports and include only fractures date. The summary of data completeness is provided in Table 7. Table 7 LUBOCINO Shale Gas data accepted for integration

Available data Integration No. Name of data Type of data Type of data

section Additional

processing and preparation

Data formats homogenization

1 water level in wells

water level Preparation of tables from reports

Conversion to GDF mat file

2 physicochemical properties of all wells

physicochemical properties

Preparation of tables from reports


3 physicochemical analysis of all wells

physicochemical analysis



4 physicochemical properties of all piezometers

physicochemical properties



5 physicochemical analysis of all piezometers

physicochemical analysis

Data relevant for the considered hazards/ water quality data



6 basic production parameters

production parameters

Technological data

Preparation of table from reports


7 stratigraphy of well no. 1

wells stratigraphy Other geo-data Preparation of picture from reports

Conversion to geotiff

20

3.2 PREESE HALL Shale Gas

This episode contains data relevant for the considered hazards (seismic): catalogue and waveforms. There is no detailed information about the catalogue. The long list of available technological data and geo-data was presented in the proposal of the project. There is no information about the formats of those data so additional availability verification is needed for both technology data and geo-data. Additionally, at least data format homogenization of all data is needed. The summary of data completeness is provided in Table 8. Table 8 PREESE HALL Shale Gas data accepted for integration


section Additional



1. Waveforms (seismograms)

waveform Conversion to seed file

2. Signals (seismograms)

Signal Triggering of continuous data and conversion to seed file

3. Preese Hall catalogue Catalogue Not needed Conversion to mat file

4. 3-D Seismic Reflection Data (post-Frac)

seismic profile Not needed- Conversion to GDF mat file

5. 2-D Heritage Seismic Reflection Data (pre-Frac)

seismic profile

Data relevant for the considered hazards/seismic

Not needed Conversion to GDF mat file

3.3 BECKINGHAM SITE conventional hydrocarbon production

This episode theoretically contains seismic data in the form of signals recorded on the surface and in the borehole and seismic profile. There is no information about availability of BECKINGHAM SITE catalogue and technological data. The owner of the data informed about troubles with collecting real data from that episode. Owing to the absence of catalogue and technological data this episode would not be integrated in the SHEER database. The data Owner proposes that other episodes from different sites will be used instead of data from the Beckingham site, which will be selected in the next phase of the project. The summary of data completeness is provided in Table 9. Table 9 BECKINGHAM SITE conventional hydrocarbon production data accepted for integration


section Additional




Signal Conversion to seed file

2. Signals (accelerograms)

Signal Conversion to seed file

3. Beckingham site catalogue

catalogue Preparation of catalogue

Conversion to mat file

4. Vertical seismic profile of wells before and after experiment

seismic profile

Data relevant for the considered hazards/seismic


21

3.4 GRONINGEN FIELD conventional hydrocarbon production

This episode is also represented by seismic data in the form of surface accelerograms and borehole seismograms. The catalogue comprises more than 800 events with local magnitude range from -0.5 up to 3.6. The geo-data is also available in the form of velocity model. The data provider mentioned also that some technological data could be available too but then special request to the data owner is needed to be applied. The summary of data completeness is provided in Table 10. Table 10 GRONINGEN FILD conventional hydrocarbon production data accepted for integration

Available data Integration No. Name Data Type Type Additional



1. Surface signals (accelerograms)

signal Not needed

2. Surface waveforms (accelerograms)

waveform Not needed

3. Borehole signals (seismograms)

signal Conversion to seed file

4. Borehole waveforms (seismograms)


5. Groningen field catalogue

catalogue

Data relevant for the

considered hazards/seismic

Not needed Conversion to mat file

6. Velocity model of Groningen field

velocity model Other geo-data Not needed Conversion to GDF mat file

3.5 GROSS SCHONENBECK geothermal energy production experiment

This episode comprises seismic, technological and geo-data. The catalogue includes 29 events with local magnitude range from -1.8 up to -1.0. The GROSS SCHONENBECK episode is totally compiled and has been already integrated. The summary of data completeness is provided in Table 11. The Gross Schoenebeck episode will be shared with SHEER users from the November 2015. The episode is integrated and stored together with metadata and is currently accessible on IS-EPOS, Fig. 8. Specific visualizations are available for all types of files (Fig. 9), e.g. the integrated visualization including all information about stations, localization of events and borehole trajectories (Fig. 10). Moreover, visualization of seismic activity with injection rate or wellhead pressure and the special 3D visualization has been arranged for this episode.

22

Table 11 GROSS SCHONENBECK geothermal energy production experiment data integrated.


section Additional




waveform


signal

3. Gross Schoenebeck catalogue

catalogue



4. Injection rate injection rate 5. Trajectory of GS3

borehole borehole trajectory

6. Trajectory of GS4 trajectory

borehole trajectory

7. Wellhead Pressure

wellhead pressure

Technological data

8. Velocity model of Gross Schoenebeck

velocity model Other geo-data

Not needed – work already done

3.6 THE GEYSERS geothermal energy production

This episode contains seismic data in the form of surface waveforms, signals and technological data connected with geothermal energy production. The catalogue comprises 15476 events with magnitude range from -0.3 up to 4.5. The summary of data completeness is provided in Table 12. Table 12 THE GEYSERS geothermal energy production data accepted for integration


section Additional






signal Triggering of continuous data and conversion to seed file

3. The Geysers catalogue

catalogue



Not needed Conversion to mat file

4. injection parameters for each well

injection parameters


5. production parameters for each well

production parameters

Technological data


23

Figure 8 Service for the presentation and data access to Gross Schoenebeck episode.

Figure 9 Service for Gross Schoenebeck episode borehole trajectory visualisation.

24

Figure 10 Service for Gross Schoenebeck episode integrated visualisation. The details of provided information about the all available data for SHEER purpose can be found in the Appendix 1.

3.7 On-site monitoring in Wysin, Pomerania, Poland

The detailed information about the seismic, air and hydrogeological monitoring on Wysin shale gas exploitation site was presented in the Deliverable No D3.1. Presently, the seismic data are on-line transmitted from the site from 16 short period stations to the local server dedicated to the SHEER project: sheerwer.igf.edu.pl. The 6 broadband and 9 short period stations work offline. The data are planned to be collected in the period 26-29 October 2015. At server the services for online data acquisition, archiving and saving have been implemented. Besides the ongoing seismic monitoring the air quality monitoring has been starting more than three months ago. Atmospheric trace gases and particulate matter concentrations measured in air pollution monitoring station located in Stary Wiec, the vicinity of drilling area Wysin, are:

1. Particulate matter measured by TEOM 1400 ambient particulate patter (PM10) monitor analyzer

2. Total hydrocarbons, methane and non methane hydrocarbons measured by Horiba APHA-370 THC immision monitor

3. Nitrogen Oxide, Nitrogen Dioxide and Nitrogen Oxides measured by API 200A analyzer 4. Ozone measured measured by API 400 analyzer 5. Carbon Monoxide measured by API 300 analyzer 6. Carbon Dioxide measured by Thermo 410i analyzer 7. Radon 222 measured by RAD7 Radon analyzer

25

Meteorological data are measured in the nearest air pollution monitoring station (distance 7 km). Basic data (ambient temperature and pressure) are measured on site. Analyzers and complementary equipment are placed in the air-conditioned container in Stary Wiec village, about 1100 meters east of the drilling site Standard quality assurance/quality control procedures are implemented in the measurement process: daily remote checs of data and instruments parameters, periodic zero/span controls, routine maintenance operations etc. Measurements are performed continuously. Hourly means are calculated from the instantaneous measurements and stored in the datalogger. Data are periodically downloaded to the computer located in the IGF PAS. After verification and validation process, data are sent to the project database on a monthly basis. The satellite data availability for Pomerania, Groningen and Blackpool areas is summarized in Table 13. Table 13 SAR data availability for three SHEER episodes: Pomerania, Groningen and Blackpool.

26

Appendices

Appendix 1 The SHEER database inquiry filled by data providers

General information about episode Episode PREESE HALL Shale Gas Provider KeU Localization Lancashire UK

☐ open Episode state

☐ close 1. Seismic data Seismic data are available Yes EQ catalogue is available Yes What kind of parameters are in the EQ catalogue Write info.

Number of EQ Write a number. Range of Magnitude M min. M max. Format of EQ catalogue Write a file format. Surface data are available Yes

Network description seismic monitoring data from 4 local Guralp 6TD & 3T broad Band (shallow surface) seismometer stations and BGS regional stations: Lancaster/Keswick/Stoke etc.

Data are row or processed procesed data Format of row data Guralp GCF and RefTek raw format Format of processed data Write a file format.

waveform continous Signal type

Select a option. Select a option. Borehole seismic data are available Select yes or no.

Microseismic or not Select yes or no.

Network description Write a description, e.g. number of station/sensors, type of sensors..

Data are row or processed Select a option. Format of row data Write a file format. Format of processed data Write a file format.

Select a option. Select a option. Signal type

Select a option. Select a option. Other seismic data are available Yes Description of the data1 3-D Seismic Reflection (post-Frac) … Format of the data 1 Write a file format. Description of the data2 2-D Heritage Seismic Reflection Data (Pre-Frac)

27

Format of the data 2 Write a file format. Description of the data3 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format. Description of the data4 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format.

2. Technology data Technology data are available Yes Description of the data 1 Daily drilling reports Format of the data 1 Report - text Description of the data 2 daily completion reports Format of the data 2 Write a file format. Description of the data 3 well trajectory information Format of the data 3 Write a file format. Description of the data 4 Pumping volumes Format of the data 4 Write a file format. Description of the data 5 Hydraulic fracture pressures Format of the data 5 Write a file format. Description of the data 5 Reservoir pressure Format of the data 5 Write a file format. Description of the data 5 Fracture treatment reports Format of the data 5 Write a file format. Description of the data 5 completion details Format of the data 5 Write a file format. Description of the data 5 flowback details and schedule of events Format of the data 5 Write a file format.

3. Geo data – additional data

Geo data are available Yes

Description of the data 1 Background local and regional geological data including end of well reports for Thistleton-1 and Hesketh-1 wells

Format of the data 1 Write a file format.

Description of the data 2 structure contour map and well location map for the Top Manchester Marl

Format of the data 2 Write a file format. Description of the data 3 3D structure projections for the Manchester marl. Format of the data 3 Write a file format. Description of the data 4 Regional Stress from Minfracs Format of the data 4 Write a file format. Description of the data 5 Complete Stratigraphic Section Format of the data 5 Write a file format.

Description of the data 5 Geomechanical Data derived from Well Logs and Core CMI image logs, caliper logs, cross-dipole sonic logs, spider caliper log and cement bond logs. Wellbore

28

deformation. Petrophysical properties: Young’s Moduli/Poisson’s Ratio.Triaxial laboratory Strength tests Pore pressure prediction based on sonic velocities

Format of the data 5 Write a file format.

Description of the data 5 Interpretations of the borehole features prepared from the logs and core photos are available. (Core may be available), Structural Features (Slickenside Interpretations)

Format of the data 5 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.

General information about episode Episode BECKINGHAM SITE conventional hydrocarbon production Provider Keu Localization Beckingham UK


☒ close

1. Seismic data Seismic data are available Yes EQ catalogue is available Select yes or no. What kind of parameters are in the EQ catalogue Write info.

Number of EQ Write a number. Range of Magnitude M min. M max. Format of EQ catalogue Write a file format. Surface data are available Yes

Network description An array of 6 accelerometers and 3 geophones, at distances from 100 to 1000m from the well.

Data are row or processed row data Format of row data ASCII Format of processed data Write a file format.

waveform trigger Signal type

Select a option. Select a option. Borehole seismic data are available Yes

Microseismic or not Yes Network description Data are row or processed row data Format of row data ASCII

29

Format of processed data Write a file format. waveform trigger

Signal type Select a option. Select a option.

Other seismic data are available Yes

Description of the data1 Vertical Seismic Profile (VSP) survey carried out before and after the hydrofracture experiment.

Format of the data 1 Write a file format. Description of the data2 Write a description, e.g. date, depth, parameters, result type. Format of the data 2 Write a file format. Description of the data3 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format. Description of the data4 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format.

2. Technology data Technology data are available Yes Description of the data 1 Write a description. Format of the data 1 Write a file format. Description of the data 2 Write a description. Format of the data 2 Write a file format. Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.


Geo data are available Yes Description of the data 1 Write a description. Format of the data 1 Write a file format. Description of the data 2 Write a description. Format of the data 2 Write a file format. Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.

30

General information about episode Episode GRONINGEN FIELD conventional hydrocarbon production Provider KNMI Location Groningen NL

☒ open Episode state

☐ close

1. Seismic data Seismic data are available Yes EQ catalogue is available Yes What kind of parameters are in the EQ catalogue Location, local magnitude, picks

Number of EQ >800 Range of Magnitude -0.5 3,6 Format of EQ catalogue Seiscomp3 Database Surface data are available Yes

Network description

Currently, the network is being extended to more than 60 200m deep boreholes (including surface accelerometer) covering the entire Groningen field with a borehole separation of 3-5 km. Also, around 18 more accelerometers are available in the most active region. In addition two deep downhole tools (3 km deep) are installed in the center of the gas field and 4 broad-band sensors are foreseen at 200m deep, distributed over the field.

Data are row or processed row data Format of row data Seed/MiniSeed Format of processed data Write a file format.

waveform accelerogram Signal type

signal accelerogram Borehole seismic data are available Yes

Microseismic or not Yes

Network description A regional borehole network, 200m deep and equipped with 4levels of 3C geophones

Data are row or processed row data Format of row data Seg-2/Seg-Y Format of processed data Write a file format.

waveform seismogram Signal type

signal seismogram Other seismic data are available Yes Description of the data1 Velocity model Format of the data 1 Custom Description of the data2 Write a description, e.g. date, depth, parameters, result type.

31

Format of the data 2 Write a file format. Description of the data3 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format. Description of the data4 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format.

2. Water quality data Water quality data are available No Period of production Write a description e.g. before, during or after a operations. Data are row or processed Select a option. Format of row data Write a file format. Format of processed data Write a file format. Type of processed data Write a description. Parameters of measurement Select yes or no. Description of the parameters of measurement Write a description.

Type of the parameters of measurement Write a file format.

3. Technology data

Technology data are available No Description of the data 1 Write a description. Format of the data 1 Write a file format. Description of the data 2 Write a description. Format of the data 2 Write a file format. Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.


Geo data are available No Description of the data 1 Write a description. Format of the data 1 Write a file format. Description of the data 2 Write a description. Format of the data 2 Write a file format. Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.

32

General information about episode Episode GROSS SCHOENEBECK geothermal energy production experiment Provider IGF (GFZ) by IS-EPOS platform Localization Gross Schoenebeck Germany


☒ close

1. Seismic data Seismic data are available Yes EQ catalogue is available Yes

What kind of parameters are in the EQ catalogue

ID, Lat, Long, Depth, Elevation, X, Y, Z, Mw, E, R, sigma_a, delta_sigma (X,Y,Z are the cartesian coordinates in UTM system where X denotes Easting, Y denotes Northing and Z denotes Depth)

Number of EQ 29 Range of Magnitude -1,8 -1,0 Format of EQ catalogue IS-EPOS mat file (catalogue) Surface data are available Yes Network description 2 surface seismometers EDLHD1201, EDLHD1124 Data are row or processed row data Format of row data miniseed Format of processed data Write a file format.


Select a option. Select a option. Borehole seismic data are available Yes

Microseismic or not Yes

Network description 6 borehole seismometers EDLHD1256, EDLHD1221, EDLHD1252, EDLHD1261, EDLHD1257, EDLHD2054

Data are row or processed row data Format of row data miniseed Format of processed data Write a file format.


Select a option. Select a option. Other seismic data are available No Description of the data1 Write a description, e.g. date, depth, parameters, result type. Format of the data 1 Write a file format.

2. Technology data

Technology data are available Yes

33

Description of the data 1 Well path - GT GRSK 3/90 well trajectory in UTM coordinates (Easting";"Northing";"Altitude above MSL (mean see level)"

Format of the data 1 CSV

Description of the data 2 Well path - GT GRSK 4/05 well trajectory in UTM coordinates (Easting";"Northing";"Altitude above MSL (mean see level)"

Format of the data 2 CSV Description of the data 3 injection rate (time, injection rate) Format of the data 3 IS-EPOS mat file (NSD non seismic data) Description of the data 4 Wellhead_Pressure (time, Wellhead Pressure) Format of the data 4 IS-EPOS mat file (NSD non seismic data)


Geo data are available Yes Description of the data 1 Velocity model Format of the data 1 IS-EPOS mat file (NSD non seismic data) Description of the data 2 Write a description. Format of the data 2 Write a file format. Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.

General information about episode Episode THE GEYSERS geothermal energy production Provider AMRA-GFZ Localization California USA


☐ close

1. Seismic data Seismic data are available Yes EQ catalogue is available Yes What kind of parameters are in the EQ catalogue Id, date, time, lat, lon, depth, magnitude, magtype

Number of EQ 15476 Range of Magnitude -0,3 4,5

Format of EQ catalogue Event catalogues in text file format and SAC waveforms files grouped by event

Surface data are available Yes Network description Berkeley-Geysers (BG) network, 32 stations 3-component

34

Data are row or processed Select a option. Format of row data Write a file format. Format of processed data SAC file format

waveform Select a option. Signal type

Select a option. Select a option. Borehole seismic data are available Select yes or no.

Microseismic or not Select yes or no.

Network description Write a description, e.g. number of station/sensors, type of sensors..

Data are row or processed Select a option. Format of row data Write a file format. Format of processed data Write a file format.

Select a option. Select a option. Signal type

Select a option. Select a option. Other seismic data are available Select yes or no. Description of the data1 Write a description, e.g. date, depth, parameters, result type. Format of the data 1 Write a file format. Description of the data2 Write a description, e.g. date, depth, parameters, result type. Format of the data 2 Write a file format. Description of the data3 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format. Description of the data4 Write a description, e.g. date, depth, parameters, result type. Format of the data 3 Write a file format.

2. Technology data Technology data are available Yes Description of the data 1 Injection parameters for each well from 1997 to 2013 Format of the data 1 xls file Description of the data 2 Production parameters for each well from 1997 to 2013 Format of the data 2 xls file Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.

3. Geo data – additional data Geo data are available Select yes or no. Description of the data 1 Write a description. Format of the data 1 Write a file format. Description of the data 2 Write a description.

35

Format of the data 2 Write a file format. Description of the data 3 Write a description. Format of the data 3 Write a file format. Description of the data 4 Write a description. Format of the data 4 Write a file format. Description of the data 5 Write a description. Format of the data 5 Write a file format.

Appendix 2 Form of MAT file catalogue

The catalogue is a variable in the Matlab format file and it is kept in a file MAT. The structure is array with named fields that can contain data of various types and sizes. In the file there is only one variable, the file name and variable name are optional. The variable describing the catalogue is a vector of structures, consisting of fields:

- field – name of field in the catalogue (text value); - type – type of field in the catalogue and way of showing the field (numeric value); - val – column array of values. For the text the column is an array type cell with text fields.

For the remaining value the column is a numeric column. The fundamental is a full catalogue i.e. the variable contains the definitions of all specified fields. When some field values are missing then for the numeric data NaN (not specified) is entered and for the text null [] is entered. In the fields "ID", "Time" and at least one of the fields "Mw" or "ML" values in all rows must be present. Table A2 The required parameters in catalogue MAT format

Name of field

Description of the field Data format

Number of data type5

Unit Comments

ID Event ID text 3 required field Time Matlab serial numerical

time double 5 days required field

Lat Latitude double 24,25 [o] – North

positive

Long Longitude double 24,25,34,35

[o] – East

positive

Depth Hypocenter depth measured from the ground level

double 11-13 [km]

Elevation Hypocenter elevation measured over the see level

double 10 [m]

X 10 Y 10 Z

Original Coordinate

10

Original coordinates if other than geographical. Description of coordinates in the metadata

EPI_err epicentral error double 10 [m] 5 The numerical value of the type of the data to be written to the field type. The Numbers description is shown below.

36

Depth_err depth error 10 [m] Nl No of stations used in the

localisation 2

M0 Scalar moment 7 [Nm] Mw moment magnitude double

0.16 4 Mw or ML must be for

all event ML local magnitude double 0.1 4 Mw or ML must be for

all event Ns_decomp No of stations used in MT

inversion double 2

DecompMethod

Method used to decompose moment tensor

text 3

MTrr Full solution: Moment tensor rr component (r – up)

double 7 [Nm]

MTss Full solution: Moment tensor ss component (s – South)

double 7 [Nm]

MTee Full solution: Moment tensor ee component (e – East)

double 7 [Nm]

MTrs Full solution: Moment tensor rs component

double 7 [Nm]

MTre Full solution: Moment tensor re component

double 7 [Nm]

MTse Full solution: Moment tensor se component

double 7 [Nm]

MT_err Full solution: Moment tensor error

double 7 [Nm]

ISO isotropic MT component double 120 [%] - positive

or negative

CLVD CLVD component double 120 [%] - positive

or negative

DC Double-Couple component double 20 [%] - only

positive

StrikeA Strike of nodal plane A double 30 [o] The values range from 0 to 360

DipA Dip of nodal plane A double 20 [o] The values range from 0 to 90

RakeA Rake of nodal plane A double 130 [o] The values range from -180 to 180

SlopeA Inclination for nodal plane A

double 20 [o] The values range from 0 to 90

StrikeB Strike of nodal plane B double 30 [o] The values range from 0 to 360

DipB Dip of nodal plane B double 20 [o] The values range from 0 to 90

RakeB Rake of nodal plane B double 130 [o] The values range

6 The values rounded to 0.1.

37

from -180 to 180 SlopeB Inclination for nodal plane

B double 20 [o] The values range from 0

to 90 Strike_err Strike error double 10 [o] Dip_err Dip error double 10 [o] Rake_err Rake error double 10 [o] Slope_err Inclination error double 10 [o] Plunge_T Plunge of T-axis double 10 [o] The values range from 0

to 360 PlungeT_err

T-axis plunge error double 10 [o]

Trend_T Trend of T-axis double 10 [o] The values range from 0 to 90

TrendT_err T-axis trend error double 10 [o] Plunge_P Plunge of P-axis double 10 [o] The values range from 0

to 360 PlungeP_err

P-axis plunge error double 10 [o]

Trend_P Trend of P-axis double 10 [o] The values range from 0 to 90

TrendP_err P-axis trend error double 10 [o] DCrr Double-Couple solution:

Moment tensor rr component (r - up)

double 7 [Nm]

DCss Double-Couple solution: Moment tensor ss component (s - South)

double 7 [Nm]

DCee Double-Couple solution: Moment tensor ee component (e - East)

double 7 [Nm]

DCrs Double-Couple solution: Moment tensor rs component

double 7 [Nm]

DCre Double-Couple solution: Moment tensor re component

double 7 [Nm]

DCse Double-Couple solution: Moment tensor se component

double 7 [Nm]

DC_err Double-Couple solution: Moment tensor error

double 7 [Nm]

DCStrikeA Double-Couple solution: Strike of nodal plane A


DCDipA Double-Couple solution: Dip of nodal plane A


DCRakeA Double-Couple solution: Rake of nodal plane A

double 130 [o] The values range from -180 to 180

DCStrikeB Double-Couple solution: Strike of nodal plane B


DCDipB Double-Couple solution: Dip of nodal plane B


DCRakeB Double-Couple solution: Rake of nodal plane B


DCStrike_err

Double-Couple solution: Strike error

double 10 [o]

38

DCDip_err Double-Couple solution: Dip error

double 10 [o]

DCRake_err

Double-Couple solution: Rake error

double 10 [o]

DCPlunge_T

Double-Couple solution: Plunge of T-axis


DCPlungeT_err

Double-Couple solution: T-axis plunge error

double 10 [o]

DCTrend_T Double-Couple solution: Trend of T-axis


DCTrendT_err

Double-Couple solution: T-axis trend error

double 10 [o]

DCPlunge_P

Double-Couple solution: Plunge of P-axis


DCPlungeP_err

Double-Couple solution: P-axis plunge error

double 10 [o]

DCTrend_P Double-Couple solution: Trend of P-axis


DCTrendP_err

Double-Couple solution: P-axis trend error

double 10 [o]

TNrr TN solution: Moment tensor rr component (r - up)

double 7 [Nm]

TNss TN solution: Moment tensor ss component (s - South)

double 7 [Nm]

TNee TN solution: Moment tensor ee component (e - East)

double 7 [Nm]

TNrs TN solution: Moment tensor rs component

double 7 [Nm]

TNre TN solution: Moment tensor re component

double 7 [Nm]

TNse TN solution: Moment tensor se component

double 7 [Nm]

TN_err TN solution: Moment tensor error

double 7 [Nm]

TNStrikeA TN solution: Strike of nodal plane A

double 30 [o] The value range from 0 to 360

TNDipA TN solution: Dip of nodal plane A


TNRakeA TN solution: Rake of nodal plane A

double 130 [o] The value range from -180 to 180

TNStrikeB TN solution: Strike of nodal plane B


TNDipB TN solution: Dip of nodal plane B


TNRakeB TN solution: Rake of nodal plane B


TNStrike_err

TN solution: Strike error double 10 [o]

TNDip_err TN solution: Dip error double 10 [o] TNRake_err

TN solution: Rake error double 10 [o]

TNPlunge_T

TN solution: Plunge of T-axis


39

TNPlungeT_err

TN solution: T-axis plunge error

double 10 [o]

TNTrend_T TN solution: Trend of T-axis


TNTrendT_err

TN solution: T-axis trend error

double 10 [o]

TNPlunge_P

TN solution: Plunge of P-axis


TNPlungeP_err

TN solution: P-axis plunge error

double 10 [o]

TNTrend_P TN solution: Trend of P-axis


TNTrendP_err

TN solution: P-axis trend error

double 10 [o]

NsP No of stations used in the P-wave spectral analysis

double 2

E total seismic energy double 7 [J] E_err total seismic energy error double 7 [J] Ep P-wave energy double 7 [J] Ep_err P-wave energy error double 7 [J] fp P-wave corner frequency double 12 [Hz] fp_err P-wave corner frequency

error double 12 [Hz]

rad_eff_P Radiation efficiency P double 12 Qp Quality factor Pwaves double 10 NsS No of stations used in the S-

wave spectral analysis double 2

Es S-wave energy double 7 [J] Es_err S-wave energy error [J] double 7 [J] fs S-wave corner frequency

[Hz] double 12 [Hz]

fs_err S-wave corner frequency error [Hz]

double 12 [Hz]

Qs Quality factor Swaves double 10 rad_eff_S Radiation efficiency S double 12 R source radius double 10 [m] R_err source radius error double 10 [m] R_model Source radius model used

(Brune, Madariaga, Sato&Hirasawa)

text 3

rad_eff Radiation efficiency double 12 sigma_a Apparent stress double 13 [MPa] delta_sigma Static stress drop double 13 [MPa] sigma_d Dynamic stress drop double 13 [MPa] sigma_rms RMS dynamic stress drop double 13 [MPa] vr Rupture velocity double 10 [m/s] vr_model Rupture velocity model

(unilateral etc.) text 3

SW_eff Savage-Wood efficiency double 12 u Fault slip double 12 [m] The Numbers of Data type: 1 – the real data without limits, 2 – the integer data,

40

3 – text value, 4 – the real number rounded to 0.1 (shown as 11), 5 – time in Matlab format serial time – the time display format; seconds with accuracy 1/10, 6 – the real data display in an engineering manner with one decimal place, e.g.: 3.5E6, 7 – the real data display in an engineering manner with two decimal place, bc – (b and c are code digits) the real data display in fix-point manner with at minimum b places before decimal and c decimal place e.g. For number 3.149. 10: „3” 11: „3.1” 12: „3.15” 20: „03” 23: „03.149” 1bc– the same manner as bc, but with place for a sign (space for sign „+”, sign ‘-’ for sign „-”)

41

Appendix 3 Form of MAT file Generic Data Format

The format of data for further processing should be the most universal and easy to use. It should contain the identity of the geographic coordinate system in which data are stored, the time zone in which the time is determined, and information about the stored data, such as: unit, data type, names of variables with descriptions. The proposed format is based on data structures that can be easily saved to a file and are easy to manipulate. This structure contains 9 variables, where d is the most essential one, because it contains the data which can be further processed. The other variables are used for the correct data description – units, coordinate system, fields etc.

Table A3. The structure of Generic Data Format Variable name Type Description

FormatName char Name of data format GDF (Generic Data Format). FormatVersion real When changing/expansion of the format change its version. It can

have one number after the decimal point. CRS char Coordinate Reference System

EPSG code (or local) mapping surveying (http://epsg.io), standard WGS84 (EPSG: 4326)

TimeZone char Acronym of Time Zone (http://en.wikipedia.org/wiki/List_of_time_zone_abbreviations), normally UTC

Description char The text description of the data contained in the file FieldDescription cell

array Description of the fields. An array contains two columns: the first contains the name of the field/column of data, the second contains a description of them. All data must be specified

FieldUnit cell array of char

Description of units for individual data, e.g. m/s. Its according to SI. An array contains two columns: the first contains the name of the field/column of data, the second contains the unit. All data must be specified.

FieldType cell array of char

Description of data type e.g. real. An array contains two columns: the first contains the name of the field/column of data, the second contains the data type description. All data must be specified.

time - matlab serial numerical time deg - angle in degrees, as for geographical coordinates, positive values for N and E. int – integer number real – the real number

d struct array or cell array char

The variable containing the data. The data may be as a single variable, a vector or an array.

Documents

Topic: LCE 16 – 2014 Understanding, preventing and … · · 2016-06-061 Topic: LCE 16 – 2014 Understanding, preventing and mitigating the potential environmental impacts and