I've slowly managed to put together a simple object that works as an add-on for slabs. Now I'm stumped on how to continue. What I would like to do is calculate stuff based on my object, and use these calculations in schedules or lists. For example I would like to calculate the area and volume, and from those values calculate an average number of apartments and so forth.
Do you have any suggestions on how to do this?
Link to object (made in Archicad 25): https://drive.google.com/file/d/1H1zIMQw84KaneYf5NkKRK1HkpV9ZGD5M/view?usp=sharing
It's never too late. I've been on the fence whether to get Grasshopper (or recommend the office to get it), but I've downloaded a trial now, so we'll se how it goes. Any clues on how to work it out in Grasshopper, or will it be self-explanatory once I start to get in to it?
No, but your original case description sounded like it could use a paremetric approach and from what I've seen on youtube clips in the past, you can basically let grasshopper create Archicad 3D elements for you.
You might even be able to drive creation of existing buildings by combining GIS data and government vector data for site plans.
Especially the combining of GIS data and the local vector data with Grasshopper could cut our work time a lot! Will try it out when I get the chance!
However, for what I'm doing now I think a simple Archicad object should be enough, and working with Grasshopper might be to complicated for these types of early stages if it's to be implemented at the office.
So, I have two more open questions:
1. How do I use the Properties Script to get
a. The area of either my object or the slab upon which it is based?
b. The total volume of it?
I figure it's maybe using REQUEST or built-in properties, but I can't figure out how to use them properly?
2. How would you go about to create setbacks on this type of building object?
In case you are looking for some more information, here is a presentation from Enzyme https://geospatialworldforum.org/speaker/presentions2019/Connecting-GIS-BIM-Workflow-Case-Studies-Eu...
If you browse to slide 19 or so onwards you get a good introduction to how they use GIS data and grashopper to create 3D site models.
With this approach the area has to be calculated by the script from the polygon coordinates. There is no existing GDL solution, the shoelace formula can be used if there are no curved edges.
Another approach could be making a label (if you don't need IES data or 3D geometry). Labels have access to slab data: http://gdl.graphisoft.com/reference-guide/column-beam-and-slab-parameters.
Properties can also be created using Property expressions without GDL.
Hi Peter! Thank you for your response.
I've set up the shoelace formula and it works fine. It feels as though it would be possible to calculate even with curved edges. The slab accessory seems to convert the arcs of the slab into a prism made up of straight polylines. I haven't really figured out where in the process this happens though.
If I look at the saved parameters, an accessory created from a rectangle slab has 15 parameters (x, y & status and the first point again with -1 as status). If I make one of the slab edges into an arc, the number of parameters reach around 150-300 instead (231 in my added screenshot). So, my thinking is that I could use those coordinates for the shoelace formula in some way to get a decently accurate result, would you say that's correct?
I haven't been able to "find" those coordinates in the Properties Script, only in the 3D. Is it possible to save them in the 3D script and let the properties script read them?
I also have not been able to control the appearance of the accessory when using an arc, neither RADIUS, TOLER nor RESOL seems to affect it. Do you know if this can be done?