Is making a Key Plan really that hard?

[Phil Read]

Here's one. Notice the imported file, text and lines are controlled via instance parameter. Now when you use in a project - you can turn on the Key Plan stuff via the sheet's Instance Parameters.

All the best -

Phil

[david.metcalf]

Lets request a Key plan tool for the next version.

[dbaldacchino]

My example is pretty much the same line of thought as what Phil posted. We have hatched regions with visibility parameters tied to parameters in the titleblock family. It's really easy to implement and the user just selects the border in the sheet view, goes to properties and checks the box for the area/s that applies. It's so easy in my opinion, that there's no real urgent need for a "tool"; we have bigger fish to fry

[bowlingbrad]

....we have bigger fish to fry

Amen brother!

[dpollard909366]

We have a pretty complex building that could be changing alot during the design process with 18 stories and 4 enlarged plans per floor - we used a plan view for each key plan.

may seem like alot of work, but the last thing we want to do is have to re-export, re-draw, or re-pdf the plans just to have key plans... seems pretty anti-revit.

we set up a 'key plan' view template, duplicated views alot, and drew a diagonally hatched filled region over each relative quadrant.

it works pretty well, and you don't ever really have to think about them after you set it up. It would be even easier with a smaller building.

I think all of the other methods you speak of are fine once the building is 90% complete, but for something in SD or DD I think you need to think parametrically.

[dbaldacchino]

Weeeeeellllll, keyplans don't have to be perfectly accurate. They're just symbols to orient you when you chop the building up in pieces to fit on sheets; remember how small it's scale is and perfection is only visible when you zoom in on your screen. After going through this process once, I'm of the idea that once you finish your keyplan at DD, you shouldn't bother fixing it unless there are massive changes. And if you want it to be perfect, just do a screen capture and save to jpeg, open the keyplan family again and insert the image and fix the outline. Takes mere minutes....and reload in your border. Done. Go have a beer

[ford347]

thanks for your posts you guys....got it. Looks good and is easy enough!

[gbrowne]

I thought we agreed ages ago on the hatch region over plan pasted into a legend method?

In fact isn't 9's default template set up to do it that way?

I had already went for a beer..

[jtpark.79952]

Hey, I was wondering this same thing and decided to use a generic annotation and it worked well. My question is how do you make a yes/no visibility parameter? I can make a yes/no parameter under family type but see no way of linking this to the filled region and don't see any way of making a visibility parameter when creating the filled region. Can someone explain this? This will be very helpful in alot of ways. Thanks

[dbaldacchino]

I thought we agreed ages ago on the hatch region over plan pasted into a legend method?

In fact isn't 9's default template set up to do it that way?

I had already went for a beer..

Well some of us haven't been in Revit "ages ago" hahaha. And quit drinking too much beer, you Brits are sucking the Germans dry!

Legends wouldn't work for me....generic annotations are more efficient when you're showing a keyplan on all sheets and have areas to turn on or off. To each his own!