In testing, I learned a few things worth sharing.
For a feature to export as an element Template, it must be defined as follows:
It was this last two that I found tricky. When I first started using Roadway Designer, I defined 2 types of components - surface and volumetric. I defined the surface components to plot in 3D/Plan, but only defined the volumetric components to display in cross section. For grading - the same component was used for cross sections and 3D/Plan display. But for any item with volume, I defined, in my templates, dual components. The closed shape components were the volumetric elements which I only expected to use in cross section. But along the "top surface" segments of these closed shape components were open components that could be displayed in 3D/Plan as meshes for rendering.
When I attempted to export these to an element template XML file, those with no default or plan display did not export.
This does bring to mind a few questions, so I am turning this into a question thread.
Is there any way, once we fully migrate to OpenRoads, to have levels for 3d/Plan display that are different than cross section display, as we could do in InRoads?
Does the current cross section tool use the defined Named Symbologies and therefore still support different cross section symbology, if defined as such?
Where is the Export XIN to Element Template tool. Somewhere under the tools menu?
At this time the cross sections do appear to use the symbology from the XIN file. It seems the ability to assign levels for 3D Plan v.s. Cross Section symbolgoy may be a difficult one. The plan seems to be to have 3D solid and mesh elements display as true dynamic cross sections reflecting elements in the 3D model as is. There has been some discussions regarding the ability to project objects such as Manholes and Pipes this also seems to be a challenge being looked at for future releases.
Mike LongstreetVermont Agency of TransportationCivil Engineering Technical SupportVTCAD Help
Guys, Joe Waxmonsky prepared a video I will attach that shows how you can get information from an XIN file to an Element Template DGNLib.
Let me ask a follow-up to my original post: What is the best way to make the Element Templates visible in MicroStation with OpenRoads?
I created a DGNLIB for the purpose of linking the native XIN file - Roads and Surveys and decided that this was also the most logical location for the imported element templates.
Is there a Civil variable that I should use or should I just use MS_DGNLIBLIST?
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Take a look at how I did this in the Bentley Civil Examples workspace PCF file. That should help.
Update: The requirement that 3D/Plan Line Display be enabled for a Feature Style to export as a component appears to have been lifted.
It is still a requirement that the Named Symbology must have a Default Line or Plan Line symbology defined. If you only defined Cross Section Lines, the component feature is exclude from the export.