Profile Named Boundary from Plan with Overlap

Adam,

No overlap in Profiles unless you create each named boundary one at a time. 

FYI, In ORD if the sheet limits ever change you will have to recreate the profiles. We have started creating a large profile grid for the complete alignment and cut sheets from that just using a reference clip.  This way you can adjust the sheets plus you will only have one profile to manage and annotate instead of 60.

Hi Zane, I have an app in the premier scholar forum that "rewrites" the bounds of named boundaries so they don't need to be recreated. I might put it in a post for the general forum.

Mark - Please share it with us if you can.  Your help is greatly appreciated! 

Thanks Mark,  I will check it out.  This is the major issue we have with named boundaries.  We can't adjust them once they are created, especially profiles.  Does this macro work if the drawing models and sheets are in a different file then the named boundaries?

Reposted from the Premier Scholars forum:

Hi all,

One thing that is driving us crazy right now is the static nature of Named Boundaries and the need to often recreate them (and associated Drawings/Sheets) when we need to edit the station or elevation ranges of Named Boundaries of Profiles, changing offsets of Cross Section Named Boundaries, or more generally make graphical edits to the Named Boundary. This almost always results in the Annotation tools not "seeing" the manual graphical edits to the Named Boundary shapes and/or issues like Drawing model references becoming misaligned, etc.

To workaround this I have developed some tools to "resync" the invisible Named Boundary elements behind the scenes with the graphical Boundary Shapes after a manual edit. More specifically:

• Updates the "invisible" Named Boundary objects behind the scenes to match the graphical shape extents after you make an edit.
• For Profile Named Boundaries, cycles through Drawing models and moves the Profile reference to the updated datum location (if the Named Boundary bottom elevation has changed).
• For Cross Section Named Boundaries, cycles through Drawing models and moves the XS reference to the updated origin location (if the Named Boundary offsets have changed).

Add-in v1.11 download link:

https://www.dropbox.com/scl/fo/1waqd2dv8yyn2jtn77xwg/h?dl=0&rlkey=p94r1utihd2sh56qjj7hbf6q9

Please give it a try - happy for any feedback and suggestions. Couldn't keep this to myself ;)

To run:

1. Download Add-in DLL file and save in C:\Program Files\Bentley\OpenRoads Designer CE 10.11\OpenRoadsDesigner\Mdlapps\ (or another mdlapp folder you have in your workspace MS_MDLAPPS variable)
2. Load app by running the keyin: MDL LOAD ARCADISCUSTOMORD2
3. Profile Named Boundary Commands can be run using the keyins:
   • To sync Profile Named Boundary edits: ARCADISCUSTOM PROFILETOOLS SYNCNAMEDBOUNDARYEDITS
   • To sync Profile Drawing References: ARCADISCUSTOM PROFILETOOLS SYNCDRAWINGMODELDATUMS
   • To run both commands above: ARCADISCUSTOM PROFILETOOLS SYNCALLCHANGES
4. Cross Section Named Boundary Commands can be run using the keyins 
   • To sync XS Named Boundary edits: ARCADISCUSTOM XSTOOLS SYNCNAMEDBOUNDARYEDITS
   • To sync XS Drawing References: ARCADISCUSTOM XSTOOLS SYNCDRAWINGMODELEXTENTS
   • To run both commands above: ARCADISCUSTOM XSTOOLS SYNCALLCHANGES

Notes:

• Naturally Sheet model references may require tweaking after Named Boundary adjustment, but this is something i'll see if can be included.
• Developed using libraries for ORD 10.11 (2022 Release 1) - untested on earlier releases
• Untested for workflows where Named Boundaries and associated Drawing models are in different DGN files
• Developed using Metric units - let me know if there are any issues with data using Imperial units

should do, ive just added that post here.

All the tool really does is edit the invisible Named Boundary object properties to reflect a change in the Named Boundary graphical element. The current implementation looks to have the these only synced during Named Boundary creation and there are no dynamics after that. This tool rewrites the latest Graphical changes to the Named Boundary object so that the annotation tool knows its new extents.

should do, ive just added that post here.

All the tool really does is edit the invisible Named Boundary object properties to reflect a change in the Named Boundary graphical element. The current implementation looks to have the these only synced during Named Boundary creation and there are no dynamics after that. This tool rewrites the latest Graphical changes to the Named Boundary object so that the annotation tool knows its new extents.

Wow Mark! thank you so much for making and sharing this app with us!  I have been saying from the begining of ORD that we needed this tools and you made it... thanks a lot!  Bentley should definately pay you (and/or your company) for thoses tools.

haha this was the product of desperation of delivery. Its amazing what you do to avoid hours of rework! 

Hey I have try to load the DLL and got this message: 

'ARCADISCUSTOMORD2' could not be loaded because 'ARCADISCUSTOMORD2' does not have an authorized digital signature.

Is there something I could do on my side for this?

Ok got it to works, thank you!!!!

what did you do differently this time to make it work?  I also had the same message.  Thanks.