[Home]
The Dewetra platform manages and allows to visualise various type of geospatial data. From the technical point of view, these data can be divided in 2 main categories:
This section describes how to:
Static datasets refer to geospatial data providing basic information and information about hazard, risk, exposure or past events (tipically not varying continuously in time). These datasets can be organised in geo-referenced format and integrated into the Dewetra platform for visualisation in the geo-viewer and to cross-reference and overlap this information with dynamic datasets to build real-time risk scenarios.
These geo-referenced data, duly stored in a data exchange folder of the reference data server of the Dewetra platform, have to be processed with 3 operations in order to be displayed on the Dewetra Platform:
The Geoserver service is an open source server for sharing georeferenced data. The home page of the Geoserver is presented as in the image below and available at the following link:
https://stlucia.mydewetra.cimafoundation.org/dds/web
The Geoserver service is organised in workspaces, in which several data stores can be created for storing georeferenced data. From a single data store, one or more layers can be created (or, according to the name of the service, "published"), which correspond to possible versions or graphical representations of the data in the store. Each layer can be associated with a style, which can be customised, to define the graphical representation that will be given to the geo-referenced data when it is published in a geo-viewer (more details in the next point).
To upload data to the GeoServer service, you first have to create a data store where you will host the georeferenced data to be displayed on the Dewetra Platform.
To create a store and host the data, the following steps must be followed:
Once the data store has been successfully created, you can proceed to the creation of a layer:
The GeoServer service has a page dedicated to "Styles" which contains all the graphic visualisation styles of the data used in the service.
The user can create a new style according to the graphical representation he wants to give to the data with the following steps:
Having created or available a style to assign to the layer, the final steps towards publication on geoserver can be undertaken:
Dynamic datasets are time-varying data providing information changing with different update rate and time steps. The publication of dynamic datasets on the Dewetra platform is possible thanks to the functionalities of the Dewetra Data Server (DDS). Being Dewetra a distributed architecture, publication of dynamic products is possible in two modalities:
This operation can be performed using Django, through the following steps:
This connection with an external server is valid also for publishing static data, available on the existing external DDS or WMS.
Here example of the information for creating a server connecting to GloFAS WMS service:
Name: GLOFAS_WMS
Descr: GLOFAS_WMS
Url: http://globalfloods-ows.ecmwf.int/glofas-ows/ows.py
User: user
Password: pwd
To enable publication of dynamic products stored in the local server, a specific system configuration is required, which consists of three steps:
The first step is simply carried out through the configuration of an .xml file, where the name and variable of the index, its location on the server and the style of the Geoserver to be used are specified (see code and example below)
<dynamicLayer descr="[NAME]" id="[NAME]">
<attribute descr="dir" hidden="true" id="dir" type="Text">
<attributeEntry descr="dir" id="[DIR]">
</attributeEntry>
</attribute>
<attribute descr="Variable" id="variable" type="List">
<attributeEntry default="1" descr="[NAME]" id="[NAME]">
<referredValue id="style" value="[LEGEND]"/>
</attributeEntry>
</attribute>
</dynamicLayer>
As a second step, it is necessary to specify which component should be used by the system to interpret the data. By means of specific software components, the Dewetra platform allows the reading of most of the commonly used static and dynamic geographic data formats (.tif, geojson, .shp, .grb, .netCDF, etc.). The component to be used, chosen among the available components, has to be specified in the text file "components.properties". For example, in case of a dataset as the global SPI (a drought monitoring index) composed by .tif files updated every month, the component to be used is called "com.acrotec.data.dds.components.DDSMapMonthlyGeotiffComponent".
Therefore, in the “components.properties” text file the following line should be added:
GLOBAL_SPI = com.acrotec.data.dds.components.DDSMapMonthlyGeotiffComponent
As a final step, the product should be published in Dewetra. This can be done through Django (see next section), having created a server for the local DDS.
To publish layer on Dewetra, the service manager Django should be used for configuration, so that the information layer appears among the layers made available in the platform. This functionality is implemented through the Dewetra 2.0 Service Manager page called "Django", a back office application developed through the "Django" web framework.
In the Django application for publishing layers on Dewetra platform (image below) it is possible to define, in addition to information such as the name of the layer, the location, the type of layer, the name of the server, the tags (referred to the ones used to group layers on Dewetra platform), group of users that can view that layer, paths and category of the layer.
To publish a static or dynamic products using Django, the following steps should be carried out:
[Home]