| Wiki Markup |
|---|
{scrollbar} |
| Table of Contents |
|---|
Introduction
One of the most important properties of DELFT FEWS as a forecasting system is its ability to efficiently deal with large volumes of dynamic data. Dynamic data covers mainly time series data in various formats (scalar- 0D, vector - 1D, grid - 2D, and polygon data - 2D). Dynamic data also includes the management of model states produced by the system.
...
Optional items may also need to be required to fulfil the requirements of the module using the time series set. This will be indicated in this manual for those modules where appropriate.
Figure3 Schema of the Time Series Set Complex type
...
- divider same function as the multiplier, but defines fraction of units in time step.
timeZone defines the timeZone of the timeStep, this is only relevant for units of a day or larger.
Note For hourly timesteps this may also be relevant in the case of half-hourly timezones. Untested at the moment.
...
A time series set may be defined to retrieve all members of an ensemble at once (for example in evaluation of ensemble statistics). This is done by defining the optional ensembleId. The ensembleId should also be defined when writing new ensemble members. (e.g. on importing ensembles in the import module).
Example:
| No Format |
|---|
<timeSeriesSet>
<description>Example time series set</description>
<moduleInstanceId>ImportTelemetry</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.obs</parameterId>
<locationId>4539.TF</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="minute" multiplier="15"/>
<relativeViewPeriod unit="hour" start="-48" end="24" endOverrulable="true"/>
<readWriteMode>read only</readWriteMode>
<synchLevel>1</synchLevel>
<expiryTime unit="day" multiplier="100"/>
</timeSeriesSet>
|
| Info |
|---|
When dealing with ensembles, the ensembleId needs only be defined if the workflow activity that is used must retrieve the complete ensemble, or if members are to be written under a new ensembleId. In other cases the ensembleId needs only be defined in the workflow definition (see Workflows chapter). For the TimeSeriesSets defined in modules there is then no difference between running in ensemble mode and running normally. |
visibilityControllingFlagSourceColumnId
All values that not passed this validation step are removed on read. Set to missing for equidistant and removed for non-equidistant. The flagSourceColumnId needs to be defined in flagSourceColumn.xml configuration file.
Manual data edits
Timeseries can be edited by the user. This can be done from the explorer (filters.xml) or from the predefined displays (displaygroups.xml). It is required that the ReadWriteMode of the TimeSeriesSet is not set to "read only".There are some characteristics concerning handling of manually edited timeseries.
...