Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


The t0 can be set to the selected time in the time slider by the button  "Set t0 to the selected time". If a location is not visible at the selected time in the time slider, the location will still be shown in the map and the filter, but will be greyed out to indicate that it is not valid at the selected time. For performance reasons the icons in the filters will not be updated according to the selected time when the time slider is shown in the map display. The MapToolTip (button "tooltip") and MapItemSelectTool (button "select locations with lasso tool") take into account the selected time in time slider. If the time slider is not selected the system time is used.

In typical WIS systems users still want to have access to the data although the locations has been "stopped" by the provided stoptime. Therefore, the option <showLocationsOutsideVisibilityPeriod>true</showLocationsOutsideVisibilityPeriod> can be defined in Explorer.xml to show all locations no matter the start-/stoptime in de Filters. Locations outside of the defined start-/stoptime will be marked using black/gray crosses instead of the typical red/darkred ones for missing data.

Filter change events

Since 2016.02 a filter button has been added which lets the user choose which change events should be included. The change events are grouped by type of change events recognized in Delft-FEWS: Map Layers, Locations, Location Attributes, Location Relations;


The transformation module automatically takes into account the time dependency of the locations. No configuration is needed in the transformation module. If an end time is introduced for a location and time series are in the database for this location after the end time, then the part of the time series which is not valid anymore will not be read from the database. The benefit of this approach is that the configurator doesn't need to remove obsolete parts of time series for the location from the database.

Note: the usage of time dependent location relations and time dependent location set constraints is not supported in the transformation module before 2020.01 because this requires to switch the location itself during the transformation. This will be supported from 2020.01 onwards. There will be a warning for transformations that do not support this, this will mainly be transformations that have multiple time input and or output (like aggregation and accumulation), because the individual transformation can not handle a change in within their input or output period. 

Secondary validation

The secondary validation module also takes into account the time dependency of the locations. The secondary validation will only run if all of the used locations are valid, the values of location attributes used in the


In that case the location of variable A will be used to determine the value of the location attributes. After that, the secondary validation will run for validating variable B which will mean that the location of this variable will be used.



Chainage Location Sets (since 2020.02)

Since 2020.02 it is possible to use time dependent chainage attributes to determine a longitudinal profile.

The longitudinal profile will be visualized with all chainage locations that are part of the profile at any time in the period of the time slider.

When at a specific moment in time a location is not part of the profile a missing value will be shown in the table, but the graph will just connect the line to the next location that is part of the profile.

The Image Added