Lock topo points to reference plane? RFC

[Maximillian]

Has anyone been able to do this? My idea is to create named reference planes along the perimeter of the foundation and to lock topo points to it. Then i could get a nice clean line in elevation.

[cphubb]

Its called a Pad

[Maximillian]

You can not slope a pad. I am working on sloped site.

[Dimitri Harvalias]

I think what Chris meant was that if you create a pad that follows the outline of your foundation wall then you'll get that nice clean line in elevaton regardless of what the slope of your site is.

If you're just looking to make sure the slope is even I believe you're stuck with placing a series of points and letting Revit resolve the slope for you.

You can place a ref plane on each elevation view and then, while editing the topo, move each point on the edge of the building and they will snap to the ref plane. Just make sure the elevation view (or section) has it's view depth set so only points along the building face are selected.

I think this is one for the next wish list cycle. Draw model lines in 3D space and associate topo points, or better yet the topo surface itself, to the model lines. This way we can define curbs, retained slopes, contours etc. just by drawing lines

[Maximillian]

Also pads that work the way the new floor tools do.

This brings me to another question:

I saw a post on revit rants that explained how to add a flexible array to a family. At one point in the instructions it calls for a corner to be constrained and locked to a line. I haven't actually tried his technique yet, but the locking of a point got me thinking, or I am misinterpreting his instructions.

I have a feeling that the next release will include ( i hope ) significant site tool upgrades due to the number of rants about it.

Sorry if I sounded short on my previous post. I have spent a day so far dealing witht this site.

[clog boy]

I don't think the locking of a point involves sites in that context, altho I didn't bother to check. You can dimension and constrain endpoints in projects and family files.
I think they were referring to constraining the end points of sweep paths to something controlled by a parameter, so the sweep will stretch and thus become 'flexible'.
Site points are another story entirely.