...
Mapping of the Thresholds configured in FEWS and the Threshold name exported in the CAP file. The order of the thresholdId’s in this mapping table will also be used to check the severity of the threshold.
To translate %SEVERITY% at least 1 map threshold element is needed. When the threshold is not present in the map no file will be exported.
At least 1 map threshold element is needed for level thresholds to determine the %MESSAGE_TYPE% because it needs the correct order of the threshold levels to find the lowest available for a parameter-location-time combination.
When the lowest available threshold can not be determined (for a parameter-location-time combination) no file will be exported.
For rate thresholds %MESSAGE_TYPE% is always "Alert" because there is no specific crossing order.
At least 1 map threshold element is needed for level thresholds to determine the %ALERT_HISTORY (DF1)% to see if lower or higher thresholds were crossed before. Otherwise it will remain empty.
For rate thresholds it will always be empty.
Configurable TAGS
The %information% tags will be hard coded in the Threshold Export module. In this example the following %information% tags are required:
...