Joe_Carrick

No, it just hides the Terrain and of course the Terrain Feature at that location. Basically it graphically removes them where the Symbol or Building exists. From a logical standpoint It seems to me that the area should be reduced by the size of the object.

I place a s Symbol (or a Building) in an area where there's a Terrain Feature (Sidewalk, Driveway or Stepping Stone) it cuts a hole in the Terrain. However, the reported area of the Terrain Feature doesn't reflect the change caused by the hole. Shouldn't that are be reported as reduced?

I also like Rene's method. I made a few tweaks for my own purposes: Created a 8" concrete stem wall with a thin white plaster interior surface - added to Library Created moldings for both the cove base and the tile coping - added to Library Use a thin tiled cove molding for the water-line (1/4" thick x 6" high) Use a Room Ceiling for the water surface This eliminates the need for any additional molding polylines and just moving the walls results in everything being adjusted accordingly.

I am available and I live in San Marcos. Please PM me with your contact information.

Glenn's right. It requires some Ruby macros. I have a set of macro's that get and display the areas of each roof planes. It wouldn't be very difficult for me to modify and display the data as you want. I would probably store the output in a CAD Detail but it could be sent to Layout on any page you want.

It's probably better to ask "Can this be done?" But essentially it's only limited by what data CA has and will in the future expose as object attributes that Ruby can use. It can't be used to actually edit the model but for annotation purposes almost anything is possible.

Thanks for the video. I think I will set up your method so I can use it in the future. Just need to get all the pieces together and organize in my user library. Some questions: What did you use for the Pool Deck (slab, stepping stone, etc) so that it automatically adjusted when you changed the size/shape of the pool? Couldn't you use the "ceiling" as the water surface instead of a molding?

You need to click on the Stair and then select the "Auto Stairwell" icon on the "Edit Toolbar". That will create the opening in the floor above.

When (which version) did CA add the ability to name our user defined "line styles" and retrieve the name from the Ruby attributes? I remember years ago that the user defined "line styles" were only given a number and there wasn't any way to get the actual name. I know I had mentioned it to someone at CA (Jason I think) but I had no clue that the real names were now available. Whoever did it and whenever they did it -- Mucho Gracias.

Thanks for the offer - but I'm more interested in a generic approach that I can use for a variety of different shapes and configurations. Ideally, it would be a specific tool (Terrain Feature - Swimming Pool) with all the options. I'm probably just dreaming. For now, I will plan on using Robert's method - at least until something better comes to mind.

Maybe X12 since it's nearing Beta testing. I think the CA staff is probably already using X12 - at least some of them would be.

When was the video made? Maybe it's a feature that will only be in a future release...…

Hi Robert, That's a pretty nice solution. I'm not sure how well it would work with a oval or kidney shaped pool. One of the things I am most interested in is being able to get and display the areas of water and the pool deck as separate items. The PSolid and Roof Plane should be sufficient for that.

I've been trying to come up with a way of doing this so that: It looks right in 3D There's an optional Pool Deck Edge (probably a Molding) The Slab (Pool Deck) has a hole that moves with the Pool Pool Surface is below top of the Slab Pool has a variable depth It's not easy. Does anyone have a great method for doing it?

You have to specify the room as the thing you want to get the internal_area of. Try this macro: ######################################################## # Macro Name: "room_internal_area" # Displays the internal area of the room a Note is in. ######################################################## # Copywrite by Joseph P. Carrick, August 2, 2019 ######################################################## referenced ? obj= referenced : obj=owner begin obj.room.internal_area.round(2) rescue "object isn't a Room" end You have to specify the room as the thing you want to get the internal_area of.

Try using the "All ON" Layer Set.

no, no, no - do not copy and paste in the plan. Send to Layout is OK but if you copy and paste in the plan then you will have 2 identical schedules and 2 labels.

Expand "CAD Details" Select and open "Window Schedule" Turn on the "Schedules" Layer It's there just like Chopsaw said.

Nothing. The macro just has to be assigned to the Label of a Layout Box. Of course you need to create the macro - name it builder_plan_name

