Page History

...

Introduction

...

Locations in the map by default are labeled with the ID, or the name or description of the location (configured in locations.xml or locationSets.xml). To specify the ID, name or description of the location, the following tags could be used: %ID%, %NAME%, and %DESCRIPTION%. In LocationSets.xml (for EsriShapeFile or CSVFile) it is also possible to replace or add text to the label, such as location attributes (using @ATTRIBUTE_ID@, Since 2013.02 or csv/dbf columns without defining an attribute with %COLUMN_NAME%), or timeseries related information (%LAST_VALUE%, %LAST_VALUE_TIME%,%FORECAST_START_TIME%, %MAXIMUM_VALUE%, %MAXIMUM_VALUE_TIME%, %MINIMUM_VALUE%, %MINIMUM_VALUE_TIME%). In case of timeseries related information, the label only shows the information for the selected parameter.

Example:

...

Code Block
xml xml
<label>%NAME% has last value: %LAST_VALUE%</label>

 

Other uses:

In the Filters.xml there is an additional option to show the last value (within the RelativeViewPeriod): lastValueVisible.

In Explorer.xml, in the map section, it is possible to configure that no labels are displayed. Likewise, the Options>>>Explorer Options "map" tab can turn labels on and off.

Zoom extents

showThresholdWarningIcons

This setting determines the default value for whether the button for showing threshold icons is selected or not.

When FEWS closes, the current state of the button will be written to the user settings.

The next time FEWS starts, the state of the button will be taken from the user settings and will overrule what is configured in the config.

Zoom extents

The zoom extents is used to define the pre-configured zoom levels that can be selected from the main The zoom extents is used to define the pre-configured zoom levels that can be selected from the main display.

Figure 8 Elements in the Explorer Options section of the Explorer configuration

...

Figure 9 Elements in the Explorer Tasks section of the Explorer configuration

explorerTask

Main element of each explorer Task. Note that multiple tasks may exist, with the elements below to be defined for each.

Attributes;

• name name of the task

iconFile

Reference to an icon file to be used in the toolbar. If left empty the name will be used to identify the task in the toolbar.

Since 2019.02, the type of the button can be added to the toolbar (Icon or Text). Only the ButtonType (in <toolbarTask>) Icon will use the configured <iconFile>. If left blank, it will show the new, default grey-scale icon provided from the code.

The complete set of new, default, grey-scale icons can be downloaded here . See also the table below in the <predefinedDisplay> section.

Mnemonic

Optional definition of a letter in the title to use as shortcut.

predefinedDisplay

Enumeration of possible displays (alternativaly, you can define a taskClass, see below and How to define an ExplorerTask - what are the possible taskClass options?):

...

default icon
(since 2019.02)

...

...

...

...

...

documents

...

...

...

...

...

...

...

...

...

plot overview

...

...

...

...

...

...

...

...

time series dialog

...

...

...

...

...

...

...

...

displayConfigFileName

Since 2013.02. Config file of the display. The display to start is recognized by the schema name in the config file

taskExe

Command line for executable to run on initiating the task (the task may be either a call to an executable or to a Java class)

taskClass

Java class to run on initiating the task (the task may be either a call to an executable or to a Java class)
The possible taskClasses are listed in the next howto
Notice that you better use the predefinedDisplay or displayConfigFileName elements.

arguments

Optional argument string to be passed to the task.
In case of a embedded vJDBC service, you can parse the actual portnumber to an application with the argument %VJDBC_PORT% or %PORT%.
Since 2012.01, the TimeSeriesDisplay can be started with preselection of a statistical function (see example below)

workDir

Optional working directory to start the task in.

Description

Optional description of the task (for reference only)

toolbarTask

Boolean flag to indicate if the task is to appear as a part of the toolbar.

Since 2019.02 this element can either has new settings and dependencies. A buttonType can be configured. Options in this enumeration are 'icon' or 'text'

...

The various explorerTasks can be organized into sub-menus through the subMenu element

<explorerTask name="Graph">
	<mnemonic>G</mnemonic>
	<predefinedDisplay>time series dialog</predefinedDisplay>
	<toolbarTask>true</toolbarTask>
	<menubarTask>true</menubarTask>
	<allowMultipleInstances>true</allowMultipleInstances>
	<accelerator>ctrl G</accelerator>
	<loadAtStartup>true</loadAtStartup>
