We populated the downstream values using a normal depth of 0.001 as a very rough approximation, but it doesn't resolve the problem of the lack of junctions. Finally the 'HecRAS Steady Flow Editor' screenshot shows the Steady Flow Boundary Conditions window. The 'HecRAS Junction Overlap' screenshot shows the overlap we created by using the 'Move Object' tool in geometric data editor. The HecRAS full catchment screenshot shows the geometric data editor for the full catchment if that provides any clues. We have tried deleting the other fields and recreating everything using the Stream Centreline Attributes tool in the RAS Geometry menu, but it hasn't helped. The 'Ba River Attribute Table' screenshot shows the unpopulated FromStation field. The 'Ba Junction Vertex Snapping' screenshot shows the vertex of the river layer line snapping to the junction using the vertex snapping feature (this was done throughout the catchment). The two upper tributaries ('Ba Junction Upper East' and 'Ba Junction Upper West') both show ToNode=5 and the lower reach ('Ba Junction Lower') shows FromNode=5 so it seems to have correctly identified the junction node. I have zoomed into one of the junctions and taken three separate screenshots showing the attributes of each of the three tributaries. The end of the stage data is identified by the HEC-DSS missing. The catchment we are working with is quite large (The Ba River in Fiji) and has a number of tributaries (see the attached screenshot 'Ba Catchment full'). The upstream stage and flow hydrograph is a mixed boundary condition where the stage hydrograph is inserted as the upstream boundary until the stage hydrograph runs out of data at this point the program automatically switches to using the flow hydrograph as the boundary condition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |