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 |
Contents
Table of Contents | ||
---|---|---|
|
...
Info |
---|
The time span defined in the time series sets in the filter has an important function. It determines the time span checked for determining status icons (e.g. missing data) in the main map display. Not all locations need to be included in a filter. Locations that are not defined, will never be visible to the user. The readWrite parameter defined in the time series set included in the filter will determine if the time series may be edited by the user. If this parameter is set to read only then the time series will not support editing. This is the case for external time series only. Simulated time series are read only by convention. Notice that editable timeSeriesSets should have synchLevel 5 to get the edits saved into the central database. |
Code Block | ||||
---|---|---|---|---|
| ||||
<!-- | ||||
No Format | ||||
Example (time series sets not expanded) --> <filter id="Config Example"> <child foreignKey="Nested Filter"/> </filter> <filter id="Nested Filter"> <timeSeriesSet/> </filter> <filter id="Main Level Filter"> <timeSeriesSet/> </filter> |
Figure32 Example of filter configuration, as defined in the example XML configuration above.
...
Since 2016.01 filters can be automatically generated based on different parameter attribute values.
Code Block | ||
---|---|---|
| ||
| ||
<filter id="groupByParameterAttribute">
<relativeViewPeriod start="-100000" end="0" unit="day"/>
<parameterConstraints>
<idStartsWith prefix=""/>
</parameterConstraints>
<groupBy>
<parameterAttributeId>ATTRIBUTE_1</parameterAttributeId>
</groupBy>
</filter>
|
This will work for multivalued attributes as well
Code Block | ||
---|---|---|
| ||
| ||
<attributeFile>
<csvFile>parameterAttributes.csv</csvFile>
<parameterId>%ID%</parameterId>
<attribute id="ATTRIBUTE_1">
<text>%ATTRIBUTE_1%</text>
</attribute>
<attribute id="ATTRIBUTE_2">
<text>%ATTRIBUTE_2%</text>
</attribute>
</attributeFile>
</parametersCsvFile>
|
In parameterAttributes.csv below multivalued attributes are defined for some parameters like "BESDWG_%" which has values "E1a" & "E1b" for "ATTRIBUTE_1".
For parameter "BEMSRTJT_m" the attribute "ATTRIBUTE_1" has values "D1" & "E1b".
ID | ATTRIBUTE_1 | ATTRIBUTE_2 |
BEMSDOVZDE | A1 | A2 |
BEMSRBTE_m | B1b | B2 |
BEMSROPVK_m2 | C2 | |
Bemonsteringstraject_m | D1 | |
Beschaduwing_% | E1a | E2a |
BREEDTE_m | ||
CHLFa_ug/l | ||
BEMSRBTE_m | B1a | |
Beschaduwing_% | E1b | E2b |
Bemonsteringstraject_m | E1b |
When "ATTRIBUTE_1" is used to generate filters based on its values the next filters are generated: A1, B1a, B1b, E1a, E1b, D1.
...