Why is the profile workflow so difficult!
I would like to know how to add profile boundaries to accommodate tall profiles to "Stair-step" the profile view on sheets. I know ORD can help with that when placing Named Boundaries for Profile views, but that only takes the active profile into account when deciding how to split and offset a sheet's profile boundaries. I can modify a profile Named Boundary's elevation prior to drawing/sheet model creation, but I also would like the ability to change the horizontal size and location. Is it possible to add or modify boundaries after the fact?
The image attached shows the original Named Boundaries in grey. I would like to modify the first one and add a second one to look like the yellow shapes. The cyan lines represents the limits of one particular plan/profile sheet. The original boundaries were created to align with a group of plan view Named Boundaries.
I assume I can still manually accomplish this by careful use of reference files, but it would seem like something I should be able to do at the time of Named Boundary placement so that I don't have to manually do it. Better yet - let me insert a named boundary later if I need to show more relief. If necessary my workaround is to make one large drawing model of the entire profile and manually reference it (multiple attachments) into each sheet's profile drawing model to achieve the stair-stepping I would like.
I came across this thread now as I have the same question. Basically I would like to split my profile into more named boundaries than what the automatic profile named boundary generator has done. This is because the profile named boundary generator does not take into account the terrain when splitting the boundaries. Has anyone figured out a useful workflow for this yet?
Rick,
There should be a toggle on the bottom of the Place Named Boundary (Profile Mode) dialog called "Use Terrains" that will allow ORD to consider the Terrain locations for splitting the boundaries.
It was on but I did not have my terrain set as active, so it did not pick it up. Thanks Joe!
Glad you got it figured out!