</explorerTask>
<subMenu name="Tools">
	<subMenu name="Data">
		<explorerTask name="Interval statistieken">
			<predefinedDisplay>interval statistics</predefinedDisplay>
			<menubarTask>true</menubarTask>
			<allowMultipleInstances>true</allowMultipleInstances>
		</explorerTask>	
	</subMenu>
	<subMenu name="Debugging">
		<explorerTask name="Attributes">
			<predefinedDisplay>attribute filter</predefinedDisplay>
			<menubarTask>true</menubarTask>
		</explorerTask>
		<explorerTask name="Database Lister">
			<predefinedDisplay>time series lister</predefinedDisplay>
			<menubarTask>true</menubarTask>
		</explorerTask>
		<explorerTask name="Workflow Navigator">
			<predefinedDisplay>workflow navigator</predefinedDisplay>
			<menubarTask>true</menubarTask>
		</explorerTask>
		<explorerTask name="Tabular config files">
			<predefinedDisplay>tabular config files display</predefinedDisplay>
			<menubarTask>true</menubarTask>
		</explorerTask>	</subMenu>
	</subMenu>	
</subMenu>

explorerTask

Main element of each explorer Task. Note that multiple tasks may exist, with the elements below to be defined for each.

Attributes;

• name name of the task

iconFile

Reference to an icon file to be used in the toolbar. If left empty the name will be used to identify the task in the toolbar.

Since 2019.02, the type of the button can be added to the toolbar (Icon or Text). Only the ButtonType (in <toolbarTask>) Icon will use the configured <iconFile>. If left blank, it will show the new, default grey-scale icon provided from the code.

Since 2022.02 all PNG/GIF icons are replaced by SVG icons. PNG/GIF icons are still supported for compatibility reasons but they will become blurry when scaled.

The complete set of new, default, grey-scale icons can be downloaded here. See also the table below in the <predefinedDisplay> section.

Mnemonic

Optional definition of a letter in the title to use as shortcut.

predefinedDisplay

Enumeration of possible displays (alternativaly, you can define a taskClass, see below and How to define an ExplorerTask - what are the possible taskClass options?):

displayConfigFileName

Since 2013.02. Config file of the display. The display to start is recognized by the schema name in the config file

taskExe

Command line for executable to run on initiating the task (the task may be either a call to an executable or to a Java class)

taskClass

Java class to run on initiating the task (the task may be either a call to an executable or to a Java class)
The possible taskClasses are listed in the next howto
Notice that you better use the predefinedDisplay or displayConfigFileName elements.

arguments

Optional argument string to be passed to the task.
In case of a embedded vJDBC service, you can parse the actual portnumber to an application with the argument %VJDBC_PORT% or %PORT%.
Since 2012.01, the TimeSeriesDisplay can be started with preselection of a statistical function (see example below)

workDir

Optional working directory to start the task in.

Description

Optional description of the task (for reference only)

toolbarTask

Boolean flag to indicate if the task is to appear as a part of the toolbar.

Since 2019.02 this element can either has new settings and dependencies. A buttonType can be configured. Options in this enumeration are 'icon' or 'text'

menubarTask

Boolean flag to indicate if the task is to appear in the tools menu

allowMultipleInstances

Boolean flag to indicate if multiple instances of task can be initiated concurrently

accelerator

Optional shortcut key, note that the shortcut keys only work for tasks in the menu bar (when <menuBarTask> is set to true). Examples of shortcuts: "shift X", "control DELETE", "alt shift X" etc.

A list of accelerator keys and their availability for use can be found here.

Permission

Optional name of the permission that is needed to use this task

doubleClickLocationEnabled

When double clicked at  a location at the map or in the list, all the explorerTasks with this option set to true are started. The location is selected before the tasks are started, so you can for example start the time series dialog (TSD) and jump to the shortcut chart of the clicked location.

Specific for TSD with the argument "Shortcuts" :

TSD with the argument "Shortcuts"  will open to the shortcut chart that is configured in DisplayGroups.xml. By default the first chart that contains the clicked location will open. To open a specific shortcut chart, an ‘explorerLocationId’  and/or   ‘explorerfilterId’ can be configured in this shortcut chart and the chart will open if the same location   is double clicked at the map or in the list. If  explorerFilterId  is configured, also the selected filter should match .

If the “Shortcuts” explorerTask has allowMultipleInstances = true,  then every separate double click will open a new “Shortcuts” display.

If allowMultipleInstances = false, then the first double click on location opens the “Shortcuts” and shows the display associated with the location.
Unlock this “Shortcuts” display with lock icon in the toolbar and next double clicks on a location will direct  to an associated display in the already opened “Shortcuts”.

An example:
If  LocA is double clicked ,  TSD will open to "Display 2",    since this display has <explorerLocationId>LocA</explorerLocationId> .

If  LocB is double clicked and the filter ModelA is selected,  TSD will open to "Display 3",    since this display has  <explorerFilterId>ModelA</explorerFilterId> and <explorerLocationId>LocB</explorerLocationId> .

<displayGroup name="Example">

...

Boolean flag to indicate if the task is to appear in the tools menu

allowMultipleInstances

