Difference between revisions of "TUFLOW Message 1033"

From Tuflow
Jump to navigation Jump to search
Line 4: Line 4:
 
|type=[[ERROR]]
 
|type=[[ERROR]]
 
|message_desc=Cross-Sectional data for the channel named "XXXX" cannot be found.  
 
|message_desc=Cross-Sectional data for the channel named "XXXX" cannot be found.  
|suggestions=Each channel requires a table describing its hydraulic properties to define its conveyance.  The properties are normally defined by digitising a cross-section in a 1d_tab layer positioned midway along the channel or at the channel ends. If the cross-section is applied at channel ends, the cross-section lines must have a vertex snapped to the channel end. If the digitised cross section has more than two vertices, one must be snapped onto the 1D network. The 1d_tab layer references an external csv file (or similar formatted file) containing either a cross-section profile or a hydraulic properties table. The hydraulic properties can also be externally sourced from a Mike 11 or ISIS model. Note that structures such as culverts and weirs, are an exception to the rule. The attribute information supplied within the 1d_nwk table are sufficient to define the hydraulic properties. <br>
+
|suggestions=Each channel requires a table describing its hydraulic properties to define its conveyance.  The properties are normally defined by digitising a cross-section in a 1d_tab layer positioned midway along the channel or at the channel ends. If the cross-section is applied at channel ends, the cross-section lines must have a mid-vertex snapped to the channel end. If the digitised cross section has more than two vertices, one must be snapped onto the 1D network. The 1d_tab layer references an external csv file (or similar formatted file) containing either a cross-section profile or a hydraulic properties table. The hydraulic properties can also be externally sourced from a Mike 11 or ISIS model. Note that structures such as culverts and weirs, are an exception to the rule. The attribute information supplied within the 1d_nwk table are sufficient to define the hydraulic properties. <br>
 
<br>
 
<br>
 
Refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for more information. For detailed instructions on setting up the 1d_nwk and 1d_tab layers, refer to <u>[[Tutorial_M11 | Module 11]]</u> of the Tutorial model. <br>
 
Refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for more information. For detailed instructions on setting up the 1d_nwk and 1d_tab layers, refer to <u>[[Tutorial_M11 | Module 11]]</u> of the Tutorial model. <br>

Revision as of 21:20, 2 December 2024

TUFLOW Message
ERROR 1033 - No XS line data downstream of channel "XXXX". Could not interpolate cross-section properties.

Alternate Message
ERROR 1033 - No XS line data upstream of channel "XXXX". Could not interpolate cross-section properties.

Message Type
ERROR

Description
Cross-Sectional data for the channel named "XXXX" cannot be found.

Suggestions
Each channel requires a table describing its hydraulic properties to define its conveyance. The properties are normally defined by digitising a cross-section in a 1d_tab layer positioned midway along the channel or at the channel ends. If the cross-section is applied at channel ends, the cross-section lines must have a mid-vertex snapped to the channel end. If the digitised cross section has more than two vertices, one must be snapped onto the 1D network. The 1d_tab layer references an external csv file (or similar formatted file) containing either a cross-section profile or a hydraulic properties table. The hydraulic properties can also be externally sourced from a Mike 11 or ISIS model. Note that structures such as culverts and weirs, are an exception to the rule. The attribute information supplied within the 1d_nwk table are sufficient to define the hydraulic properties.

Refer to the TUFLOW Manual for more information. For detailed instructions on setting up the 1d_nwk and 1d_tab layers, refer to Module 11 of the Tutorial model.


Up
Go-up.png 1xxx Messages