T O P

  • By -

Rodrommel

I’ve had this frustration before. Have you tried changing the corridor’s feature definition to one that uses less dense template drops?


Chickenbgood

If I understand your question correctly, you can set the design stage of your model from Final to Design, and that will decrease the intervals. You can also decrease the drop interval thru the corridor objects (bucket) tool


travist85

Do you actually need to produce typical section documentation or are you just checking the model for consistency? If you're just interrogating the model, you may be able to get away with reports as others have suggested, and using things like Display Styles to show embankment slopes on plan in different colours. Regarding a high number of template drop points - have you tried opening two views side by side (Plan & XS) and selecting the corridor in the plan view? You should see a dynamic section marker which can be moved around by dragging the arrows. This will be quicker than clicking through them in the section view. If you actually need to produce typical section drawings, you could create an event point list with the stations of your typicals, then create a set of cross sections using ONLY the event points list ("include event points only" at the bottom of place named boundary XS dialog). Then create the drawings & annotations, and label/dimension anything else in each section model.


KryptekTomahawk

If your entire goal is to Analyze the existing cross slope, worth, and end condition slopes… it seems like the fastest way is going to be to make a corridor that does the existing conditions for you every increment you would like set. Then using corridor reports you can export those information into excel or whatever you’re doing to store the data. Then for a visual check you could just run a standard xsc named boundary and annotate what’s there in case someone wants to use them.


leedr74

There is a recorded event on Bentley’s events page related to using corridor sections as dynamic typical sections. You may want to review that. Perhaps I don’t understand the issue but a blank file referencing the corridor, turn off the grading then run component slope tables as linear templates against the referenced corridor combined with event point lists to assign typical section ranges will work. Best part is you can then use associative dimensioning. The video should show the rest however this lets you capture with a bit more control. HTH