Welcome to the RAS Solution Forums HEC-RAS Help Geo-RAS XS lengths incorrect

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #5801
    Anonymous
    Guest

    I am setting up a model using GeoRAS and the 3D cut lines generated by GeoRAS do not match the stationing of my 2D cross sections. For example, my initial cross section in the XS Cut Lines layer is 500 feet long and the 3D cut line generated is 510 feet long. This creates a slight stretching of the cross section. If I zoom in closely to the cross sections, the 3D cross section zigzags back and forth some where the original cross section is straight.

    Has anyone experienced this and found a solution?

    #9323
    user
    Participant

    In my case , my cross sections always turn out straight or based on the cutline I drawn on DEM. The only time my cross section zigzag is when I deal with data points from field survey . Sometimes my exported cross section doesn’t turn up in the correct position , so I have to adjust them through XS cut line table .

    #9324
    Anonymous
    Guest

    I am using an ArcGIS tin and it does look like the xs may be zigzagging to points. Have you found a way to straighten out the section so the length isn’t artificially extended? I have so many cross sections it would take quite a long time to do it by hand.

    #9325
    Anonymous
    Guest

    I did figure out a solution to this problem for anyone who comes across it in the future. The default resolution size for the feature dataset generated by GeoRAS was 1 unit (1 foot in my case). This meant that the 3D cut lines were forced to fit a 1′ grid and had to zigzag along the XS lines I had drawn. I created a new geodatabase and feature dataset with a much lower resolution size (.003′ in the xy directions). After setting this new geodatabase as the target location for GeoRAS I was able to regenerate 3D cut lines that matched my initial cross sections very closely. Hope this helps someone in the future!

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.