Difference between revisions of "TUFLOW Message 2230"
Jump to navigation
Jump to search
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
|tuflow_message=ERROR 2230 - Every vertice around merge region has been assigned a null (-99999.) elevation point. | |tuflow_message=ERROR 2230 - Every vertice around merge region has been assigned a null (-99999.) elevation point. | ||
| − | |alt_msg= | + | |alt_msg=CHECK 2230 - Every vertice around merge region is outside model domain. Skipping. |
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=A merge polygon (does not have Shape_Option of "NO MERGE") has null -99999 elevation assigned at every vertice around the polygon. The null (-99999) elevation point snapped to the polygon (region) tells TUFLOW not to merge into the surrounding zpts at that location. If all points are set to -99999, TUFLOW can't merge region. | + | [[CHECK]] |
| − | |suggestions=Set the Shape_Option on the polygon to "NO MERGE", to prevent the polygon from merging with existing topography. If you want the polygon to merge, remove some of the null elevation points. | + | |message_desc=*If ERROR 2230 - A merge polygon (does not have Shape_Option of "NO MERGE") has null -99999 elevation assigned at every vertice around the polygon. The null (-99999) elevation point snapped to the polygon (region) tells TUFLOW not to merge into the surrounding zpts at that location. If all points are set to -99999, TUFLOW can't merge region. |
| − | + | ||
| − | + | *If CHECK 2230 - A merge region has been located outside of the model domain, TUFLOW will skip this region. | |
| − | + | ||
| − | + | |suggestions= | |
| + | *If ERROR 2230 - Set the Shape_Option on the polygon to "NO MERGE", to prevent the polygon from merging with existing topography. If you want the polygon to merge, remove some of the null elevation points. This can also occur if a polygon is using the "MERGE ALL" option whilst attempting to triangulate across an area where elevation data has not previously been defined. This occurs because TUFLOW's default elevation is initialized to a value of -99999. In this case, make sure that base topography data is defined in the area where the error is occurring. Note: 2d_zsh inputs are processed globally, even if outside the active code areas. | ||
| + | |||
| + | *If CHECK 2230 - Check that the object is intended to be outside of the model domain (and therefore skipping is ok). | ||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 19:41, 1 November 2024
TUFLOW Message
ERROR 2230 - Every vertice around merge region has been assigned a null (-99999.) elevation point.
Alternate Message
CHECK 2230 - Every vertice around merge region is outside model domain. Skipping.
Description
- If ERROR 2230 - A merge polygon (does not have Shape_Option of "NO MERGE") has null -99999 elevation assigned at every vertice around the polygon. The null (-99999) elevation point snapped to the polygon (region) tells TUFLOW not to merge into the surrounding zpts at that location. If all points are set to -99999, TUFLOW can't merge region.
- If CHECK 2230 - A merge region has been located outside of the model domain, TUFLOW will skip this region.
Suggestions
- If ERROR 2230 - Set the Shape_Option on the polygon to "NO MERGE", to prevent the polygon from merging with existing topography. If you want the polygon to merge, remove some of the null elevation points. This can also occur if a polygon is using the "MERGE ALL" option whilst attempting to triangulate across an area where elevation data has not previously been defined. This occurs because TUFLOW's default elevation is initialized to a value of -99999. In this case, make sure that base topography data is defined in the area where the error is occurring. Note: 2d_zsh inputs are processed globally, even if outside the active code areas.
- If CHECK 2230 - Check that the object is intended to be outside of the model domain (and therefore skipping is ok).
| Up |
|---|
 2xxx Messages
|