Trees as key descripor symbols

[ESchomberg]

I think this is last question regarding my last learning serge. I created blocks of trees with a hole in the center and put a size for the tree, example 22.

They insert perfectly with my point styles and description key being set up now however I can't click on the tree and change the size within the block I assume because it is actually a part of a point number it won't take me to block editor. So I have to explode the tree 3 times in order to be able to change the tree size. Is there a way around this? I have diligently tried.

[ChicagoLooper]

Hi @ESchomberg 

Use tree block as a symbol that represents a cogo point, not as a placeholder to store a Block Attribute. 

What is the object type displayed at the top of the Properties Palette?

If it's a cogo, are you using an appropriate Label Style which displays the SIZE as a label?

[ESchomberg]

I just made up a drawing and inserted several points using the point styles and description key sets.

[Pointdump]

Hey Erik,
Good question!
A couple of ideas to bat around. Either enlarge your description key set to make a separate key for each size, or make a script to insert a dynamic tree block at each location.
And from @tcorey a lisp solution >>>Here<<<.
Dave

[ESchomberg]

Hmmm. I have not dived into dynamic blocks yet, is there an easy way you could point me in the right direction?

[caddie99]

Here is how I do it.

1. Create a point style each tree size   mine are Tree2  thru tree72   even numbers only scaled accordingly

2. use descriptor keys on import to assign the point style

ie    22 oak    would assign point style tree22  

[ESchomberg]

I thought about that bud darn, I will have like 30 oak trees, 30 pines, 30 palms and so on...but I may just have to do it

[Todd_Rogers]

You need to use the $ under the format column. With this option, it will read the size in the description and assign a scale from the checked box to apply the X-Y scaling automatically. You should only need ONE tree block for each type of tree, ONE oak, ONE maple, ONE poplar, etc.

[BrianHailey · Accepted solution]

If I understand correctly, you want the number in the middle of the tree symbol to change to match the size of the tree. Do you also want to scale the tree symbol based on the size of the tree? I ask because the drawing you provided has a 12" oak with a "55" in the middle of the symbol:

If I'm assuming correctly, you could create a user defined property for the tree size and then add that to your label style so it appears at the center of the point. Once you create a user defined property, you'll see it as an option in your label style:

[ESchomberg]

Thank you sir, good information 

[BrianHailey]

If you're importing points, this would be an additional column in the point file. You would then need to create a new point file format (just copy the one you normally use) that includes the user defined property. If you are creating the points manually, it will just be another property you can add data to.

[ESchomberg]

No, I'm importing points collected from the field. And you were correct, I just put a 55 in there to have a number that I can edit but it didn't work out that way without exploding the tree 3 times. I don't really need the tree scaled to exact size either, I just scaled them to 5' in the point styles.

[ESchomberg]

Sorry, I'm gonna need some time to look into this. I can't solve this one immediately 

[rl_jackson]

Erik,

All of the advice provided is good, and there are different ways to skin a kitty for the most part I try to keep it simple if possible. I use just two-point codes and two symbols in South Florida, TREE and PALM. The reason for this is due to the # of exotic trees located in the area whether their fruit trees (Star, Avacado, Orange, Kiwi etc...) or normal trees (Oak, Pine, Banyan) and the sheer number of different palms which some look similar to the other. The field crews are not Arborist or Landscape Architects, in my opinion, this is better left up to the professional that is qualified to make such determinations without imposing any unwanted liability on the company, not to mention that most projects will require a professional to make those determinations anyway. Below is my description of TREE this can be coded in the data collector with a size which will appear in the point label style in the drawing (I don't always do labels). Take special not to the Description Key of TREE* the asterisk is a key feature of getting the data to appear in the drawing if needed. Of course, the 2nd & 3rd column are Point Style and Point Label Style respectively and then is the format column, this is what will be used to fill in the information for the Point Label Style when the points are imported (Red Underline). Now in the format I have used $1" Tree, the $1 is key (circled in green) as is the * previously mentioned. By entering a code in the data collector of TREE 12 (space required) the TREE symbol is used for the Point Style and the Point Label in the drawing will read 12" Tree (red portion also included in format). This format can also included additional field for spread or height if so, desired just by adding $2 (spread) $3 (height) and can be further formatted so that the Point Label gets each on a separate row in the label by using \P (way to hard code a return in ACAD) within the format.

 

HTH

Rick

[ESchomberg]

Goodness, this all sounds so complicated. Thank you, I will sit down this weekend and try to sort all this info

[Pointdump]

Hey Erik,
Some good stuff >>>Here<<< and >>>Here<<< on creating Dynamic Tree Blocks.
It's a real shame that COGO Points can't use Dynamic Blocks.
Dave

[Cadguru42]

---

@Pointdump wrote:

It's a real shame that COGO Points can't use Dynamic Blocks.

---

Yeah, that's a very important point (pun!). Dynamic blocks don't work with C3D styles. I had the same issue as the OP a long time ago and learned to use the arguments (the $1, $2, etc.) in the point description to get the symbol size to scale based on the size. 

I highly recommend going through some tutorials on C3D styles and labels to help you better understand what's going on.

[ESchomberg]

Yeah this is alot of good information. Seems like there is always something just around the corner that is new to learn on cad. I have just not had the time to delve into all this yet but I certainly will.