# New Block Attribute Export command

**URL:** <https://discourse.mcneel.com/t/new-block-attribute-export-command/138691>\
**Category:** Serengeti (Rhino BETA)\
**Created:** [February 28, 2022, 9:45pm UTC](https://discourse.mcneel.com/t/new-block-attribute-export-command/138691 "2022-02-28T21:45:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mary](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/mary/32/764567_2.png) [@mary](https://discourse.mcneel.com/u/mary)\
**Post date:** [February 28, 2022, 9:45pm UTC](https://discourse.mcneel.com/t/new-block-attribute-export-command/138691/1 "2022-02-28T21:45:57Z")

</div>

There is a new command in the **Rhino 8 WIP** for you to try.

Before this command, extracting block attribute values for analysis might have been done with a script, Grasshopper with Elefront or you may have even exported DWG and used AutoCAD.

Here is how you can use the command.

1. Download a **Rhino 8 WIP (Windows or Mac)** dated _March 15, 2022_ or later.

2. You can preselect blocks with commands **SelBlockInstance** or **SelBlockInstanceNamed**.

3. Start the command.  
_Command_: **TestExportBlockAttributes**

4. Use the preselected block or select blocks with attributes to export

5. Check the Block Attributes to Export  
 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/9/c/99c7e6bf4833fd69514d69e78356548ad3e044e0.png)

6. Pick name and location for **CSV** file.  

7. Open **CSV** file in Excel, Google sheets or other program for analysis or formatting.

8. Return the table to Rhino by printing your your spread sheet to **PDF** and importing your PDF to Rhino. The data is not linked, but the table layout is maintained.

We are sure there will be suggestions to make this more powerful.  
But it is a place to start. Let us know if it works for you.

Sincerely,  
Mary Ann Fugier

![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/b/c/0/bc0123a51966b00136c3ef0018373746581031be.jpeg)

---

<div class="post-metadata">

**Author:** ![Jacob\_Thuesen](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jacob_thuesen/32/382857_2.png) [@Jacob\_Thuesen](https://discourse.mcneel.com/u/Jacob_Thuesen)\
**Post date:** [August 19, 2022, 11:57am UTC](https://discourse.mcneel.com/t/new-block-attribute-export-command/138691/3 "2022-08-19T11:57:02Z")

</div>

I like this as a beginning of creating BOMs and BOQs. We are now trying to implement this method in our pipeline at my work. One thing I would love to add is dimensional information of the block like width, height and depth. The information is already in the “BoxEdit” and it would be great if we could have it as an attribute.

---

<div class="post-metadata">

**Author:** ![tay.othman](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/tay.othman/32/766134_2.png) [@tay.othman](https://discourse.mcneel.com/u/tay.othman)\
**Post date:** [August 21, 2022, 12:15am UTC](https://discourse.mcneel.com/t/new-block-attribute-export-command/138691/4 "2022-08-21T00:15:20Z")

</div>

I see a use for it with the setting for a Drawing List where I can extract Sheet Data from a single Rhino File, I haven’t done that but I’ll give it a try soon.

By Tying the below attributes to a title block I get the info for below:

1- Sheet Name  
2- Sheet Number  
3- Sheet Issue Date  
4- Revision Description.

---

<div class="post-metadata">

**Author:** ![arlind.dervishaj](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/arlind.dervishaj/32/628560_2.png) [@arlind.dervishaj](https://discourse.mcneel.com/u/arlind.dervishaj)\
**Post date:** [September 28, 2022, 9:35am UTC](https://discourse.mcneel.com/t/new-block-attribute-export-command/138691/5 "2022-09-28T09:35:06Z")

</div>

I haven’t been using Blocks in Rhino a lot. I am curious how was the data of attributes displayed as text in the 3D space along the elements?

I see this feature could be very useful, for example to edit properties in an excel/CSV file. Import the CSV to populate the block with properties and values, or to change the existing values. This feature could be even more powerful if it could work between Revit properties of a family/type/instance of a component and a block in Rhino, some equivalency, to have interoperable properties.