1st Data Package: 00 Background Layers - 1) Create Layers

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

This tasks relates to the actual creation (data collection, spatial processing, making available in SDI) of Background Layers of the 1st Data Package. See also #4

Several sources (Excel Sheets, Mock-Ups) for potential background layers are available in the project. Note: For the 1st Data Package only a few of them will be considered.

1) Local Effects Input Layers

Most of the layers that are created as input for hazard with local effects (see clarity-h2020/csis#33) can be used as static background layers. In order to use such a layer in the CSIS, it should be pre-calculated for whole Europe and made available via GeoServer (WFS/WMS) and GeoWebCache (TMS/WMTS), respectively.

The Models Excel Sheet identifies the following 16 layers:

#	Layer name	Sources
1	Water	Urban Atlas
2	Roads	Urban Atlas
3	Railways	Urban Atlas
4	Trees	Urban Atlas + Street Tree layers
5	Vegetation	Urban Atlas + European Settlement Map
6	Agricultural areas	Urban Atlas
7	Buildings	European Settlement Map
8	Built open spaces	European Settlement Map
9	Dense Urban Fabric	Urban Atlas
10	Medium Urban Fabric	Urban Atlas
11	Low Urban Fabric	Urban Atlas
12	Public, military and industrial units	Urban Atlas
13	Basins	EU-Hydro
14	Flow accumulation steams	USGS - HydroSHEDS
15	DEM	EU-DEM
16	Surface Temperature	SL_2_LST_

There are additional background layers related to Hazard with Local Effects listed in this Excel Sheet that served as input for Hazard with Local Effects Mock-Ups.

Hazard	Parameter (folder)	Parameter (single layer)
Heat Wave	Buildings	Building Density
Heat Wave	Buildings	Building Quality
Heat Wave	Open spaces	Surface Features
Heat Wave	Open spaces	Hillshade
Pluvial Flood	Open spaces	Building Fabric
Pluvial Flood	Open spaces	Slope
Pluvial Flood	Open spaces	Surface Quality

Some of them may overlap with the layers in the Models Excel Sheet.

So those are the background layers that should be available (at least) in the HC LE Step:

Important: In this context, those layers are used only for visualisation purposes, e.g. to put some informative maps in the report. Therefore they have too look nice (proper SLDs to be defined) in contrast to their harmonised and rasterised versions (see #5 (comment)) that are never shown to end users.

2) Inventory Layers

There are other background layers that are not an immediate output of hazard with local effects preparation, but they may be related to that, e.g. they may serve as basis for creating the Local Effects Input Layers or as input final (rasterised) Exposure Layers.

The Mock-Ups Excel Sheet identifies the following inventory layers:

Group	Layer	Dataset
Municipality	City boundary	Urban Atlas/EuroGlobalMap
Population	Population by municipality	Eurostat
Population	Population density	Eurostat + Urban Atlas
Buildings	Residential	European Settlement Map + Urban Atlas
Buildings	Non Residential	European Settlement Map + Urban Atlas
Open spaces	Paved surfaces	European Settlement Map
Open spaces	Green surfaces	European Settlement Map
Infrastructure	Fast roads	Urban Atlas/EuroGlobalMap
Infrastructure	Roads	Urban Atlas/EuroGlobalMap
Infrastructure	Railways	Urban Atlas/EuroGlobalMap

Since some of those inventory layers are used to derive the 16 Local Effects Input Layers and potentially the rasterised Exposure Layers, it shouldn't be a problem to make them available in our GeoServer instance, too.

3) Base Layers

There are other base layers that are readily available as TMS or WMS, e.g. OpenStreetMap or OpenTopoMap and thus that can be used in the Map Component without the need to import them into one of our own Data Repositories. They are configured at the level of the Map Component itself and thus do not need to be included as Resource in a particular Data Package.

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

Status:

• The bash scripts involved to process the input data to create the 16 Input Layers for Hazard-LE are not final yet, there is static data involved. The idea is to have one script per output layer. But there is need of a master script to manage database table names and to share information between them. The scripts will be made made available in a dedicated repository.
• The output of the scripts is currently stored à in a postgis instance that runs in a VM of ATOS server.
• the layers are currently manually published in geoserver using postgis database as data source
  • http://5.79.69.33:8080/geoserver/clarity/wms?service=WMS
  • http://5.79.69.33:8080/geoserver/clarity/ows?service=WFS

Note: Further Hazard-LE-calculation related tasks are not considered in this particular issue as these layers are here only relevant for serving as static background layers.

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

@negroscuro @maesbri @Itsman-AT Such background layers are only useful if they show the actual geometries (roads, buildings, etc.) and not only grid cells. If the Local Effects Input Layers are generated and stored as vector grids, we probably need keep some intermediate result (e.g. temporary layers extracted from the input data sources?) of the processing chain and make it available via our own GeoServer instance.

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

Some of the background layers (only for Naples reference area) are available here, they can be used for an initial demo Data Package but should later be moved to the CSIS GeoServer Instance for reasons explained here.

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

Background Layers are available in HC-LE.