referencenawer.blogg.se - Autocad standard layers list

Open your most recent (or best) project that utilizes your current template.

They all essentially ask the same thing, but from different vantage points: do you really need that Layer? Whenever you rebuild your template, or are thinking critically about the project you’re working on, there are a number of questions you should ask yourself about your Layering system. I also pester him to write more just about as often. I seriously reread them once a quarter, if not more often. I have a lot to say about Layers, obviously, but for a Masters class on Layer simplification, read Ken’s articles. We’ll look at many of them more closely in the future, but for now I want to stay focused on the humble Layer.ĭid I write Ken Huggins’ name enough time? I can never say enough good things about Ken’s articles on regarding Layers and data organization. Each of those reasons could theoretically remove Layers from your file. The points Link and Laszlo make are about visibility, but they are also about organization. Here’s a great thread I learned about while on Twitter: A collection of reasons why an element might not be visible. Now in Archicad 18, we have so many other ways: Renovation Filters, Partial Structural Display, Pens, etc. In Archicad 9 or 10, the way to hide elements was always through Layers (essentially). If elements on a given Layer can be divided easily using Find and Select, then you might not need to separate those elements out into two Layers. Think back to my articles on Find and Select (part 1 and part 2). How would those two methodologies affect how you work in Archicad? Layers aren’t always the answer. Or just two layers: on plan and not on plan. Imagine if you had one layer per design scheme.

After all, managing 10 layers is much easier than keeping 100 organized. And when we cut down the number of Layers from 100 to 50 to 10 or even 1, then we can really start making them work for us. We can let other aspects of the program do some of the work we’ve been slavishly making Layers do. While Layers can handle massive amounts of organizational options, they don’t have to. Or more importantly they can be parred down to their essence to better take advantage of all their other features and potential. So while Layers do act like those old pinboard layers, Layers can function differently in Archicad. But in Archicad we have a ton of ways of sorting and displaying data: renovation status, IFC properties, Structural Function, Element Classification, Position, linking elements to a Change, Model View Options, etc.

And most importantly Layers allow us to take advantage of the automation that Layer Combinations provide us (spoiler alert: that’s Part 3 of this series). Layers determine whether an element is editable or not (locked/unlocked). Layers determine whether elements interact with other elements ( Layer Intersection Groups).

Layers allow us to turn elements into wireframe in 3D. Layers are an essential metadata tag on elements to help classify and organize them into groups. Well first of all, there’s the concept of graphic data, digital approximations, and metadata. But (and you should all see this coming) just because we did something one way in one program doesn’t mean we need to do it that way in another. We view Layers like simple bins of 1980s LEGO bricks. We understand layers because we used them before. And to be honest that’s what we all see Layers as when we jump to Archicad from CAD. They think digital approximation of an ancient method (whether they know it or not). The grumpy BIMmers think Layers and think AutoCAD. Layers used to be physical things! Wow.Īnyways, back to the story. Nevertheless, the day I learned about the origin of layers from an older coworker, my mind was blown. It’s hard to find discussions on the Internet about this archaic ritual, so I might have some details wrong. This is before my time, thus I don’t know the exact details. Each layer of a drawing was literally a different sheet, which when overlaid and pinned in different combinations eliminated some repetition of work (only draw the walls once!). Which in turn were just a replication of the old pin-bar drafting technique of laying different sheets of Mylar over each other. They equated Archicad Layers to AutoCAD layers. It turns out those grumpy BIMmers raised some good questions, although the most salient point was something unintentional. But they did get me thinking about Layers.

They probably weren’t that bad and we all actually do get along very well. Layers aren’t worthy of BIM.” Okay I’m getting a little hyperbolic. They mocked “layers are so CAD! BIM should only have real things in it. Last year I got into an argument with some non-Archicad BIM users-this happens more than it should. This article was created by Jared Banks in 2015