Git Product home page Git Product logo

project-support-wp8's Introduction

GeoEra-GIP

Hi

Welcome to the GeoERA-GIP!

project-support-wp8's People

Contributors

bgsmase avatar dependabot[bot] avatar koalageo avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

project-support-wp8's Issues

test versions of second cluster of datasets from MUSE

Sent by David Garcia ([email protected]). Created by fire.


Dear support team,

Please, find enclosed the second set of test datasets from which we will create the templates that MUSE partners should follow to create the following datasets: Land Surface Temperature, Confined or Artesian Aquifers, Mining areas and Flood risk. Could you, please, have a look and let us know whether they fulfil the requirements to be uploaded to EGDI?

The shapefiles we are sending are part of the actual datasets, which have been created for testing purposes. Apart from the Land Surface Temperature, which will be shared as GeoTiffs, the final/complete datasets will be uploaded in GeoPackage format to EGDI. See an example of one of these GeoPackages in attachments (Conf_artesian_Aquifers.gpkg). Could you, please, check whether that GeoPackage fulfils EGDI requirements?

We are currently creating the first 3 final dataset compilations, which I will upload as 3 different GeoPackages to EGDI in the coming weeks.

Thanks in advance for providing a rapid feedback!!

Regards,

David.


Attachments:

  1. Conf_artesian_Aquifers.gpkg
  2. LandSurfaceTemp_Test01.zip
  3. FloodRisks_Test01.zip
  4. ConfinedArtesianAquifers_test01.zip
  5. MiningAreas_Test01.zip

Geoera HOVER WP3 – Task 3-5c product for thermal and natural mineral waters – clustering (multiple points at one location)

Sent by Elster, Daniel. Created by fire.


Dear all,

we decided to use the 1 km EEA reference grid to show our point data since we can�t share exact coordinates in most cases. Furthermore, we don�t want to show raster grids but point data (center of each grid), see example below.

However, in some cases we will have multiple entries at one location and I am asking for suggestions for the following question: How shall we deal with clustering?

Many thanks,

Daniel

N1

|

G2

|

Center of grid

---|---|---

Bad Gastein, Kristallquelle

|

1kmE4558N2674

|

4558000

|

2674000

Bad Gastein, Tauernquelle

|

1kmE4558N2674

|

4558000

|

2674000

Bad Radkersburg, Stadtquelle

|

1kmE4778N2638

|

4778000

|

2638000

Projected Coordinate System: ETRS_1989_LAEA

Projection: Lambert_Azimuthal_Equal_Area

False_Easting: 4321000,00000000

False_Northing: 3210000,00000000

Central_Meridian: 10,00000000

Latitude_Of_Origin: 52,00000000

Linear Unit: Meter

__

Geographic Coordinate System: GCS_ETRS_1989

Datum: D_ETRS_1989

Prime Meridian: Greenwich

Angular Unit: Degree

--
Daniel ELSTER, MMSc.
Hydrogeologe / Hydrogeologist
Fachabteilung Hydrogeologie & Geothermie / Department of Hydrogeology & Geothermal Energy

Geologische Bundesanstalt / Geological Survey of Austria
Neulinggasse 38, 1030 Wien, �sterreich

Web: www.geologie.ac.at

Support for coverage data

We have an issue raised by TACTIC concerning adding grid data into GeoPackage. Input data is ESRI ASCII grid. I see in the http://egdi-public.gitlabpages.geus.dk/egdi-documentation/#/main-content/DeliveringDataToEGDI document that both .asc and .grd is supported for Delivering 3D models, would it be correct to say those formats also work for for 2D coverages?

It has been mentioned but not referenced that GeoTIFF and NetCDF will also be supported, is that correct?

For grid data supplied as a GeoPackage raster will EGDI support the Tiled Gridded Coverage Data extension?

[FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Sent by Aurete Pereira Created by fire.


Dear GIP-P support team

As decided in the FRAME - GIP-P bilateral meeting, GIP-P is going to help us on our deliverable due in July (D8.2: Implement IT equipment infrastructure capable of interacting with internal system requirements to ensure delivery and increase the reliability of data and information to the EURMKB). In order to accomplish this, FRAME is ready to release a prototype of the REE metallogenic map of Europe to be represented in EGDI for testing purposes. To whom should I deliver this map?

Looking forward to hearing from GIP-P.

Best regards

Aurete Pereira

Unidade de Informa��o Geocient�fica

__

cid:image002.png@01D617F9.7513B650

__

lneg__

Laborat�rio Nacional de Energia e Geologia, I.P.

Estrada da Portela, Bairro do Zambujal – Alfragide

Upload failed when importing with style

Dear all,
As part of the testing of GeoConnect³d data, I followed the cookbook guidelines to save a simple simbolisation in the geopackage, but when trying to upload the following error appears:

Capture

There was no problem to upload the same geopackage without importing style.
Any tips on how should I proceed? We will rely a lot on simbolisation.

Best,
Renata

HIKE fault GeoPackage test dataset - problem with attribute table field names

Sent by Bell, Patrick D. Created by fire.


From: Ede, R. (Rob) van
Sent: 18 June 2020 12:58
To: Bell, Patrick D.
Subject: RE: GeoERA WP8 Data Provider Support monthly telecon

Hi Patrick,

as all the latest meetings were planned on days that I don�t work, I could not attend. But I have a question for the people in the workpackage now, concerning GeoPackages (with my HIKE hat on):

The issue came up after I delivered a latest test-GeoPackage to Martin Hansen yesterday. The complete discussion, as well as the GeoPackage is in the attached email. Martin pointed me to WP8 for assistance :-)

Do you know the answer / solution?

Cheers,

Rob

...snip...


Attachments:

  1. image002.jpg
  2. msg-7461-1093.txt
  3. image001-5.jpg
  4. Preparation_the_HIKE_data_for_delivery_V2.pdf
  5. GC3D-tester3.gpkg
  6. msg-7461-1094.html

Uploading GeoTIFF in dev platform results in error

Attempting to upload a GeoTIFF file supplied by the HOVER project in the development EGDI platform results in error:

Exception: The following projections (epsgs) are not supported: 9001

Detailed log
java.lang.Exception: The following projections (epsgs) are not supported: 9001 at org.apache.jsp.geopack2_jsp._jspService(geopack2_jsp.java:669) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.tomee.catalina.OpenEJBSecurityListener$RequestCapturer.invoke(OpenEJBSecurityListener.java:97) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:798) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)

Geoera HOVER WP3 – Task 3-5c product for thermal and natural mineral waters – vocabularies and codelists

Sent by Elster, Daniel

Dear all,

we decided to create a project vocabulary for hydrochemical data in HOVER WP3 Task 3-5 � product for thermal and natural mineral waters�, the �descriptions and instructions for completing a GeoERA

Project Vocabulary template� created by Christine H�rfarter are considered (draft version see attachment).

My question is how to deal with values, units and values below detection limits

Example:

Arsenic = created in project vocabulary

|

Value = unclear how to solve

|

If detection limit is present = unclear how to solve, not necessarily present

|

unit = unclear how to solve

---|---|---|---

Arsenic

|

0,2

|

<

|

�g/l

Many thanks!
Daniel

--
Daniel ELSTER, MMSc.
Hydrogeologe / Hydrogeologist
Fachabteilung Hydrogeologie & Geothermie / Department of Hydrogeology & Geothermal Energy

Geologische Bundesanstalt / Geological Survey of Austria
Neulinggasse 38, 1030 Wien, �sterreich

Tel: +43-1-7125674-334
Fax: +43-1-7125674-56
E-Mail:
Web: www.geologie.ac.at


Attachments:

  1. 2020_07_2020_HOVER_Test_ProjVocab_Template_Sheet.xlsx
  2. Vs5_21032019_GeoERA_Template_Description_PV_WP4_RvE.pptx

GeoEra Intranet

Sent by Aasly Kari Aslaksen ([email protected]). Created by fire.


Hi!

I have problems loading the GeoEra Intranet page, didn’t work yesterday either

Regards,

Kari Aslaksen Aasly

E_post_signatur_2

|

Kari Aslaksen Aasly
Team Leader

Natural construction materials

