Creation of the drawing Model is Optional in sheet production in MicroStation. I believe this should be true for civil Plan as well. We should be able to create a drawing seed that does not have the option ON for creating drawing.
Most of the Plan Sheets that we cut today do not need the extra overhead of drawing models. This would not be the case for cross sections or profiles.
| Civil Product Used | OpenSite Designer, OpenRoads Designer, OpenRail Designer, OpenTunnel Designer, OpenBridge Designer, OpenBridge Modeler |
We have several pressing features that we must implement first, and we do not want to divert resources away from those efforts.
While we appreciate your request, we need to prioritize the features that will have the most significant impact on our users. Therefore, we cannot commit to implementing this feature unless there is enough user support to justify the cost and effort required.
Thank you for your understanding and support.
It also allows us to add some automatic annotations to the model like north arrows and match lines. It is best practice to not put those in the Sheet model.
1
Future consideration
I'd also like the option to Create Drawing Models "Without Creating Sheets" Specifically when creating Profiles. Many times we have a drawing sheet already created, but then later on in the process, it gets decided to add a Profile to the existing sheet. Currently, when you create a Civil Profile Named Boundary, the software generates the profile model, "and also" a Sheet model. However, in many cases, the sheet model is not needed. We just simply reference the Profile Model to the existing sheet, so then we always need to delete the newly generated sheet model every time.
Note: when creating Named Boundary From "2 points" there does seem to be an option to "Not Create Sheet Model" (by unticking the box) however, Named Boundary from 2 points Does Not Work for Civil Profiles. Perhaps the easy fix, is to just allow this to function with Profiles as well.
Just to comment, our process is that we manually define our plan saved views to generate the drawing models, not using the automated plan sheet generator. But we generate the drawing model into the DGN with the sheet model, to reduce the number of DGN files total. This also makes it easier to switch between the sheet model and drawing model for edits as it is just a model switch not a DGN open. Occasionally we will create a single drawing model of the overall project for project-wide annotations, etc., the define the sheet saved views there.
This is also the same file structure created by creating cross sections to single sheet DGN files. One sheet model and all of the XS drawing models that are displayed in that sheet.
Thank you, I get that you may not see the benefit or prioritize it highly. This particular "idea" was proposed internally to Bentley's prior system years back.
I was under the impression that the intent of this "ideas" page is to propose ideas so users can vote on what is important to them to improve the software.
Sorry, but I do not understand why it is so costly. It seems to me that having Civil override the operation of platform leads to code bloat and is more costly and problematic in the long run.