ORD Feature Definition Hierarchy

Question

Here is a handy diagram I created to illustrate to myself some of the relationships in the OpenRoads Designer Feature Definition setup:

Benzi Papo · Accepted Answer

Here is my method to bulk import the above mentioned into a DGNLIB file: 
 
 Feature Definitions 
 1. Import Levels/Filters from CSV file. 
 2. Import Element Templates from XML file. Make sure all Levels used by these Templates have been created in step 1. 
 3. Import Feature Symbologies from XML file. Make sure all Templates used by these Symbologies have been created in step 2. If a Symbology points to an Annotation Group that group must already exist. 
 4. Import Feature Definitions from XML file. Make sure all Symbologies used by these Features have been created in step 3 . 
 
 Steps 3 and 4 may require closing and opening the Explorer to reflect the changes (small bug). 
 
 Annotation Groups 
 Annotation groups and definitions do not have a bulk import feature but can be imported in two manners: 
 1. Copy one or more annotation groups or definitions using Project Explorer. Copying a group does not copy its contained definitions. 
 2. Create a new entry for the Annotation Group using Project Explorer. Right-click "Manage" then click the import icon to load an XML file. This method creates both the group and definitions. 
 The second method is more robust and flexible. With the first method I found that If the same Annotation Definition is used by several Annotation Groups then any change to that definition affects all groups that use that definition. The only way around this is to duplicate the mentioned definition. If you create a new Annotation Group using the import XML method then all works as expected. This is because the Annotation Manager will create duplicate definitions if needed during the import.

ORD Feature Definition Hierarchy

Top Replies