Leiv Eirikssons vei 39

NO-7040 Trondheim
Mobile: +4747319441
Phone: +4773904238
[email protected]

www.ngu.no

---|---

ikon_fb ikon_youtube ikon_twitter

Questions on EGDI metadata editing tool and the tool for uploading products.

Sent by Margarita Patricia Sanabria Pabón Created by fire


Dear Pavla and Martin,

Today I had a little chat with Stephan Broda and Martin Krombholz from HOVER WP7 and some quesitions arise regarding the metadata tool and the upload tool.

HOVER WP7 will deliver 6 products in GeoTIFF format. The point is, that each product is made up of several GeoTIFs. For example, the product call "Groundwater Vulnerability to Pollution INPUT DATA Maps in Pilot Areas according to DRASTIC" comprise 77 GeoTIF (7 GeoTIF files per pilot area ,11 pilot areas in total).

They would like to know if there is any tool or recommendation from your side that allows to automatize the metadata edition process. Some of the fields to be filled in will be the same and only some like keywords or extension etc. will vary. Pavla, if you could tell them how to proceed it would help them a lot.

On the other hand, we have a few questions for Martin. The GeoTIF format is one of the accepted formats, right? and the GeoTIF files will be stored in EGDI repository, I am right? If this the case, when uploading a GeoTIF to the repository, they will get an url pointing the file location, just in case they needed, is that correct?

They will wait for your answers to proceed and if necessary a little chat, Stefan and Martin are available and can arrange a meeting through zoom.

Thanks in advance for your help

Kind regards,

Marga

MUSE - Test data sets

Sent by Steiner, Cornelia. Created by fire.


Dear GeoERA support team,

On behalf of David Garcia, I am sending you the first three test data sets of MUSE and the project vocabularies for the corresponding parameters. Please provide feedback to us about the following:

� Test data sets: Let us know, if the test data sets are okay and can serve as templates for the other pilot areas, or if anything has to be changed.

� Project vocabularies: Is the documentation of parameters not included in INSPIRE sufficient?

Please let us know, when we can expect your feedback.

Thank you and kind regards,

Cornelia Steiner

--
Cornelia STEINER, MSc.
Geologin / Geologist
Fachabteilung Hydrogeologie & Geothermie / Department of Hydrogeology & Geothermal Energy

Geologische Bundesanstalt / Geological Survey of Austria
Neulinggasse 38, 1030 Wien, �sterreich

Web: www.geologie.ac.at


Attachments:

  1. final_test_water_protection.zip
  2. final_data_other-gw-use.zip
  3. final-SGE-systems.zip
  4. VocabSch_Inst_WProt_OtGW_CST_clean.xlsx

Geoera HOVER WP3 – Task 3-5c product for thermal and natural mineral waters – queries and filters

Sent by Elster, Daniel. Created by fire.


Dear all,

we wish to use filters and queries for our product, e.g. select all natural mineral waters with a Calcium (GEOERA project vocabulary) concentration above 100 mg/l that come from carbonateSedimentaryRock (INSPIRE), a temperature below 20 �C (codelist) and groundwater age older than 10.000 years (codelist). It would be great to choose up to 4 levels of queries and to be able to set a range for values (like concentrations of Calcium), please see example data below.

Many thanks for technical suggestions!

Best wishes,
Daniel

N1

|

Bad V�slau, Bohrbrunnen VI/2

|

Bad V�slau, Bohrbrunnen VII

|

Bad V�slau, Ursprungsquellen

---|---|---|---

N2

|

V�slauer

|

V�slauer

|

V�slauer

N3

|

AUSTRIA

|

AUSTRIA

|

AUSTRIA

G1

|

natural mineral water (Directive 2009/54/EC)

|

natural mineral water (Directive 2009/54/EC)

|

natural mineral water (Directive 2009/54/EC)

G2

|

1kmE4785N2781

|

1kmE4784N2781

|

1kmE4784N2781

G3

|

single artesian well

|

single artesian well

|

captured spring group

G4

|

bottled natural mineral water

|

bottled natural mineral water

|

bottled natural mineral water

G5

|

nA

|

nA

|

nA

G6

|

nA

|

nA

|

nA

G7

|

25

|

25

|

25

B1

|

705

|

465

|

nA

B2

|

623

|

306

|

nA

B3

|

643

|

465

|

nA

B4

|

karsticAndFractured

|

karsticAndFractured

|

karsticAndFractured

B5

|

confinedArtesian

|

confinedArtesian

|

confinedArtesian

B6

|

carbonateSedimentaryRock

|

carbonateSedimentaryRock

|

carbonateSedimentaryRock

B7

|

all

|

all

|

all

B8

|

nA

|

nA

|

nA

B9

|

nA

|

nA

|

nA

B10

|

nA

|

nA

|

nA

B11

|

nA

|

nA

|

nA

B12

|

upperTriassic

|

upperTriassic

|

upperTriassic

B13

|

upperTriassic

|

upperTriassic

|

upperTriassic

A1

|

older than 10.000

|

older than 10.000

|

older than 10.000

H1

|

30-40

|

30-40

|

20-30

H2

|

<1

|

<1

|

<1

H3

|

848

|

856

|

745

H4

|

7,27

|

7,07

|

7,19

H5

|

nA

|

nA

|

nA

H6

|

nA

|

nA

|

nA

H7

|

14,32

|

14,06

|

9,53

H8

|

2,01

|

1,88

|

1,71

H9

|

101,97

|

99,52

|

94,07

H10

|

41,45

|

40,51

|

37,75

H11

|

2,95

|

2,96

|

1,75

H12

|

0,046

|

0,045

|

0,05

H13

|

<0,001

|

0,002

|

0,006

H14

|

0,0001

|

0,1

|

0,1

H15

|

nA

|

nA

|

nA

H16

|

245,8

|

246,3

|

298,5

H17

|

nA

|

nA

|

nA

H18

|

0,83

|

0,85

|

0,51

H19

|

20,38

|

20,65

|

14,92

H20

|

nA

|

nA

|

nA

H21

|

nA

|

nA

|

nA

H22

|

201,32

|

204,87

|

119,73

H23

|

0,78

|

0,78

|

5,5

H24

|

nA

|

nA

|

nA

H25

|

0,001

|

0,001

|

0,001

H26

|

nA

|

nA

|

nA

H27

|

0,005

|

0,004

|

0,003

H28

|

nA

|

nA

|

nA

H29

|

<0,0005

|

<0,0005

|

<0,0005

H30

|

<0,0001

|

<0,0001

|

<0,0001

H31

|

nA

|

nA

|

nA

H32

|

0,00032

|

0,00027

|

0,0002

H33

|

nA

|

nA

|

nA

H34

|

0,0012

|

0,0012

|

0,0012

H35

|

0,02

|

0,019

|

0,013

H36

|

nA

|

nA

|

nA

H37

|

nA

|

nA

|

nA

H38

|

nA

|

nA

|

nA

H39

|

nA

|

nA

|

nA

H40

|

nA

|

nA

|

nA

H41

|

nA

|

nA

|

nA

H42

|

nA

|

nA

|

nA

H43

|

0,003

|

0,004

|

0,003

H44

|

nA

|

nA

|

nA

H45

|

nA

|

nA

|

nA

H46

|

nA

|

nA

|

nA

H47

|

nA

|

nA

|

nA

C1

|

nA

|

nA

|

nA

--
Daniel ELSTER, MMSc.
Hydrogeologe / Hydrogeologist
Fachabteilung Hydrogeologie & Geothermie / Department of Hydrogeology & Geothermal Energy

Geologische Bundesanstalt / Geological Survey of Austria
Neulinggasse 38, 1030 Wien, �sterreich

Web: www.geologie.ac.at

RE: [FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Sent by Aurete Pereira). Created by fire.


Dear Martin

Here is a screen shot from the GeoPackage

With these layers you can produce two maps:

1 - overview map of Europe showing the approximate extent of the key REE metallogenic area in Europe (layers main.alkaline_igneous_rocks, main carbonite, main.iron_oxide_apatite_etc and main.secondary_resources)

