...
<inputForecastSequenceVariable> which contains forecasts that determine a sequence of periods in which forecasts and crossings should be within in order to be matched to eachother. The sequence periods are determined via <startSequenceValueProperty .../> and <endSequenceValueProperty .../> and their value property id's and values. For <startSequenceValueProperty id="Phase" value="NEW"/> <endSequenceValueProperty id="Phase" value="FIN"/> sequence periods will be from the forecast series with valueProperty "Phase" = "NEW" until a forecast series with "Phase" = "FIN" and then new periods will start from the next "NEW" until the next "FIN" and so on.
There can be multiple threshold crossings for each location, based on <thresholdCrossing .../> elements
...
If the forecast was sent before the actual crossing minus the lead time, the forecast will be counted as correct which counts as a value +1 for the <outputHitCountVariable>.
If the forecast was sent after the actual crossing minus the lead time, the forecast will be counted as missed time which means a value +1 for the <outputMissedTimeCountVariable>.
If the forecast was sent even after the actual crossing (so not even without minus the lead time), the forecast will be counted as missed height which means a value +1 for the <outputMissedHeightCountVariable>.
If the forecast was never matched with a crossing, the forecast will be counted as false alarm which means a value +1 for the <outputFalseAlarmCountVariable>.
For all the crossings that are never matched with a forecast will also be counted as missed height which means a value +1 for the <outputMissedHeightCountVariable>.