OK, it's now finished and ready for Prime-Time. See https://chieftalk.chiefarchitect.com/topic/23944-site-area-analysis-macro-system/

It might work as just a one line macro. I'm not sure because sometimes Ruby doesn't like too many methods on a single line. IAE you can try it: result = referenced_full_filename.rpartition("_Builders/")[2].rpartition("/")[0]

I now have my new X11 Site Area Analysis completed. The price for this System is $125.00 - payable into my PayPal Account joe.carrick@dslextreme.com A complete description follows: SITE AREA ANALYSIS MACRO PACKAGE Created by Joseph P. Carrick October 13, 2019 This macro package uses a single macro %site_Areas% placed in the Label of any Chief Architect Object that has the area attribute. Normally that will be a closed Polyline, Polyline Solid, Slab or a Terrain Feature such as a Driveway or Sidewalk. There are several aspects of the Object that are taken into account in how the data is used: Layer - generally names and Labels the area Line Styles – property and setback are automatically recognized Line Styles -- new, existing and demo are also automatically recognized - the Polyline will be labeled as “(N)”, “(E)”, “(D)” Floor Level (referenced floors) are automatically recognized for any building Layers Names containing "Building", "Home", "Structure", "Residence", "Garage", "Storage", "Shed" are automatically recognized as BUILDINGS. Layers Names containing "Building", "Home", "Residence" are automatically recognized as HABITABLE Layers Names containing "Roof", "Slab", "Walk", "Driveway", "Water", "Concrete" are recognized as IMPERMEABLE. Layers Names containing "terrain" will be analyzed according to their material for Impermeable recognition. Layer “(O)” is recognized as an overlapping area of the Impermeable areas and subtracted from the total Impermeable areas. If a Layer Name contains “(N)”, “(E)”, “(D)” they are recognized as NEW, EXISTING & DEMO respectively. There can be only one Property Line and one Setback Line. The same Layer can be used for more than one object. The system will keep track of them as different areas The same Layer can be used on different floors and if the floor is displayed as a “Reference Floor” the areas will be included. The following macros are included to list, calculate & display the accumulated data: %site_Areas_FAR% - displays the Floor Area Ratio %site_Areas_List% - displays the list of all areas %site_Areas_List_Demo% - displays the list of all Demo areas %site_Areas_List_Existing% - displays the list of all Existing areas %site_Areas_List_Ground_Floor% - displays the list of all 1st Floor areas %site_Areas_List_Habitable% - displays the list of all Habitable areas %site_Areas_List_Impermeable% - displays the list of all Impermeable areas %site_Areas_List_New% - displays the list of all New areas %site_Areas_List_Coverage% - displays the lot coverage calculations %site_Areas_total_New_plus_Existing - displays the total of New and Existing All of the above macros are contained in a Library Object named “SITE AREA ANALYSIS RTB” which when placed in a Plan will add all the macros into the plan. There are also Annosets and Layer Sets that can be imported to make setup easier. These have been provided to use with Imperial Units but can be the basis for Metric versions. The macros are designed to recognize which system is in use and use the appropriate units in the data display. Whenever something is changed in the plan, the data in the RTB should be updated automatically. However, this might not always happen so it's important to press and hold the F5 key for a couple of seconds to insure the data is correct. This must be done before printing a Layout.

Build Wall Framing?

Sure, but a better method would be to use: result = referenced_full_filename.rpartition("_Builders/") result = result[2].rpartition("/") result = result[0] This way you only have to know that you want to eliminate everything up-to and including "_Builders/" and everything after the last "/". Note that I'm using the "/" instead of the "\" because that's what Chief uses in the referenced_full_filename attribute.

The actual characters would be required - or the number of "/" characters - or maybe if you just want to eliminate everything after the last "/". There are several possibilities. The macro can become more complex - actually just longer - depending on what rules you want to follow. Ruby is mostly about manipulating data and performing calculations. This case is basic manipulation of a text string - which is very much just an array of characters.