The Eckler project templates have been setup to work with a specific layering format and in some cases specific layer names. I've even included layer filters with the templates that allow a drafter to display only specific layer groups, this makes turning off all existing piping, for instance, a lot easier than trying to select the layers in a large group. I've also created short lisp routines to allow a specific group of layers, i.e. new pipe or new above ground pipe, to be frozen and then thawed again when you want them visible.
Another big issue with trying to stick with the same layer name on a regular basis is, if one drafter creates a layer for a pipe called "NP-WM_004" and the standard layer name is "NP-WM-004" you may wind up with two layers for the same flow stream of piping if two different drafters work on a drawing, or if a command that automatically creates a layer name during it's use is run. Our symbol popup box is setup to create layers and set them current when inserting blocks. If I create a layer called "Title-text" and put annotation on it for a detail or plan view, then run then click the Symbol toolbar button and select a main title block, it will create the "Titles" layer and now I have two layers with the same type of information on them.
We have a "acad-template" drawing that contains all the latest layers, multileader styles and other common data. If when layers are needed this block is inserted the layer names will remain the same all the time, and it's faster to insert the block with the toolbar button than to manually create new layers anyway. After the layers that are needed have been populated with data simply run the purge command to remove any unused layers along with other unused objects in the drawing that may be bloating the file size.
This is an ongoing and evolving monster that we'll always deal with. It's almost impossible to create a layer for every object that may be drawn, and not everyone will think the same way when creating layers for specific objects. We all just need to do our best to use what's setup as a specific standard, even if we don't always agree.
If you have any comments please send them to: author