Boolean flag to indicate if multiple instances of task can be initiated concurrently

accelerator

Optional shortcut key, note that the shortcut keys only work for tasks in the menu bar (when <menuBarTask> is set to true). Examples of shortcuts: "shift X", "control DELETE", "alt shift X" etc. 

Permission

Optional name of the permission that is needed to use this task

doubleClickLocationEnabled

When double clicked at  a location at the map or in the list, all the explorerTasks with this option set to true are started. The location is selected before the tasks are started, so you can for example start the time series dialog (TSD) and jump to the shortcut chart of the clicked location.

Note 1:
This functionality has been designed before the introduction of docking displays and assumes that each double click opens a new TSD. To be able to open a new TSD (with argument shortcuts), this task should have the option allowMultipleInstances=true. An already opened shortcuts TSD is not able to switch to an another shortcut chart.

Note 2:
a TSD with the argument shortcuts will open to the shortcut chart that is configured in DisplayGroups.xml. By default the first chart that contains the clicked location will open. To open a specific shortcut chart, an ‘explorerLocationId’ can be configured in this shortcut chart and the chart will open if the same location is double clicked at the map or in the list.

An example:
if LocB or LocC is double clicked , TSD will open to "Plot LocB" resp. "Plot LocC". If LocA is double clicked , TSD will open to "Plot LocC" , since this shortcut has <explorerLocationId>LocA</explorerLocationId>

<displayGroup name="Example">
            <display name="Plot LocA">
                        <locationId>LocA</locationId>
                        <plotId>Discharge</plotId>
            </display>                   
            <display name="Plot LocB">
                        <locationId>LocB</locationId>
                        <plotId>Discharge</plotId>
            </display>             <display name="Display 1">
    
            <display name="Plot LocC">
      <locationId>LocA</locationId>
                        <plotId>Discharge</plotId>
            <explorerLocationId>LocA</explorerLocationId> 
</display>                   
 	        <display  <locationId>LocC</locationId>name="Display 2">
                        <plotId>Discharge<<explorerLocationId>LocA</plotId>explorerLocationId> 
            </display>            
<<locationId>LocB</displayGroup>

loadAtStartup

In this field can be configured which windows will be opened by default when the system starts up. This feature can only be used in docking mode.

Examples

In the below example for an explorerTask references are made to:

...

locationId>
                        <plotId>Discharge</plotId>
            </display>   
 	        <display name="Display 3">
                        <explorerFilterId>ModelA</explorerFilterId> 
	                    <explorerLocationId>LocB</explorerLocationId>			
	                    <locationId>LocC</locationId>
                        <plotId>Discharge</plotId>  
            </display>
</displayGroup>

loadAtStartup

In this field can be configured which windows will be opened by default when the system starts up. This feature can only be used in docking mode.

Examples

In the below example for an explorerTask references are made to:

• %WEB_SERVICE_PORT%, port where the embedded web service is running. This port is also written to the third line in running file in the region home
• %HOSTNAME%, the actual JDBC host, returned as IP adress
• %REGION_HOME%, internal variable of FEWS: returns the current FEWS application directory
• %FEWSDIR%, internal variable of FEWS: returns reference to the current FEWS application directory

• $ART_VERSCHIL_EXE$, a variable from the global properties

  Code Block
  xml xml
  <explorerTask name="Art_Verschil tool"> <iconFile>%FEWSDIR%/icons/matlab.ico</iconFile> <mnemonic>B</mnemonic> <arguments>/VJDBC_HOST=localhost /VJDBC_PORT=@VJDBC_PORT@</arguments> <workDir>%REGION_HOME%/Modules/Art_Verschil</workDir> <taskExe>$ART_VERSCHIL_EXE$</taskExe> <toolbarTask>true</toolbarTask> <menubarTask>true</menubarTask> <accelerator>ctrl B</accelerator> </explorerTask>

  
  

The next example calls the TimeSeriesDisplay with a preselected Statistical function:

<explorerTask name="Ensemble exceedence analysis">
  <iconFile>exceedence.png</iconFile>
  <arguments>statisticalFunction ensemblePercentileExceedence</arguments>
  <taskClass>nl.wldelft.fews.gui.plugin.timeseries.TimeSeriesDialog</taskClass>
  <toolbarTask>true</toolbarTask>
  <menubarTask>true</menubarTask>
</explorerTask>

Predefined Dashboards

Since 2019.02 FEWS supports creating and using dashboards. These dashboards can be created by the user or be predefined by a configurator. The predefined dashboards are configured through a "dashboards.ini" file (in the root config files) which contains the settings that would otherwise be stored in the user settings if the dashboard was user-defined. More information on the dashboards can be found in the User Guide > 33 Dashboard Display.

