Forum Replies Created
-
AuthorPosts
-
jadamsParticipant
Found the solution. I have to import as GIS culverts to not be wormhole 🙁
jadamsParticipantBTW if anyone is interested I determined that if you want to further model scour after a soil layer is theoretically removed, you must manually edit the sections to show the loss of the soil layer.
jadamsParticipantOddly I don’t seem to have the rapid oscillation when I run it on my machine. However I do still have the hydraulic jump after Section 130 for your higher flow profiles.
jadamsParticipantAs a rule cross sections should never touch. By letting them touch you effectively model the same volume twice.
jadamsParticipantTry this. Copy your xml file for backup purposes. Now open the original file with a text editor. Once open delete all the numbers behind the decimal point (including the decimal point) on the spatial extent line.
If this doesn’t work make sure you have no spaces in the geodatabase name or the file path location. I have had this trip up the creation routine before.
jadamsParticipantAre you working on a networked drive? If so that may be causing the error. ArcMap/GeoRAS sometimes has problems creating databases or items on a networked drive.
jadamsParticipantI noticed from your image that it looks like if you mirrored the topographic information the banks would be in the correct locations. You must draw streams in GeoRAS from upstream to downstream AND you must draw cross sections from Left to Right as facing Downstream. I would guess that you may have drawn them the opposite way. If all your sections are this way you can reverse the cross sections in RAS. Do so by left-clicking the section in the geometry editor and say reverse direction. You can graphically see what RAS thinks is the left side of the section by where the label is located, it is generally on the left side. Also you can see: Reverse Sections Link for more information.
jadamsParticipantAs far as I know there isn’t an automated way to edit the station elevation data from the Deck Editor
. If there is I am very interested in knowing how myself. Because of this I still manually tabulate road information in excel and then ctrl+c and ctrl+v it into the editor. jadamsParticipantThere is no image to show the error.
jadamsParticipantBridge “Width” is the width of the bridge deck; i.e. (40ft) while the “Distance” is the length along the stream from the up stream cross section (BU in your diagram) to the upstream edge of the bridge deck.
So as you said RAS knows the distance between Bu and DU. By giving the “Distance” value you tell RAS where the upstream edge of the bridge is. By giving the “Width” value RAS then calculates the downstream edge of the bridge and can thus accurately place it between Bu and DU.
jadamsParticipantMake sure all the fields exported out of Geo-Ras correctly. Make special note of the the downstream lengths and manning’s n values. Sometimes these will not export as anticipated or you may have forgotten the appropriate GIS fields for them to export.
April 7, 2015 at 6:08 pm in reply to: Multiple Reach Unsteady State Analysis- Model Instability #9240jadamsParticipantFor unsteady simulations ensure you have meet the samuel’s equation for section spacing {0.15(depth)/Slope}. This will help with some stability issues. Also this does apply to near your junctions. Often when issues appear near them you may need sections closer in each direction to it to assist with resolving inherent instabilities. Also adjust your timestep by Courant condition {Spacing/V+c} but not less than 5secs or you can take the time of the flood rise / 20.
jadamsParticipantI have received this error when working on a network drive. Try setting the data to export to the hard drive.
jadamsParticipantYou can rewrite the sta-elevation information once they are extracted but it yes it poses a risk of loosing bank stations and horizontal manning’s “n” values if you have them assigned. You can just use the xsec point cleaner to get the section down to the allowable limits of points if you have to.
jadamsParticipantKeep in mind you do not have to have a an XYZ for each station elevation point for the cut lines table. If I am not getting the sections from GIS, I use a similar procedure as you. But since XS lines should have minimal changes in directions you can simply input the vertices for the actual lines. So you could have 90 station-elevation entries and if it was a straight section you could only have 2 entries in the cut lines table.
-
AuthorPosts