• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 141 subscribers
  • Views 3187 views
  • Users 0 members are here

Civil Cell will not tie down

Matt Hay
Offline

I am attempting to place some civil cells in a design file and am running into errors.  In the plan view  (top down) everything looks correct, but in isometric views, the civil cell is always attached to the surrounding terrain or template drops.  the civil cells work in about half of the applications, but the other half  show large spikes of surface from the civil cell a hundred or more feet tall (one was about 107,000' tall) above or below the surrounding area.

The same civil cell for all FOUR intersections between proposed sidewalk (in pink) and the existing drives.  In this picture, the civil cell works for the intersections moving from bottom right to top left, but they fail to insert properly headed the other direction.  (NOTE: there are several other locations throughout the file where both directions inserted completely correctly in both directions. There are also areas where the civil cell spikes extend well below the surrounding terrain.)

My query is in reference to the cause of this error.  What are some reasons that only some of these civil cells fail?  Is there an issue with the civil cell?  The civil cell design library? Could it be a problem with the template drops around the civil cells?  Could the issue be with the survey file (Am I attempting to tie to ridiculous terrains in the sky?)?

Any and all help is appreciated;  Thank you for your time.

  • 0 Offline

    What is the exact product and version you are using?  There has been a focus on civil cell issues as new updates are released so it would be good to know the version of the product.  One of the first things we suggest for civil cell issues is upgrading to the latest build (currently 08.11.09.878), so you can delete and replace the civil cells to see if it was an issue with how cells were ruled or constructed.

    Can you explain how the verticals/profile for the returns were defined in the civil cell?  Are you applying a template so an end condition can target a terrain to tie the returns to the sidewalk terrain/corridor?  What I notice is how this lower right section appears to have a near vertical face in the edge but it is successfully intercepting the sidewalk.  Then for the opposite return in that civil cell, it has an issue with the profile and how that is defined or set to target something (direction in which the reference element is created?).   So I didn't know if this was some sort of taper section to slope down to the sidewalk. The profile or an applied end condition slope seems to be the issue so that is definitely where you should focus.  Have you tried to rebuild that return element in the civil cell on the side which doesn't solve correctly? 


    For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki

  • 0 Offline in reply to Chris Key
    I'm going to list my responses to keep things as organized as I can...
    1: I am currently using Version 08.11.09.832, and I will have to continue to use it until my company and Bentley can come to some agreement with the way our licensing is distributed.
    2: (I'll do my best to explain this, but if it's confusing - please let me know)
    First - a basic intersection civil cell is placed for the driveway, tied to existing terrain, as the project does not call for any work to be done to the actual drives/side streets.
    Second - the sidewalk/multi-use path ADA compliant ramp civil cells are input. The walk parts of the civil cell are constrained to the sides of the walk as input by the template drop for the multi-use path. The civil cell is set up to allow for a maximum 1' vertical change over a set distance (in accordance with ADA compliance regulations). The end of the path where it intersects with the drive is tied to the edge of pavement of the drive. This should allow for the walk to raise or lower from the proposed profile to the existing pavement elevation across the driveway.
    Third (not completed in the photo) - the terrain models/template drops are clipped to show only the final design. (ie. - the template drop will be clipped by the driveway civil cell boundaries, and both the driveway linear templates for tie downs and the template drops along the length of the path are clipped by the ADA ramp civil cells - hopefully yielding a continuous, smooth multi-use path for the full length of the project. (*the near vertical face that the smaller arrow you drew is are a result of not clipping the design and the angle at which the image is presented.)

    I have rebuilt the cells multiple times over the span of a week, making slight modifications to how the cells are built each time they are recreated. There is only one hard-coded number in the entire civil cell, and that is the length over which the vertical change is to occur. I checked ahead of placing the cell that each instance has a vertical change less than 1', so the cell should function as designed.

    I have the cells built currently in the civil cell dgnlib so that the intersection occurs in the same orientation as the placements that are experiencing issues. This is the most confusing part to me, because the cells placed where the direction is contrary to the base civil cell design are the ones that show up correctly most often.
Communities
Support and Services
Training and Learning
Social Media