Corridor clipping isn't functioning

Hello,

I've run in to an inconsistent issue where a part of a corridor doesn't get clipped sometimes. The brown part is grading for ditches and similar thing sometimes happens with upper layers overlaying a civil cell for intersection.

Parents
  • You may have selected the 3D terrain for the "clipping element".  I would recommend creating a separate 2D clipping shape separate from the corridors.  In some cases, I'll use the terrain of a surface template driven sideroad (terrain boundary element shape), but typically don't try to clip one corridor from another to dodge potential unnecessary processing in the file.  If you want the 2D clip shape to be dynamic off the changing corridor design, simply utilize CivilAccudraw or generate the shape from ruled elements of that intersecting corridor.  

    ORD 2021 R1 (10.10), 2022 R1 (10.11.00.115), 2022 R3 (10.12.02.04) | MS 10.16

     Bentley Accredited Road Designer Bentley Accredited Road Modeler

     

      colliersengineering.com 

    Answer Verified By: Reinis Labans 

  • This seems to have been the issue. Selecting the elements on the 2D plane clipped everything correctly. Thank you!

  • I very strongly preach to my users that they should never reference 2D to 3D. Our state has many areas with less than 100' of elevation and 2D elements are often drawn too close to the 3D generated graphics resulting in more confusion as opposed to clarity. Let the 3D stand on its own and trust the 2D to locate it correctly horizontally.

    We do have some mountains, but a workflow that needs specific geographic location limits is not a productive workflow. If you learn to depend upon it and then are working where it's a hinderance instead of a help, you now have no practical experience on how to get the project completed without that capability. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • It's so good to hear others preach this as well. Every training or chance I get, I like to say "with a select few exceptions, work in 2D and let ORD do all of the 3D work for you. Why make it harder on yourself?" I echo your thoughts about flat terrain too, considering most of Florida is dead flat and we have very low elevations as well.  

    Eddie Giese, PE
    Production Manager | Senior Roadway Engineer | Associate
    Licensed in FL & PA
    ACEC FDOTConnect Instructor on behalf of FDOT

    Patel, Greene & Associates, LLC
    PowerGEOPAK V8i SS10 (08.11.09.918)
    OpenRoads Designer 2022 R3 (10.12.2.4)
    ProjectWise Explorer CE 10.0.3.453

    OpenRoads Conceptstation CONNECT Edition (10.0.16.84)
    LumenRT Pro CONNECT Edition (16.17.60.73)

    premier-scholar-badge road-designer-badge

  • Totally agree!  Outside of using the stamp tool for illustration purposes (worked well in the past for stamping quick pav markings on 3D for LumenRT), there's really no need for Bentley to have the functionality of 2D references in a 3D model space.  Maybe there's a config var to restrict the functionality since most of our work is design based.  At least a more invasive prompt stating you're attaching a non-3D file to a 3D view.  Knowing Microstation covers so many disciplines, I can see why this would be a software engineering quirk we'll have to live with!  The list of "What Not to Do's" is ever expanding ;D 

    ORD 2021 R1 (10.10), 2022 R1 (10.11.00.115), 2022 R3 (10.12.02.04) | MS 10.16

     Bentley Accredited Road Designer Bentley Accredited Road Modeler

     

      colliersengineering.com 

  • I've had a lot of debates about this with our OpenBridge team - they use a 3d only seed and it is horrible when ORD 2d-3d data comes in. This is despite the fact that OBM works perfectly with the same 2d-3d workflows as ORD, but "apparently" OpenBridge was not designed to work this way...

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

  • I'm new to ORD and this is just a thing I'ļl have to live with until I'm done with the current design which consists of about 50 different smaller roads and different sizes and types in decent progress already. And the design is specifically to deliver IFC models with specific requests with signs and other road furniture. So having 3d in hands reach helps the speed a lot. It's a journey and a half so totally gonna note that 2D away from 3D is a must. I appreciate the help.

Reply
  • I'm new to ORD and this is just a thing I'ļl have to live with until I'm done with the current design which consists of about 50 different smaller roads and different sizes and types in decent progress already. And the design is specifically to deliver IFC models with specific requests with signs and other road furniture. So having 3d in hands reach helps the speed a lot. It's a journey and a half so totally gonna note that 2D away from 3D is a must. I appreciate the help.

Children
No Data