2 - Simplified spatial distribution of REE occurrences in Europe, and respective genetic types. (layers main.ree_deposit_type and main.ree_deposit_class).

main.ree_deposit_type refer to different genetic type and main.ree_deposit_class refer to occurrence type ( Deposit, prospect or occurrences). This data set were extracted from EURARE database which I think must be equal to the one obtained from M4EU database harvesting (performed by GeoZs). You can do a test by using the dataset from the harvesting instead of this one and see if the result is the same. For this kind of data (points) it was decided that every Europeans partners (FRAME, Mintell4EU and MREG) will update the M4EU database so that the final result should be the same.

In the GeoPackage there is one more layer main.ree_deposits that classified REE deposit based on deposittype, and occurrence as in the figure below:

I hope this is enough descriptions and screen shots for you to make a decision.

Please note that this GeoPackage is for testing. The purpose is to have a FRAME prototype of the REE metallogenic map of Europe presented in EGDI in july, at least. I’m creating metadata for this map in the EGDI Metadata Catalog also to test it.

Best regards

cid:image002.png@01D617F9.7513B650****

Aurete Pereira

Unidade de Informa��o Geocient�fica

From: Martin Hansen
Sent: 19 de junho de 2020 13:03
To: Aurete Pereira ; J�rgen Tulstrup ; [email protected]
Cc: Lidia Quental ; Daniel Oliveira
Subject: SV: [FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Hi Aurete,

Do you have a description of the map or perhaps a screen shot? Then I can better decide if you can upload the data yourselves or ve need to have it by mail.

Best regards,

Martin

Fra: Aurete Pereira
Sendt: 19. juni 2020 12:03
Til: Martin Hansen ; J�rgen Tulstrup ; [email protected]
Cc: Lidia Quental ; Daniel Oliveira
Emne: RE: [FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Hi Martin

It’s a GeoPackage.

Best regards

cid:image002.png@01D617F9.7513B650

Aurete Pereira

Unidade de Informa��o Geocient�fica

From: Martin Hansen
Sent: 19 de junho de 2020 09:14
To: J�rgen Tulstrup ; Aurete Pereira; [email protected]
Cc: Lidia Quental ; Daniel Oliveira
Subject: SV: [FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Dear Aurete,

We have a testing system where users can upload GeoPackages, Shapefiles and documents. On what format do you have your map.

Best regards,

Martin

Fra: J�rgen Tulstrup
Sendt: 19. juni 2020 07:52
Til: Aurete Pereira ; [email protected]; Martin Hansen;
Cc: Lidia Quental ; Daniel Oliveira
Emne: SV: [FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Dear Aurete,

Sorry for not answering this on before. I was a little in doubt if we already have a system to receive it.

Martin: Is the uploading system in place and ready to receive a map like this. Or should Aurete send it by mail?

Med venlig hilsen/best regards

J�rgen

Fra: Aurete Pereira
Sendt: 18. juni 2020 12:21
Til: [email protected]
Cc: J�rgen Tulstrup ; Lidia Quental ; Daniel Oliveira
Emne: [FRAME WP8] GeoPackage of the REE metallogenic map of Europe delivery - whom should I contact to deliver this prototype map?

Dear GIP-P support team

As decided in the FRAME - GIP-P bilateral meeting, GIP-P is going to help us on our deliverable due in July (D8.2: Implement IT equipment infrastructure capable of interacting with internal system requirements to ensure delivery and increase the reliability of data and information to the EURMKB). In order to accomplish this, FRAME is ready to release a prototype of the REE metallogenic map of Europe to be represented in EGDI for testing purposes. To whom should I deliver this map?

Looking forward to hearing from GIP-P.

Best regards

Aurete Pereira

Unidade de Informa��o Geocient�fica

__

cid:image002.png@01D617F9.7513B650

__

lneg

Laborat�rio Nacional de Energia e Geologia, I.P.

Reprojecting datasets documentation and implications for global datasets

Re documentation:

http://egdi-public.gitlabpages.geus.dk/egdi-documentation/#/main-content/SpatialData?id=projections

THe EGDI platform by default displays maps and data sets in projection EPSG:3034. If necessary, individual maps can be set up in other projections, but included data sets will then have to also support that projection or be able to be re-projected on the fly. On the fly re-projection can slow down the map and also distort the details of images.

The EGDI platform by default delivers data sets as WMS in the following projection EPSG:4326, EPSG:4258, EPSG:3043, EPSG:3044, EPSG:3045, EPSG:25831, EPSG:25832, EPSG:25833, EPSG:32631, EPSG:32632, EPSG:32633, EPSG:32618, EPSG:32619, EPSG:32620, EPSG:32621, EPSG:32622, EPSG:32623, EPSG:32624, EPSG:32625, EPSG:32626, EPSG:32627, EPSG:32628, EPSG:3034, EPSG:900913 and EPSG:3857.

Setting aside that there is no EPSG:900913 :)

THe EGDI platform by default displays maps and data sets in projection EPSG:3034.

Does that mean that other projections will be allowed to be selected, if so which ones will be selectable?

If necessary, individual maps can be set up in other projections, but included data sets will then have to also support that projection or be able to be re-projected on the fly

If datasets are provided as services for consumption by the EGDI portal I can see that they must provide support for the supported projections, but I don't understand the implications for supplied datasets. Surely the EGDI platform services/API will do the necessary reprojections.

For HOVER we have a global dataset, whilst EPSG:3034 is limited to Europe, what are the implications for the dataset?

PROJCRS["ETRS89-extended / LCC Europe", BASEGEOGCRS["ETRS89", ENSEMBLE["European Terrestrial Reference System 1989 ensemble", MEMBER["European Terrestrial Reference Frame 1989", ID["EPSG",1178]], MEMBER["European Terrestrial Reference Frame 1990", ID["EPSG",1179]], MEMBER["European Terrestrial Reference Frame 1991", ID["EPSG",1180]], MEMBER["European Terrestrial Reference Frame 1992", ID["EPSG",1181]], MEMBER["European Terrestrial Reference Frame 1993", ID["EPSG",1182]], MEMBER["European Terrestrial Reference Frame 1994", ID["EPSG",1183]], MEMBER["European Terrestrial Reference Frame 1996", ID["EPSG",1184]], MEMBER["European Terrestrial Reference Frame 1997", ID["EPSG",1185]], MEMBER["European Terrestrial Reference Frame 2000", ID["EPSG",1186]], MEMBER["European Terrestrial Reference Frame 2005", ID["EPSG",1204]], MEMBER["European Terrestrial Reference Frame 2014", ID["EPSG",1206]], ELLIPSOID["GRS 1980",6378137,298.257222101, LENGTHUNIT["metre",1,ID["EPSG",9001]], ID["EPSG",7019]], ENSEMBLEACCURACY[0.1], ID["EPSG",6258]], PRIMEM["Greenwich",0, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]], ID["EPSG",8901]], ID["EPSG",4258]], CONVERSION["Europe Conformal 2001", METHOD["Lambert Conic Conformal (2SP)", ID["EPSG",9802]], PARAMETER["Latitude of false origin",52, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Longitude of false origin",10, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Latitude of 1st standard parallel",35, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Latitude of 2nd standard parallel",65, ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]]], PARAMETER["Easting at false origin",4000000, LENGTHUNIT["metre",1,ID["EPSG",9001]]], PARAMETER["Northing at false origin",2800000, LENGTHUNIT["metre",1,ID["EPSG",9001]]], ID["EPSG",19985]], CS[Cartesian,2, ID["EPSG",4500]], AXIS["Northing (N)",north, ORDER[1]], AXIS["Easting (E)",east, ORDER[2]], LENGTHUNIT["metre",1,ID["EPSG",9001]], USAGE[SCOPE["Conformal mapping at scales of 1:500,000 and smaller."], AREA["Europe - European Union (EU) countries and candidates. Europe - onshore and offshore: Albania; Andorra; Austria; Belgium; Bosnia and Herzegovina; Bulgaria; Croatia; Cyprus; Czechia; Denmark; Estonia; Faroe Islands; Finland; France; Germany; Gibraltar; Greece; Hungary; Iceland; Ireland; Italy; Kosovo; Latvia; Liechtenstein; Lithuania; Luxembourg; Malta; Monaco; Montenegro; Netherlands; North Macedonia; Norway including Svalbard and Jan Mayen; Poland; Portugal including Madeira and Azores; Romania; San Marino; Serbia; Slovakia; Slovenia; Spain including Canary Islands; Sweden; Switzerland; Turkey; United Kingdom (UK) including Channel Islands and Isle of Man; Vatican City State."], BBOX[24.60,-35.58,84.17,44.83]], ID["EPSG",3034]]

General rules for naming data sets and fields (documentation)

In the General rules for naming data sets and fields section of the documentation subsection Fields containing URL’s

http://egdi-public.gitlabpages.geus.dk/egdi-documentation/#/main-content/SpatialData?id=general-rules-for-naming-data-sets-and-fields

The documentation should be changed to note that when following the standards, that the attribute names are case sensitive.

the example has

FAULT_TYPE | FAULT_TYPE_URI

but for GeoSciML-Lite Shear Displacement Structure View these attributes must be called

faultType | faultType_uri

and instead of

YOUNG_UNIT_URI

you must use

representativeYoungerAge_uri

Aquifer definition

Sent by Javier Mesa S.


I am writing to you because I am making a discussion about the definition of aquifer. and I would like to ask you what definition do you use in your projects

Thanks 

Javier Mesa

Clarify standardisation needed for HOVER WP5

Some proposals for making the HOVER data compatible with standards have been made in a bilateral GIP-P - HOVER meeting. The WP5 scientists have some further questions about these proposals which can be discussed here.

MICKA forces vertical reference system and extent when not appropriate

Comment from HOVER metadata creator for a 2D TIFF dataset

MICKA seems to be forcing me to put the file "Presentation Form" as "Model digital". This would be fine (and accurate), but in doing this it's forcing me to define a vertical reference system and extent, which isn’t appropriate for this data. I have put in some dummy values to these fields to make the metadata record valid, but they are basically meaningless.

Is there some assumption in MICKA that model implies geographic x/y and height/depth?

Is it possible to set vertical reference to

<gmd:verticalElement gco:nilReason="inapplicable">

wms setup

HELP!!!

Edward Lewis | PGradCert (Geostats), MGeol, MAusIMM | Geospatial Analyst (Standards)

3DGEO-EU Test data

Sent by (Schimpf)


Dear support-team,

according to the data delivery plan of 3DGEO-EU we have some test data (WP1 deliverable 1.2):

NLS3D_ZMAP _ _ 11 single ASCII files( each layer in one file): spatial data for usage in 3D database.

This you will find in the zip file “ZMAP_ASCII.zip” __

NLS3D_GIS _ _ 11 single ASCII files( each layer in one file): spatial data for usage in 3D database.

This you will find in the zip file “ESRI_ASCII.zip” __

NLS3D_area _ _ 1 ESRI polygonshape file: spatial data.

This you will find in the zip file “3DGEO_EU_WP1PILOT_AREA.zip”

NLS3D_NETCDF __ This you will find in the zip file “NETCDF.zip” __

You can download the data here:

https://storage.driveonweb.de/dowdoc/367b4d841176d90a504d33d434d124690ae3c77519ae9890

Please note that the 3D model NLS3D is not public yet. Please make sure, while testing, that it is for internal use only! If this is not possible, please contact me.

Regards,

Lars

WP7-lead 3DGEO-EU

Request for creation of a forum - raw materials theme - GeoERA / Harmonization & technical issues

Dear team,

Hope to find you well.

Within the scope of the Lisbon FRAME workshop of the past 17-18th September, it has been decided that it would be important if the GeoERA projects, namely the raw materials theme, could have a place where to promote good practices, tackle implementation / technical issues related to data set harmonization and harvesting processes or simply for sharing experiences.

Can you please assist with this request by creating such a forum and please confirm, if necessary, with the Mintell4EU/Minerals4EU/GIP-P teams at GEUS ?

Kind regards and thank you in advance,
Filipe Santos.
Waymotion / LNEG
Tm: +351963981844

Test upload of NetCDF to EGDI for HOVER WP5

HOVER WP5 are producing NetCDF files with values for "Nitrate stored in the unsaturated zone". They are considering setting up a WCS to publish this data but we can also test what the EGDI platform can provide if the data was uploaded to it. Information and download link at https://www.bgs.ac.uk/services/ngdc/citedData/catalogue/800dd09b-5848-4803-a70c-cd15d5590f16.html.

EGDI metadata catalogue contains record at https://egdi.geology.cz/record/basic/71ba9d69-0596-1f70-e054-002128a47908.

MINDeSEA WP3 GeoPackage Data Delivery

Sent by Trevor Alcorn. Created by fire.


Dear GeoERA,

Please find attached a GeoPackage we have produced for MINDeSEA WP3 on Seafloor Massive Sulphide Deposits.

Data Management

1. 12 tables

a. 1 geometry point feature table 'MineralOccurrence'

​b. 11 attribute tables

2. Relationships as follows

Kind regards,

Trevor

Disclaimer:

This electronic message contains information (and may contain files), which may be privileged or confidential. The information is intended to be for the sole use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information and or files is prohibited. If you have received this electronic message in error, please notify the sender immediately. This is also to certify that this mail has been scanned for viruses.

Tá eolas sa teachtaireacht leictreonach seo (agus b'fhéidir sa chomhaid ceangailte leis) a d'fhéadfadh bheith príobháideach nó faoi rún. Is le h-aghaidh an duine/na ndaoine nó le h-aghaidh an aonáin atá ainmnithe thuas agus le haghaidh an duine/na ndaoine sin amháin atá an t-eolas. Murab ionann tusa agus an té a bhfuil an teachtaireacht ceaptha dó bíodh a fhios agat nach gceadaítear nochtadh, cóipeáil, scaipeadh nó úsáid an eolais agus/nó an chomhaid seo. Más trí earráid a fuair tú an teachtaireacht leictreonach seo cuir, más é do thoil é, an té ar sheol an teachtaireacht ar an eolas láithreach. Deimhnítear leis seo freisin nár aims odh víreas sa phost seo tar éis a scanadh.
­­


Attachments:

  1. SeafloorMassiveSulphideDepositsGeoPackage.gpkg

Import of GeoTIFF fails in EGDI test platform

Trying to import a hover TIFF file with associated metadata (https://egdi.geology.cz/record/basic/600ee753-5b98-4805-af06-23100a010833) fails as below:

Upload failed
Exception : ERROR: insert or update on table "map_layers" violates foreign key constraint "map_layers_fk" Detail: Key is not present in table "map_projections". org.postgresql.util.PSQLException: ERROR: insert or update on table "map_layers" violates foreign key constraint "map_layers_fk" Detail: Key is not present in table "map_projections". at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2310) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2023) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217) at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:421) at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:166) at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:137) at eu.egdiadmin.model.DatabaseInterface.insertTableRow(DatabaseInterface.java:306) at eu.egdiadmin.control.DatabaseController.insertLayer(DatabaseController.java:327) at eu.egdiadmin.dataimport.common.DataImporterBase.insertLayerRow(DataImporterBase.java:91) at eu.egdiadmin.dataimport.geotiff.GeoTiffDataImporter.importAsLayer(GeoTiffDataImporter.java:47) at org.apache.jsp.geopack3_jsp._jspService(geopack3_jsp.java:685) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.tomee.catalina.OpenEJBSecurityListener$RequestCapturer.invoke(OpenEJBSecurityListener.java:97) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:798) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)

