...
In a script configuration, the start and end time, and events for the script are specified. A script is a directory in the scenario/script database in which files relevant for that script are collected, including the script configuration file. For more information, see scenario/script database.
| Section |
|---|
| Column |
|---|
| Schema definition overviewThe global structure of the XML-schema for the script configuration is |
|
...
shown on the right. The title key is an optional identifier for the script.The time zone for the Water Coach is specified within the section timeZone. All times in the script configuration must be specified relative to this time zone. The time zone can be specified as a name using the keyword name (e.g. GMT, MET, ...) or as an offset to the default time zone GMT using the keyword offset (e.g. +02:00, -06:00, ...).The start and end date/time for the script have to be specified using attributes date and time in the format YYYY-MM-DD and hh:mm:ss, respectively. The date/time of the data in the FEWS local data store does not have to match the date/time of the script. The actual date/time (or current system time) of the local data store can be specified with the key dataStart (if this key is not specified, dataStart is assumed to be equal to scriptStart). With this functionality, it is possible to play a scenario of several years ago as if it happened today.The configuration of stories (events), the forecastTable, forecastNote, and dictionaryFiles for a script are explained below. |
| Column |
|---|
 Image Added
|
|
Stories
...