Annotation Layer Strategy

[Anonymous]

I'm trying to come up with the most efficient method of managing annotation for differnet types of floor plans. For example... in a set of plans on one level I might have floor plans for... main level dimensions; main level room finish schedules; main level power & lighting; main level reflected ceiling plans; main level furniture plans, etc.

So with all of these drawings based on the main level... can I have just one level of annotation that will work on all layouts... or will I need an Annotation Layer established for each type of plan that I am noting up in order to not have content from the other plans appear on the wrong layout. This might seem pretty elementary... but I would appreciate any input that one might have conserning this question. - Thanks.

[Laura Yanoviak]

scoreville wrote:
... or will I need an Annotation Layer established for each type of plan that I am noting up in order to not have content from the other plans appear on the wrong layout.

This is the way to go.

[Anonymous]

Thanks for the reply... I was afraid this would be the way to do this in ArchiCAD. It seems that there could be a more efficient way to manage annotation... with say maybe 3 or 4 annotation layers for an entire project, rather than 15 - 20 separate annotation layers that would need to be managed in a template.

[vfrontiers]

Agreed.... You will need a layer for each plan's notation.

Floor Plan (Notes)
Clg Plan (Notes)
etc, etc,

In addition, I have included a WORKSHEET (or Independent Detail in AC10) called NOTES.... As I use a KEY NOTE system, this NOTES window allows me a space to type out all the notes, properly formatted for my sheets. By use of the layers described above, I simply apply that plans LAYER COMBO to this window for a VIEW of each of the Key Notes to place in the layouts. So... only ONE "Notes" window, but many NOTES views for layouts.

Notes Window + Clg Plan Layer Combo = Key Notes for Clg Plan
Notes Window + Floor Plan Layer Combo = Key Notes for Floor Plan
etc., etc.

[Anonymous]

Keep layering as simple as possible!!! Creating too many layers can be a huge management problem. The plan views need the most layer management, as the other views are isolated to the window they are in (i.e. sections, details, worksheets, etc...) Personally, I find it wasteful, even on large projects, to put dimensions, notes, fills, etc. on separate layers if they only show up in the same plan view. You can easily select info by tool or "find and select". Only create separate layers (dimensions,notes, etc.) for the most common plan views when needed. I typically place all 2D info on the ArchiCAD layer that is added to a section, elevation, detail, etc. because they are isolated to their own window anyway, the info is always on no matter which view you just came from, and in Teamwork you can use any layer for 2D embellishing of the isolated windows as long as you include that window in your workspace.

DON'T USE THE AIA NAMING METHOD!!! It is idiotic and based on the old AwfulCAD mentality. Name layers something that makes sense and not some abbreviated code. There are plenty of characters to work with to be descriptive enough for those who may open this file in the future.

[Brad Elliott]

Just to clarify a point. You need a layer for each different plan type but not for each story.

[Anonymous]

[Notes Window + Clg Plan Layer Combo = Key Notes for Clg Plan
Notes Window + Floor Plan Layer Combo = Key Notes for Floor Plan]

I see. So would it be best to set up all of those notes on possibly an entire story dedicated to all of these keynotes and then create those view windows in the view map from this story and the necessary individual layer combinations?

[vfrontiers]

scoreville wrote:
[Notes Window + Clg Plan Layer Combo = Key Notes for Clg Plan
Notes Window + Floor Plan Layer Combo = Key Notes for Floor Plan]

I see. So would it be best to set up all of those notes on possibly an entire story dedicated to all of these keynotes and then create those view windows in the view map from this story and the necessary individual layer combinations?

NO!... just a detail window or WORKSHEET (new in AC11)...

[vfrontiers]

Eric wrote:
Keep layering as simple as possible!!! Creating too many layers can be a huge management problem. The plan views need the most layer management, as the other views are isolated to the window they are in (i.e. sections, details, worksheets, etc...) Personally, I find it wasteful, even on large projects, to put dimensions, notes, fills, etc. on separate layers if they only show up in the same plan view. You can easily select info by tool or "find and select". Only create separate layers (dimensions,notes, etc.) for the most common plan views when needed. I typically place all 2D info on the ArchiCAD layer that is added to a section, elevation, detail, etc. because they are isolated to their own window anyway, the info is always on no matter which view you just came from, and in Teamwork you can use any layer for 2D embellishing of the isolated windows as long as you include that window in your workspace.

With the LAYER COMBO feature... I personally don't see any problem with having a large number of layers... but that's a different debate...

Regarding the layer approach that puts NOTES, DIMS, FILLS and more onto one layer, I have trouble with... I prefer to keep the same layers throughout Schematic Design, DD, and working drawings... Therefore, it is necessary to isolate dims, notes, and fills to achieve all the different Schematic looks as well as produce working drawings.

[Anonymous]

Keep layering as simple as possible!!! Creating too many layers can be a huge management problem.

I tend to agree and am frightened by the nightmare this could become by creating to many or unnecessary layers within a CAD template. So when it comes to elevations and sections and details you tend to leave all annotation on the ArchiCAD layer because...

• 1- those windows are complete independent from all drawing content; 2- the archiCAD layer is always on so you won't have to worry about turning on or off that layer for revision or publishing. = more efficient quality control.