Saturday, 17 March 2012

Troubles with overlapping pads in Revit

Have you ever hasd that infuriating message about not being allowed to have overlapping pads in Revit?  Why should it matter?  It would be so much easier if the lower pad took precedence in the overlapping area, and just cut into the topography.  Well that is not the way that the software is written, so here is the technique that I use to get around the problem:
Pads at different heights cutting into a Site terrain (building hidden) 
You can see from the image above that the building being modeled has a basement over part of its floor area, so a pad is required for the basement, and then other pads are required for the various different heights of floor slabs at ground level.  Some of the pad edges need to be curved.

Option 1.
To make sure that the pads don't overlap, you could try creating the basement one first, and copy the sketch lines (to clipboard);  then start the next pad and paste the sketch lines in the adjoining area where they share a boundary, before completing the rest of the sketch.  Well, this can work sometimes, but usually not if any of the shared boundary between pads contains arcs - Revit usually considers two adjoining pads to overlap even if the adjoining boundary is one arc of exactly the same radius in the same place (perhaps it segments the arcs but does it differently for each pad?  Who knows, but it does not work).  You could try segmenting the arcs yourself to ensure that copy and pasting lines works.

Another problem with this method (assuming no arcs), is that when it comes time to change the pads you have to do a lot of double handling with temporary changes, copying lines between pads, then final changes, all to avoid any overlaps during the change process. 

Option 2.
A much better solution is to create Reference Planes along the common boundary lines between each pad, before creating the pads.  Then, when sketching the pad boundaries, you need only to pick the reference lines and lock to them (and trim the corners).  This will ensure that the boundaries do not overlap.  Another big advantage is that when you want to change the pad, all you need to do is move each reference line, and it will alter both pads at the same time, ensuring that you don't get those annoying messages - and you don't even need to go into edit/sketch mode for the pads.
Reference planes define boundaries for pads
You might want to put the reference planes into a workset that has its visibility hidden by default so that they don't clutter the screen, and so that they don't get accidentally deleted.  Just to be sure, you might also name the reference planes (pad boundary 1, pad boundary2 etc) so that your users know what they are for.

When it comes to arc segments of adjoining pads, you can use the same technique providing the extent of the arc segment is identical in length (as well as radius).  Obviously you cannot create curved reference planes so you'll need to use another technique - perhaps a gridline or just a line (model or annotation).

I hope this saves as much time for any readers here as it has for me.


  1. Thanks for tips, I like option 2
    but just to be clear, are all your pads on one level?
    I have this problem of making pads of different levels on one topography. I just slice topography and.... it's a mess anyway.
    sometimes topography just becomes like a face without volume.
    You have any tips for these too?


  2. When you say "one level", not sure if you mean Revit level, or just one height. So they are all on the same Revit level, but with different vertical offsets - so, at different heights. Sorry, no solutions for the horrible effects you sometimes get when slicing a section through topography - it can be very unpredictable, in that sometimes a pad causes an area without cut hatching in the topography - probably a bug.