<?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>Corridor Modeling - Template Defaults to a Construction Layer</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/234819/corridor-modeling---template-defaults-to-a-construction-layer</link><description>All, 
 Was wondering if any of you have ever experienced this. I am in the IDOT (Illinois Dept of Transportation) workspace. 
 As shown below, in my template library, the aggregate is modeled with feature definition. Whilst, in Cross Section Viewer and</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Corridor Modeling - Template Defaults to a Construction Layer</title><link>https://communities.bentley.com/thread/729694?ContentTypeID=1</link><pubDate>Fri, 02 Sep 2022 12:05:40 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c8353eaa-ef49-4b8c-9665-7a5f4d6c165f</guid><dc:creator>Steven Vander Giessen</dc:creator><description>&lt;p&gt;Have you checked the Feature Symbology and Element Template (symbology template; not corridor template) settings for that feature definition? I know nothing about the IDOT workspace but I&amp;#39;m guessing that the workspace DGNLIBs are set up so that feature definition appears on the DNC layer.&lt;/p&gt;
&lt;p&gt;If you&amp;#39;re on ProjectWise with low-level permissions or otherwise unable to modify symbologies on a project-wide scale, you can always modify or create a new one in your active DGN. Sometimes it can be a good idea to create these things in a seed file that you always use personally to create new files so that they have all your special preferences. You could copy that feature definition and make your own - call it &amp;quot;Daniel&amp;#39;s Special Subbase&amp;quot; or something.&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/234523452345fdghdfgh.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;Another option is to find a feature definition that results in what you want. This might have unintended downstream effects when it comes to annotating things, etc, but IMO you&amp;#39;re not forced to use a subbase feature definition merely because your component represents subbase. Try something wacky that obviously has no relationship whatsoever to subbase. Railroad-related feature definitions are a favorite of mine since I have not and will probably never use them otherwise.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>