...
- exportStateActivity to export module states
- exportTimeSeriesActivity to export time series for scalar or polygon time series
- exportDataSetActivity to export module datasets
- exportMapStacksActivity to export time series for grid time series
- exportProfilesActivity to export time series for longitudinal profile time series
- exportCustomFormatTimeSeriesActivity to export time series in a custom format using a third party serializer
- exportRatingCurveActivity to export rating curves
- exportParameterActivity to export module parameters
- exportTableActivity to export table (e.g. rating table)
- exportNetcdfActivity to export scalar or grid time series in Netcdf format
- exportRunFileActivity to export a run file (The run file contains general information that is used by the pre and post adapter)
- exportCustomFormatRunFileActivity to export a custom format run info file that can be used by the model
- exportAreaSelectionActivity exports bitmasks for the model adapter with a polygon embedded in the TaskProperties as input (is currently only used within NGMS)
- exportLocationAreaActivity exports bitmasks for the model adapter with location ids from the TaskProperties as input (is currently only used within NGMS)
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?>
<Run xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews/PI" xsi:schemaLocation="http://www.wldelft.nl/fews/PI http://fews.wldelft.nl/schemas/version1.0/pi-schemas/pi_run.xsd" version="1.5">
<logLevel>info</logLevel>
<timeZone>0.0</timeZone>
<startDateTime date="1900-01-01" time="00:00:00"/>
<endDateTime date="2100-01-01" time="00:00:00"/>
<time0 date="2000-01-01" time="00:00:00"/>
<workDir>workdir</workDir>
<outputDiagnosticFile>diagnostic</outputDiagnosticFile>
</Run>
|
exportCustomFormatRunFileActivity
Activity to create a custom run info file. This activity replaces tags in a template file with actual (modified) values. The template file can contain location attribute tags between '@' signs, general adapter tags between '%' signs and global properties between '$' signs. The specified template file will be copied to the specified export file before the tags are replaced. So the template file itself is not changed. If the export file already exists, then it will be overwritten.
Elements of the ExportCustomFormatRunFileActivity configuration
description
Optional description for the activity.
templateFile
The pathname of the template file relative to the rootDir (or absolute path). This file can contain location attribute tags between '@' signs, general adapter tags between '%' signs and global properties between '$' signs.
exportFile
The pathname of the export file relative to the exportDir (or absolute path). This file is created during the workflow run and will be a copy of the template file in which the tags are replaced with actual (modified) values. If this file already exists, then it will be overwritten.
locationId
Optional. Location attribute tags in the template file will be replaced with the corresponding (modified) attribute values of the location with this locationId. If this is not specified, then location attribute tags will not be replaced.
configuration example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
exportAreaSelectionActivity (currently NGMS only)
Exports an area selection mask as a PiMapStack. This activity requires an embedded polygon to be specified within the areaSelectionShapeFileBase64 field of the TaskProperties. This file is then available to be used by the pre and post adapter.
description
Optional description for the activity. Used for reference purposes only.
exportFile
File name of the file to be exported. Always placed into the export dir.
...
Exports an area selection mask in the form of a PiMapStack. This activity requires selectedLocationIds to be specified within the TaskProperties. This selection is then available to be used by the pre and post adapter.
description
Optional description for the activity. Used for reference purposes only.
exportFile
File name of the file to be exported. Always placed into the export dir.
...
Root element for the definition of an execute activity. For each external executable or Java class to run, an executeActivity must be defined. Multiple entries may exist.
description
Optional description for the activity. Used for reference purposes only.
...
It is available in the same way for importTimeSeriesActivity, importMapStacksActivity, importPiNetcdfActivity and importProfilesActivity.
description
Optional description of import activity. Used for reference purposes only
...