I routinely create blocks of deed descriptions, subdivisions and other plats to create mosiacs of properties that I will later use for the calculation of additional field points on a survey being preformed. However when I create a block, and list a line that has been rotated it still reports that the line is due south or whatever bearing it was originally drawn at.
Is this supposed to work this way? Is there a setting that I'm missing somewhere?
If this is the way it works - it is totally wrong in my opinion, and is a serious deficiency with respect to the surveying.
Solved! Go to Solution.
I've not experienced this since I don't list bearings in rotated blocks. But I do have a theory.
A block is a single definition in the drawing shown multiple times. So I think what's happening is that CGList is reporting the bearing from the original definition.
I do have a workaround since I work in a similar manor. Instead of using Blocks use Groups. While this will double or triple, in my case, the amount of linework in the drawing. Lines don't increase a file's size that much. This still allows you to move the deed plots as a single unit but you can still affect the lines individually if you want.
I triple the size because I have one instance of the lines in their original bearing systems, one where I have created a mosaic in the system that seems most common the them and one where I've rotated them after a field analysis.
I agree. It would be best if the command gave the original data of the block and the scaled/rotated data. Or another command that gave the real data would be sufficient. Also, if you cglist an arc in a block, you don't get the arc information.
(running C3D 2012 sp3, Win7 64bit)
To get options for the Group command enter -GROUP (note the hyphen). That will give you the option to explode the group. I agree. Not having the dialog box is something you have to get used to.
Looks like its time to do an alias edit ? Rick
Or you could get fancy and use the Undefined and Redefine lisp commands in your acaddoc.lsp. See example on page 86 and 87 in this [Link] .