1st Data Package: 03 Exposure Layers #10

p-a-s-c-a-l · 2018-12-06T12:55:19Z

Create Population Exposure Layers and make them available in CSIS.
This encompasses the following steps:

provide population exposure data (PLINIVUS?)
transformation to the harmonised Grid
expose Layers (WCS/WMS) via GeoServer (currently located at METEOGRID Server)
define some simple styling for Layers
Create Data Package Meta-Data in CSIS (see also https://github.com/clarity-h2020/data-package
1st Data Package: 00 Background Layers - 2) Create Data Resource #7)
Provide meta-data for Data Management Plan (if not already available from D2.2 activities)

Questions:

ATM we've got only population exposure for the Naples reference region coming from WP2, right?
Where can I find the respective meta-data? Is it available in CKAN?

p-a-s-c-a-l · 2019-02-25T08:03:42Z

What is the status here? There are 3 Population Layers available for DC1 on METEOGRID GeoServer. @bernhardsk Are those the same that are used for impact calculation in EMIKAT?

humerh · 2019-02-25T08:19:39Z

As described in my last mail: YES!! Von: Pascal Dihé <notifications@github.com> Gesendet: Montag, 25. Februar 2019 09:04 An: clarity-h2020/data-package <data-package@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Betreff: Re: [clarity-h2020/data-package] 1st Data Package: 03 Exposure Layers (#10) What is the status here? There are 3 Population Layers available for DC1 on METEOGRID GeoServer. @bernhardsk<https://github.com/bernhardsk> Are those the same that are used for impact calculation in EMIKAT? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#10 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ATWGJP59x_qhh3UvA04WP9IAyKwYQrWBks5vQ5jhgaJpZM4ZGdCA>.

maesbri · 2019-03-08T12:29:02Z

@ghilbrae , in order to add these population exposure layers (https://clarity.meteogrid.com/geoserver/Exposure/wcs?request=GetCapabilities) in the data package I need the following information:

what is origin source used to make the calculations
what is the time frame (temporal extent) for which this data refers to?

ghilbrae · 2019-03-11T08:31:44Z

@maesbri I'll check with my colleagues and will come back with an answer.

ghilbrae · 2019-03-11T09:07:33Z

what is origin source used to make the calculations

It seems the source is a layer uploaded to ATOS' FTP by @negroscuro

what is the time frame (temporal extent) for which this data refers to?

They refer to the current state.

maesbri · 2019-03-11T10:03:38Z

what is origin source used to make the calculations

It seems the source is a layer uploaded to ATOS' FTP by @negroscuro

That's too vague ... I need to add the concrete reference to the layers used (preferrrably the link to the Geoserver layer)

what is the time frame (temporal extent) for which this data refers to?

They refer to the current state.
Once I know the layers I can check their metadata for the time range

stefanon · 2019-03-11T10:44:01Z

@maesbri Dear Miguel,
about exposure data, the layer you were talking about was result of elaboration starting from ISTAT population census data tables. You'll find the "ISTAT census data - population " dataset description in CKAN.

what is origin source used to make the calculations

That was the source, but population data needed to be related to the geographic census zones and EU grid, the work was done by METEOGRID

what is the time frame (temporal extent) for which this data refers to?

the population data refers to year 2011 as in CKAN description.

maesbri · 2019-03-19T14:59:34Z

@therter , I have now updated the naples data package with the 3 resources referring to the population exposure (they are linked to the eu-gl step "exposure evaluation", let me know if they should refer to additional eu-gl steps too).

therter · 2019-03-20T09:06:02Z

@maesbri The resource with the url https://csis.myclimateservice.eu/node/434 has no mapview property. Is this correct?

And the resource https://csis.myclimateservice.eu/node/409 has also no mapview attribute

maesbri · 2019-03-20T09:37:32Z

I forgot to fill in those fields. It should be fixed now :)

p-a-s-c-a-l · 2019-06-28T08:44:39Z

Exposure Data (Population) for whole Europe will be served from a new EMIKAT API. The Data Package and the table rest API have to be updated accordingly.

p-a-s-c-a-l · 2019-07-10T06:25:32Z

The EE Resources in this Data Package Package currently contain Local Census Data - Population for the Naples Region from ISTAT (Italian National Institute of Statistics). These resources will be moved to a new DC1 Data Package that is available for subscribers only! The current resources are replaced with the Europe-Level Population exposure data from Copernicus.

p-a-s-c-a-l · 2019-07-15T06:23:27Z

Population Exposure Data is avilable in EMIKAT: clarity-h2020/emikat#10 (comment)
The resources have to be updated accordingly.

DenoBeno · 2019-07-30T08:07:25Z

@heinrich: Pascal says that the population data is in EMIKAT now? Is this correct?

humerh · 2019-07-30T09:15:56Z

The population exposure layer is accessible at:

https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_EL_POPULATION_INTERPOLATED.2016/table/data?rownum=1000

emikatID=2846

humerh · 2019-07-30T09:16:33Z

We use the Populationen Data from EUROSTAT (1km*1km) and split this data to the 500m-Grid by using Landcover data from Copernicus. This data are available for all Europe.

DenoBeno · 2019-07-30T14:38:08Z

I have added "European population distribution" resource to European data package now.

https://csis.myclimateservice.eu/node/682/edit#browser

Issues:

I don't know what is the license for this data. If it's based on EUROSTAT and COPERNICUS,

Land cover COPERNICUS data has this license: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32013R1159 (In short https://land.copernicus.eu/faq/about-data-access)
EUROSTAT: https://ec.europa.eu/eurostat/about/policies/copyright

This are both "use as you want, but inform people that it's from us and that you have modified it (if applicable)". I explained this in the description and choose three different licenses for the data resource:

Furthermore, there are several paths to this resource, as explained in clarity-h2020/emikat#10

Additional Services available:
EMIKAT REST: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_EL_POPULATION_INTERPOLATED.2016/table/data?rownum=1000

or EMIKAT GeoJSON: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_EL_POPULATION_INTERPOLATED.2016/table/geojson?rownum=1000

or CSV: https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_EL_POPULATION_INTERPOLATED.2016/table/csv?rownum=1000

or WMS:
WMS: https://service.emikat.at/geoserver/clarity/wms?service=WMS&version=1.1.0&request=GetMap&layers=clarity:view.2955&bbox=4673500.0,1980000.0,4691500.0,1988000.0&width=768&height=341&srs=EPSG:3035&format=image/gif&CQL_FILTER=SZ_ID=2846

Now, I have added them all, but what are the service types for the first three? :-(

DenoBeno · 2019-07-30T14:42:54Z

Furthermore, I run into a strange bug shown here:

This is probably due to automated title generation. I propose to let the user define a title - at least we could then Call these references "European population data - EMIKAT GeoJSON" or such.

DenoBeno · 2019-07-30T14:43:46Z

Furthermore, the EMIKAT data access is password protected. How is this supposed to work in the DP?

humerh · 2019-07-30T15:54:43Z

You inserted this Path:
https://service.emikat.at/EmiKatTst/api/scenarios/2846/feature/tab.CLY_EL_POPULATION_INTERPOLATED.2016/table/data?rownum=1000

Instead of the fixed ID 2846 there should be a placeholder for the emikatId, which is an attribute in the study.

Maybe the path should be replaced to:
https://service.emikat.at/EmiKatTst/api/scenarios/$emikatId/feature/tab.CLY_EL_POPULATION_INTERPOLATED.2016/table/data?rownum=1000

@maesbri can you clarify this?

humerh · 2019-07-30T15:57:50Z

The password has to be provided by "Basic Authentication" Header.

p-a-s-c-a-l · 2019-07-31T06:32:21Z

Furthermore, the EMIKAT data access is password protected. How is this supposed to work in the DP?

There is currently a temporary workaround implemented (basic auth) since offering Single-Sign-On seems to be stalled.

p-a-s-c-a-l · 2019-09-26T08:36:43Z

The respective Population Exposure Resource is described here
Flood (Buildings?) Exposure resources still pending

DenoBeno · 2019-10-14T15:54:56Z

Indeed, we need buildings exposure for the flooding. Not sure what all goes under "buildings" though. Are we going to have separate layers for the different types of buildings?

p-a-s-c-a-l · 2019-10-30T07:59:16Z

Population Exposure Layers available for 1st data package. Flood is a different issue.

p-a-s-c-a-l added data-package meta-data labels Dec 6, 2018

p-a-s-c-a-l added this to the 1st Data Package milestone Dec 6, 2018

p-a-s-c-a-l assigned luis-meteogrid Dec 6, 2018

p-a-s-c-a-l added this to To do in T2.2 Demonstrator-specific data collection via automation Dec 6, 2018

p-a-s-c-a-l assigned ghilbrae Dec 6, 2018

p-a-s-c-a-l added this to To do in T7.3 Data Management via automation Dec 6, 2018

p-a-s-c-a-l added this to To do in T1.3 Climate Services Co-creation via automation Dec 6, 2018

p-a-s-c-a-l assigned p-a-s-c-a-l and stefanon Dec 6, 2018

p-a-s-c-a-l mentioned this issue Dec 7, 2018

1st Data Package: 01 HC Layers #8

Closed

6 tasks

maesbri mentioned this issue Dec 10, 2018

CLARITY Data Package: Example clarity-h2020/csis#20

Closed

7 tasks

p-a-s-c-a-l mentioned this issue Dec 12, 2018

Implement EE Table clarity-h2020/table-components#3

Closed

5 tasks

p-a-s-c-a-l added the SHOWSTOPPER Feature or bug, that, if not addressed, renders the CSIS essentially useless label Dec 14, 2018

p-a-s-c-a-l added the BB: Data Package Tool Data Package Export and Import Tool Building Block label Jan 14, 2019

p-a-s-c-a-l moved this from To do to In progress in T7.3 Data Management Feb 5, 2019

p-a-s-c-a-l moved this from To do to In progress in T1.3 Climate Services Co-creation Feb 13, 2019

p-a-s-c-a-l removed this from In progress in T7.3 Data Management Apr 30, 2019

p-a-s-c-a-l mentioned this issue Jun 28, 2019

Exposure - Switch to EMIKAT API clarity-h2020/table-state-rest-api#7

Closed

p-a-s-c-a-l moved this from In progress to Data Packages in T1.3 Climate Services Co-creation Jul 2, 2019

p-a-s-c-a-l moved this from Backlog: Low Priority to Backlog: High Priority in T1.3 Climate Services Co-creation Jul 3, 2019

p-a-s-c-a-l moved this from Backlog: High Priority to In Progress in T1.3 Climate Services Co-creation Jul 15, 2019

p-a-s-c-a-l mentioned this issue Jul 15, 2019

Meta-Data for 1st Data Package clarity-h2020/ckan#18

Closed

2 tasks

DenoBeno assigned humerh Jul 30, 2019

p-a-s-c-a-l closed this as completed Sep 26, 2019

T1.3 Climate Services Co-creation automation moved this from In Progress to Done Sep 26, 2019

T2.2 Demonstrator-specific data collection automation moved this from To do to Done Sep 26, 2019

p-a-s-c-a-l reopened this Sep 26, 2019

T1.3 Climate Services Co-creation automation moved this from Done to In Progress Sep 26, 2019

T2.2 Demonstrator-specific data collection automation moved this from Done to In progress Sep 26, 2019

p-a-s-c-a-l added this to To do in T3.2 Climate Intelligence via automation Oct 30, 2019

p-a-s-c-a-l closed this as completed Oct 30, 2019

T1.3 Climate Services Co-creation automation moved this from In Progress to Done Oct 30, 2019

T2.2 Demonstrator-specific data collection automation moved this from In progress to Done Oct 30, 2019

T3.2 Climate Intelligence automation moved this from To do to Done Oct 30, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

1st Data Package: 03 Exposure Layers #10

1st Data Package: 03 Exposure Layers #10

p-a-s-c-a-l commented Dec 6, 2018 •

edited by DenoBeno

p-a-s-c-a-l commented Feb 25, 2019

humerh commented Feb 25, 2019 via email

maesbri commented Mar 8, 2019 •

edited

ghilbrae commented Mar 11, 2019

ghilbrae commented Mar 11, 2019

maesbri commented Mar 11, 2019

stefanon commented Mar 11, 2019

maesbri commented Mar 19, 2019 •

edited

therter commented Mar 20, 2019 •

edited

maesbri commented Mar 20, 2019

p-a-s-c-a-l commented Jun 28, 2019 •

edited

p-a-s-c-a-l commented Jul 10, 2019

p-a-s-c-a-l commented Jul 15, 2019

DenoBeno commented Jul 30, 2019

humerh commented Jul 30, 2019

humerh commented Jul 30, 2019

DenoBeno commented Jul 30, 2019

DenoBeno commented Jul 30, 2019

DenoBeno commented Jul 30, 2019

humerh commented Jul 30, 2019 •

edited

humerh commented Jul 30, 2019

p-a-s-c-a-l commented Jul 31, 2019

p-a-s-c-a-l commented Sep 26, 2019 •

edited

DenoBeno commented Oct 14, 2019

p-a-s-c-a-l commented Oct 30, 2019

1st Data Package: 03 Exposure Layers #10

1st Data Package: 03 Exposure Layers #10

Comments

p-a-s-c-a-l commented Dec 6, 2018 • edited by DenoBeno

p-a-s-c-a-l commented Feb 25, 2019

humerh commented Feb 25, 2019 via email

maesbri commented Mar 8, 2019 • edited

ghilbrae commented Mar 11, 2019

ghilbrae commented Mar 11, 2019

maesbri commented Mar 11, 2019

stefanon commented Mar 11, 2019

maesbri commented Mar 19, 2019 • edited

therter commented Mar 20, 2019 • edited

maesbri commented Mar 20, 2019

p-a-s-c-a-l commented Jun 28, 2019 • edited

p-a-s-c-a-l commented Jul 10, 2019

p-a-s-c-a-l commented Jul 15, 2019

DenoBeno commented Jul 30, 2019

humerh commented Jul 30, 2019

humerh commented Jul 30, 2019

DenoBeno commented Jul 30, 2019

DenoBeno commented Jul 30, 2019

DenoBeno commented Jul 30, 2019

humerh commented Jul 30, 2019 • edited

humerh commented Jul 30, 2019

p-a-s-c-a-l commented Jul 31, 2019

p-a-s-c-a-l commented Sep 26, 2019 • edited

DenoBeno commented Oct 14, 2019

p-a-s-c-a-l commented Oct 30, 2019

p-a-s-c-a-l commented Dec 6, 2018 •

edited by DenoBeno

maesbri commented Mar 8, 2019 •

edited

maesbri commented Mar 19, 2019 •

edited

therter commented Mar 20, 2019 •

edited

p-a-s-c-a-l commented Jun 28, 2019 •

edited

humerh commented Jul 30, 2019 •

edited

p-a-s-c-a-l commented Sep 26, 2019 •

edited