| Wiki Markup |
|---|
{scrollbar} |
| Excerpt | ||
|---|---|---|
| ||
Functionality to define qualifiers to time series, next to locationIds and parameterIds |
Function: | Configure topology of an IFD environment |
Where to Use? | Mandatory for a IFD installation |
Why to Use? | The topology.xml is necessary to be able to use panels like the topology panel and the forecast panel |
Description: | Topology panel is used to define the topology of an IFD environment. Also the behaviour of the forecast panel which is used to start |
Available since: | DelftFEWS201001 |
Contents
| Table of Contents |
|---|
Overview
The topology.xml is an mandatory configuration file when you are setting up an IFD-environment. This configuration file is used to configure the topology of a region.
...
The topology of a region is configured by defining the indvidual nodes off a region and grouping them. Below an example from the topology of the abrfc region
| Code Block | ||||
|---|---|---|---|---|
| ||||
<topology xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="chps1/schemas/topology.xsd">
<nodes id="ABRFC">
<workflowId>ABRFC_Forecast</workflowId>
<nodes id="NMWTX" name="NMWTX">
<workflowId>NMWTX_Forecast</workflowId>
</node>
<node id="EGLN5" name="EAGLE NEST DAM">
<workflowId>EGLN5_Forecast</workflowId>
</node>
<node id="CMMN5" name="CIMARRON 4SW">
<previousNodeId>EGLN5</previousNodeId>
<workflowId>CMMN5_Forecast</workflowId>
|
...
If this option is enabled and a node is run, all previous nodes in the topology tree are run before running the selected node, even if the nodes are not connected by the defined topology. Default this option is not enabled, then only the upstream nodes will be run.
enableSelectNodesFromMap
If This option is set to false by default. If this option is enabled it will not be possible to select nodes by clicking on the location in the map, if that node has a locationId and a filterId configured in the Topology file.
enableAutoSaveOnRun
Default is false. When this option is set to true all edits will be automatically saved to the database without having to press apply or confirm when a node is run.
...