I have used the 'Edit Terrain Model' command 'Delete Edge Triangles' to clean up my triangles which changes the shape of my perimeter. If I 'Reactivate Survey Processing Rules' I'll lose my edits and the perimiter will redraw to the original extents. So I want to save the edited perimiter as a linear feature in Survey with a Boundary feature type. The method I'm trying to use is to right mouse click over 'ALL Linear Features' and select 'Add Graphic Linear Feature'. The problem I'm having is when I'm prompted to identify element I get the message "Zero length element not allowed".
If you export out the clean terrain model and open it in the old SS2 explorer menu you can then use the old SS2 explorer to view the perimeter and add that as your boundary. Let me know if that makes any sense.
This makes sense but we're trying to develop workflows for our office that doesn't use any of the legacy inroads files. I anticipate our office going this route at some point in the future and I'm just making sure all of our current workflow can be apapted to Open Roads.
For PowerGEOPAK, here's what I've put together as a workflow recommendation for our users, based partially on work in this and related forums. I don't know if something similar would make sense for InROADS, as I don't use it.
RECOMMENDATIONS
Note that saving a clip boundary using the method outlined here will ONLY preserve your triangle edits along the boundary of the project. No internal edits will be preserved. Our suggestion is to NEVER edit the internal triangle structure; rather, you should edit the source data to fix any issues, so that the triangles reflect your intent.
Don't forget that one of the best advances in SS3 terrain modeling is that ALL functions can be undone. If you do something and your triangle edits revert, stop, take a breath, and UNDO. Now take time to think about what you need to do, and prevent the problem if possible.
(Note- I posted this previously here: https://communities.bentley.com/products/road___site_design/f/5922/t/98064.aspx)
Answer Verified By: Corey Baird
I should probably just have reposted the items listed under "item 6", rather than this whole process.
Thank you Frank. This is what I was trying to accomplish. Have you ever had a problem with the boundary becoming corrupted when you File Fence to a new DGN. I'm experiancing the problem with the boundary shown in the two screen captures below.
I've probably seen something like this, but not necessarily due to a file fence operation. (Unfortunately, we've all seen more than our fair share of corrupt Microstation elements!) I'm guessing the boundary was corrupt before you exported it. Try doing a reference merge of just that boundary line into a clean file. Perhaps you can find - or eliminate - the corruption that way. It has worked for me in the past, for various types of corruption. If that doesn't work, try using a tool that forces the line to be redrawn, such as "change curve direction" or something similar.
Frank Boston
Michigan Dept of Transportation
Survey Support
Not quite sure of your workflow... but watch the minute long video for perhaps an easy more efficient way to get the boundary.
HTH
Michael Barkasi
Application Engineer
Reality Modeling
Also wanted to add if its desirable to have a shape. The horizontal offset boundary line can be copied (becoming a "Line String") then selected and made into a complex shape.