Roofs an Worksheets

[Tobias]

I have a worksheet to calculate the sq ft of roofs for a building. The worksheet looks for both roof objects and roof slabs, because the roof is made up of both roof objects and Slabs. I have found that the worksheet then counts roof objects twice - first the area of the roof object, and then counts the roof slabs again.

[Jim Smith]

What if you added a classes to you criteria? That way you could total a slab and/or a roof object.

[Tobias]

Jim,

I have done that. What the worksheet is doing is reporting the area of the roof object in total, and also reporting the area for each individual slab that make up that roof object. So, for roof created with the create 'roof object....' command I am getting 2x the area reported on the worksheets. What I ended up doing to make it work (after figuring out what was going on) was unlocking and un-grouping all the roof objects into their individual roof slabs.

Getting a tab bit frustrated with being VW's beta tester.

[Jim Smith]

Tobias, I know what you mean, one thing about the Roof Object I find is I have to convert it to a Roof Face pretty much every time to make a roof that actually works properly. It's a great tool to get a roof started, but If two pitches intersect for example there is often a lot of trial & error afterwards to get it to model properly. I'm guessing every Roof Object becomes a Roof Face in every project- just how we work.

[michaelk]

What are you using for criteria?

I just tried it with both roof objects and roof faces.

=DATABASE((ST=ROOFFACE)) does exactly what it sounds like you need.

=DATABASE((T=ROOF)) does only roof objects.

If you are using both, you would get the double results you describe.

hth

mk

[Tobias]

Indeed you are correct, sir. Thank you.

This points to the need (I think) for an interface more like this for the database criterion, making editing them and changing them less of a chore:

[michaelk]

I agree. The UI for entering criteria is too clunky. It's often easier to just type it in.

mk