This check operates with the manual persistency marker that can be set by the user in the TimeSeriesDialog. This check will copy a persistent flag to the next timestep and will mark this next timestep as persistent. This is repeated until a different manual flag source is found.The purpose of the FlagPersistencyCheck is to automatically mark series unreliable, also for new imports. This is useful for when it is known from an import that the data is not correct, for instance when a remote sensor instrument is not functioning correctly.

Mark persistent unreliable with TimeSeriesDialog (Data Editor)

For this check to function, a special flag is available in Delft-FEWS. The persistent unreliable flag. When the data delivered by a station is suspected to be unreliable from a certain point in time the value can be set to persistent unreliable from the TimeSeriesDialog (Data Editor).

Schedule secondary validation FlagPersistencyCheck after import

Second step in this procedure is to run the secondary validation module FlagPersistencyCheck after every import. This module will set all values from this station to unreliable from the time where the flag was set. The values will be set to unreliable until the time at which a manual reliable is set for this station. NB. It is not possible to set missing values with a persistency marker to reliable again.

Configuration example
<secondaryValidation xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/secondaryValidation.xsd"
    <!-- variableDefinitions can be global or nested -->
            <timeSeriesType>external historical</timeSeriesType>
            <timeStep unit="hour" multiplier="1"/>
            <relativeViewPeriod unit="day" start="-7" end="0"/>
            <readWriteMode>read only</readWriteMode>
	<flagPersistencyCheck id="FlagPersistencyCheck">
	<logMessage>%AMOUNT_CHANGED_FLAGS% flags set to unreliable persistence for location=%LOCATION_NAME%</logMessage>
  • No labels