Difference between revisions of "TUFLOW Message 2492"
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
|alt_msg=WARNING 2492 - Duplicated SA boundary name "<>" - treated as single boundary and added selected cells to original boundary polygon.<br> | |alt_msg=WARNING 2492 - Duplicated SA boundary name "<>" - treated as single boundary and added selected cells to original boundary polygon.<br> | ||
|type=[[CHECK]]<br>[[WARNING]] | |type=[[CHECK]]<br>[[WARNING]] | ||
| − | |message_desc= | + | |message_desc=From the 2023-03-AA Build and onwards, models with duplicated SA boundaries (boundaries using the same name) will be treated separately; as if they were different boundary names with the same hydrograph. Prior to the 2023-03-AA Build, duplicated SA boundaries would be treated as a single boundary and the cells selected by each polygon grouped together. |
| − | |suggestions= | + | |
| + | |suggestions=Check that the duplicated boundary name in the 2d_sa layer and behaviour described above is intended. The old method can be invoked by reverting to the pre-2023 defaults and WARNING 2492 is produced instead of the check message. | ||
| − | |||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 19:25, 22 June 2023
TUFLOW Message
CHECK 2492 - Duplicated SA boundary name "<>" - applied as separate boundary.
Alternate Message
WARNING 2492 - Duplicated SA boundary name "<>" - treated as single boundary and added selected cells to original boundary polygon.
Description
From the 2023-03-AA Build and onwards, models with duplicated SA boundaries (boundaries using the same name) will be treated separately; as if they were different boundary names with the same hydrograph. Prior to the 2023-03-AA Build, duplicated SA boundaries would be treated as a single boundary and the cells selected by each polygon grouped together.
Suggestions
Check that the duplicated boundary name in the 2d_sa layer and behaviour described above is intended. The old method can be invoked by reverting to the pre-2023 defaults and WARNING 2492 is produced instead of the check message.
| Up |
|---|
 2xxx Messages
|