SV: Products from HOVER WP7 to be uploaded in GeoTIFF format

Sent by Martin Hansen ([email protected]). Created by fire.


Good morning Marga,

We are working on the GeoTIFF upload now and I hope it will be available soon. So if you could wait a little then the we should have the functionality ready.

Best regards,

Martin

Fra: Margarita Patricia Sanabria Pab�n [email protected]
Sendt: 10. november 2020 20:50
Til: [email protected]; Martin Hansen [email protected]
Cc: Broda, Stefan [email protected]; Klaus Hinsby [email protected]; Gourcy Laurence [email protected]
Emne: Products from HOVER WP7 to be uploaded in GeoTIFF format

Dear Martin,

HOVER WP7 is ready to deliver final products in GeoTIFF format, but since the administration module does not yet support the upoading of GeoTIFF, they are not sure how to proceed.

Do they have to fill in the metadata and then email you the GeoTIFFs with some kind of number or identifier so you can relate the metadata to the GeoTIFFs?

Do they have to delay the delivery date of their products until this functionality is ready?

They are about to send a document with the deliverable amendments and they need to know if they have to delay the deliverable date or not.

Thanks in advance

Kind regards,

Marga

Margarita Sanabria

Geoscientific Information Systems Division

Spanish Geological Survey(IGME)

