<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/101920/does-use-of-native-ddb-vs-element-templates-for-feature-definitions-affect-processing-time</link><description>As I get set up for SS3 I am wondering if linking to the ddb means that there will always be some processing time to &amp;quot;go find&amp;quot; the information in the ddb when trying to apply a feature definition to my graphics. Is the time required for that greater than</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303240?ContentTypeID=1</link><pubDate>Fri, 17 Oct 2014 17:41:39 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c057f15d-dca2-490d-9490-27d70d8231cf</guid><dc:creator>Nico Roman</dc:creator><description>I am sorry but I was wrong. &lt;br /&gt;
They are not “imported” into the file – they are linked to the DDB. Which means that whenever you use a feature such as “Centerline”, if it’s pointing to a DDB item, it must go to the DDB to get all the information (level, color, etc.).&lt;br /&gt;
&lt;br /&gt;
The thing to do though is ONLY use DDB features for items that need stationing. Everything else use element templates.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303230?ContentTypeID=1</link><pubDate>Fri, 17 Oct 2014 16:57:12 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:5292899a-0c3a-41b9-bb7f-778eba1f22c1</guid><dc:creator>Katie Johnson</dc:creator><description>Thanks, Sean, this is the sense I had, but I haven&amp;#39;t really worked in SS3 enough times to see if it was consistent or not.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303212?ContentTypeID=1</link><pubDate>Fri, 17 Oct 2014 15:48:32 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:750836b6-d1a6-42bc-bff2-15712ca3b710</guid><dc:creator>Sean Keene</dc:creator><description>Katie,&lt;br /&gt;
&lt;br /&gt;
We have found that it does take more time to process when you link a dgnlib to an existing ddb for feature definitions.  Each time you need to assign a feature definition the program reads the entire ddb, but once the feature definition is assigned then it stays in the current dgn.  It depends on how large the ddb is for the time frame.  We have a few clients that have large ddb&amp;#39;s and we can see a significant increase in time when trying to assign feature definitions.  This increase in time is practically gone when we use element templates.&lt;br /&gt;
&lt;br /&gt;
Sean&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303054?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2014 17:55:27 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:da69598c-24b7-4eeb-9ec5-49c8439a48ba</guid><dc:creator>Katie Johnson</dc:creator><description>Thanks!&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303050?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2014 17:46:35 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c89ab31e-fc63-4336-98df-83a9e3b161d0</guid><dc:creator>Nico Roman</dc:creator><description>yes. they features will be in your dgnlib. you can just send the dgnlib to your client with the dgn.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303048?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2014 17:31:07 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:6faef856-e6ce-44a9-94be-30fe3070874b</guid><dc:creator>Katie Johnson</dc:creator><description>So once linked those definitions reside in the dgnlib where I linked them? (and later they get imported and held into the dgn file where they were used)? &lt;br /&gt;
If I need to transfer files - between my office and my client for example - then do I need to worry about whether a compatible ddb gets found (as far as the feature definitions go)?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does use of native ddb vs. element templates for feature definitions affect processing time?</title><link>https://communities.bentley.com/thread/303046?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2014 17:24:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:7ddd4784-69aa-4db0-8ed3-a475756828e5</guid><dc:creator>Nico Roman</dc:creator><description>No. it imports the ddb items, it should not affect speed.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>