View source for TUFLOW Message 3022

{{TUFLOW_Message
|tuflow_message=ERROR 3022 - Number of Boundary Level Graphs exceeded. Maximum is 253.
<br> 
|alt_msg=ERROR 3022 - Maximum number of Boundary tracer graphs exceeded.<br>
ERROR 3022 - Number of groundwater boundary Level Graphs exceeded. Maximum is 255.
|type=[[ERROR]] 
|message_desc=HPC has a limit of 253 for unique HT plus HQ boundaries, and 255 for GT boundaries.
|suggestions=
HT, HQ, and GT boundaries should only be digitised in the location where water is entering/exiting the model, i.e. not along the whole code perimeter.<br>
For HT boundary:
* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.
* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line.
For HQ boundary:
* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).
For GT boundary:
* Check total number of GT boundaries in the 2d_bc layer isn't more than 255.

|uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]]
}}