Hej
I am looking for best practice to deliver 3D CAD files (dgn) to our Client. We do not want to deliver native files with corridors definitions, as there are to many relationships, references, etc. We would like to deliver just the Default-3D model. The problem is that exporting just this Default-3D model will strip OpenRoads Civil Specific Data (Feature Name, Feature Definition, Start/Stop Stations, etc). Same with Copy Fence to File command or merging Default-3D to an external 3D file.
The solution would be to create imodel where the Civil Business Data is retained but unfortunately linear features that has originally gaps in the native model, once exported these gaps are being healed/closed with a linear segment with no vertexes.
I would appreciate any piece of advice.
Adam\\
ORD 2019 R2
Hi Adam,
As far as I know, exporting the 3d model only will have the civil data stripped but elements will retain the same Element ID, so how about using Asset Manager to add Item Types of all the data you need, ie. Feature info, stations, etc. to your 3d Civil elements and then use the Item Type Export Instances tool to export the Item Types out. This will store the Item Type data with the related Element ID.
You could then export your 3d model out to a 3d CAD DGN and use the Item Type import tool to Import Instances. If all goes to plan, the same Item Type data it had before being "uncivililised" will be reattached.
I haven't tested this workflow, but should work well in theory.
Regards,
Mark
OpenRoads Designer 2023 | Microstation 2023.1 | ProjectWise 2023
Answer Verified By: Adam Wieczorek
Also, from what I hear, attributed IFCs MAY be coming in the not too distant future so we will potentially have some more options to deliver business data....
My first thought is: What's wrong with delivery of the same DGN deck used by the designer. I'm sure that no offence was intended, but there is a note of mistrust in the very question asked. It almost sounds like "My designers and I are smart enough to deal with the complexity of this design but the rest of you are not, so I'll dumb it down for you."
By delivering exactly what was designed then the downstream consumers of the model have exactly what you designed. Any other mechanism for delivery of the model will make a variety of compromises which diminish the data.
Of course, for any given purpose, the recipient may request or demand a certain deliverable, which is a whole different issue. If I must meet demands of deliverable (we all do) is one thing and will vary by recipient. Unilaterally (as a designer) devising a standard of delivery from myself to all others really only serves to create more work for me, for which I am likely not getting paid. Lacking a deliverable requirement by client or stakeholder, I will just deliver the DGN stack, which gives the recipient complete freedom to slice and dice it in any way they choose.
Robert Garrett Senior Consultant
www.envisioncad.com
Robert:
By "dgn stack", I am assuming that you are speaking of all dgn deliverables; that is, dgn files and associated references only, or are you speaking of all dgnlibs, rsc's, cels as well?
If you use the quantity report by named boundary command and allow clipped graphics the command will copy in all liners and components from your 3d model in to a new file AND maintain the feature definitions and names.