scrollbar |
---|
What | Required | Description | schema location |
---|---|---|---|
Filters.xml | yes | Definition of filters in the main map display | http://fews.wldelft.nl/schemas/version1.0/filters.xsd |
...
Instead of an extensive definition of all possible time series that usually will be repeated for different types of locations and various districts, it is possible to define the timeSeriesSets once and to use it various times through all filters. At this point you refer to such a timeSeriesSets and optionally add some constraints on the location attributes. Notice that location attributes only can be defined in the locationSets for locations that are read from an ArcGIS shape DBF file. See the example below.
It is possible to define filters that may become empty: no locations comply with the constraints. These filters are not displayed. An advantage of this approach is that all possible filters can be defined once and automatically become visible when a location complies to the constraints.
...
GroupBy
parameter attribute
Since 2016.01 filters can be automatically generated based on different parameter attribute values.
...
When selecting filter "E1b" both parameters "Beschaduwing_%" & "Bemonsteringstraject_m" will appear because they both have "E1b" in their multivalued "ATTRIBUTE_1":
Group by location and qualifier attributes
Since 2020.01 it is also possible to atomatically generate filters based on location and qualifier attributes.
Nested GroupBy
GroupBy filters can be nested as well and mutliple parameter, location and qualifier attributes can be used in any order and there is no limit on how many attributes to specify.
However, creating too many of separate subfilters can result in a drastically degraded performance.
The config example below will first create subfilters based on parameters which all have the same parameter attribute values.
The parameter filters will have subfilters based on location attributes and those subfilters will in turn have their own subfilters based on qualifier attribute values.
Code Block | ||||
---|---|---|---|---|
| ||||
<filter id="GroupByNested" name="GroupByNested">
<relativeViewPeriod start="-31" end="0" unit="day"/>
<groupBy>
<parameterAttributeId>ParameterGroup</parameterAttributeId>
<locationAttributeId>L_meetprogrammahistorie</locationAttributeId>
<qualifierAttributeId>groep</qualifierAttributeId>
</groupBy>
</filter> |
Additional time series
Additional time series can be configured in filters. These series are found via attribute functions of the selected time series and the additional time series. When the attribute functions evaluate to the same value the additional time series are added as invisible by default. When additional time series are available the icon of the visibility dialog will change which shows that invisible time series are available and can be made visible. Each additional time series element can be given a name, this name will be used as prefix in the legend of the time series and as GroupNode label in the visibility dialog.
...