Sheet Legends

[samir_rezk]

Hi,

I am curious what is the consensus on putting the sheet legend in the xref vs. the sheet models vs. the sheet paper space! What is the pros and cons! What is the best practice on dealing with legends in general. Seems to me the legend creation and updating takes more time than necessary.

thanks.

[surajpanayath]

The easy method is to use the proper layer with different line type for each legend, then use the attached lisp for making legends. this will automatically create the LEGEND with layer name and the line type which you used in the layer. 

[Joe-Bouza]

Hi Samir

IMHO the real answer is CAD Standards. If the standards are perfect a legend and abbreviation sheet is all that is needed and no one has to ever think legend again.

...Alas this is in the fairytale chapter of Cad standards.

I do both  I try to develop one in MS of the xref as design progresses and open a vport in the sheet.

Some sheet have minimal stuff and a PS legend is pasted in from a standards file

[rl_jackson]

I have a single legend in PS that just about everything mostly point blocks, and abbreviations that cover all of our survey's. Since I'm not doing Existing vs. Proposed it makes life easy, and here in FL the Engineer just includes our survey in the design.

[samir_rezk]

Thank you @surajpanayath @Joe-Bouza @rl_jackson . My line types are usually set at the layer level, but I often have layers in the xref that is not part of sheet file so there lies my problem! Also each sheet has a slightly different list utility vs. grading as an example! 

[Joe-Bouza]

Agreed it can be a PITA...

..."yes reviewer-person the circles with letter are manholes, the rectangle with smaller rectangle in the middle are catch basins and the lines connecting to them are pipes"... 😮

[samir_rezk]

Lol 😂

[surajpanayath]

Dear Samir 

From xref it is a little bit tough, But you can extract Line type and blocks with name & shape by using Auto Lisp from open Xref files Copy Paste to PS.

BLock with Name Lisp also available.

[nostupidquestions]

for a survey the legend is fairly straight forward. i just pull up my list of points, sort by point style and insert the block symbol for each point style. the linetypes generally don't change. for construction plans it just depends. in my mind there would be one sheet with the legend and notes but sometimes contractors pull sheets out of the plans for the subcontractor (or so i've been told) so we put a legend on most of the sheets. i usually create a block for the legend and copy it so the sheets in that group, like utility sheets get a utility legend, drainage sheets get a drainage legend. i try to keep the legend very basic but occasionally a reviewer can't figure out what's going on and i have to get more detailed. sometimes a reviewer wants a comprehensive legend and those items labeled in the drawing, as in a wetland hatch in the legend and then a label in the drawing pointing out the wetland.

[cwr-pae]

I have started putting my legends in the source files. It takes a little care in putting them where they can be stacked together for plans with multiple xrefs. In some cases I have more than one legend in a xref (notably survey/topo) to reduce the legend in some client files. For instance I don't always have to note every single little object/line/hatch for topo/survey data in every plan. This way I can quickly match changes required for various type plans, mainly color/plot weights using layer manager. For some plans, depending on the P.E. (not P.U.) in charge I have managed to have a 'Topographic Legend' separate from the 'Work Legend' which makes things a little easier to manage.

For some of my work legends I have started using a table with blocks for the symbols & lines to help keep things together and organized.

[rl_jackson]

@cwr-pae 

depending on the P.E. (not P.U.) in charge

🤣🤣🤣

[TerryDotson]

I've always been fond of legends that ONLY contain the relevant objects that exist in  a drawing, as opposed to a massive legend of everything ever used by the firm, etc.  Looping through the objects and evaluating what symbols (blocks) are used (including in CogoPoints), also obtaining only the linetypes used makes for lean 100% relevant legends.  These tables can be updated on demand or drawing open, etc.

[chriscowgill7373]

It depends on what you are going for.  If the legend should be the same on multiple pages, xref may be the best method.  I prefer paperspace for its placement, because it saves the time of creating a viewport on each sheet to show the same area.  In other instances, where you are only showing the information on the sheet, starting with a block and deleting what you dont need is sometimes the best option (although having it automated as Terry suggests is a better option).   The legend I've used in the past had everything on a separate set of layers and blocks that would not change size, so that it would match the plans (assuming standards were followed)