It is possible to set permissions for the predefined dashboards through the Explorer.xml. 

	<predefinedDashboards>
		<dashboard name="BE Compose">
			<permission>Development</permission>
		</dashboard>
	</predefinedDashboards>

The configured "name" should match the name of a predefined dashboard present in the dashboards.ini file. The configured permission will then be applied to that dashboard, controlling for which users this dashboard will be present in the dashboards menu (thus allowing them to open it).

statusBar

The status Bar settings define the elements that can be shown in the FEWS Explorer status bar. This includes the configuration of the date/time and elements like showing the user, usergroup, etc..

Image Added

Figure 10 Elements in the Status bar section of the Explorer configuration

dateTimeFormat

String defining the time format for time displayed in the status bar. For example HH:mm:ss will display time as 10:43:26.
Using <dateTimeFormat>dd-MM-yyyy kk:mm</dateTimeFormat> leads to hrs-indication of "24" of previous day instead of "00" (by using kk instead of HH).

userName / userGroup

scheduledTaskEndWarning

<statusBarConfig>
   <description>Standard date-time format</description>
   <dateTimeFormat>HH:mm:ss</dateTimeFormat>
   <timeGMT>true</timeGMT>
   <timeCurrent>false</timeCurrent>
   <timeLastRefresh>true</timeLastRefresh>
   <statusOfSystem>true</statusOfSystem>
   <mouseCoordinates>true</mouseCoordinates>
   <userName>true</userName>
   <scheduledTaskEndWarning>
      <color>aquamarine1</color>
      <time unit="minute" multiplier="75"/>
   </scheduledTaskEndWarning>
</statusBarConfig>

showLocationsOutsideVisibilityPeriod

Optional boolean value. Default is false.

When true Locations with a start and end time that does not include system time will be visible with a specific icon (instead of not being visible at all).

Image Added

Image Added

restSettings

This section includes additional settings for the FEWS Explorer.

Image Added
Figure 11 Elements in the Rest Settings section of the Explorer configuration

defaultSelectFilterId

Defines the default filter to be selected on starting the fewsExplorer

geoDatum

Default definition of the geographic datum. This is an enumeration of geographic datums supported. As further geographic datums are supported, the list will be expanded;

For the enumeration of geoDatums suppoted, see Appendix B

globalDatum

It is possible to configure global datum label in a display group:

<globalDatum>AHD</globalDatum>

localDatum

Since 2020.02 it is possible to configure local datum label to specifically set the reference level of a certain axis in a display group:

<localDatum>someLocalDatum</localDatum>

dateTimeFormat

Format definition for time strings in displays (e.g. yyyy-MM-dd HH:mm:ss is resolved to 2004-07-03 10:43:26)

cardinalTimeStep

Default cardinal time step for the system. The system time will be rounded down to the actual time to the closest cardinal time step.

Attributes;

• unit (enumeration of: second, minute, hour, day, week)
• multiplier defines the number of units given above in a time step.
• divider same function as the multiplier, but defines fraction of units in time step.

timeZone

Defines the default time zone for the system. The default time zone is used for all times in user displays, unless locally overruled. This includes time series displays and the system time. The time zone used by the system should conform to a time zone that does not consider summer time. If this optional entry is not included then the timeZone is considered to be UTC+0:00 (or GMT). The time zone can be defined in two ways:

• timeZoneOffset: The offset of the time zone with reference to UTC (equivalent to GMT). Entries should define the number of hours (or fraction of hours) offset. (e.g. +01:00)
• timeZoneName: Enumeration of supported time zones. See appendix B for list of supported time zones.

logPanelConfig

Configuration of the log panel at the bottom of the main display. This can be configured to show all messages (DEBUG level and up), or filtered from a defined level. Two types of log message can be displayed; those generated by the DEBUG logger and those by the EVENT logger. In normal use the latter is defined to show messages from a level of INFO or above. The former is not normally used except for configuration in the stand alone when additional information may be useful. Different settings are available for stand alone clients and for operator clients

Image Added
Figure 12 Elements in the Log Panel section of the Explorer configuration

clientFilter

Root element of a definition of filters (multiple entries may exist).

clientId

Definition of log filters for Operator client or for Stand alone system (both may be included).

logFilter

Root element for log filter definition

eventType

Filter applicable to System logger or to debug logger. Enumeration of "system"or "event".

Level

Level of log message below which messages are not displayed. Enumeration of DEBUG, INFO, WARN, ERROR, FATAL ERROR

rollingBarrelOptions

This allows you to set the rolling barrel options for the client. Available options for the type are:

• not_automatic: The Rolling Barrel will only run if you launch it using the F12 menu
• startup_only: The Rolling Barrel will only run when starting up the client
• shutdown_only: The Rolling Barrel will only run at showdown of the client
• interval: The Rolling Barrel will run at the specified interval

