PDA

View Full Version : Door Schedule Format - Double and Triple



phyllisr
2006-01-02, 08:21 PM
There must be a better way.

We prefer (2) 3'-0" and could also use 2 @ 3'-0". I cannot come up with an elegant solution for either and am not thrilled about my current approach. Graphically, it leaves a great deal to be desired.

The clip is my current method to get the door schedule to appear the way we prefer without a lot of manual editing and insuring all the dimension and panel information is not open to user error.

I created parameters used in a "circular" formula all derived from the OOTB width parameter. The attached clip demonstrates my method. Everything works perfectly but it looks ridiculous. I am aware I can create a "Schedule Width" parameter and manually enter (2) @ 3'-0" but that really defeats the goal of avoiding double-editing and leaving room for User Error, creating yet one more step when adding a Family Type. It would seem logical that some sort of expression builder or VBA syntax might work but I cannot figure out how. Ideally, I would like one column for width that would return the Panel Width only if the Panel Quantity were 1 and would return the Panel Quantity plus the @ symbol plus the Panel Width if the quantity were more than 1. Or parentheses on either side of the Panel Quantity, a space, and the Panel Width.

Has anyone figured a way to do this? I would doubt I am the first to ask but I was unable to find something with my search syntax.

Thanks in advance,
PBR

Added comment: This also creates a problem with scheduling doors that reside in a curtain wall. I have no clue how to do this.

Mr Spot
2006-01-02, 08:52 PM
I don't believe you can remove individual lines, its all or none. Rather than having two separate parameters for the number of panels and the @ symbol, why not just include them in one... That will get rid of one of the lines.

We typically use uneven doors and as such our sizes need to read:

2040x820x40+470x40 or typical. We have to resort to using a type parameter in this instance that is just entered in as text. We can't use the type name as there are often a few different versions of a doors of a similar size. I agree there needs to be a method of coding schedule information.

The only solution currently would be to export to excel or access and edit it there, problem being you would then need to either import it back in as a jpg or use it separately and be sure to update it systematically.

HTH.

phyllisr
2006-01-02, 09:06 PM
We typically use uneven doors and as such our sizes need to read:

