Updating or adding a data layer in an MSP Challenge Simulation Platform Edition is a two-fold process. On the one hand, the dataset needs to be prepared to integrate the platform; on the other hand, the server needs to know that the new dataset needs to be added to that specific Edition of the MSP Challenge. The so-called “configuration file” has the role of defining which layers, visualisation options, and models are used in each Edition of the MSP Challenge. To update or add a new data layer in an MSP Challenge edition, we upload the data layer and the configuration file containing that data layer’s definitions in a web-tool specially designed for the effect – GeoImport [1].
How to deal with the configuration file is covered in Customise your session. In this section we will cover how to prepare your geo-data to integrate it in the MSP Challenge Simulation Platform.
Formats accepted
The MSP Challenge accepts both vector and raster formats. For vector data, the platform uses shapefiles[2], and for raster data GeoTIFF[3] (Geographic Tagged Image File Format).
To use shapefiles in the platform only the files with extension .shp, .dbf, and .shx are needed. The .TIFF file is enough in case of raster files.
Data preparation
Some of the data preparation aspects apply to both vector and raster data and are explained here. Others are specific for vector or raster data and are described in the respective sub-sections.
- Geographical area coverage
Ensure that the data layer to be added covers only the geographical area designed as the “Play area”. Each Edition of the platform has a layer called _PLAYAREA_XX, where XX are the first letters of the region corresponding to that Edition. For example, the Adriatic Edition’s play area is “_PLAYAREA_AS”.
- Coordinate Reference System and Projection
Always save your files using the coordinate reference system and projection used in the platform: ETRS89 and Lambert Azimuthal Equal Area (EPSG:3035)
Vector
- Geometry
The shapefile itself can’t have invalid geometries; the platform cannot deal with invalid geometries. The use of multi-polygons, multi-lines or multi-points is not supported. Remove duplicated geometries. If possible, avoid subtractive polygons as this can originate problems in the platform. Simplify geometries for use in the platform; aim for files (.shp) to have less than 100 MB.
- Categories
If the dataset has categories, for instance, in a data layer about pipelines, we can have different categories, such as “active” or “inactive”. These are mapped in the platform by using “types”. A field named “type” (all low caps) needs to be introduced in the attributes table; this field needs to store integer values from 0 to n; each value will correspond to a type. It is good practice to also add a “type_1” field with the category description. The type’s name(s) and visualisation options are defined in the Edition’s configuration file (see Customise your session). Check if the types in the configuration file correspond to the types used in the new dataset and update if needed.
- Naming convention
Use the following name convention for vector layers: “RR_Layer_Name”, in which RR are the first letters of the region, for instance, AS for the Adriatic Sea.
Raster
- Geographical area coverage
Ensure that the data layer to be added covers only the geographical area designed as the “Play area”. Each Edition of the platform has a layer called _PLAYAREA_XX, where XX are the first letters of the region corresponding to that Edition. For example, the Adriatic Edition’s play area is “_PLAYAREA_AS”.
- Raster values
In the MSP Challenge, the rasters’ cells values range from 0 (minimum or no data) to 255 (maximum). To make sure a raster file is displayed correctly in the platform, you need to know the minimum and maximum values in the raster file and optimise its visual settings before saving it as a tiff (rendered image). In the saved image, verify if the “no data” or zero values correspond to black and the maximum values to white. In the configuration file, the layers’ types need to be defined to correspond to the interval values that we want to show in the platform (see configuration file).
- Naming convention
Use the following name convention for raster layers: “RR_Layer_Name_raster”, in which RR are the first letters of the region, for instance, AS for the Adriatic Sea.
Upload the data in MSP Challenge's GeoServer
To upload a layer in MSP Challenge's GeoServer use the geoimport tool created by BUas, accessible from https://auth.mspchallenge.info/geoimport. Do not forget to update the configuration file before this step. See how to download the default configuration file and update it at Customise your session (Sections 1, 1.1 and 1.3.4 are the most relevant in this case).
You do need to log-in with your MSP username and password. If you don't have an account yet, you can create one by clicking on "register" on the top menu.
Browse or drag all your the relevant files (shapefile with extensions .shp, .shx and .dbf or TIFF with the configuration file) in the "actions" box.
The web-tool guides you trough the process and makes a series of verifications to make sure the dataset complies with the requirements.
After GeoImport has loaded the layers in the GeoServer, one more step is needed before users can access the changes in the updated Edition of the Platform. The configuration file needs to be added in the server manager and a new server needs to be set-up. Section 1.5 of Customise your session guides you through that process.
[1] https://auth.mspchallenge.info/geoimport
[2] https://doc.arcgis.com/en/arcgis-online/reference/shapefiles.htm
[3] https://www.ogc.org/standards/geotiff
[4] https://epsg.io/3035
Co-funded by the European Union.