Example:

<rollingBarrelOptions>
	<type>interval</type>
	<interval unit="hour" multiplier="1"/>
</rollingBarrelOptions>

Schema:
Image Added

parameterListConfig

This allows you to set the default sorting option for the parameters in the Explorer. Available options are:

• default: Use the default sorting from the configuration file Parameters.xml.
• name: Sort by parameter name (ascending).

Example:

<parameterListConfig>
	<sortOption>name</sortOption>
</parameterListConfig>

Schema:
Image Added

notification

The system can notify the completion of a manually dispatched task run when the notification property is enabled (i.e. enabled=TRUE).

Image Added

numberOfTimeSeriesBlobsForWarning

Number for the amount of time series blobs in database that indicates when the OC should give a popup warning on startup that FEWS is not designed for unlimited amount of data. Default is 1 million.

  <numberOfTimeSeriesBlobsForWarning>1000000</numberOfTimeSeriesBlobsForWarning>

Image Added

  <showIconForUnacknowledgedWarnings>true</showIconForUnacknowledgedWarnings>

ocConfigDirPermission

When a local config dir in the OC region home is detected the user is asked to restart using this config dir. This feature is for testing purposes and can be disabled for normal users by specifying a required permission.  Fews will always first start with the database config before asking to restart. The permission from the original config is used.

<ocConfigDirPermission>admin</ocConfigDirPermission>

DebugMenuPermission

If the user has the debug menu permission, by pressing F12, the debug menu appears. Please note, if this permission is not configured, then the debug menu can be accessed by all users. An example of how to configure the debug menu permission and an screenshot of the debug menu follow:

<debugMenuPermission>admin</debugMenuPermission>

Image Added

Filemenu options

From the FEWS Explorer File menu it is possible to configure a number of additional menu items (from which a few can also be found in the <F12> menu) . They are explained below.

Open most recent forecast

Opens the most recent forecast for selection (in dataviewer).

<fileMenu>
	<openMostRecentForecast visible="true"/>
</fileMenu>

Open most recent current forecast

Opens the most recent  current forecast for selection (in dataviewer).

<fileMenu>
	<openMostRecentCurrentForecast visible="true"/>
</fileMenu>

Open last forecast

Opens the last forecast for selection (in dataviewer)

<fileMenu>
	<openLastForecast visible="true"/>
</fileMenu>

Set system time to last available

Sets the system time to last available.

<fileMenu>
	<setSystemTimeToLast visible="true"/>
</fileMenu>

Delete localdatastore

Deletes the local datastore.

<fileMenu>
	<deleteLocalDataStore visible="true"/>
</fileMenu>

Exporttimeseries -  interactiveExportFormats

From the FEWS Explorer File menu it is possible to export selected time series to a subset of the export file formats. To enable the Export Timeseries file menu option, it should be enabled in the Explorer.xml file. See Interactive Export

someSeriesCompletelyMissingIconVisible

When set to true, an orange cross will appear for locations/parameters/nodes where some, but not all timeseries contain missing data. Default is false (for backward compatibility)

DocumentViewer

The Documentviewer is used to show documents connected to workflows in the IFD. It is also possible to show documents connected to values in timeseries (eg picture of peilschaal). Here is more information on application and configuration.

vjdbcServicePortRange

The FEWS Stand Alone can start an embedded VJDBC server automatically or through the debug mode.

Starting VJDBC server automatically:

When the Explorer.xml file of the Stand Alone system contains an additional element “vjdbcServicePortRange”, the Delft-FEWS internal vjdbc server will start automatically when the Stand alone is started. For the port number a range of the port numbers can be provided, for example   <vjdbcServicePortRange start="2000" end="2005"/>

We advice to use the portrange starting from 2000.

Starting VJDBC server through the debug mode :

When there is no “vjdbcServicePortRange” configured,  you can start VJDBC server  with Explorer F12 menu option “M start embedded vjdbc server”.  Then the  embedded VJDBC Server will use port number 2000.

