Deleting Attributes and the One Layer Model
Over on BIM Engine, I’ve been writing a series of articles about Layers in ArchiCAD. As part of that exploration I want to talk about the One Layer Model (or the One Surface Model or the One <insert Attribute here> Model).
Why would you want a One Layer Model, or a model with a particular Attribute distilled down to non-existence? Lots of reasons, but mostly it boils down to temporary simplification. Imagine you have a hyper detailed model, then you want to look at options for a dormer or landscaping or some other localized detail. What if you could ring-fence the model and give it an on/off switch? Or what if you could easily create: base model, option 1, option 2, option 3, etc. Or perhaps you want to create a two or three tone model (a model with just two or three Surfaces, see image above). Or maybe you want a complex model to be on one Layer so that it can become background entourage for something else (yes you could just hotlink it in or do other tricks). The point here is to explore and understand how we can misuse ArchiCAD to our advantage. To be natively creative within ArchiCAD, we need to understand how to break the rules and head down whatever path the design process leads. Sometimes that means modeling and working in a way that creates an orphaned model. That’s okay. That’s good. That’s a bigger discussion for another time.
There are a number of ways to simplify a model, and one of them is to delete and replace Attributes as fast as possible. Here’s how:
- Save As (we are going to do some non-undoable destructive stuff).
- Delete Attributes like a mad person.
- Work in simplified freedom.
To make this technique viable, and not tedious to do as part of your creative process (ei, to be able to simplify a model quickly and effortlessly), you need to learn a specific technique:
Notes and Further Reading:
- As I note in the video, the exact technique I show, while clever, is a bit unnecessary for Layers and Building Materials as you can select multiple BMats or Layers at once, delete and replace them, and no data is lost. This makes consolidating Building Materials or Layers insanely easy-as you can select as many of these Attributes as you want and merge them down without loss. So watch the video as there’s other valuable information, but just use the faster method of selecting a bunch at once. Damn. I tested this before making the video and it didn’t work for some reason. Fortunately an astute viewer caught my mistake. THANK YOU!
- The Power of One. Ken Huggins talked about this back in 2012 (and I’ve been thinking about it ever since). But we’re going a step further by showing how to take any model with tons of Layers and consolidate it down to just one or two.
- If your model relies on Layer Intersection Groups, the resulting One Layer Model will have a few goofy moments as elements will all interact. If this is problematic, you might need to consolidate down to two or three base Layers. Then again, what you are doing is creating a schematic model, so a little crudeness might be okay.
- If you are doing this to test options in 3D, you might want to delete everything on hidden Layers, and just merge down to one Layer the stuff you can see. Remember this is about being loose and fast. Once you have a solution, you will go back to your original file and work properly.
- If you are doing this delete and replace gambit, you could start by going to the Attribute Manager and deleting all the unused Attributes to speed the process up even more. This is especially important with Fills, Line Types and Surfaces, as they don’t work as smoothly with the process shown in the video (because after deleting you aren’t returned to a master list like for Layers and Building Materials AND more importantly, you can’t select multiple Attributes at once and merge them like you can with BMats and Layers). My solution with these Attributes is to just delete and replace with whatever random Attribute comes up as the Attribute to be replaced with until you get down to just a few. Then when the list is smaller, be careful, tweak, and set up the remaining Attribute(s) to be what you want. If you are deleting 100 Surfaces, it doesn’t matter what Surfaces 1-90 are merged into. Just that the final surfaces are merged correctly into the remaining ones.
- If you are merging down to 3 or 4 Attributes (say Solid, Transparent, and Translucent Surfaces), consolidate the Attributes that are unique first (ei, the two Surfaces that will be merged into Transparent and the four that will be merged into Translucent) before doing the bulk work of merging the rest into the remaining Attribute (Solid in this example).
- For more on deleting and replacing Attributes, check out the Help Center.
- For more on monochromatic models (there are lots of ways to do this), check out this video I did in 2014: Monochromatic Models in ArchiCAD.
Subscribe to my blog to read more about the tricky world of being an Architect in the 21st century: Shoegnome on Facebook, Twitter, and RSS feed.
Karoly Horvath
Hmmmm interesting, but let me highlight some things:
-If you intend to use layers to show options, remember that walls /colums etc on a turned off layer still interfere with walls/columns etc on other layers. This results in nasty junctions and ugly white spots… Instead of layers, if the options don’t consist of too many model elements, it may be better to use the reno filters and create option filters that way. O course if the options are too complex, well probably modules is the way to go
-Yet I see real good opportunity in reducing the number of attributes: It results in a clean file to start with.
So far I removed all surfaces from my template, leaving “Existing, New, Demolished and Glass” only to start with. This way you can make sure that you will only have surfaces that actually are used in the project.
I quite like that it is now so easy to add new surfaces from catalog in AC18
-This leads me to a great wish.
I wish if in future ArchiCADs I could clean out all attributes and add them back into the project from a central depository (catalog if you like) as I go. For most users it would be so much easier and also it would mean that the project file only contains attributes that are necessary!
I know that to an extent the above can be done if you use the attributes manager, but that is quite clunky. I can’t se forcing all users to constantly go to attribute manager if the need a new fill or any attribute that does not yet exist in the project. Adding new attributes should work the same way as it works now for surfaces!!!!!
Funny, but I think that the way surfaces work now was not at all designed to make attribute management easy, but it was just a byproduct of introducing CineRender.
I love this byproduct. I wish same method was introduced to All Attributes!
Cheers,
Karoly
Jared Banks
The hidden layers problem: I mention this in the post, partially. If you set the hidden layers (for different schemes) to a layer intersection group of 0 when hidden, then there’s no problem. They won’t interact with the visible elements. This is probably a must for using Layers as different options.
I guess if you started a file with next to no attributes, you could just copy elements in from other files and they’d bring in their attributes. It could get messy but now since ArchiCAD will match names instead of index numbers for attributes, it’s a little clear.
But I do agree, having the ability to import attributes like we can with surfaces now would be great. But this is a big wish, right? Central Attribute management? Anything that improves attribute management and functionality is great to me!
wwabim
I LOVE that hidden layer to Intersection Group 0 idea! I’ll be adding that into our office template ASAP!
Also worth noting, and I think I mentioned this once before; if you have a teamwork project rather than a PLN or PLA, be sure to reserve all before deleting and replacing with… otherwise any unreserved elements will have missing attributes!
Jared Banks
Layer Intersection Group set to 0 is super valuable to know about! Glad to enlighten.
Pingback: Layer Intersection Groups | WWA BIM
Stig
Be aware that if the intersection is set to 0, the items in that layer don’t intersect with items in its own layer either.
Jared Banks
right! The general rule is: elements on a Layer with the same layer intersection group will interact (ei, cut each other, follower Building Material priorities, etc.). Elements on Layers with different layer intersection groups won’t interact (ie, priority junctions won’t work). Elements on Layers with a layer intersection group of 0 won’t interact with anything, including other elements on a Layer with layer intersection group 0.
tm
love that rendering of green building that opens this blog up…amazing is that your work or existing building?
Jared Banks
It’s a model I built. It was a collaboration with David Jefferis of Grayform Architects and Paul Brow when he was working with Butler Brothers (all out of Houston, TX). The project is definitely a mind-meld of the three of us, but the lion’s share of the design credit goes to Paul. He’s a super talented architect and designer. He and I worked together years and years ago when I was still in school. I should write about the experience of working with Paul. He was probably my first real architectural mentor. And my search to replace him when I moved to Minnesota (ei, find a new job where I could work with a similar mentor) set me on the path to discovering ARCHICAD.