Years ago when hand-drafting, our firm used 2 @ 1'-0" / 2'-0". We have accepted the ADT method 1'-0" (2'-0") just because it is what it is. This is also not so easy to do in Revit parametrically. Does this mean you assume I am out of luck with my formula property idea and there is no syntax that would allow me to add text in a formula with an expression builder?

Thanks,
PBR

aaronrumple
2006-01-02, 09:19 PM
Out of luck. Which is why vbscript is needed within formulas...

phyllisr
2006-01-02, 09:21 PM
Out of luck. Which is why vbscript is needed withing formulas...

Have you done anything similar with a VBA formula?

sbrown
2006-01-02, 11:41 PM
My workaround is to not use the width and height parameters at all, but to name the door (2)3'-0" x 7'-0". Very simple and works for me. Not parametric though. I've been asking about this since release 2.0 and never seen any fix. it gets worse when you start making families over the years and some you have a parameter for panel width but some are stock doors so you have to modify them and add the parameter... Doors need to be reworked and figured out how to schedule like the industry schedules them

janunson
2006-01-03, 01:07 PM
been a long standing wish of mine for more formatting in tables, and text formulas for parameters... either of these would solve your problem, but neither is currently available.

jcoe
2006-01-03, 03:03 PM
I use a shared parameter called "Number of Leafs" for my doors. When I build my nested door families I fill in the parameter in the family and when it loads into the project it is updated in the schedule. Unfortunately, when you have a single-leaf door, the 1 shows up in the column - which I do not like. It is not a clean method because now you have an additional, and unnecessary, column in the schedule. It does not address the issue of the uneven leaf sizes, but we steer away from those most of the time so we have not persued a way to deal with them. This method seems to work so far internally, but we will see when the project goes to bid in a couple months.

phyllisr
2006-01-04, 12:05 AM
Thank you all. Stay tuned for a future post. We are going to tackle this with VBA and I will share if we get it to work as we wish. Fortunately, my boss is very skilled and will help me with this one. I am still at the VBA for Absolute Beginners stage.

PBR

1/6/06
Work-arounds it is. I give up. VBScript in formulas is now the top of my personal wish list. Well, maybe not the top...

thand
2008-07-09, 03:49 PM
Just wanted to know if there has been any resolution or updates to any of the recent Revit releases that allows door schedules to read in such a manner?

I know this was a pretty old post, but does anyone have a solution to this matter?

We would like our door schedule to read (2) 3'-0" x 7'-0" x 1 3/4" for double doors and
3'-0" x 7'-0" x 1 3/4" for single doors...

Can this now be done?



Thanks

janunson
2008-07-09, 03:56 PM
the solutions above are still the only way. bummer. Post a wish on the wishlist!

sbrown
2008-07-09, 06:17 PM
I find naming the door type is the best way, it makes it easy for users to chose the door size they want. so like my post before, just name your door type(not family) the full (2) 3'-0"x7'-0" x 1 3/4". The only thing you have to do is make sure your size is really right, but since you probably are allready calling the door type something like 6'-0" x 7'-0", just change that.

david.kingham
2008-07-09, 10:16 PM
Here's the most elegant solution I could come up with while still maintaining the parametric information:

I created 2 shared parameters (Panel One Width and Panel Two Width) and gave them a formula of half the width for double doors or for uneven panels I have a parameter to increase the size of one of the panels. For single doors I only put in Panel One Width, this makes panel two show up blank in the schedule for singles....

greg.mcdowell
2008-07-25, 07:59 PM
Hey! That's pretty slick. Would you mind sharing that?

hermeytheelf
2008-12-19, 08:31 PM
I figured out how to do this with calculated values in the schedule. No additional parameters, either Project or Shared needed to be created. The trick is in formulas and canceling out the units to make ‘PANEL 2’ appear blank when the door is less than 4’-9" wide. The 'Width' parameter is hidden in the schedule but is necessary to allow the formulas to work.
PANEL 1 Calculated Value = if(Width < 4' 9", Width, Width / 2)
PANEL 2 Calculated Value = if(Width < 4' 9", (0' / 0), (Width / 2))
Both Calculated Values are 'Length'
Group (header) created above these two values named 'WIDTH'

This is based on the assumption that one would never have a single panel door that is wider that 4'-6" and one would never have a pair of doors that is less than 5'-0" total opening.

patricks
2008-12-19, 09:28 PM
You could even make those formulas say 4' - 0", at least for those using International Building Code, as your maximum door leaf width per code is 48".

I don't think we've ever done uneven door leaf widths, but to denote double doors we just have a Yes/No checkbox parameter called "PAIR" in the schedule. The width column refers to the individual door leaf only.

cdatechguy
2008-12-19, 09:34 PM
We call out the full opening width and then call out the panels being double, such as 6'-0"x7'-0" PR F....If needed I can call out different panel widths as well. Default is Panel1 & Panel 2 = Width/2

hermeytheelf
2008-12-19, 09:54 PM
I don't think we've ever done uneven door leaf widths,
I'm sure that we are going to run into that. Shared parameters will most likely be our friends at that time


We call out the full opening width and then call out the panels being double, such as 6'-0"x7'-0" PR F....If needed I can call out different panel widths as well. Default is Panel1 & Panel 2 = Width/2
Is 6'-0"x7'-0" PR F the Type name and that is what you are scheduling by? How are single panel doors not affected by the Panes1 & Panel2 calculated values?

Scott Womack
2008-12-22, 11:05 AM
I'm sure that we are going to run into that. Shared parameters will most likely be our friends at that time

Is 6'-0"x7'-0" PR F the Type name and that is what you are scheduling by? How are single panel doors not affected by the Panes1 & Panel2 calculated values?

Our firm has managed to partially "change its ways". We let the door families schedule the entire opening width, 6'-0" x 7'-0", and then use door types legend to show that that door is two leafs. Type A is a single flush door panel, and type B shows two single door panels together. We have now managed to standardize the door legend, and thus door panel types as well. This means there is only one panel column, and no formulas required.

paubin
2009-03-07, 04:11 PM
Hey nice font in that screen capture. What is that called?

david.kingham
2009-03-07, 09:47 PM
I assume you're talking to me Paul? If so you can download them here http://forums.augi.com/attachment.php?attachmentid=23501&d=1148393358

paubin
2009-03-08, 03:12 PM
Hey thanks! I appreciate it.

patricks
2009-03-09, 03:14 PM
hmm I see the Architext Narrow is a bit different, at least on the capital I's which have serifs where they do not in the regular Architext font.

We've been using the regular Architext font for years, and now with 2009 since we can change the text width in dimensions, I have changed all dimension types in our template to have a width factor of 0.8 for dimension text.

david.kingham
2009-03-09, 03:23 PM
Yeah I added that to the I Patrick, I also narrowed the whole font by .8, this was long before you could change the width factor in Revit, although you still can't change it in schedules so this is still the better method imho