Difference between revisions of "TUFLOW Message 1033"
(Created page with '{{TUFLOW_Message |tuflow_message=ERROR 1033 - No XS line data downstream of channel ",a,". Could not interpolate cross-section properties. |alt_msg=ERROR 1033 - No XS line data ...') |
|||
| (10 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
| − | |tuflow_message=ERROR 1033 - No XS line data downstream of channel " | + | |tuflow_message=ERROR 1033 - No XS line data downstream of channel "XXXX". Could not interpolate cross-section properties. |
| − | |alt_msg=ERROR 1033 - No XS line data upstream of channel " | + | |alt_msg=ERROR 1033 - No XS line data upstream of channel "XXXX". Could not interpolate cross-section properties. |
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc= | + | |message_desc=Cross-Sectional data for the channel named "XXXX" cannot be found. |
| − | |suggestions= | + | |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_xs or 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 cross-section is positioned midway along the channel, it must have either: |
| − | + | * Only two vertices crossing the 1D network. | |
| − | + | * In case of more than two vertices, one must be snapped onto a 1D network vertex. | |
| − | + | The 1d_xs or 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 Flood Modeller. 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> | |
| + | 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> | ||
| + | |||
| + | |||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 09:04, 3 January 2025
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_xs or 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 cross-section is positioned midway along the channel, it must have either:
- Only two vertices crossing the 1D network.
- In case of more than two vertices, one must be snapped onto a 1D network vertex.
The 1d_xs or 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 Flood Modeller. 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 |
|---|
 1xxx Messages
|