| 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 |
...
| 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. |
| 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>
|
...
timeSeriesSetId & constraints
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.
Group by parameter attribute id
Since 2016.01 filters can be automatically generated based on different parameter attribute values.
| No Format |
|---|
<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
| No Format |
|---|
<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>
|
| No Format |
|---|
<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>
|