Jump to content
TUFLOW Forum

Search the Community

Showing results for tags 'culvert'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About This Forum and Announcements
    • How to Use This Forum
    • Forum Feedback
    • Announcements
  • TUFLOW Modelling
    • 1D/2D Linking
    • 1D Domains
    • 2D/2D Linking
    • 2D/2D Nesting
    • 2D Domains
    • Boundaries
    • Documentation & Tutorial Model
    • Dongles/Licensing/Installation
    • Ideas / Suggestions / New Features
    • Mass Balance/Mass Error
    • MATH Errors & Simulation Failure
    • Restart Files
    • Post-Processing
    • Software/Hardware Requirements
    • Text Files (.tcf, .tgc, .tbc, .ecf)
    • Utilities
    • Miscellaneous
  • Other Software
    • ISIS-TUFLOW
    • MapInfo/Vertical Mapper
    • miTools
    • Other GIS/CAD
    • SMS
    • XP-SWMM2D
    • UltraEdit/Excel
    • TUFLOW Apps

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hi TUFLOW family, I have a question regarding modelling older arch culverts in TUFLOW where the bottom of the culvert contains curved edges (see attached image). For the culvert I'm currently trying to model, when I include the curved sections in the the required HW table, TUFLOW throws the following error: https://wiki.tuflow.com/index.php?title=TUFLOW_Message_1343. To get around this, I made the sides completely straight - and that worked fine, but I'm concerned that the flow through the culvert may now be overestimated. Modelling the culvert this way (as an irregular culverts in a 1d_nwk layer) obviously has constraints when H values don't always increase. Does anyone have a solution to a way around this problem? Given there are a lot of historical 'arch' culverts around Australia, this may be a limitation if the curved sections cannot be modelled.
  2. I am developing several 1D TUFLOW models to simulate existing natural channels and then proposed conditions where a portion of the existing channel becomes replaced with a new box culvert. Both the existing and proposed models have several culverts incorporated into them. In my example, the actual culvert length is 80 feet while the culvert 1d channel segment between cross-sections is 100 feet. The XS lines immediately downstream and upstream of the culverts are slightly beyond the each end of the culvert. In this example, there is a 15’ difference on the left side and a 5’ difference on the right side. The actual culvert lengths were manually entered into the 1d_nwk attribute table; these lengths, however, will not match the channel length between the U/S XS and the D/S XS. Does TUFLOW inherently account for this difference? In other hydraulic modeling programs, you have to specify the distance from the culvert headwall to the adjacent XS – does the same apply for TUFLOW? We want to make sure that TUFLOW is correctly calculating culvert losses based on the true length and that the extra sectional length between the start/end of the culvert and the adjacent XS is being accounted for. If you could provide some insight into how TUFLOW handles this situation and performs calculations that would be appreciated and helpful for us to get a better understanding of the program so we can modify our models if needed. We have several culverts in both the Rag Run and Poorhouse Run models so it is important we clarify this issue. In addition, I am curious as how TUFLOW uses the geographic location of the cross-sections and 1d_network channels. Does TUFLOW use the XS data contained within the CSV files in combination with the specific locations of the XS lines to build the model? Do the channel lengths in the 1d_nwk GIS attribute table have to match the actual length of the stream segment between consecutive cross-section lines? Any help would be greatly appreciated as we are relatively new at using TUFLOW.
×
×
  • Create New...