Exposure - Switch to EMIKAT API

[p-a-s-c-a-l]

Exposure Data (Population) for whole Europe will be served from a new EMIKAT API.
This means, that the table API for aggregating Exposure Data has to be updated accordingly.
Additionally, the respective Exposure Resources in the Data Package have to be updated as well as the Table Component.

@humerh Could you please provide an example request and response? To keep the changes to the table-state-rest-api minimal, it would be helpful if EMIKAT API could offer the the same API as currently used by the table-state-rest-api to access the underlying exposure data. @ghilbrae Is it WCS, WFS, ...?

It may be necessary to parametrise the URL as described here. Likewise the parameters have to be supported by the table-state-rest-api. This is somehow related to #3.

[ghilbrae]

As we used geoserver to publish the data/layers, we took advantage of its capabilities regarding OGC standards. In short, we are using WCS to access the layers and get the information needed for the tables.

[ghilbrae]

I know this is not high priority rn but if we need to switch the table API to EMIKAT I'll need info on the EMIKAT API, WCS, WMS, etc. endpoints and also a user/pass or token or whatever it is that it's needed to connect to the service. Thanks!

https://github.com/clarity-h2020/csis/wiki/Services-endpoints-(used-by-CSIS)

[p-a-s-c-a-l]

I know this is not high priority rn but if we need to switch the table API to EMIKAT I'll need info on the EMIKAT API, WCS, WMS, etc. endpoints and also a user/pass or token or whatever it is that it's needed to connect to the service. Thanks!

Questions / Discussions regarding the EMIKAT Exposure API should continue here.

[p-a-s-c-a-l]

There is no WCS Endpoint, so you would need to the use CSV endpoint.

CSV Format Population Exposure for Europe:

GRID_ID;Population 
500mE46730N19800;395.0 
500mE46730N19805;394.0 
500mE46735N19800;394.0 
500mE46735N19805;394.0 

However, for local data it look different:

OBJECT_ID;GRID_ID;POPULATION_LT15;POPULATION_15TO65;POPULATION_GT65
49704;500mE46735N19805;73.88189697265625;320.4410095214844;58.539100646972656
49678;500mE46735N19810;54.60070037841797;178.06399536132812;27.587299346923828
49691;500mE46735N19815;21.633699417114258;81.45919799804688;10.961799621582031
49730;500mE46735N19820;435.5150146484375;1500.4000244140625;254.0070037841797
49731;500mE46735N19825;820.666015625;3915.60009765625;640.0349731445312
49710;500mE46735N19830;726.43798828125;3172.10009765625;596.3989868164062

And of course for different Element at Risk Types.

[therter]

An example response for the table-state-rest-api can be found here. The request for table-state-rest-api can be found here

[p-a-s-c-a-l]

We'll provide Simplified Table Components until the above questions have been resolved. So putting this on hold. ATM no further modifications to the table API are needed.

[humerh]

In my opinion this is already done!!

[p-a-s-c-a-l]

@humerh Depends on where the original population Exposure is stored in EMIKAT or in Meteogrid WCS?

[p-a-s-c-a-l]

We don't need to switch to EMIKAT API since the exposure data is available on METEOROID Geoserver too.