Corridor Modeling - Template Defaults to a Construction Layer

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 when i cut cross sections, it defaults to Draft_DNC, which is a do not construct construction layer.

A workaround I have is to change the feature definitions manually in the cross section viewer. However, this setting does not save and would require editing every time I would enter the file.

  

  • 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'm guessing that the workspace DGNLIBs are set up so that feature definition appears on the DNC layer.

    If you'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 "Daniel's Special Subbase" or something.

    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'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.