C/ R�os Rosas 23 | Madrid, 28003 | Espa�a

( +34 913.495.974 ext. 5974

[email protected], www.igme.es

Skype:margaritasanabriapavon

InfoIGME: http://info.igme.es

Testing GitHub

Sent by Bell, Patrick D. Created by fire.


This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.

WMS for M4EU?

Dear all,

Hope to find you all well.

Here in Portugal, our current version of M4EU is 2017-Prosum-v1.1.2.

Does someone have experience implementing Inspire compliant WMS services with this version, that can be shared in this forum?

We are afraid that in order to create an Inspire compliant WMS service,
deegree webservices 3.4 should be used so that WMS 1.3.0 can be provided.
Can someone please confirm this?

Kind regards,
Manuel Filipe Santos.
LNEG

RE: Products from HOVER WP7 to be uploaded in GeoTIFF format

Sent by Margarita Patricia Sanabria Pabón ([email protected]). Created by fire.


Thanks Martin for your quick reply.

When do you think the GeoTIFF upload will be ready? Is just to be able to write a date on the amendments document.

Best,

Marga

Margarita Sanabria

Geoscientific Information Systems Division

Spanish Geological Survey(IGME)

C/ R�os Rosas 23 | Madrid, 28003 | Espa�a

( +34 913.495.974 ext. 5974

[email protected], www.igme.es

Skype:margaritasanabriapavon

InfoIGME: http://info.igme.es


De: Martin Hansen [email protected]
Enviado: mi�rcoles, 11 de noviembre de 2020 8:21
Para: Margarita Patricia Sanabria Pab�n [email protected]; [email protected] [email protected]
Cc: Broda, Stefan [email protected]; Klaus Hinsby [email protected]; Gourcy Laurence [email protected]
Asunto: SV: Products from HOVER WP7 to be uploaded in GeoTIFF format

Good morning Marga,

We are working on the GeoTIFF upload now and I hope it will be available soon. So if you could wait a little then the we should have the functionality ready.

Best regards,

Martin

Fra: Margarita Patricia Sanabria Pab�n [email protected]
Sendt: 10. november 2020 20:50
Til: [email protected]; Martin Hansen [email protected]
Cc: Broda, Stefan [email protected]; Klaus Hinsby [email protected]; Gourcy Laurence [email protected]
Emne: Products from HOVER WP7 to be uploaded in GeoTIFF format

Dear Martin,

HOVER WP7 is ready to deliver final products in GeoTIFF format, but since the administration module does not yet support the upoading of GeoTIFF, they are not sure how to proceed.

Do they have to fill in the metadata and then email you the GeoTIFFs with some kind of number or identifier so you can relate the metadata to the GeoTIFFs?

Do they have to delay the delivery date of their products until this functionality is ready?

They are about to send a document with the deliverable amendments and they need to know if they have to delay the deliverable date or not.

Thanks in advance

Kind regards,

Marga

Margarita Sanabria

Geoscientific Information Systems Division

Spanish Geological Survey(IGME)

C/ R�os Rosas 23 | Madrid, 28003 | Espa�a

( +34 913.495.974 ext. 5974

[email protected], www.igme.es

Skype:margaritasanabriapavon

InfoIGME: http://info.igme.es

Geographic location on metadata

@Kramolisova
Could you please provide the longitude and latitude for datasets with spatial extent in Europe (including Greenland)? Of course I can put the values but if you provide them than all should use the same values.

Thank you in advance.
Best regards

the server https://data.geoscience.earth does not respond

There is a problem with the server where the code lists Project name is. The server is not responding https://data.geoscience.earth. The EGDI metadata catalogue has integrated this codelist to the search and edit and due to this doesn’t work properly and it is slowed down. Could you solve this problems and let us know about any failures in advance in the future. An avalanche of EGDI Metadata Catalogue users is been asking us for help since morning.

MINDeSEA WP3 GeoPackage Data Delivery

Sent by Francisco Javier González Sanz


Many thanks Trevor! Good work

Have a nice weekend

Javier


De: Trevor Alcorn
Enviado: jueves, 28 de mayo de 2020 14:43
Para: [email protected]
Cc: Francisco Javier González Sanz ; 'Henrik.Schiellerup' ; Xavier Monteys ; James Trench
Asunto: MINDeSEA WP3 GeoPackage Data Delivery

Dear GeoERA,

Please find attached a GeoPackage we have produced for MINDeSEA WP3 on Seafloor Massive Sulphide Deposits.

Data Management

1. 12 tables

a. 1 geometry point feature table 'MineralOccurrence'

​b. 11 attribute tables

2. Relationships as follows

Kind regards,

Trevor

Disclaimer:

This electronic message contains information (and may contain files), which may be privileged or confidential. The information is intended to be for the sole use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information and or files is prohibited. If you have received this electronic message in error, please notify the sender immediately. This is also to certify that this mail has been scanned for viruses.

Tá eolas sa teachtaireacht leictreonach seo (agus b'fhéidir sa chomhaid ceangailte leis) a d'fhéadfadh bheith príobháideach nó faoi rún. Is le h-aghaidh an duine/na ndaoine nó le h-aghaidh an aonáin atá ainmnithe thuas agus le haghaidh an duine/na ndaoine sin amháin atá an t-eolas. Murab ionann tusa agus an té a bhfuil an teachtaireacht ceaptha dó bíodh a fhios agat nach gceadaítear nochtadh, cóipeáil, scaipeadh nó úsáid an eolais agus/nó an chomhaid seo. Más trí earráid a fuair tú an teachtaireacht leictreonach seo cuir, más é do thoil é, an té ar sheol an teachtaireacht ar an eolas láithreach. Deimhnítear leis seo freisin nár aims odh víreas sa phost seo tar éis a scanadh.
­­

Geoera HOVER WP3 – Task 3-5c product for thermal and natural mineral waters – multilingual legends

Sent by Elster, Daniel. Created by fire.


Dear all,

we have to provide a multi-lingual legend for our product according to the HOVER proposal. However, I am not sure what needs to be translated from our side (WP3 participants). Please find the overview of our contents that we would like to show below.

Many thanks for your support!
Daniel


|

Field

|

unit

|

type

|

explanation

|


|


|


|


---|---|---|---|---|---|---|---|---

Name

|


|


|


|


|


|


|


|


N1

|

name of source

|

|

text

|

Please provide the name of source from the list of recognized natural mineral waters, otherwise a name for the thermal water source

|

|

|

|

N2

|

official name of natural mineral water

|

|

text

|

Please provide the trade description from the list of recognized natural mineral waters; not relevant for thermal waters

|

|

|

|

N3

|

country

|

|

text

|

|

|

|

|

General information

|

|

|

|

|

|

|

|

G1

|

classification

|

|

choose from list

|

|

|

|

|

G2

|

location

|

|

choose country specific grid cell ID

|

download country specific grids from https://www.eea.europa.eu/data-and-maps/data/eea-reference-grids-2

|

|

|

|

G3

|

type of water source

|

|

choose from list

|

|

|

|

|

G4

|

intended use 1

|

|

choose from list

|

|

|

|

|

G5

|

intended use 2

|

|

choose from list

|

|

|

|

|

G6

|

intended use 3

|

|

choose from list

|

|

|

|

|

G7

|

yield class

|

l/s

|

choose from list

|

extraction allowed by water law

|

|

|

|

Aquifer

|

|

|

|

|

|

|

|

B1

|

If borehole: true vertical depth

|

m

|

number

|

below terrain

|

|

|

|

B2

|

If borehole: screen or open hole: FROM (true vertical depth)

|

m

|

number

|

below terrain

|

|

|

|

B3

|

If borehole: screen or open hole: TO (true vertical depth)

|

m

|

number

|

below terrain

|

|

|

|

B4

|

Aquifer media type

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/AquiferMediaTypeValue __

|

|

|

|

B5

|

Aquifer type

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/AquiferTypeValue __

|

|

|

|

B6

|

Lithology of the aquifer 1

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/LithologyValue __

|

|

|

|

B7

|

Proportion, lithology of the aquifer 1

|

|

choose from CGI Geoscience codelist

|

http://resource.geosciml.org/classifier/cgi/proportionterm __

|

|

|

|

B8

|

Lithology of the aquifer 2

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/LithologyValue __

|

|

|

|

B9

|

Proportion, lithology of the aquifer 2

|

|

choose from CGI Geoscience codelist

|

http://resource.geosciml.org/classifier/cgi/proportionterm __

|

|

|

|

B10

|

Lithology of the aquifer 3

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/LithologyValue __

|

|

|

|

B11

|

Proportion, lithology of the aquifer 3

|

|

choose from CGI Geoscience codelist

|

http://resource.geosciml.org/classifier/cgi/proportionterm __

|

|

|

|

B12

|

Aquifer, younger age

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/ __

|

|

|

|

B13

|

Aquifer, older age

|

|

choose ID from INSPIRE code list

|

http://inspire.ec.europa.eu/codelist/GeochronologicEraValue/

|

|

|

|

Groundwater age information

|

|

|

|

|

|

|

|

A1

|

groundwater age

|

|

choose from list

|

|

|

|

|

Hydrochemistry

|

|

|

|

please provide a representative hydrochemical analysis of the raw water not the finishes product

|

|

|

|

H1

|

Temperature class

|

�C

|

choose from list

|

water temperature at the outlet

|

|

|

|

H2

|

Total dissolved solid class

|

g/l

|

choose from list

|

|

|

|

|

H3

|

Specific conductivity

|

�S/cm; 25�C

|

number/text

|

representative hydrochemical analysis

|

|

|

|

H4

|

pH

|

|

number/text

|

representative hydrochemical analysis

|

|

|

|

H5

|

Redox potential (Eh)

|

mV

|

number/text

|

representative hydrochemical analysis

|

|

|

|

H6

|

Oxygen (O2)

|

mg/l

|

number/text

|

representative hydrochemical analysis

|

|

|

|

H7

|

Sodium (Na)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H8

|

Potassium (K)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H9

|

Calcium (Ca)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H10

|

Magnesium (Mg)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H11

|

Strontium (Sr)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H12

|

Barium (Ba)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H13

|

Iron (Fe total)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H14

|

Manganese (Mn total)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H15

|

Ammonium (NH4)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H16

|

Bicarbonate (HCO3)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H17

|

Carbonat (CO3)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H18

|

Fluoride (F)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H19

|

Chloride (Cl)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H20

|

Bromide (Br)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H21

|

Iodide (I)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H22

|

Sulfate (SO4)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H23

|

Nitrate (NO3)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H24

|

Hydrogen Sulfide (HS)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H25

|

Aluminium (Al)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H26

|

Antimony (Sb)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H27

|

Arsenic (As)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H28

|

Beryllium (Be)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H29

|

Lead (Pb)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H30

|

Cadmium (Cd)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H31

|

Cesium (Cs)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H32

|

Chrome (Cr)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H33

|

Cobalt (Co)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H34

|

Copper (Cu)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H35

|

Lithium (Li)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H36

|

Molybdenum (Mo)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H37

|

Nickel (Ni)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H38

|

Mercury (Hg)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H39

|

Rubidium (Rb)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H40

|

Selenium (Se)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H41

|

Uranium (U)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H42

|

Vanadium (V)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H43

|

Zinc (Zn)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H44

|

Tin (Sn)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H45

|

m-Silic acid (H2SiO3)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H46

|

o-Boric acid (H3BO3)

|

mg/l

|

number/text

|

representative hydrochemical analysis, if under detection limit provide < + number e.g. <0,2; if not available <DL

|

|

|

|

H47

|

gas phase dominance

|

dominance

|

choose from list

|

|

|

|

|

Comments

|


|


|


|


|


|


|


|


C1

|

free comment

|

|

text

|

|

|

|

|

|

|

|

|

|

|

|

|

name of the attriubute

|

G1

|

G3

|

G4 to G6

|

G7

|

A1

|

**H1 **

|

H2

|

H43

Field

|

classification

|

type of water source

|

intended use

|

yield class (l/s)

|

groundwater age (years)

|

temperature class

|

total dissolved solid class (g)

|

gas phase dominance

1

|

thermal water source

|

single well

|

bottled natural mineral water

|

<5

|

younger than 60

|

<15

|

<1

|

Methane (CH4)

2

|

natural mineral water (Directive 2009/54/EC)

|

well field

|

natural mineral water publicly available

|

5-25

|

older than 60

|

15-20

|

1-14,5

|

Carbon dioxide (CO2)

3

|

Natural mineral water (national law recognition)

|

single artesian well

|

thermal water for balneology

|

25

|

older than 10.000

|

20-30

|

14,5

|

Nitrogen (N2) including noble gases

4

|

|

artesian well field

|

thermal water for heating

|

|

older than 11.500.000

|

30-40

|

|

5

|

|

single captured spring

|

thermal water for electricity production

|

|

|

40-50

|

|

6

|

|

captured spring group

|

|

|

|

50-60

|

|

7

|

|

single gallery

|

|

|

|

60-70

|

|

8

|

|

gallery group

|

|

|

|

70-80

|

|

9

|

|

|

|

|

|

80-90

|

|

10

|

|

|

|

|

|

90-100

|

|

11

|

|

|

|

|

|

100

|

|

--
Daniel ELSTER, MMSc.
Hydrogeologe / Hydrogeologist
Fachabteilung Hydrogeologie & Geothermie / Department of Hydrogeology & Geothermal Energy

Geologische Bundesanstalt / Geological Survey of Austria
Neulinggasse 38, 1030 Wien, �sterreich

Web: www.geologie.ac.at

Question from MUSE and first dataset for testing

Sent by David Garcia. Created by fire.


Dear Martin and GIP-P support team,

I am writing to you today as a MUSE partner. I have a request for you:

  • Martin Hansen: We sent you several months ago a test dataset (see in attachments) for testing the functionality "From getfeatureinfo creation of an automatic report querying a selection of layers" and see how that dataset will look in EGDI (see email below). However, we never got a feedback from you because the document repository was still under construction. During our recent bilateral meetings with other projects, I understood that the document repository is not finish, but we can already do some testing. Hence, I was wondering if you could give our request a try and provide a feedback. Is that possible? If so, how do you recommend to do that testing? E.g., should we upload the pdfs to the Doc Rep providing metadata, etc. and then you establish the link to the spatial data or you do everything yourself as a test?

  • [email protected]: This dataset is in the final form that will be delivered. Hence, I was wondering if you could have a look and let us know if it is OK concerning data standardization, formats, etc. In principle, this is a simple file consisting of a GIS file (in this case a shapefile – we can also deliver it in GeoPackage format) containing points, which will go to EGDI database and which define the location of geothermal installations. Those points will be linked to PDFs (in attachments), which contain all the information we want to share from those locations. Hence, (at least the GIP-P recommend otherwise) the GIS file will not contain any attribute. The idea is that when an user clicks on a point, a window will pop-up showing the information contained in the PDF linked to that location. Could you, please, let us know your opinion? Is that OK concerning standards, etc.? Otherwise, could you, please, provide some advice on how we could improve this dataset to make it compatible with EGDI regulations?

Thank you in advance!

David.

From: David Garcia
Sent: 27 February 2020 17:09
To: Martin Hansen
Cc: J�rgen Tulstrup; Steiner, Cornelia
Subject: Question from MUSE and first dataset for testing functionality "From getfeatureinfo creation of an automatic report querying a selection of layers"

Dear Martin,

How are you? I have a question/requirement and a first dataset for testing from MUSE.

Question:


My colleagues from MUSE are wondering whether it would be possible to link the fact sheets they have generated from each pilot area (available at https://geoera.eu/projects/muse3/pilot-urban-areas-in-the-muse-project/) to the respective polygons defining each pilot area in the webGIS of GeoERA/MUSE (https://data.geus.dk/egdi/?mapname=egdi_geoera_muse#baslay=null&optlay=&extent=701260,973940,5537170,3851000&layers=muse_project_areas_region). Would that be possible?

Testing:

We (MUSE) have our first product (almost) ready, but before producing the final version, we would like to test one of the datasets to be sure that EGDI meets our expectations and vice versa. We were therefore wondering if you could upload the shapefile here attached and test the functionality "From getfeatureinfo creation of an automatic report querying a selection of layers" by linking each point included in the shapefile to its respective PDF factsheet (also in attachments). Could you do that and get back to us to see how that test goes?

Many thanks in advance!

David.


Attachments:

  1. PDFs.zip
  2. Shapefile.zip

GeoERA Hotlime Pilot Areas

As a member of the GeoERA Hotlime project I just wanted to mention that the Map Layer on the EGDI Platform showing the outlines of the 10 pilot areas of the Project is not working..

Kind regards,

Clemens Porpaczy

Products from HOVER WP7 to be uploaded in GeoTIFF format

Sent by Margarita Patricia Sanabria Pabón ([email protected]). Created by fire.


Dear Martin,

HOVER WP7 is ready to deliver final products in GeoTIFF format, but since the administration module does not yet support the upoading of GeoTIFF, they are not sure how to proceed.

Do they have to fill in the metadata and then email you the GeoTIFFs with some kind of number or identifier so you can relate the metadata to the GeoTIFFs?

Do they have to delay the delivery date of their products until this functionality is ready?

They are about to send a document with the deliverable amendments and they need to know if they have to delay the deliverable date or not.

Thanks in advance

Kind regards,

Marga

Margarita Sanabria

Geoscientific Information Systems Division

Spanish Geological Survey(IGME)

C/ R�os Rosas 23 | Madrid, 28003 | Espa�a

( +34 913.495.974 ext. 5974

[email protected], www.igme.es

Skype:margaritasanabriapavon

InfoIGME: http://info.igme.es

Raster in GeoPackage - Converts to RGB

Dear Hans,
We are in the final stages of the hotlime and we are preparing our datasets to be sent ( Temperature at top of reservoir, thickness of the reservoir, Heat in place for the entire reservoir and the fault network).

For the fault network, the file is a shapefile and for the others they are rasters.
We have projected them in the coordinate system that it was indicated in the instructions (see document attached) "Coordinate system for all spatial products should be ETRS89 / LCC Europe (EPSG:3034) – as confirmed by GIP-P".
When we want to add the raster to the geopackage, there is a problem as the raster gets converted....

See images below that illustrate the problem.
• Pink raster with the right color scheme is the temperature of reservoir. As you can see is a GRID.
• When we add it into the geopackage using the "add raster to GeoPackage" it converts it into a RGB raster (see images below).

Is it possible that we get a link to the instructions?
In the same document there was a link on how to create the GeoPackage https://geoera-gip.github.io/documentation/data.html#providing-gis-data but this link does not work anymore.

Kind regards,
Beatriz

Help with geopackages using QGIS for GeoERA TACTIC project

-----Original Message----- From: Mansour, Majdi

I am working on TACTIC GeoERA project with GEUS and other partners. GEUS were trying to create a geopackage out of a simple ascii file using QGIS and were failing. I just wonder if you know how to create these geopackages and if you can offer any guidance.

Geoera intranet access

Sent by Peter van der Keur ([email protected]). Created by fire.


Hello,

There seems to be a problem accessing the GeoERA intranet. We unsuccessfully tried this morning for uploading TACTIC deliverables.

Pls. advise, thank you.

Best regards,

Peter


Peter van der Keur , Ph.D.

Senior scientist

Geological Survey of Denmark and Greenland (GEUS) ****

Dept. of Hydrology ****

Oster Voldgade 10, DK-1350 Copenhagen K

Denmark

Tel. 0045 29893192 (cell phone)

https://eng.geus.dk/water-resources/

Skype : petervanderkeur

[HARVESTING] How providers can check if miningfeatureoccurence <XOR> constrain is satisfied

You need to check if one miningfeatureoccurence.miningfeatureoccurencedbk (MFO) is linked to miningfeatureoccurencedbk field in one and only one of mine, miningactivity, miningwaste, prosumminingactivity, prosumminingwaste, processingtransformationplant, processingtransformationactivity tables.

To do that you can use the query below. Query return rows with incorrectly linked MFO’s in first column. Other columns are dbk's of the tables in which MFO's are linked to. To satisfy constrain one and only one not null dbk from connected tables is allowed. This mean that correct entries will have six [null] values in each row (but correct entries are not shown by the query).

SELECT
t1.miningfeatureoccurrencedbk,
t1.minedbk,
t1.miningactivitydbk,
t1.miningwastedbk,
t1.processingtransformationplantdbk,
t1.processingtransformationactivitydbk,
t1.prosumminingactivitydbk,
t1.prosumminingwastedbk FROM
(SELECT *, ((CASE WHEN t.minedbk IS NULL THEN 1 ELSE 0 END)

  • (CASE WHEN t.miningactivitydbk IS NULL THEN 1 ELSE 0 END)
  • (CASE WHEN t.miningwastedbk IS NULL THEN 1 ELSE 0 END)
  • (CASE WHEN t.processingtransformationplantdbk IS NULL THEN 1 ELSE 0 END)
  • (CASE WHEN t.processingtransformationactivitydbk IS NULL THEN 1 ELSE 0 END)
  • (CASE WHEN t.prosumminingactivitydbk IS NULL THEN 1 ELSE 0 END)
  • (CASE WHEN t.prosumminingwastedbk IS NULL THEN 1 ELSE 0 END)) AS sum_of_nulls FROM
    (SELECT
    public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk,
    public.Mine.mineDbk,
    public.MiningActivity.miningActivityDbk,
    public.MiningWaste.miningWasteDbk,
    public.ProcessingTransformationPlant.ProcessingTransformationPlantDbk,
    public.ProcessingTransformationActivity.processingTransformationActivityDbk,
    public.ProSUMMiningActivity.prosumMiningActivityDbk,
    public.ProSUMMiningWaste.prosumMiningWasteDbk
    FROM
    public.MiningFeatureOccurrence
    LEFT OUTER JOIN
    public.ProcessingTransformationPlant ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.ProcessingTransformationPlant.miningFeatureOccurrenceDbk
    LEFT OUTER JOIN
    public.Mine ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.Mine.miningFeatureOccurrenceDbk
    LEFT OUTER JOIN
    public.ProcessingTransformationActivity ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.ProcessingTransformationActivity.miningFeatureOccurrenceDbk
    LEFT OUTER JOIN
    public.ProSUMMiningWaste ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.ProSUMMiningWaste.miningFeatureOccurrenceDbk
    LEFT OUTER JOIN
    public.MiningWaste ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.MiningWaste.miningFeatureOccurrenceDbk
    LEFT OUTER JOIN
    public.ProSUMMiningActivity ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.ProSUMMiningActivity.miningFeatureOccurrenceDbk
    LEFT OUTER JOIN
    public.MiningActivity ON public.MiningFeatureOccurrence.miningFeatureOccurrenceDbk = public.MiningActivity.miningFeatureOccurrenceDbk) t)t1
    WHERE t1.sum_of_nulls < 6;

Test upload of Georeferenced reports for HOVER WP5

HOVER WP5 is producing geo-referenced reports of "Conceptual models of nitrate transport in the unsaturated zone" and "denitrification potential mapping". For each report there will be a polygon outlining the area to which it refers. They wish to upload this data to the EGDI platform so that the polygons can be displayed on a map and linked to the reports so that a user can select a polygon and see the associated report. This functionality exists on the EGDI platform so they would like to test the format of data they need to supply.

GeoERA GIP-P: data delivery plan

Sent by Margarita Patricia Sanabria Pabón. Created by fire.


Dear Martin and Stefan,

I am not sure the to upload system for spatial data is currently accessible. I think you need to have permission to access it.

I copy Martin Hansen and Andrej Vihtelič GIP-P WP6/WP7 leaders. They can answer your question and give you the necessary permissions. Martin or Andrej can you provide an answer to our HOVER WP7 colleagues (see email below)? Please, Take in account that HOVER WP7 products are several GeoTIF.

Thanks in advance.

Kind regards,

Marga

Margarita Sanabria

Geoscientific Information Systems Division

Spanish Geological Survey(IGME)

C/ Ríos Rosas 23 | Madrid, 28003 | España

( +34 913.495.974 ext. 5974

www.igme.es

InfoIGME: http://info.igme.es

De: Krombholz, Martin
Enviado el: lunes, 24 de agosto de 2020 18:03
Para: Margarita Patricia Sanabria Pabón
CC: Broda, Stefan
Asunto: WG: GeoERA GIP-P: data delivery plan

Dear Marga,

we´re trying to understand the workflow for delivering spatial data to the GIP-P. As far as I have understood it is necessary to create a metadata entry for any dataset (at the EGDI Metadata Editor website https://egdi.geology.cz/record/new) before uploading the dataset(s). That is clear and has worked in the past (by harvesting or manual entry using Stefan´s login details). But WHERE is the geo-data upload possible, and where can I find a detailed documentation of this procedure? The various sources of MIcKA Documentation (https://czechgeologicalsurvey.github.io/MICKA-Docs/index.html, https://czechgeologicalsurvey.github.io/MICKA-Docs/mickacookbooklite.html, https://data.geus.dk/gip-p/DeliveringDataToEGDI.docx) don´t explain this really.

Thanks for your help & best wishes from Berlin (Team Stefan Broda)!
-----------------------------------------------------------------------------------

Martin Krombholz

Basic Information – Groundwater and Soil (B2.2)

Federal Institute for Geosciences and Natural Resources

Branch Office Berlin

Wilhelmstr. 25-30

13593 Berlin

GERMANY

www.bgr.bund.de/Informationsgrundlagen-Grundwasser

-----------------------------------------------------------------------------------

Von: Broda, Stefan
Gesendet: Mittwoch, 12. August 2020 16:38
An: Krombholz, Martin ; Duscher, Klaus
Betreff: WG: GeoERA GIP-P: data delivery plan

Zur Info

Von: Gourcy Laurence
Gesendet: Montag, 10. August 2020 11:47
An: Margarita Patricia Sanabria Pabón ; daniel.elster ; Jens Aamand ; Matthew Ascott, Klaus; Broda, Stefan ; Lopez Benjamin
Cc: David Garcia ; Tulstrup, Jørgen
Betreff: RE: GeoERA GIP-P: data delivery plan

Dear all

I updated the doc. Thanks for WP’s feedback respecting GIP deadline (24 August…)

Laurence

Laurence GOURCY

Evaluation et valorisation des connaissances sur l’eau/ Evaluation and valorisation of the water knowledge

Responsable d’unité/Unit Head

https://orcid.org/0000-0003-3897-4479

De : Margarita Patricia Sanabria Pabón
Envoyé : jeudi 23 juillet 2020 19:57
À : Gourcy Laurence ; daniel.elster; Jens Aamand; Matthew Ascott; Hinsby, Klaus; stefan.broda; Lopez Benjamin
Cc : David Garcia ; Tulstrup, Jørgen
Objet : GeoERA GIP-P: data delivery plan

Dear Laurence and HOVER WP leaders,

In June David García, leader of the GIP-P WP2, sent an email requesting your collaboration to agree on a delivery plan for the products (see email below and document attached). I encourage you to look at the delivery plan document as it contains examples that will help you understand what information needs to be completed.

As agreed at the GW PB meeting on June 6th, and in order to facilitate your task, I am enclosing the pre-filled data delivery plan document with the products described so far in the bilateral meeting. Please check the information already included for your WP, correct/add whatever you consider and complete the missing information. It is very important that you fill in the columns regarding test and feedback dates, as well as the final delivery dates. These dates should not be final but as realistic as possible.

Please pay attention to my comments as they are questions/doubts that it would be nice to solve through this document.

The original deadline for submission of the information was June 30th. During the GW PB meeting in June, a new deadline was agreed for August 24.

During the week of August 24-28, I will answer any questions that arise and gather all the replies to send them to David Garcia on Monday, August 31. If possible, I would appreciate to receive a single document collecting all products information from your project instead of several documents (one per WP). This will avoid misunderstandings, copy/paste errors and help to establish a clear and coordinated data delivery plan.

Thanks in advance for your collaboration and I wish you a great summer holiday,

Marga

PS: I will be on vacation from July 27th to August 21st.

Margarita Sanabria

Geoscientific Information Systems Division

Spanish Geological Survey(IGME)

C/ Ríos Rosas 23 | Madrid, 28003 | España

( +34 913.495.974 ext. 5974

www.igme.es

InfoIGME: http://info.igme.es

De: David Garcia
Enviado el: martes, 2 de junio de 2020 16:05
Para: Stefan.Knopf; Schimpf; Hartmann; Gessel, S.F. (Serge) van ; Hintersberger, Esther ; Gerold Diepolder ; Götzl, Gregor ; Claus Becher Ditlefsen; Peter Britze; Uffe Larsen; Kris Piessens; Renata Barros ; Heldal Tom johan.tenveen; Francisco Javier González Sanz; Maria Judge; Xavier.Monteys; David Whitehead; Mikael Pedersen; Lisbeth Flindt Jørgensen ; Lidia Quental ; daniel.oliveira; Broers, H.P. (Hans Peter); Anker Lajer Højberg; Bianchi, Marco; dma
; rswa; Gourcy Laurence ; khi; c.slenter
CC: ane.bang-kittilsen; Jørgen Tulstrup ; Margarita Patricia Sanabria Pabón ; Darnault Romain; James Trench ; Trevor Alcorn
Asunto: data delivery plan

Dear GSPs’ colleagues,

I am writing to you because we must produce a data delivery plan for the GeoERA project, in which we describe how, when and which data the various GSPs will be delivering to EGDI. This data delivery plan is a compilation of individual data delivery plans created by each GSP. These should contain not only the (expected) dates of delivery for each dataset and document that will be submitted to EGDI, but also as much information as possible about the data, the testing process and how the data will be delivered to EGDI. The idea is to end with a document, comprising: what type of data the projects will produce, when test data will be (or have been) delivered to the GIP-P, what feedbacks are expected from the GIP-P, and when/how the final datasets will be delivered to EGDI.

I have taken the liberty of creating an example of how GSPs could organise their data delivery plan (see in attachments). This consists of three tables to be filled out individually by each GSP. If any of you believe that this example does not cover the particularities of your project, you are welcome to modify it according to your needs. However, if you do so, please, discuss the changes with the GIP-P liaison officer following your project; these are: Romain Darnault (HotLime, GARAH, 3DGEO-EU and HIKE); Margarita P. Sanabria Pabón (all Groundwater projects); James Trench & Trevor Alcorn (all Raw Material projects); David García Moreno (MUSE and GeoConnect3D). You can find the emails of each liaison officer in cc.

The data delivery plan comprising all individual GSPs’ data delivery plans is due in September 30th, 2020. Hence, I would be very grateful if you could send me your data delivery plans by July 30th, so we have time to review it together and write the GeoERA data delivery plan in time to meet the deadline.

In other business, the GeoERA support team is up and running (email address: [support AT geoera.eu]). You can already send test data for them to verify formats, compatibility with standards, as well as to test functionalities, ask questions or request assistance to create standardized GIS files or services. Note that all emails send to [support AT geoera.eu] and the answers provided by the support team are publicly available at https://github.com/GeoEra-GIP/Project-Support-WP8/issues.

Have a nice week!

Regards,

David García Moreno

GIP-P – WP2 coordinator

Geological Survey of Belgium

Royal Belgian Institute of Natural Sciences

Jennerstreet 13 - 1000 Brussels - Belgium.

PS. All documentation/guidelines on data formats, etc. created so far by the support team are available at https://geoera-gip.github.io/documentation/index.html.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.