Page History

...

• validationIconsViewPeriod: Since 2017.01, optional element. Calculate validation icons in the specified period. By using this you can for example ignore the validation problems for the most recent data.

• validationIconsVisible: Optional element allowing the user to make use of the additional validation icons available in the explorer (2009.01). When set to true, all validation icons in the relative view period of the time series sets will be shown.

ignoreDoubtfulAndUnreliableFlagSourceColumnId

Hide validation icons when this flag source column is filled.

...

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.

Dynamic filter without

...

TimeSeriesSets

Without time series sets the filter only contains time series that are available in the database. For every filter FEWS walks through all the time series available in the database. When a time series is deleted it is removed from the filter on the next compact index files, this happens on a live system at least once a day.

...

	<filter id="dynamic">
        <timeSeries>
            <moduleInstanceId>ImportFC</moduleInstanceId>
         </timeSeries>
		<relativeViewPeriod start="-10" end="0" unit="day"/>
	</filter>

GroupBy 

parameter attribute

Since 2016.01 filters can be automatically generated based on different parameter attribute values. 

It can also be extended with

• valueType
• locations, via <locationId>'s or <locationSetId>'s. For more info see: LocationSets
• parameters, via <paramaterId>'s and/or <parameterGroupId>'s. 
• qualifiers, via 1 or more <qualifierId>'s
• timeSeriesType
• timeStep
• aggregationPeriod
• cycle
• ensembleId
• ensembleMemberId

GroupBy 

parameter attribute

Since 2016.01 filters can be automatically generated based on different parameter attribute values. 

	<filter id="groupByParameterAttribute">
        <timeSeries>
            <moduleInstanceId>ImportFC</moduleInstanceId>
        </timeSeries>
		<relativeViewPeriod start="-100000" end="0" unit="day"/>
		<parameterConstraints>			
			<idStartsWith prefix=""/>
		</parameterConstraints>
		<groupBy>
			<parameterAttributeId>ATTRIBUTE_1</parameterAttributeId>
		</groupBy>
	</filter>

...

In parameterAttributes.csv below multivalued attributes are defined for some parameters like "BESDWG

• Beschaduwing_%

...

• has values "E1a" & "E1b"

...

• for ATTRIBUTE_1

...

• Bemonsteringstraject

...

• _m

...

• has values "D1" & "E1b"

...

• for ATTRIBUTE_1

When ATTRIBUTE_1 When  "ATTRIBUTE_1" is used to generate filters based on its values the next filters are generated: A1, B1a, B1b, E1a, E1b, D1.
When selecting filter "E1a" only parameter "Beschaduwing" will appear because that is the only one with with "E1a" as value for "for ATTRIBUTE_1"

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

...