BRISEIDE Project, Geoserver, GeoNetwork and GeoBatch for the management of dynamic MetOc data
In this post I wanted to talk about the work we are doing for the BRISEIDE european project.
The ambitious aim of the project, as stated on its website, is the delivery of:
- time-aware extension of MetOc data models developed in the context of previous/ongoing EU INSPIRE related projects (e.g. in the context of GMES, eContentPlus)
- application (e.g. Civil Protection) based on the integration of existing, user operational information
- value added services for spatio-temporal data management, authoring, processing, analysis and interactive visualisation
Within the context of the project, GeoSolutions will work under the leadership of SinerGIS in order to provide near-real time ingestion, cataloging and publishing of meteorological data provided by the stakeholders to be used as inputs for running processes to perform, as an instance, fire propagation models in emergency situations.
The infrastructure we are setting up is depicted in the deployment diagram here below. Basic building blocks are as follow:
- GeoServer for providing WMS, WCS and WFS services with support for the TIME dimension. It is worth to point out that it will also provide WPS capabilities.
- GeoNetwork, for publishing metadata for all data with specific customizations for managing the TIME dimensions in the dataset (we are going to biriefly describe them later on)
- GeoBatch, for performing preprocessing and ingestion in near real time of data and related metadata with minimal human intervention.
Incoming files are composed by a compressed set of .asc (ascii images) files which are:
- Converted into re-tiled GeoTiff images
- Embedded overviews are added to each image
The groovy script produces an ImageMosaicCommand which is essentially an xml command which is sent to the ImageMosaicAction which:
- Check for the layer existence on the target GeoServer
- If success copy all the files to the target directory
- Create the Store and the layer to contain the ImageMosaic
- Configure the layer on the GeoServer using desired parameters
- Produce an XML file with the ImageMosaic properties
The groovy script read the produced ImageMosaic output, enrich it with some other useful information then pass that object to the FreeMarkerAction which using a template and the passed data model will produce the xml metadata file (as described above).
The GroovyScriptAction ends sending this file to the next action which is the GeoNetworkAction which will send the metadata to the target GeoNetwork server using the desired (specified by configuration) options.
the GeoSolutions Team.