This VJDBC functionality can be used to analyse the database of the Stand Alone using external tools like DBVisualizer. Or it can be used to start a FEWS  Stand Alone in participant mode or the Water Coach in participant mode (Application configuration#Participantmode)

piServicePortRange

Since 2022.02 the FEWS Stand Alone or Operator Client can start an embedded tomcat server with the Delft-FEWS Web Services automatically or through the debug mode.

Starting FewsWebServices

$ART_VERSCHIL_EXE$, a variable from the global properties

...

<explorerTask name="Art_Verschil tool">
  <iconFile>%FEWSDIR%/icons/matlab.ico</iconFile>
  <mnemonic>B</mnemonic>
  <arguments>/VJDBC_HOST=localhost /VJDBC_PORT=@VJDBC_PORT@</arguments>
  <workDir>%REGION_HOME%/Modules/Art_Verschil</workDir>
  <taskExe>$ART_VERSCHIL_EXE$</taskExe>
  <toolbarTask>true</toolbarTask>
  <menubarTask>true</menubarTask>
  <accelerator>ctrl B</accelerator>
</explorerTask>

The next example calls the TimeSeriesDisplay with a preselected Statistical function:

...

<explorerTask name="Ensemble exceedence analysis">
  <iconFile>exceedence.png</iconFile>
  <arguments>statisticalFunction ensemblePercentileExceedence</arguments>
  <taskClass>nl.wldelft.fews.gui.plugin.timeseries.TimeSeriesDialog</taskClass>
  <toolbarTask>true</toolbarTask>
  <menubarTask>true</menubarTask>
</explorerTask>

Predefined Dashboards

Since 2019.02 FEWS supports creating and using dashboards. These dashboards can be created by the user or be predefined by a configurator. The predefined dashboards are configured through a "dashboards.ini" file (in the root config files) which contains the settings that would otherwise be stored in the user settings if the dashboard was user-defined. More information on the dashboards can be found in the User Guide > 33 Dashboard Display.

It is possible to set permissions for the predefined dashboards through the Explorer.xml. 

	<predefinedDashboards>
		<dashboard name="BE Compose">
			<permission>Development</permission>
		</dashboard>
	</predefinedDashboards>

The configured "name" should match the name of a predefined dashboard present in the dashboards.ini file. The configured permission will then be applied to that dashboard, controlling for which users this dashboard will be present in the dashboards menu (thus allowing them to open it).

statusBar

The status Bar settings define the elements that can be shown in the FEWS Explorer status bar. This includes the configuration of the date/time and elements like showing the user, usergroup, etc..

Image Removed

Figure 10 Elements in the Status bar section of the Explorer configuration

dateTimeFormat

String defining the time format for time displayed in the status bar. For example HH:mm:ss will display time as 10:43:26.
Using <dateTimeFormat>dd-MM-yyyy kk:mm</dateTimeFormat> leads to hrs-indication of "24" of previous day instead of "00" (by using kk instead of HH).

userName / userGroup

scheduledTaskEndWarning

<statusBarConfig>
   <description>Standard date-time format</description>
   <dateTimeFormat>HH:mm:ss</dateTimeFormat>
   <timeGMT>true</timeGMT>
   <timeCurrent>false</timeCurrent>
   <timeLastRefresh>true</timeLastRefresh>
   <statusOfSystem>true</statusOfSystem>
   <mouseCoordinates>true</mouseCoordinates>
   <userName>true</userName>
   <scheduledTaskEndWarning>
      <color>aquamarine1</color>
      <time unit="minute" multiplier="75"/>
   </scheduledTaskEndWarning>
</statusBarConfig>

showLocationsOutsideVisibilityPeriod

Optional boolean value. Default is false.

When true Locations with a start and end time that does not include system time will be visible with a specific icon (instead of not being visible at all).

Image Removed

Image Removed

restSettings

This section includes additional settings for the FEWS Explorer.

Image Removed
Figure 11 Elements in the Rest Settings section of the Explorer configuration

defaultSelectFilterId

Defines the default filter to be selected on starting the fewsExplorer

geoDatum

Default definition of the geographic datum. This is an enumeration of geographic datums supported. As further geographic datums are supported, the list will be expanded;

For the enumeration of geoDatums suppoted, see Appendix B

dateTimeFormat

Format definition for time strings in displays (e.g. yyyy-MM-dd HH:mm:ss is resolved to 2004-07-03 10:43:26)

cardinalTimeStep

Default cardinal time step for the system. The system time will be rounded down to the actual time to the closest cardinal time step.

Attributes;

• unit (enumeration of: second, minute, hour, day, week)
• multiplier defines the number of units given above in a time step.
• divider same function as the multiplier, but defines fraction of units in time step.

timeZone

Defines the default time zone for the system. The default time zone is used for all times in user displays, unless locally overruled. This includes time series displays and the system time. The time zone used by the system should conform to a time zone that does not consider summer time. If this optional entry is not included then the timeZone is considered to be UTC+0:00 (or GMT). The time zone can be defined in two ways:

• timeZoneOffset: The offset of the time zone with reference to UTC (equivalent to GMT). Entries should define the number of hours (or fraction of hours) offset. (e.g. +01:00)
• timeZoneName: Enumeration of supported time zones. See appendix B for list of supported time zones.

logPanelConfig

Configuration of the log panel at the bottom of the main display. This can be configured to show all messages (DEBUG level and up), or filtered from a defined level. Two types of log message can be displayed; those generated by the DEBUG logger and those by the EVENT logger. In normal use the latter is defined to show messages from a level of INFO or above. The former is not normally used except for configuration in the stand alone when additional information may be useful. Different settings are available for stand alone clients and for operator clients

Image Removed
Figure 12 Elements in the Log Panel section of the Explorer configuration

clientFilter

Root element of a definition of filters (multiple entries may exist).

clientId

Definition of log filters for Operator client or for Stand alone system (both may be included).

logFilter

Root element for log filter definition

eventType

Filter applicable to System logger or to debug logger. Enumeration of "system"or "event".

Level

Level of log message below which messages are not displayed. Enumeration of DEBUG, INFO, WARN, ERROR, FATAL ERROR

rollingBarrelOptions

This allows you to set the rolling barrel options for the client. Available options for the type are:

• not_automatic: The Rolling Barrel will only run if you launch it using the F12 menu
• startup_only: The Rolling Barrel will only run when starting up the client
• shutdown_only: The Rolling Barrel will only run at showdown of the client
• interval: The Rolling Barrel will run at the specified interval

Example:

<rollingBarrelOptions>
	<type>interval</type>
	<interval unit="hour" multiplier="1"/>
</rollingBarrelOptions>

Schema:
Image Removed

parameterListConfig

This allows you to set the default sorting option for the parameters in the Explorer. Available options are:

• default: Use the default sorting from the configuration file Parameters.xml.
• name: Sort by parameter name (ascending).

Example:

<parameterListConfig>
	<sortOption>name</sortOption>
</parameterListConfig>

Schema:
Image Removed

notification

The system can notify the completion of a manually dispatched task run when the notification property is enabled (i.e. enabled=TRUE).

Image Removed

numberOfTimeSeriesBlobsForWarning

Number for the amount of time series blobs in database that indicates when the OC should give a popup warning on startup that FEWS is not designed for unlimited amount of data. Default is 1 million.

...

  <numberOfTimeSeriesBlobsForWarning>1000000</numberOfTimeSeriesBlobsForWarning>

Image Removed

showIconForUnacknowledgedWarnings

Boolean option whether to show an opaque warning icon (Image Removed) in the status bar when unacknowledged warnings are present in database. Only if no unacknowledged errors are present. 

...

  <showIconForUnacknowledgedWarnings>true</showIconForUnacknowledgedWarnings>

Image Removed

Filemenu options

From the FEWS Explorer File menu it is possible to configure a number of additional menu items (from which a few can also be found in the <F12> menu) . They are explained below.

Open most recent forecast

Opens the most recent forecast for selection (in dataviewer).

<fileMenu>
	<openMostRecentForecast visible="true"/>
</fileMenu>

Open most recent current forecast

Opens the most recent  current forecast for selection (in dataviewer).

<fileMenu>
	<openMostRecentCurrentForecast visible="true"/>
</fileMenu>

Open last forecast

Opens the last forecast for selection (in dataviewer)

<fileMenu>
	<openLastForecast visible="true"/>
</fileMenu>

Set system time to last available

Sets the system time to last available.

<fileMenu>
	<setSystemTimeToLast visible="true"/>
</fileMenu>

Delete localdatastore

Deletes the local datastore.

<fileMenu>
	<deleteLocalDataStore visible="true"/>
</fileMenu>

Export timeseries -  interactiveExportFormats

From the FEWS Explorer File menu it is possible to export selected time series to a subset of the export file formats. To enable the Export Timeseries file menu option, it should be enabled in the Explorer.xml file.

Example:

<fileMenu>
	<exportTimeSeries visible="true"/>
</fileMenu>

By default the exported time series will not do any ID mapping on exporting. Pre-defined ID mapping configuration files can be configured in the interactiveExportFormats element. In the example below the export type iBever will always use the ID Mapping configuration file IdExportKwaliteit. For each export type a default ID mapping file can be configured. InteractiveExports will always export missing values.

The following exportTypes are available:

• csv
• dutch-csv
• gin-xml
• Hymos 4.03
• Hymos 4.5
• iBever
• Menyanthes
• pi-xml
• generalCsv (with the use of Table Layout)

Example:

<interactiveExportFormats>
	<interactiveExportFormat>
		<name>iBever Export</name>
		<exportType>iBever</exportType>
		<IdMapId>IdExportKwaliteit</IdMapId>
	</interactiveExportFormat>
	<interactiveExportFormat>
		<name>HYMOS Transferdatabase 4.03</name>
		<exportType>Hymos 4.03</exportType>
		<IdMapId>IdHYMOS</IdMapId>
		<flagConversionsId>ExportHYMOSFlagConversions</flagConversionsId>
	</interactiveExportFormat>
	<interactiveExportFormat>
		<name>HYMOS Transferdatabase 4.50</name>
		<exportType>Hymos 4.5</exportType>
		<IdMapId>IdHYMOS</IdMapId>
		<flagConversionsId>ExportHYMOSFlagConversions</flagConversionsId>
	</interactiveExportFormat>
	<interactiveExportFormat>
		<name>General CSV Sample Export</name>
		<exportType>generalCsv</exportType>
		<IdMapId>IdImport_HydroBiologie</IdMapId>
		<table>
			<dateTimeColumn name="DATE_SMP" pattern="dd-MM-yy HH:mm"/>
			<locationColumn name="LOC_CODE"/>
			<unitColumn name="Eenheid"/>
			<parameterColumn name="PARAMETER_ID"/>
			<qualifierColumn name="PAR_REF" prefix="PAR_REF_"/>
			<qualifierColumn name="PROD_CODE" prefix="PROD_CODE_"/>
			<qualifierColumn name="ANAL_CODE" prefix="ANAL_CODE_"/>
			<qualifierColumn name="TYPE" prefix="TYPE_"/>
			<propertyColumn name="COST_CODE" key="COST_CODE"/>
			<attributeColumn name="Groep" id="Groep"/>
			<valueColumn name="Waarde"/>
		</table>
	</interactiveExportFormat>       
 </interactiveExportFormats>

...

<interactiveExportFormats>
	<interactiveExportFormat>
		<name>General CSV</name>
		<exportType>generalCsv</exportType>
		<IdMapId>GeneralCsv</IdMapId>
		<table>
			<dateTimeColumn pattern="dd-MM-yy HH:mm"/>
			<locationColumn name="Location"/>
			<parameterColumn name="Parameter"/>
			<flagSourceColumn name="A" id="A"/>
			<flagSourceColumn name="B" id="B"/>
			<flagSourceColumn name="C" id="C"/>
			<flagSourceColumn name="D" id="D"/>
			<flagSourceColumn name="E" id="E"/>
			<valueColumn name="Value"/>
		</table>
	</interactiveExportFormat>
</interactiveExportFormats>

It is also possible to configure your own serializer class as long as this class implements the interface Serializer<TimeSeriesContent>. An example is given below for the UmAquo CSV serializer:

<interactiveExportFormat>
    <name>Umaquo 2011 CSV files</name>
    <serializerClassName>nl.wldelft.webservice.umaquo.timeseriesserializers.UmAquoCsvTimeSeriesSerializer</serializerClassName>
    <!-- Configure the binDir if jars of serializer are not located in FEWS bin directory -->
    <!-- <binDir>%RegionHome%/Modules/aquo-bin</binDir>-->
    <fileFilter>csv</fileFilter>
    <exportUnreliable>true</exportUnreliable>
    <properties>
        <int key="SCHEMA_VERSION" value="2011"/>
    </properties>
    <IdMapId>IdExportUmAquo</IdMapId>
    <unitConversionsId>ExportUmAquoUnits</unitConversionsId>
    <flagConversionsId>ExportUMAquoFlagConversions</flagConversionsId>
</interactiveExportFormat>

someSeriesCompletelyMissingIconVisible

When set to true, an orange cross will appear for locations/parameters/nodes where some, but not all timeseries contain missing data. Default is false (for backward compatibility)

DocumentViewer

The Documentviewer is used to show documents connected to workflows in the IFD. It is also possible to show documents connected to values in timeseries (eg picture of peilschaal). Here is more information on application and configuration.

vjdbcServicePortRange

The FEWS Stand Alone can start an embedded VJDBC server automatically or through the debug mode.

Starting VJDBC server automatically:

When the Explorer.xml file of the Stand Alone system contains an additional element “vjdbcServicePortRange”“piServicePortRange”, the Delft-FEWS internal vjdbc embedded tomcat server will start automatically when the Stand alone is started. For the port number a range of the port numbers can be provided, for example   <vjdbcServicePortRange start<piServicePortRangestart="20008080" end="20059000"/>

We advice to use the portrange a port range starting from 20008080.

Starting VJDBC server FewsWebServices through the debug mode :

When there is no “vjdbcServicePortRange” configured,  you can start VJDBC server  with Explorer F12 menu option “M start embedded vjdbc server”.  Then the  embedded VJDBC Server will use port number 2000.

This VJDBC functionality can be used to analyse the database of the Stand Alone using external tools like DBVisualizer. Or it can be used to start a FEWS  Stand Alone in participant mode or the Water Coach in participant mode (Application configuration#Participantmode)

 “piServicePortRange” configured,  you can start the Fews Web Services with Explorer F12 menu option “start embedded tomcat web services”.  Then the embedded tomcat fews web services will use a free port in the range 8080-9000. The web service is typically accessible at: http://localhost:8080/FewsWebServices/ when port 8080 is not in use.

  showLocationsOutsideVisibilityPeriod