Layers Best Practices

[dsalvagni]

I am curious what every one does with layers.  at my firm we have a blank template with no layers loaded in it and we have blocks in our tool pallete that have the layers in it for certain drawings, i.e. floorplans, details or elevations, etc. and the drafter will just click the block that they are drawing (detail) and those layers would load into the drawing and then they would delete the block.  Is this the best way to do it?

[ianjchap]

Hi @dsalvagni,

If you're using the same Layer names all the time that meet some naming standard, then always best to have these built into a Template somewhere so you have them from the off.

You'll find it a big time saver to have these thought about in advance an applied to the template.

I imagine not all the work you'll do will be done via a block, so good to have these setup.

Ideally blocks should be setup on layer 0 then inherit the Layer properties they're put onto. This isn't always the case however and there are valid reasons to have blocks set up on specific layers.

[VincentSheehan]

There are tools you can use. Design Center can work. Create a drawing with all the layers then use Design Center to import what layers you need. The company I work for has an in-house app to manage layers. There may be something on the Autodesk App Store.

[imadHabash]

Hi,

@dsalvagni 

>>Is this the best way to do it?

Let's just say it's a practical and good way to work as long as you ultimately get the desired result. There are other methods, such as using a pre-built template (.dwt). However, this is not very practical, especially when using the Purge command, as all unused layers will disappear.

[Kent1Cooper]

I recommend the drawing Template file approach, with separate Templates for the different purposes [types of drawings].

Another thing you can do is to define commands that create all the Layers [with their colors and linetypes, etc.] as well as Text and Dimension Styles and so on, for your different drawing types.  You could open a blank drawing and run the command to make it a drawing of a particular purpose.  Even if a drawing was not made that way, but was based on a Template for its type of drawing, there could be Layers that you want in there but that have nothing on them yet, which could get Purged out.  Such a command would return the missing Layers, without your needing to know which they are as you would need to if using the Design Center to bring them back in.  [Likewise for unintentionally Purged Styles, etc.]

[chriscowgill7373]

We have a primary template with the layers necessary for our more common tasks.  We have a secondary file that contains the list of all other standard layers.  We use National CAD Standard for our naming, which groups layers that are related together, so importing the layers required for additional tasks is pretty straight-forward, using Design Center or an in-house app.

[Jason.Piercey]

I keep a plain text file (formatted INI style) with layer definitions grouped into sections for different uses. I developed a custom routine to read the file and create the layers on the fly.  I find that it works great and avoids any issues with existing block definitions requiring renaming or purging before the new/updated blocks with revised layer properties can be used.