Function: |
Configure predefined timesteps for a fews environment |
Where to Use? |
To define verbose timesteps or to define yearly or monthly time steps |
Why to Use? |
Yearly and monthly time steps can only be configured in the timesteps.xml. For verbose timesteps it might be |
Description: |
Definition of timesteps which can be referenced from other configuration files |
Available since: |
|
Contents
Overview
The timesteps.xml can be used to configure timesteps. This file is usefull to define verbose timesteps and refer to the definition of these timesteps to
from other configuration files.
Configuration
When available on the file system, the name of the XML file is for example:
TimeSteps 1.00 default.xml
TimeSteps Fixed file name for the TimeSteps configuration
1.00 Version number
default Flag to indicate the version is the default configuration (otherwise omitted).
Schema
Below the schema of the TimeStep.xml configuration files.
timeStep
Attributes;
- id: Unique Id of level threshold. This id should be used when referencing to this definitation from other configuration files.
The following link describes in detail of to configure a timestep.
yearlyTimeStep
A timeStep that defines a pattern of dates in a year. This pattern will be repeated every year.
Each date in the year can have a different aggregation period (season).
The start of the aggregation period is exclusive and the end of the aggregation period is inclusive.
This yearlyTimeStep is meant for seasons, therefore limited to four dates.
If more than four dates in a year are required, then please use the monthDays option in the timeStep element instead of this yearlyTimeStep
Schema yearly time step
Below the schema of the yearly time step 
