block marrying

This will either be extremely difficult or so simple I will want to shoot
myself:

This deals with a tree removal drawing our company is creating. In our
drawing we have a block with attributes that identifies the tree number and
tree variety. On top of this block is another block that is a symbol of a
tree. They came from different offices. In order to extract/highlight the
types of trees to be removed in a given area, we need to create a new block
that combines the two blocks.

The goal is to have the new blocks have names like Oak, Pine, Fruit, etc.
and keep the current attribute values while maintaining their current
location. That way when the conversion is complete we can extract how many
Oak trees are in Unit 1, Unit 2, etc. Did I explain this okay?

If this is as complicated as I think it is going to be, please feel free to
contact me directly so that we might talk about contracting with you to
compensate for your services.

Thanks,

Jeff

 

Further explanation. I had my boss look at what I originally posted before
I posted it, but you know how that goes. Forget the creation of the new
blocks. Lets run with this in a different direction. Apparently what we
need is more along the lines of this:

In this drawing I described (a portion of which is posted in the customer
files area with the same subject title) are blocks that have invisible
attributes (the green "X"), one of which is a tree number. On top of some
of these blocks are other blocks that don't have attributes (the blue
triangle). When we perform an attribute extraction we would like for the
routine to check and see if this second block is on top of it and list this
in a column to the extraction file.

I guess the best way to describe it would be if the block with attributes
had an additional attribute that would represent the second block. This
additional attribute would then have its own column in the extraction file.
If the block exists, the column would show a 1 and if it doesn't exist a 0.
Or something to that effect. I hope that this is making sense.

Thanks in advance for you efforts,

Jeff

 

We use 2000i, however my boss has 2002. She created the file I posted and I
think she has it set up to save back to 14. I think it is due to the
project she is mainly working on was started in R14. I would write it for
the 2000 version of the software.

If the blocks have different insertion points, that is probably due to
different offices creating the files. We just inserted one into the other.
If you can create a routine, work on the assumption of the same insertion
point. If we need to move them around a little, so be it.

As for the elev/thick remark, I am told that we want tree removal files with
a 0 elevation.

 

I really appreciate this. I look forward to seeing them.

Jeff