Topic: DB - Spread/Isolated Footing

[akdrafter]

Anyone seen a DB for a spread/isolated footing? I am attempting to make an all(mostly) encompassing DB to handle numerous spread/isolated footing situations. I have attached a dwg(v2007) as an example of possibilities.

Any help or ideas is... as always... greatly appreciated.

Thanks

[whdjr]

I haven't seen one but I haven't been looking for one either.  You can try looking over at the Augi site.  They have a big collection and may have what you are looking for.

Are you just looking for a block or are you asking for someone to build this for you?

[akdrafter]

If it's built, no need to reinvent. I am pretty sure that my limited experience with db's will make this an interesting one to get done.

[Guest]

If it's built, no need to reinvent. I am pretty sure that my limited experience with db's will make this an interesting one to get done.

Take a shot at it, then post back with what you've been able to do.  That's one of the best ways to learn how to do for future DBs.

[akdrafter]

Here is a footing part. Pretty basic. I have started to create some typical rebar types and am doing ok with them so far, but to make a type 2/17 is a daunting task. What I have found is that I make each of the bar sizes(geometry) in different areas of the drawing, add all of the params/actions, move everything to a base point and then modify the cpolygon areas and such. So... for a type 2/17(I say 2/17 because they are basically the same shape and for details, it works. So... a type 2/17 has these configurations: AB & ABG

--

Shaped like a the letter C.

Sizes: 3 - 11, 14 & 18

Dimensions: A(leg always present), B(always present) & G(leg on/off)

All have wipeouts via the use of a polyline that matches the geometry of the bar, except at the arcs which I created a polygon with 128 sides and offset 1/128" to the inside of the geometry. Once plotted you can't even tell that there is that small offset. It is visible on the screen as a sloppy looking line. hahahaha.... I haven't done it yet, but I figured if I put the wipeout polyline and the wipeout itself on the defpoints layer I would not ever have to worry about it not plotting as defpoints is hard coded into the AutoCAD database to never plot.

I used visibility states to define the legs to display.

I also played with using a non-plotting dimension to have a visual on the size as I stretched it. Not sure that is a good way to go.

I can't remember if I updated this one to stretch all legs whether on or not. I seem to remember having issues with that... some error.

--

So far I have sizes 3-8 and I stopped there, but can't remember why. hahahahaha....

I shall post for the sake of sharing and VERY welcome critiques.

[TimSpangler]

Can you save them down, I can't open them in 06

[akdrafter]

dwg v04

[Guest]

Just for the heck of it, here's a DB wall that I've created (still needs some tweaking) that is intended to be a starting point for a wall detail.  I know it doesn't help you with your issue, but I figured I'd share it since it has to do with structural.

Well, anyways... here 'tis.

[Guest]

dwg v04

I think they're going to be useless in '04 because '04 didn't have DBs.

[whdjr]

dwg v04

I think they're going to be useless in '04 because '04 didn't have DBs.

v04 is the same file format as 06.

[whdjr]

dwg v04

Instead of drawing all those different actual geometry sizes, look at a block using lookups.  Look at the steel beam shape in the Civil tab of the AutoCad tool palette.

As if you have any questions.

[Guest]

dwg v04

I think they're going to be useless in '04 because '04 didn't have DBs.

v04 is the same file format as 06.

Ahhh....but even so, he's got '06 which doesn't have DBs does it?  Weren't they introduced in 2007 (I can't keep up with what came out when).

[whdjr]

dwg v04

I think they're going to be useless in '04 because '04 didn't have DBs.

v04 is the same file format as 06.

Ahhh....but even so, he's got '06 which doesn't have DBs does it?  Weren't they introduced in 2007 (I can't keep up with what came out when).

'06

[akdrafter]

I am using Vanilla AutoCAD 2008.

[whdjr]

Look at this simple light block for what lookups can do.

[Guest]

dwg v04

I think they're going to be useless in '04 because '04 didn't have DBs.

v04 is the same file format as 06.

Ahhh....but even so, he's got '06 which doesn't have DBs does it?  Weren't they introduced in 2007 (I can't keep up with what came out when).

'06

Alrighty then.  That settles it.  We skipped 06 so that's why I wasn't sure.

Thanks Will.

[akdrafter]

Here is a basic straight bar with lookups.

[whdjr]

dwg v04

I think they're going to be useless in '04 because '04 didn't have DBs.

v04 is the same file format as 06.

Ahhh....but even so, he's got '06 which doesn't have DBs does it?  Weren't they introduced in 2007 (I can't keep up with what came out when).

'06

Alrighty then.  That settles it.  We skipped 06 so that's why I wasn't sure.

Thanks Will.

No prob.

[whdjr]

Here is a basic straight bar with lookups.

I'm having to download TrueView now because TrueConvert doesn't handle 2008 dwgs.  Will reply after I look at the file.

[akdrafter]

my bad... I keep forgetting to save to v04. off I go to the prefs....err.... options. Old habits die hard.... or haven't died at all. hehehehehe... change my shortcut keys to: pr=options.

[whdjr]

That looks good.  If you want to associate a specified LENGTH just add the length column beside the SIZE column.  Then when you specifiy a listing in your lookup it changes the size and the length.

[akdrafter]

Good point. There are some basic configurations that could generically apply to many different situations. It is getting to that basic configuration and having the ability to simply select the components to make up the variations that is going to be the time saver. The original topic of this thread is the one I think is going to test my patience. I haven't posted a "has this been done" in the augi forum yet....although I have been getting quite a few "shared" ideas. Cool stuff. Just have to keep focused and not get caught up in too many bells and whistles in which too much is too much. Been drawing for a long time and I am certain I could still draw things the old fashioned way faster than using some of the bells and whistles they are coming up with today...all while keep the drawing simple... and small in file size.

[akdrafter]

dwg v04

Instead of drawing all those different actual geometry sizes, look at a block using lookups.  Look at the steel beam shape in the Civil tab of the AutoCad tool palette.

As if you have any questions.

Problem is...and maybe not...enlighten me... the bend diameter/radius is different for each bar.  durrrrrr... now I see the different columns in the lookup table. Hmmm... now this brings up a whole host of things to accommodate for the (11) different bar sizes. Each one will have (2) different radius's, inner and outer.

I see that the linework is not polylines... which would need to be the case in order to adjust the radius of the different bar types. Sounds like I need to do a drawing and some dimensioning to plot out to keep things straight.

[whdjr]

dwg v04

Instead of drawing all those different actual geometry sizes, look at a block using lookups.  Look at the steel beam shape in the Civil tab of the AutoCad tool palette.

As if you have any questions.

Problem is...and maybe not...enlighten me... the bend diameter/radius is different for each bar.  durrrrrr... now I see the different columns in the lookup table. Hmmm... now this brings up a whole host of things to accommodate for the (11) different bar sizes. Each one will have (2) different radius's, inner and outer.

I see that the linework is not polylines... which would need to be the case in order to adjust the radius of the different bar types. Sounds like I need to do a drawing and some dimensioning to plot out to keep things straight.

You use a scale action for radiuses.  Is that what your talking about?

[Josh Nieman]

Just for the heck of it, here's a DB wall that I've created (still needs some tweaking) that is intended to be a starting point for a wall detail.  I know it doesn't help you with your issue, but I figured I'd share it since it has to do with structural.

Well, anyways... here 'tis.

Good looking block, Matt.  Ya'll dimension in model space, or do you make an exception for details, for the sake of automation?  I'm setting up a library of details, and one of the kickers I'm dealing with is whether to show the dimensions in model space or not, for the sake of being able to paste the whole shebang, or just let the individual dimension it.

Basically my options are

1)  Geometry in model space along with a separate DIM Style for blocks that I'd just use overrides to make it right (since each block is a singular special instance) and make it easy dragon droppings.

2)  Geometry in model space, along with separate paper space block to paste in paper space... kind of a hassle, not very intuitive.  Get's 'er done though, while following the singular dim style we set.

3)  Geometry in model space and screw the dimensions, the user can do that them self. (not a very good thought for someone trying to automate processes)

[akdrafter]

My bad...again. D is the diameter.

As an example:

Type 2 - Size 3(#3) with standard 90%%c<<-- hook(6") has an inside bend radius of 2.25" the outside bend radius is 2.625".

Type 2 - Size 4(#4) with standard 90%%c<<-- hook(8") has an inside bend radius of 3.0" the outside bend radius is 3.5".

per CRSI ACI 318. Funny thing is they list "D" which to me means diameter when it in there context means Distance.

So, in order to use a lookup table I have to associate each radius(2 ea.) for each bar type. Not sure how to use wipeouts with this type of db though. I like using the wipeouts because it gives a real world look to it. Draw orders can be a beotch, but it's a give and take.

[whdjr]

What are using the wipeouts for?

[akdrafter]

I use the wipeouts to give the details a real world look. I am detailing to real world and not to the "what the engineer thinks will work". It's a "can it be built" approach.